-
Notifications
You must be signed in to change notification settings - Fork 16
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
3683c98
commit 0119e95
Showing
2 changed files
with
27 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,26 @@ | ||
# Releasing | ||
|
||
The version scheme we use is **MAJOR.MINOR.PATCH** and stored in the [product_version](../product_version) file at the root of this repository. | ||
|
||
Open Crawler follows its own release versioning and does not follow the Elastic stack unified release schedule or versioning. | ||
|
||
## How to release | ||
|
||
Releasing is done entirely through Buildkite. | ||
The Open Crawler build can be found here: https://buildkite.com/elastic/crawler-docker-build-publish | ||
|
||
Builds will only run from a versioned branch. | ||
|
||
Build steps: | ||
|
||
1. Click `New Build` | ||
2. Enter a message (e.g. `x.y release`) | ||
3. Choose a commit | ||
- the default `HEAD` is usually fine | ||
4. Choose a version branch with the pattern `x.y` | ||
- Builds will only run from a versioned branch, you cannot build from `main` | ||
5. Click `Create Build` | ||
6. Wait a minute for the Buildkite configuration to be loaded | ||
- When it has loaded, a `Build Information` button will appear | ||
7. Enter the build information | ||
8. Wait for the build to finish |