-
Notifications
You must be signed in to change notification settings - Fork 24
Do not run relase-images on forked prs #366
Conversation
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.
Skipping CI for those, how we are going to validate them instead?
@filipesperandio it's not the entire ci, just the job for releasing images. Do you think releasing images is a necessary step for validating prs ? |
🤦 I was tired... |
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.
I am OK shipping this anyways, but seems like we only actually release images for master and channel-* branches here: https://github.com/codeclimate/codeclimate-duplication/blob/master/bin/deploy#L10-L13
mmmm, interesting because it is getting triggered on #364 |
6205888
to
109177c
Compare
…ter and channel branches
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.
Yeah, that build seems to break on docker login
, even before the bin/deploy
call, but I agree this is even better as we skip the step entirely, have CIRCLE env vars checked on Circle related files and make it more visible.
👍
@filipesperandio Exactly it was breaking before the |
We are receiving failed builds from prs open by the community due to running the
relase-images
ci job. This work removes this job for those cases.See #364