Closed mrdavidlaing closed 11 years ago
Thanks - we have a few such potential split CI brain situations due to testing whether Travis and/or esp. BuildHiive might be good enough for most/all of our CI needs.
Given that wee seem to gravitate to slightly more complex builds again (esp. Cloud Foundry deployment), we should probably accept this for the time being and remove the Travis/BuildHive configurations (after all, these are shared and valuable community resources)?
OTOH, depending on project, these public CI instances provide some drive by PR, but I think that alone doesn't warrant keeping them around ;)
Given that wee seem to gravitate to slightly more complex builds again (esp. Cloud Foundry deployment), we should probably accept this for the time being and remove the Travis/BuildHive configurations (after all, these are shared and valuable community resources)?
@mrdavidlaing - I forgot to mention that this question is blocking the merge, insofar I'd remove the Travis configuration right away in case ;) - so what's your current take on that question?
:+1: for removing the Travis/BuildHive configurations
As discussed in #37