[COMPASS-3587] spike: evaluate using azure pipelines instead of travis Created: 24/Apr/19  Updated: 26/Aug/21  Resolved: 26/Aug/21

Status: Closed
Project: Compass
Component/s: None
Affects Version/s: None
Fix Version/s: No version

Type: Task Priority: Major - P3
Reporter: Irina Shestak (Inactive) Assignee: Unassigned
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Story Points: 3
Documentation Changes: Not Needed

 Description   

With the recent travis acquisition I am a little uncertain about the future of travis as the service we started using way back when. With a lot of support engineers from travis getting let go, it worries me that maintenance and future development of this product might stagnate.

I've heard quite a few people switching to azure pipelines and having great success with it, and wanted to take a little bit of time on whether it's worth considering switching over as well.

Three points:

1) i feel like travis builds are now taking a lot longer to run (this needs proper numbers)
2) they let go a lot of engineers two months ago and I feel like the product is now in bare-bones maintenance mode; i am weary to rely on it
3) it’s now owned a by VC firm and that never goes well \o/



 Comments   
Comment by Maurizio Casimirri [ 26/Aug/21 ]

We already moved travis and Azure pipelines to Github actions and Evergreen

Generated at Wed Feb 07 22:33:38 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.