# From Travis Enterprise to BuildKite in 50 repositories

DevFeed: [From Travis Enterprise to BuildKite in 50 repositories](<https://devfeed.tech/articles/from-travis-enterprise-to-buildkite-in-50-repositories-37862.md>)

Original publisher: [Read original article](<https://carlosbecker.com/posts/travis-to-buildkite/>)

Author: Carlos Alexandro Becker

Published: 2017-03-11T00:00:00Z

Content type: opinion

Language: en

Sources: [Carlos Becker](<https://devfeed.tech/sources/carlos-becker.md>)

Topics: [ci](<https://devfeed.tech/topics/ci.md>), [migration](<https://devfeed.tech/topics/migration.md>), [GitHub](<https://devfeed.tech/topics/github.md>), [Git](<https://devfeed.tech/topics/git.md>)

Tags: [ci](<https://devfeed.tech/tags/ci.md>), [github](<https://devfeed.tech/tags/github.md>), [migration](<https://devfeed.tech/tags/migration.md>), [pull-requests](<https://devfeed.tech/tags/pull-requests.md>), [repositories](<https://devfeed.tech/tags/repositories.md>)

## AI overview

A ContaAzul engineer describes moving 50 repositories from Travis Enterprise to Buildkite. The team found Buildkite easier to set up and more satisfactory, while the main drawback was the manual migration process.

## Source excerpt

At ContaAzul, we use the CI infrastructure a lot. We open several pull requests in several projects every day, and we block the merge until the build pass. We consider our master branches are sacred, and we can't afford too much waiting to change them.