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

Automated releases #11

Open
VanAxe opened this issue Mar 1, 2017 · 3 comments
Open

Automated releases #11

VanAxe opened this issue Mar 1, 2017 · 3 comments

Comments

@VanAxe
Copy link
Contributor

VanAxe commented Mar 1, 2017

We should use CI to automatically generate binary and source code releases.

Perhaps I can contribute to this.

@otremblay
Copy link
Owner

otremblay commented Mar 1, 2017 via email

@VanAxe
Copy link
Contributor Author

VanAxe commented Mar 13, 2017

Yeah, I'm thinking CircleCI or CodeShip.

Personally, I'd rather have run this in Concourse... but we'd need to find someone willing to sponsor build time.

Circle and CodeShip both have a free tier.

I'll submit a PR with something.

@otremblay
Copy link
Owner

As of today, this is partially fixed by #15. We only need a thing that pulls this: curl 'https://circleci.com/api/v1.1/project/github/otremblay/jkl/latest/artifacts?branch=master&circle-token='$CIRCLE_TOKEN
and puts it somewhere. Maybe like, github release or something, once the build has passed.

And/or make the build config clever so that it can check that it is on master, and go the extra step to call on Github to make a release if it is on master.

For the record: I'm cool with "all things committed to master become a release".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants