-
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
Bump elastic stack version automation #25148
Conversation
curl -s https://artifacts-api.elastic.co/v1/versions/8.0.0-SNAPSHOT/builds/8.0.0-3beeb19e | jq .manifests { "last-update-time": "Mon, 19 Apr 2021 16:38:33 UTC", "seconds-since-last-update": 11 }
💚 Build Succeeded
Expand to view the summary
Build stats
Trends 🧪❕ Flaky test reportNo test was executed to be analysed. |
/test |
testing/environments/snapshot.yml
Outdated
@@ -3,7 +3,7 @@ | |||
version: '2.3' | |||
services: | |||
elasticsearch: | |||
image: docker.elastic.co/elasticsearch/elasticsearch:8.0.0-SNAPSHOT | |||
image: docker.elastic.co/elasticsearch/elasticsearch:8.0.0-3beeb19e-SNAPSHOT |
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.
❤️
This is great. On a related note there was a recent ES where it automatically updates the geoip database leading to some unpredictable behavior despite pinning the version. I started an issue at #25159 to discuss. |
See my comment in elastic/fleet-server#252. I was thinking if there are options to get best of both worlds.
If we don't update it frequently it will be like all other dependencies that we only update it when we really need it. |
For clarity, I'll amend this PR to do only one thing, which it's the one related with the script to be consumed by the automation we are talking about. The other changes were just to validate this worked as expected. |
.ci/bump-stack-version.sh
Outdated
|
||
echo "Commit changes" | ||
git config user.email | ||
git checkout -b "update-stack-version-$(date "+%Y%m%d%H%M%S")" |
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.
In order to reuse an existing PR then the branch creating should only happen if set.
In other words,
There is a requirement to support:
- Reusing an existing PR if there is already an open PR with a previous bump.
- Creating a new PR if the above is not true or it's configured to create always independently.
…ng-versions-stack * upstream/master: (28 commits) Add support for parsers in filestream input (elastic#24763) Skip flaky test TestFilestreamTruncate (elastic#25218) backport: Add 7.13 branch (elastic#25189) Update decode_json_fields.asciidoc (elastic#25056) [Elastic Agent] Fix status and inspect command to work inside running container (elastic#25204) Check native environment before starting (elastic#25186) Change event.code and winlog.event_id type (elastic#25176) [Ingest Manager] Proxy processes/elastic-agent to stats (elastic#25193) Update mergify backporting to 7.x and 7.13 (elastic#25196) [Heartbeat]: ensure synthetics version co* [Heartbeat]: ensure synthetics version compatability for suites * address review and fix notice * fix lowercase struct * fix version conflict and rebase * update go.* stuff to master * fix notice.txt * move validate inside sourcempatability for suites (elastic#24777) [Filebeat] Ensure Kibana audit `event.category` and `event.type` are still processed as strings. (elastic#25101) Update replace.asciidoc (elastic#25055) Fix nil panic when overwriting metadata (elastic#24741) [Filebeat] Add Malware Bazaar to Threat Intel Module (elastic#24570) Fix k8s svc selectors mapping (elastic#25169) [Ingest Manager] Make agent retry values for bootstraping configurable (elastic#25163) [Metricbeat] Remove elasticsearc.index.created from the SM code (elastic#25113) [Ingest Manager] Keep http and logging config during enroll (elastic#25132) Refactor kubernetes autodiscover to avoid skipping short-living pods (elastic#24742) [libbeat] New decode xml wineventlog processor (elastic#25115) ...
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.
Thanks!
(cherry picked from commit cc29196) # Conflicts: # .mergify.yml
(cherry picked from commit cc29196) # Conflicts: # .mergify.yml
(cherry picked from commit cc29196) # Conflicts: # .mergify.yml
@Mergifyio backport 6.8 |
(cherry picked from commit cc29196) # Conflicts: # .gitignore # .mergify.yml
Command
|
What does this PR do?
Enable automerge with mergify
And provide script to bump the versions:
This PR is one part of the required changes to enable the automation.
Why is it important?
Handle the stack versions on a PR basis to ensure breaking changes are handled correctly.
Tests
I ran this script in my local environment and produced -> v1v#4