-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Add automated-redeploy Make task #6109
Conversation
b7cc92b
to
686197f
Compare
Codecov Report
@@ Coverage Diff @@
## main #6109 +/- ##
=======================================
Coverage 82.05% 82.05%
=======================================
Files 100 100
Lines 5773 5773
=======================================
Hits 4737 4737
Misses 1036 1036 |
This should be ready, it is rebased, prior tests failed for no discernible reason and then forgotten. Please merge. |
Hi 😄, this issue has been automatically marked as stale because it has not had recent activity. Don't worry you can continue to work on this and ask @publiclab/reviewers to add "work in progress" label 🎉 . Otherwise, it will be closed if no further activity occurs in 5 days -- but you can always re-open it if you like! 💯 Thank you for your contributions 🙌 🎈. |
This is a way to automated and trace our deployment process! It is currently working and triggered manually from Jenkins (must have pushed to
stable
branch first).Note that currently it uses
Makefile.beta
which is a copy of the Makefile on disk. Makefile on disk has uncommitted changes that could conflict if this is merged (I've not tested what happens in the event of conflicts).The idea is that Jenkins triggers a specific predefined command in production with the right environment (env vars and directory). This command is defined in this Makefile:
make automated-redeploy
which will:Make sure these boxes are checked before your pull request (PR) is ready to be reviewed and merged. Thanks!
rake test
@publiclab/reviewers
for help, in a comment belowIf tests do fail, click on the red
X
to learn why by reading the logs.Please be sure you've reviewed our contribution guidelines at https://publiclab.org/contributing-to-public-lab-software
Thanks!