Skip to content

Conversation

@NotMyFault
Copy link
Member

Closes #8380 by automating this.

@dduportal
Copy link
Contributor

I am late to the party, but could we use the version provided by the agents in ci.jenkins.io? We keep it up to date and it would avoid downloading too much on each build

@NotMyFault
Copy link
Member Author

I am late to the party, but could we use the version provided by the agents in ci.jenkins.io? We keep it up to date and it would avoid downloading too much on each build

Surely, which version is currently installed?

@dduportal
Copy link
Contributor

I am late to the party, but could we use the version provided by the agents in ci.jenkins.io? We keep it up to date and it would avoid downloading too much on each build

Surely, which version is currently installed?

Currently it's 22.18.0: https://github.com/jenkins-infra/packer-images/blob/2.60.0/provisioning/tools-versions.yml#L32

You have a working example of automation (but using updatecli) which retrieves the Maven version of the currently deployed agents: https://github.com/jenkins-infra/jenkins-infra/blob/1d51037e666d47cddc0bf0da3b6fa35592d0a741/updatecli/updatecli.d/jenkinscontroller-tools-maven.yaml#L16-L32.

Note: It's important to note that the main branch of https://github.com/jenkins-infra/packer-images must NOT be used because it is not released (not tag yet) / deployed (waiting for the tag) 95% of the time. We usually deploy it once a week (average on a whole year).
For instance, it currently shows version 2.19.0 (merged earlier today) but not released yet: https://github.com/jenkins-infra/packer-images/blob/main/provisioning/tools-versions.yml#L32

@dduportal
Copy link
Contributor

Looks like this PR is superseded by #8522

Can you confirm @NotMyFault?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants