-
Type: Task
-
Status: Resolved
-
Priority: Major
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: Jenkins X
-
Team:PLATFORM
-
Sprint:nxplatform 11.1.24
-
Story Points:3
First, we need to validate that we can, on a fresh Jenkins X team:
- Upgrade the Jenkins X environment to align on the platform team environment (Custom Jenkins image with its plugins from https://github.com/nuxeo/jx-platform-jenkins, myvalues.yaml from https://github.com/nuxeo/jx-platform-env).
- Import some repositories for testing:
- Do some PRs, check that the pipelines are running fine.
- Upgrade the team/namespace to HTTPS.
- Check that we can access to every service: Jenkins, Nexus, Docker registry.
- Upgrade the Jenkins X environment with the right expose controller values for HTTPS.
- Update the GitHub webhook to HTTPS.
- Update the PRs.
- Check that the test pipelines are working fine.
See https://jira.nuxeo.com/browse/NXBT-3136?focusedCommentId=426062&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-426062 about the platform-https team created for this test.
If everything is OK, perform the HTTP -> HTTPS switch to the platform namespace: apply steps 4. to 9.
- depends on
-
NXBT-3141 Fix or remove build of builder-rpm
- Resolved
-
NXBT-3140 Fix or remove build of nodejs-njx builder
- Resolved
- is related to
-
NXBT-3145 More configuration as code for the Jenkins X platform team
- Resolved
-
NXBT-3136 Create a platform-staging team in the K8s production cluster
- Resolved
-
NXBT-3152 Switch the Jenkins X WebUI team from HTTP to HTTPS
- Resolved
-
NXBT-3242 Use Jenkins custom version for AI team in Jenkins X
- Resolved
- Is referenced in