loading...

re: Debugging Travis CI is very hard. VIEW POST

FULL DISCUSSION
 

I feel your pain. I took the time to migrate a Travis CI configuration over to Buildkite. It was infinitely better! You have to host the CI server yourself, but you can control the resources and environment.

 

Any advice or gotchas to look out for when making the switch. I am thinking about taking the leap as Travis is just not featured enough for all the things we want to do.

 

It was over a year ago when I made that migration, and have since switched companies, but I don't recall anything that was glaringly difficult. I found the Buildkite documentation to be very well written. I found the Buildkite configuration to be drastically different, in that it allows for a more modular configuration compared to the Travis CI configuration. I was working on a Docker based project, so I found it very convenient that I could run my integration tests concurrently. Since Buildkite is self-hosted, I was able to ensure that my pipelines were always running consistently and fast.

That said, I do remember having to take some extra steps to ensure that my environment secrets were secure. Buildkite has a few methods, but I used agent hooks to achieve what I needed: buildkite.com/docs/pipelines/secre...

Best of luck! I hope it works for your use case! :)

Thanks for the insight!

At first glance, the BuildKite docs do look very well written which is always encouraging and from searching around, it seems like it might be a little more work to set up but a lot of people really like it.

code of conduct - report abuse