-
-
Notifications
You must be signed in to change notification settings - Fork 697
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
Automate release process #338
Comments
This should be easy. Travis-ci supports deployments to npm. |
Thanks for the comment @lo1tuma, and you're right - travis supports publishing to npm which greatly simplifies the releasing of modules; however the publish step is a small part of the whole chai release process, which includes building a browser version, updating bower, tagging, updating/deploying docs and more. Let's wait for #337 before discussing this. |
I have added credentials into the The biggest challenge for total automation is the website. While it is mostly static, the plugins list has server-side components which prevents it from being a completely static GitHub-hosted site. Perhaps its time to pay attention to chaijs/chai-docs#34? |
Update on this: 2.1.0 has been released with the travis.yml auto-deploy, which works fairly successfully. Here are some notes about pain points:
/cc @logicalparadox for thoughts |
Hey @logicalparadox - do you have any thoughts on the above? |
I don't have solutions for all of these woes, but if I don't have a solution I can tell you why I did what I did so as to make reasonable decisions about what can change.
Other Notes
Oh, and @keithamus, make sure to add yourself as a contributor in CONTRIBUTING.md. |
When we have a documented release process (#337) we should try to automate it as much as possible.
The ideal solution would be that applying a tag to a commit can create & build a release. That is our goal - but we need to wait for #337 before seeing how far we can get with this.
The text was updated successfully, but these errors were encountered: