#release-engineering - September 2020

hey all, anyone using the JTE plugin… looking at it, but dont want to go too far down if there are known limitations, setup running jenkins in a gke cluster with kubernetes agents

anyone using harness.io ? I’m curious about pricing (ballpark to see if its even worth looking further at)

Our release process for CloudFormation (CDK) has failed us a few times recently. Meaning that when we go to deploy to PROD the deploy fails due to an expected diff.

It's due to the fact that we're only using two accounts, TEST & PROD. So all of the iterations of the CloudFormation template while they're being worked on are deployed to TEST,. So TEST gets iterations of the CloudFormation and we skip those iterations when go to PROD.

Without adding another account to the mix, my thought is that we could update our pipeline so that at the point of PR merge we reset the deployed CloudFormation template in TEST to what is running in PROD then apply the changeset from the PR to TEST. This should recreate what will actually get deployed to PROD and catch those cases where skipping iterations creates unexpected conflicts.

Is this inline with what others are doing or am I starting from the wrong place altogether?

What are the benefits of using a licensed version of Jenkins? I’ve looked at the Cloud Bees website and googled, but I haven’t found a clear idea of what the licensed version does.

I’m asking because I have a client who has Jenkins license. I want to determine whether we should shift to the open source version.

What precommit hooks you have enabled for terraform? I enabled chechov but I feel that it detects too many issues that are not actually issues for us 🙂