Skip to content
This repository has been archived by the owner on Jun 12, 2024. It is now read-only.

Commit

Permalink
remove manual build steps
Browse files Browse the repository at this point in the history
(cherry picked from commit 18a9e6b)
  • Loading branch information
Matthew Fisher committed Oct 19, 2017
1 parent 6e383bb commit 24ef23d
Showing 1 changed file with 2 additions and 18 deletions.
20 changes: 2 additions & 18 deletions docs/contributing/release-checklist.md
Original file line number Diff line number Diff line change
Expand Up @@ -207,25 +207,9 @@ git tag $RELEASE_NAME-rc1
git push upstream $RELEASE_NAME-rc1
```

~~Jenkins will automatically create a tagged release image and client binary to test with.~~
CircleCI will automatically create a tagged release image and client binary to test with.

At the present time, [Jenkins does not support](https://issues.jenkins-ci.org/browse/JENKINS-34395)
building releases from tags, so it is up to the release maintainer to create the release candidate
binaries themselves and upload the docker image to DockerHub. This can be done by running

```
make clean
make bootstrap
make build-cross
VERSION=$RELEASE_NAME-rc1 make dist checksum
DOCKER_REGISTRY=docker.io IMAGE_PREFIX=microsoft VERSION=$RELEASE_NAME-rc1 make docker-binary docker-build docker-push
```

Afterwards, the release maintainer will need to upload the binaries and checksums to Azure Blob
Storage. If the release maintainer does not have access to the container, PM @bacongobbler for
more information.

For testers, the process to start testing after Jenkins finishes building the artifacts involves
For testers, the process to start testing after CircleCI finishes building the artifacts involves
the following steps to grab the client from Azure Blob Storage:

linux/amd64, using /bin/bash:
Expand Down

0 comments on commit 24ef23d

Please sign in to comment.