-
Notifications
You must be signed in to change notification settings - Fork 524
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] automate update-beats #5692
Conversation
Jenkinsfile
Outdated
@@ -1,551 +1,104 @@ | |||
#!/usr/bin/env groovy | |||
// Licensed to Elasticsearch B.V. under one or more contributor |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For testing purposes
This reverts commit d20c5da.
Some errors with the make update-beats
|
💚 Build Succeeded
Expand to view the summary
Build stats
Test stats 🧪
Trends 🧪 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Awesome, thank you very much @v1v! ❤️
Amazing, thank you! |
@Mergifyio backport 7.17 |
(cherry picked from commit bd10c37) # Conflicts: # .ci/scripts/update-beats.sh
✅ Backports have been created
|
Motivation/summary
Jenkins job that:
update-beats
.go.mod
,go.sum
,NOTICE.txt
.ONLY on daily basis for the
master
branch. If needed, it's possible to trigger it on PR/tag/other-branches using the Jenkins UI.Mergify does the rest:
How to test these changes
Within the pipeline itself
Dry Run
No dry run
And created https://github.com/elastic/apm-server/pull/5703/files
NOTE: Bear in mind the PR was created on the top of this PR, that's the reason for having more changes. When running on the master branch, this should not be the case.
Related issues
Closes #4941
Requires #5690