Release Process

Here are some notes about the process we use to run releases. The code for building kibana and pushing the release is a part of the repo but there are a few manual steps in the process.

prereqs

Before running the release you need to have credentials for s3 that will allow you to upload the builds for the download.elastic.co bucket.

setup credentials

1. get the keys from another contributor and place in a .aws-config.json file at the root of the kibana repo. Use the following format:

{
  "key": "<access key>",
  "secret": "<secret>"
}

1. Make a copy of this file outside of the repo, in case it gets deleted (via git clean for instance)

running the release

1. pull the latest version from release branch
2. replace all instances of previous version with new version (4.2.0-snapshot to 4.2.0-beta1 for example)
3. package.json - "version" field
4. README.md - title - snapshot urls
5. commit those changes

git commit -a -m "version <version>"

1. tag that commit

git tag "v<version>"

1. clean out all changes (including .DS_Stores files and other hidden files)

git clean -fdxn -e ".aws-config.json" -e "config/kibana.dev.yml"
## check files that would be removed
git clean -fdx -e ".aws-config.json" -e "config/kibana.dev.yml"

1. install node modules

npm install

1. run the release task

grunt release

1. distribute links to the team so they can test
2. once verified push commit and tag to upstream

git push upstream <branch>
git push upstream v<version>

1. Make sure we update this page https://www.elastic.co/downloads/kibana with the link to the new README.md like

• https://github.com/elastic/kibana/blob/v4.3.0/README.md
  or
• https://github.com/elastic/kibana/blob/4.3.1/README.md
  (may or may not have the "v" in it depending on branch or label)