-
Notifications
You must be signed in to change notification settings - Fork 22
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
Improve build/release automation #32
Comments
I would like to be able to contribute to this issue |
I currently do the following steps... For each change: To package a release: I'd love to see some or all of this automated in rake. Some of this already exists in Cuke4Duke; you could use that as an example. Better yet, I'd love to see an automated process that produces multiple packages for the different .NET versions (e.g. VS2008, VS2010, Mono, etc.) To get involved, fork the project, make changes, and send a pull request. (Check out the guidelines on the wiki to contribute most effectively: https://github.com/richardlawrence/Cuke4Nuke/wiki/Contributing) Thanks! |
There are currently too many manual steps involved in a new Cuke4Nuke release. Update gem/Rakefile to fix this.
When building a gem...
The text was updated successfully, but these errors were encountered: