Fixed the wrong project id in Jenkinsfile. #25322 #25326
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
|
I pushed this change as pz-pr-25326, for Jenkinsfile to be considered as trusted (https://ci.eclipse.org/glassfish/job/glassfish_build-and-test-using-jenkinsfile/job/pz-pr-25326). |
arjantijms
approved these changes
Jan 15, 2025
dmatej
approved these changes
Jan 17, 2025
|
This was
|
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.
This fixed the wrong project id path when getting the secrets vault for Develocity API key. The correct project id is
ee4j.glassfish.Additionally, to get scans publishing on CI (both Jenkins and GitHub Actions), a helpdesk ticket needs to be opened in order for those credentials to be created, as explained in the parent issue.