-
Type: Task
-
Status: Resolved
-
Priority: Minor
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: Continuous Integration
-
Epic Link:
-
Sprint:nxplatform #57
-
Story Points:3
Instead of relying on "jx upgrade platform", as done for jenkins, see NXBT-3353.
Let's include in the platform-ci repository the templates of the attached nexus-0.1.41.tgz and chartmuseum-1.1.7.tgz, requirements of the jenkins-x-platform tag formerly used.
Note: since NXBT-3609 and https://github.com/nuxeo/platform-ci/commit/aeab5b8156eee42995bcaefd470aaea7eddf842b, all builds are relying on the internal Nexus deployed in Kubernetes. A very annoying side effect is that when running "jx upgrade platform", the nexus pod is systematically restarted, thus, the running builds are failing with 503 when requesting Nexus during the restart time. Using helmfile to deploy Nexus should fix this as it won't try to upgrade the nexus chart release if it hasn't changed (which is the case most of the time when a change occurs in platform-ci).
- is related to
-
NXBT-3615 [Platform CI] Clean up Jenkins X related stuff
- Resolved
-
NXBT-3609 [Platform CI] Speed up Maven builds with an internal Nexus proxy
- Resolved
-
NXBT-3588 [Kubernetes CI] Fix broken Nexus after node pool upgrade
- Resolved
-
NXBT-3548 [Platform CI] Fix stuck `jx upgrade platform`
- Resolved
-
NXBT-3219 Use the team Nexus in the Jenkins X platform team
- Resolved
-
NXBT-3386 Set up the Docker registry
- Resolved
-
NXBT-3387 Set up the chart repository
- Resolved
- is required by
-
NXBT-3603 [Platform CI] Fix CI deployment stuck build
- Resolved