-
Notifications
You must be signed in to change notification settings - Fork 25
Moved all CI/CD to Travis #255
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
Conversation
eabfae3 to
9e85e14
Compare
Signed-off-by: Rafael Porres Molina <rafa@sourced.tech>
|
Deployed in staging correctly https://code-annotation-staging.srcd.run/, although I don't have permissions to further test anything cc @src-d/applications |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
question
Co-Authored-By: David Pordomingo <david.pordomingo.f@gmail.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM.
We developed this long time ago, it was a kind of wip and staled more than a year ago, so my level of confidence in this review is 7/10.
Checks I did:
- deploy is done following the same steps in Travis than in former Drone,
- deploy in Staging works, and data is kept between deploys, and the server https://code-annotation-staging.srcd.run is also accessible and running.
- confirmed with Infra that we have snapshots of current production database, and a way to rollback.
I'd recommend:
- merge,
- tag -> deploy
- perform a sanity check to ensure the data is there -> and forget this issue 🤞
Signed-off-by: Rafael Porres Molina rafa@sourced.tech