Uploaded image for project: 'Nuxeo ECM Build/Test Environment'
  1. Nuxeo ECM Build/Test Environment
  2. NXBT-3614

[Platform CI] Deploy Nexus and Chartmuseum with a Helm chart

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Resolved
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Continuous Integration

      Description

      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).

        Attachments

          Issue Links

            Activity

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: