spike: evaluate using azure pipelines instead of travis

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Won't Fix
    • Priority: Major - P3
    • No version
    • Affects Version/s: None
    • Component/s: None
    • None
    • 3
    • Not Needed

      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/

            Assignee:
            Unassigned
            Reporter:
            Irina Shestak (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: