Pushing to Production in Bitbucket Pipelines HD 

This is not really a tutorial but a quick presentation of action results. Important details of how and why are omitted. A bit frustrating for someone who went to youtube to find more in depth 'hands on' information than can't be found in the articles on the Bitbucket website.

So the nonprod build deploy and test was done on your feature branch. Deploy was done of main. If main has changes ahead of your feature branch that doesn't work well with your already tested code, you just broke prod and your tests were worthless. You should always build once, deploy multiple times. This doesn't do that. The promoted asset could be ahead of the tested asset. Don't give people bad ideas. The best solution is to add a preprod/staging env on that master branch and retest before a prod deploy. Alternatively have a manual deploy of the existing artifact in the first run pipeline (note, this doesn't solve the issue of prod being ahead you would need to also solve that)

I have one situation here..but first hatts off to yiu guys for making pipeline process for us, now my question Using my .yml script i was able to create the docker image of code and to push & store it in my AWS ECR as well means my CI is done Now for CD my question is to deploy my new image i need to connect it to my containers/pod , so tht my containers will run with ths new image. How i will connect my new docker image from ECR to my K8s cluster and make it run on ths new image ?

1. Draw some circles 2. Draw the rest of the owl.

about nothing