-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Backports changes from weekly to LTS 2.346 line #249
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Use rollback instead of rollblack
Remoting releases from older baselines (like stable-4.13.x) need to deliver a signed jar file for compatibility. This pull request changes the default branch used for remoting releases from release.ci.jenkins.io to use the stable-4.13.x branch instead of the master branch. Remoting development on the remoting master branch no longer requires a signed jar file with the removal of Java Web Start in jenkinsci/remoting#532 The release.ci.jenkins.io job that delivers remoting with signed jars is no longer used for releases of the master branch of the remoting repository. This change should allow us to deliver remoting 4.13.1. Remoting releases from the master branch will continue to use JEP-229 as was done for https://github.com/jenkinsci/remoting/releases/tag/3020.vcc32c3b_cc767
…4.13.x-branch Release signed remoting from stable-4.13.x branch, not master branch
Co-authored-by: GitHub Actions <41898282+github-actions[bot]@users.noreply.github.com> Co-authored-by: Hervé Le Meur <[email protected]>
…ava` binary - jenkins-infra/docker-packaging#36 removed JDK8 and changed the `JAVA_HOME` value - #237 and #232 changed the Docker image but we forgot to update the pod config
fix(release) Rely on the Docker image `PATH` to locate the default `java` binary
Ref. openssl/openssl#11672. This is a short-term measure to fix the weekly release process.
fix(release) use openssl legacy provider for pkcs12
Display Maven version information without stopping build
…i/... ... jenkins-infra/release/PodTemplates.d/release-linux.yaml" Made with ❤️️ by updatecli
…i/... ... jenkins-infra/release/PodTemplates.d/release-linux.yaml" Made with ❤️️ by updatecli
…dbba8951cba27b0e8393f6419e599b857c5fa2ca3f32a917 [updatecli] Bump jenkinsciinfra/packaging Docker image version to 2.1.40
…i/... ... jenkins-infra/release/PodTemplates.d/package-linux.yaml" Made with ❤️️ by updatecli
…i/... ... jenkins-infra/release/PodTemplates.d/package-linux.yaml" Made with ❤️️ by updatecli
chore(Jenkinsfiles) remove deprecated label directive for kubernetes agent definitions
…dbba8951cba27b0e8393f6419e599b857c5fa2ca3f32a917 [updatecli] Bump jenkinsciinfra/packaging Docker image version
timja
approved these changes
Jun 10, 2022
NotMyFault
approved these changes
Jun 10, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Twin of #248