-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
ci: refactor pushDockerImages main pipeline #30795
Merged
v1v
merged 3 commits into
elastic:main
from
v1v:feature/packaging-main-pipeline-refactor
Mar 16, 2022
Merged
ci: refactor pushDockerImages main pipeline #30795
v1v
merged 3 commits into
elastic:main
from
v1v:feature/packaging-main-pipeline-refactor
Mar 16, 2022
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
This pull request does not have a backport label. Could you fix it @v1v? 🙏
NOTE: |
Collaborator
/test |
Unfortunately, If I wanna test this out, I need to commit a change in any beats, since the pipeline changes won't run the packaging stage in the main pipeline. |
This reverts commit 9aa8d30.
cachedout
approved these changes
Mar 15, 2022
kuisathaverat
approved these changes
Mar 15, 2022
mergify bot
pushed a commit
that referenced
this pull request
Mar 16, 2022
(cherry picked from commit de3e4cc) # Conflicts: # Jenkinsfile
This was referenced Mar 16, 2022
mergify bot
pushed a commit
that referenced
this pull request
Mar 16, 2022
(cherry picked from commit de3e4cc)
v1v
added a commit
that referenced
this pull request
Mar 16, 2022
(cherry picked from commit de3e4cc) Co-authored-by: Victor Martinez <[email protected]>
v1v
pushed a commit
that referenced
this pull request
Mar 17, 2022
kush-elastic
pushed a commit
to kush-elastic/beats
that referenced
this pull request
May 2, 2022
chrisberkhout
pushed a commit
that referenced
this pull request
Jun 1, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
backport-7.17
Automated backport to the 7.17 branch with mergify
backport-v8.1.0
Automated backport with mergify
backport-v8.2.0
Automated backport with mergify
Team:Automation
Label for the Observability productivity team
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 does this PR do?
Apply #30414 in the main pipeline.
Why is it important?
Packaging
pipeline is aimed to run on merge commits, whilemain
pipeline runs on a PR basis too. Let's align the implementation since the scripts are not anymore available in Beats but in the apm-pipeline-library (see elastic/apm-pipeline-library#1550)Test
I committed 9aa8d30 to be able to trigger the package stage in the main pipeline:
and it worked:
https://beats-ci.elastic.co/blue/organizations/jenkins/Beats%2Fbeats/detail/PR-30795/4/pipeline/33261#step-34606-log-1
I'll revert those changes now