Skip to content
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

[Wiki] Kibana upgrade tags #5647

Merged
merged 4 commits into from
Feb 17, 2022
Merged
Show file tree
Hide file tree
Changes from 2 commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions wiki/releasing-versions.md
Original file line number Diff line number Diff line change
Expand Up @@ -28,6 +28,15 @@ The latest changes have now been pushed to GitHub, a new `git` tag now exists on

<sup>_\* GitHub Pages sites are cached aggressively and can sometimes take a couple of minutes to update._</sup>

### Deploying to eui.elastic.co

In addition to the GitHub pages deployment, we need to manually deploy to the [EUI Bekitzur environment](https://github.com/elastic/infra/tree/master/terraform/providers/gcp/env/elastic-bekitzur) (which will eventually be the canonical home of the EUI docs).
thompsongl marked this conversation as resolved.
Show resolved Hide resolved

* Go to [the Jenkins job page](https://kibana-ci.elastic.co/job/elastic+eui+deploy-docs/build)
* Log in (uses Elastic single sign in)
* Change the `branch_specifier` parameter to the new version tag name (e.g., `v48.0.0`)
* Click "Build"

### Tag the release in GitHub

We also update the [release's tag in github](https://github.com/elastic/eui/tags) by _creating a release_ for the version and copying over its _CHANGELOG.md_ entries. (TODO: screencast this next time to include a GIF here)
Expand Down
2 changes: 1 addition & 1 deletion wiki/upgrading-kibana.md
Original file line number Diff line number Diff line change
Expand Up @@ -16,7 +16,7 @@ If the upgrade includes a large number of commits or has known breaking changes,
* Or run `yarn test:jest` locally
9. Resolve and commit reported issues (see [Resolving errors](#resolving-errors))
10. Open a PR or mark existing as "Ready for review" (see [PR template](#pr-template))
* Add the `EUI`, `auto-backport`, `release_note:skip`, and relevant version tags
thompsongl marked this conversation as resolved.
Show resolved Hide resolved
* Add the `EUI`, `ci:deploy-cloud`, `release_note:skip`, and relevant version tag(s) (the next minor version that has not yet entered feature freeze)
* Mention/ping any teams that are waiting on features to be available

## Resolving errors
Expand Down