[Jenkins-Build] Migrate push steps from ANT to Jenkins pipeline #613
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
Contributor
Test Results 299 files ±0 299 suites ±0 5m 52s ⏱️ -19s For more details on these failures, see this check. Results for commit 551df10. ± Comparison against base commit 4da844f. ♻️ This comment has been updated with latest results. |
HannesWell
force-pushed
the
jenkins_pushFromPipeline
branch
4 times, most recently
from
9fe4cd5 to
c19f1e6
Compare
This also has the advantage that for commits pushed to maintenance branches, the follow-up commits created by the build pipeline are pushed to the same branch automatically.
HannesWell
force-pushed
the
jenkins_pushFromPipeline
branch
3 times, most recently
from
c970f0f to
551df10
Compare
This was referenced Apr 12, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Replace the ant target
push_remote_from_workspaceby equivalent steps in the Jenkins pipeline.This is part of the continued effort to simplify the SWT build and migrate off ANT scripts, as tracked in #513.
It also has the advantage that for commits pushed to maintenance branches the follow-up commits created by the build pipeline are pushed to the same branch automatically.
Generally I suggest to backport the pipeline as it is after this change to active maintenance branches in order to avoid the need to build maintenance binaries locally.
This would eventually make the jobs in https://ci.eclipse.org/releng/view/SWT%20Natives/ obsolete.