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

research how to automatically make releases to github using the API #21

Closed
andrius-ordojan opened this issue Mar 30, 2016 · 5 comments
Closed

Comments

@andrius-ordojan
Copy link
Contributor

andrius-ordojan commented Mar 30, 2016

I plan to store the releases on github. I want it to be a manual step in the jenkins pipeline. That means I need to know how to automate the process.

documentation here

@buep
Copy link
Contributor

buep commented Apr 5, 2016

What will the result of this issue be?

@buep
Copy link
Contributor

buep commented Apr 5, 2016

This is not going to be part of the current PAC jira work package. The release is going to be done by tagging the version that is releases - just like we did earlier.
Issue #20 is including a short text about how we release and how the users find our releases. That is good enough for now.

Make this issue workable, but explaining exactly what it will include how the release will be done.
Then we consider it it a feature for later.

@buep
Copy link
Contributor

buep commented Jun 22, 2016

Please groom

@buep
Copy link
Contributor

buep commented Nov 4, 2016

Closing - we don't understand what it is... we get zip and tars native in Github based on tags.
I might have been relevant, if we one day pack PAC as binary, e.g. Windows installer.
But that will be part of that work.

@buep
Copy link
Contributor

buep commented Nov 4, 2016

See #85 for creatinng PAC releasenotes on Github.

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