Depending on what service you’re using for version control, I’d look towards built in CI/CD systems (GitHub actions, bitbucket pipelines, etc). I’ve mostly moved away from Travis, Circle, and Semaphore for these solutions and haven’t looked back.
Sr. Software Engineer at CallRail building microservices to support 3rd party integrations. PhD student at the University of Nebraska studying bioinformatics, machine learning, and algorithms.
Interesting. Yeah, I use GitHub so I guess I should look into GitHub actions.
On one hand, it's probably great having all the functionality you need coming from one place. On the other hand though, sometimes I wonder if it's better to diversify your tools in case one company starts to really suck. Like, if Travis were a one-stop-shop for DevOps and I had all my eggs in that basket, I'd have to migrate way more than just the CI pipeline right?
I guess like with all things in software engineering, it's a tradeoff.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Depending on what service you’re using for version control, I’d look towards built in CI/CD systems (GitHub actions, bitbucket pipelines, etc). I’ve mostly moved away from Travis, Circle, and Semaphore for these solutions and haven’t looked back.
Interesting. Yeah, I use GitHub so I guess I should look into GitHub actions.
On one hand, it's probably great having all the functionality you need coming from one place. On the other hand though, sometimes I wonder if it's better to diversify your tools in case one company starts to really suck. Like, if Travis were a one-stop-shop for DevOps and I had all my eggs in that basket, I'd have to migrate way more than just the CI pipeline right?
I guess like with all things in software engineering, it's a tradeoff.