I'm currently managing an infrastructure repository that uses Terraform to set up resources on AWS for various projects. My setup includes a functioning VPC and other networking essentials. Now, I'm considering migrating to OpenTofu and transitioning our CI/CD process from Jenkins to Bitbucket Pipelines. I'm wondering if it's wise to create a new VPC for this in a new mono-repo, or if I should just utilize the existing VPC. Additionally, I'm planning to move our staging environment on-site, using NGINX and ALB for traffic management, while keeping AWS solely for production services. I'd really appreciate your insights on this!
5 Answers
If I were you, I’d steer clear of Atlassian products. If I had a choice, I’d always go with GitLab instead.
Anything’s better than Jenkins! Bitbucket isn’t my top pick either, but it's still a step up from Jenkins in terms of infrastructure and using YAML for your pipeline.
Honestly, I'd suggest moving out of Bitbucket too. GitLab is way better for CI/CD.
Honestly, unless you have a really good reason for isolation, there's no need to create a new VPC. Reusing the existing one will simplify things. I'd recommend focusing on getting Jenkins migrated to Bitbucket Pipelines first. You can even prototype the process to test it out before making a complete switch.”,
You might think you're moving out of the frying pan, but really you're just heading into the fire. Both Jenkins and Bitbucket Pipelines aren’t exactly praised by the community.
Related Questions
Can't Load PhpMyadmin On After Server Update
Redirect www to non-www in Apache Conf
How To Check If Your SSL Cert Is SHA 1
Windows TrackPad Gestures