Improve release jenkins build #512
Open
+1,054
−842
Conversation
This file contains hidden or 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
sgraband
force-pushed
the
sg/improvePublishing
branch
4 times, most recently
from
faf4b2c to
dac4fa4
Compare
sgraband
force-pushed
the
sg/improvePublishing
branch
12 times, most recently
from
1bd9ac4 to
2c49087
Compare
sgraband
force-pushed
the
sg/improvePublishing
branch
from
2c49087 to
c417b1d
Compare
sgraband
force-pushed
the
sg/improvePublishing
branch
3 times, most recently
from
0f47deb to
6f0574e
Compare
Signed-off-by: Simon Graband <[email protected]>
sgraband
force-pushed
the
sg/improvePublishing
branch
from
6f0574e to
e074132
Compare
Signed-off-by: Simon Graband <[email protected]>
Signed-off-by: Simon Graband <[email protected]>
sgraband
force-pushed
the
sg/improvePublishing
branch
from
b432302 to
c0181e9
Compare
Signed-off-by: Simon Graband <[email protected]>
sgraband
force-pushed
the
sg/improvePublishing
branch
from
c0181e9 to
a623e16
Compare
Signed-off-by: Simon Graband <[email protected]>
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.
What it does
Improvements include a multi step setup, consisting of:
Where now each of the steps can be triggered individually and if one succeeds we do not need to run it again.
This is done by creating artifacts between the steps and a build number parameter, that can be reused to retrieve the successful runs.
Also tried to improve the error handling where we now should fails faster without having to wait for all steps before we can start a new build.
The build now needs to be manually triggered for releases. This avoids overhead for merging non release changes.
For PRs the building and signing is still executed. We could remove the signing from this, but for testing this PR is should be useful.
Updated the Jenkins pipeline configs for this.
How to test
This PR should trigger the build. I would like to test this with the Theia IDE release today.
Successful PR build: https://ci.eclipse.org/theia/job/theia-ide-pr-check/view/change-requests/job/PR-512/39/
Successful Dry_RUN (manually triggered):
Review checklist
Reminder for reviewers