-
Notifications
You must be signed in to change notification settings - Fork 816
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: enable update-build-and-publish
step on main
in eui-release
pipeline
#7695
base: main
Are you sure you want to change the base?
Conversation
Preview staging links for this PR:
|
💚 Build Succeeded
cc @tkajtoch |
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.
🚢 🎉
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.
Can we update https://github.com/elastic/eui/blob/main/wiki/eui-team-processes/releasing-versions.md with what the new steps are for releasing? How do we trigger a release? Are we pressing a button on buildkite, adding a tag/label to a PR, etc?
@cee-chen this PR only enables automatic preleases. Automated releases still need to be tested, and I'll document them as soon as I'm sure they work fine |
Ah gotcha, sorry for the confusion! TBH I'd love documentation around the pre-releases as well, in particular how we envision using them for Kibana upgrades (would go under https://github.com/elastic/eui/blob/main/wiki/eui-team-processes/upgrading-kibana.md) |
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.
Tomasz explained we need to test first before writing any final documentation - apologies for the back and forth/blocker! 🚢
Summary
This is a follow-up to the changes introduced in #7662. It enables the automatic prerelease versioning and publishing step in
eui-release
Buildkite pipeline onmain
branch changes.QA
Manual QA is necessary after the change is merged.