Split docker-jenkins-weekly and docker-jenkins-weekly.ci for infra.ci and weekly.ci

[NotMyFault]

Service(s)

infra.ci.jenkins.io, weekly.ci.jenkins.io, Docker Hub

Summary

As outlined in jenkins-infra/docker-jenkins-weekly#1459 (review), I'd like to split the docker images to create a minimalistic one for weekly.ci and leave infra.ci as-is.
Given both instances serve different needs, we don't need the majority of plugins on weekly.ci at all.

TODO:

• Create a GH repository in jenkins-infra: docker-jenkins-weekly.ci (unless someone has a better name in mind)
• Create a new docker repo with the same name in jenkinsciinfra on docker hub
• Update kubernetes-management accordingly

I can take care of 1) and 3) :)

Reproduction steps

No response

[dduportal]

@NotMyFault I believe we should be able to use a bake file instead and keep only 1 repository?

[NotMyFault]

@NotMyFault I believe we should be able to use a bake file instead and keep only 1 repository?

Right right, we actually just need a different set of plugins 🤔
Everything else remains the same. Good catch!

Do you think you could come up with a simple bake file? I'm not that well-versed with the hashicorp config lang 😓

[lemeurherve]

@NotMyFault I'll prepare the docker bake 🙂

[lemeurherve]

Instead of creating another docker image I plan to publish the weekly.ci.jenkins.io image variant as specific tag with a suffix like for example 1.23.1-2.439-weeklyci

(or 1.23.1-2.439-🦄 ? )

[lemeurherve]

Opened jenkins-infra/docker-jenkins-weekly#1462 cherry-picking jenkins-infra/docker-jenkins-weekly#1459 as a good candidate for differentiation between these variants.

Next steps:

• Updating kubernetes-management config and updatecli manifest

[lemeurherve]

weekly.ci.jenkins.io config has been updated to use its specific variant in jenkins-infra/kubernetes-management#4850

Updatecli manifest update verified with jenkins-infra/kubernetes-management#4849

Confirmed that Blue Ocean plugins and dependencies aren't available anymore on weekly.ci.jenkins.io:

Closing this issue.

[lemeurherve]

Reopening as we need to get distinct lifecycle for these variants.

To do so, scripts and shared pipeline need to be updated to allow working on a specific target only (infra.ci.jenkins.io or weekly.ci.jenkins.io variant).

[lemeurherve]

Opened a pull request to build none, one or both variants depending on the modified files, and to create distinct plugins update pull requests: jenkins-infra/docker-jenkins-weekly#1471

[lemeurherve]

Result of the PR, from jenkins-infra/docker-jenkins-weekly#1471 (comment):

The merge of this PR on main has correctly triggered a build of both variants: https://infra.ci.jenkins.io/job/docker-jobs/job/docker-jenkins-weekly/job/main/365/

And the GHA has correctly opened two distinct pull requests:

• chore(deps): update infra.ci.jenkins.io plugins #1476

• chore(deps): update weekly.ci.jenkins.io plugins #1477

Finally, these pull requests have themselves correctly triggered a build of only their corresponding variant.

Closing this issue as completed.

[lemeurherve]

Note that running the last-weekly GHA results in a unique pull request containing the Jenkins version update and both plugins lists update, as both should be updated every time the Jenkins version changes:

• feat(deps): bump jenkins weekly to 2.441 docker-jenkins-weekly#1478

[lemeurherve]

Reopening as I need to adapt kubernetes-management updatecli manifests to update only infra.ci.jenkins.io or weekly.ci.jenkins.io if only one of them has a new version.

[lemeurherve]

Update:

• Distinct updatecli manifests put in place in chore(updatecli/docker-jenkins-weekly): adapt manifests to individually update instances kubernetes-management#4867
• Test publication of weekly.ci.jenkins.io image variant only: test: update only pipeline-graph-view in weekly.ci plugins to get a single image variant docker-jenkins-weekly#1490
• Result: Bump Jenkins Weekly docker image version on weekly.ci.jenkins.io to 1.26.2-2.441-weeklyci kubernetes-management#4892, only weekly.ci.jenkins.io updated, no PR for infra.ci.jenkins.io ✅

Closing this issue as both variants have their own lifecycles now.