Set up CI with Azure Pipelines #1517
Conversation
|
@dejanpan @kfunaoka this in no way aims to replace the work in https://gitlab.com/AutowareAuto/AutowareAuto but just as a temporary workaround for the current Travis woes (e.g. #1396). The functionality provided in this PR is equivalent to what we have now with Travis (i.e. fairly limited), but it's just to have something that runs reliably now. Having said that, I wonder if it'd just make more sense to jump into GitLab right now and have the Apex CI replace the current Travis setup instead of dealing with temporary solutions like this PR. |
|
Hey there. I'm a PM on Azure Pipelines. If there's anything I can do to help out, let me know. Happy to be your stopgap while you work through Travis issues, though of course we'd love to be your permanent CI solution! |
|
@vtbassmatt thanks for the offer and sorry for the late response. We're most likely going to switch to Gitlab, since we already have #1563 and also the tools that the AutowareAuto project have already written, which use Gitlab as well. In any case, at a personal level, I have to say that I'm really happy with VSTS/Azure DevOps, I've migrated all my opensource projects from Travis and AppVeyor to it :-) |
|
Closing in favor of #1563 |
|
No worries, thanks for looking at us! And we'll be here if you change your minds 😉 |
Status
PRODUCTION / DEVELOPMENT
Description
Given that Travis has been a bit unreliable for some time, I wanted to give Azure Pipelines (https://azure.microsoft.com/en-us/services/devops/pipelines/) a try. This PR adds a YAML configuration file that is functionally equivalent to the current Travis file.