Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create an automated deployment step in the travis build #5

Open
3 tasks
ray-millward-tessella opened this issue Mar 12, 2019 · 0 comments
Open
3 tasks
Labels
O4.2 Build environment

Comments

@ray-millward-tessella
Copy link
Contributor

Description:
The travis build should include a step at the end of a successful build that deploys a version of the code back to GitHub (GitHub Releases) - this should only run against the master branch and the resulting package name should include the version number.

Acceptance criteria:

  • There is a github release step at the end of the travis build that deploys the built artifacts back to GitHub.
  • The release step only runs against changes to master (i.e. after pull requests are merged in)
  • The resulting package should include the version number
@ray-millward-tessella ray-millward-tessella added the O4.2 Build environment label Mar 13, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
O4.2 Build environment
Projects
None yet
Development

No branches or pull requests

1 participant