I guess if it’s a temporary thing we can wait a little and see if Travis gets it fixed. So +1 for option 1.
If something really urgent comes up we can still go for option 2. From what I learned it‘s really hard to get builds back to green if they have been broken some time, so I would like to stay away from Option 3 :-)
- Gregor Hi all,
back then when I set up Travis CI for our GitHub repository, I requested to mark the Travis CI checks as being required for pull requests:
Back then I thought that this would be a good idea. However, currently Travis is having some issues (again) and fails to fetch artifacts from certain Maven repositories due to SSL certificate issues.
Unfortunately this blocks us from merging pull requests which are otherwise fine.
I see a few options: - Wait for the Travis team to fix these issues. We have to wait for a few CQs anyway.
- Temporarily configure the Travis check to be optional which would allow us to merge
- Permanently allow us to merge pull requests although Travis is failing. Of course, we should do this only if necessary.
Any thoughts?
Christian
--
|
