Here are my requirements and I go back-and-forth on how to achieve them:
- Must build Java spring-boot apps
- Artifacts must be released to artifactory repository
- Docker image to be built directly relating to the artifact
group/artifactId/version
- Docker image to be deployed to AWS ACR
- Container deployment via cloud formation
- Maintain 2 branches in a git repo:
dev
andmaster
.dev
releases to our development environment andmaster
is for prod (I have tried to explain that this approach made sense when code was app (php) but not when you have a release artifact) - All branches off
dev
must build and test independently but NOT release even snapshots (doesn't apply to master as no one should be working off master) - best part
dev
andprod
builds must be done under entirely different AWS credentials and accounts into totally different VPCs
Given these requirements I believe need a multi-configuration
pipeline - one for the {prod/master} and {development/dev} arrangement to successfully capture the credential and deployment differences and point them at different branches. What I can't seem to do is get the dev
configuration to ALSO build the branches from dev - I have no pattern I can match - the branches don't look like dev-.*
- they are mapped directly to Jira tickets.
Can I even do such a thing? I feel like this last part is where my multi-config is breaking down.