commit | 40c0bd1a36d70736b84e925889cdad417e429fd4 | [log] [tgz] |
---|---|---|
author | Ahmet Altay <aaltay@gmail.com> | Tue Apr 23 14:50:16 2019 -0700 |
committer | GitHub <noreply@github.com> | Tue Apr 23 14:50:16 2019 -0700 |
tree | 02e191a9ad1db092337736db907578f8258c0810 | |
parent | 0d81a3a1dcc05787aec99039c6b1e5369783df42 [diff] | |
parent | 3781aca3e9e11f0014c291815c92f6385d97c5e5 [diff] |
Merge pull request #9 from apilloud/release-2.12.0 Update wheels process to stage to gcs and pull version from branch
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:
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 of that version.
Confirm that build successful and wheels get staged in beam-wheels-staging.