commit | 9a2f2a85892bcd0466d74a255f7dcbe11bfeae07 | [log] [tgz] |
---|---|---|
author | Andrew Pilloud <apilloud@google.com> | Mon Apr 22 10:43:35 2019 -0700 |
committer | Andrew Pilloud <apilloud@google.com> | Mon Apr 22 10:57:01 2019 -0700 |
tree | 9343ed9a2404b060240dc564397f72911399aefe | |
parent | 0d81a3a1dcc05787aec99039c6b1e5369783df42 [diff] |
Stage to gcs
beam-wheels
is a helper repository of apache beam, which helps a Release Manager build python wheels on Linux/MacOS in a release process.
There are 2 major parts in this repository.
multibuild as git submodule, helps build python wheels based on different os.
travis configuration files, setups environment variables and deployment strategy.
.travis.yml
contains a set of environment variables and steps of build process.deploy_travis.sh
defines that final python wheels will be deployed to dist.apache.org/dev using svn with your apache credential.config.sh
defines custom build steps.Fork this repo into your own github account.
Sign up travis with your github account and add this folk beam-wheels repository into travis.
In travis build console > More options > Settings > Environment Variables:
VERSION
with ‘Display value in build log’ enabled (e.g.VERSION=2.6.0).ACCESS_KEY_ID
and SECRET_ACCESS_KEY
with ‘Display value in build log’ disabled. These values can be obtained from the GCP Storage Settings under the interoperability tab.Create and push a new branch(e.g. release_2_6_0) into your fork beam-wheels repository, which will trigger the travis build.
Confirm that build successful and wheels get staged in beam-wheels-staging.