chore(githubAction): add build workflow initial work for argocd move

[Basma1912]

One-line summary

• I used an AI to write some of this code.

Significant changes and points to review

Issue / Bugzilla link

Testing

[pmac]

It looks fine to me. @stevejalim you mind taking a look?

[Basma1912]

I just added the prod runner to the workflow.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 79.06%. Comparing base (54584d8) to head (0bc6e90).
Report is 189 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #15385      +/-   ##
==========================================
+ Coverage   78.66%   79.06%   +0.40%     
==========================================
  Files         156      160       +4     
  Lines        8165     8355     +190     
==========================================
+ Hits         6423     6606     +183     
- Misses       1742     1749       +7     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[stevejalim]

r+wc

Looks good to me - thanks @Basma1912 !

I have a couple of queries, all just to be sure I understand it

1. Am I right that we'll be using eactly the same image for dev, stage and prod, just adding a new tag as we move from main -> stage -> prod?

Put another way, on a push to main, we'll get an image created and tagged with dev-abcd123, then when we push to stage, the image will already exist in GAR and will just have the stage-abcd123 tag added, and then a similar think for prod (with a different style of label). Is my take right? I just want to be sure that we can still be sure that the same container image used on dev/stage is what we ship to prod. (I think it will be)

2. Am I right that there'll be an event/trigger set in ArgoCD to start running our integration tests against a particular environment once the rollout to that environment is complete?

Thanks for your work on this! ArgoCD seems great

[Basma1912]

@stevejalim sorry I missed the mention , looking at this

push to main -> build an image for DEV env
push to run-integration-tests - > build an image for test env
push to stage - > build an image for stage
push tags - > build an image for prod

[ the above is what currently in place for bedrock ]

looking at the event router .. I don't have any context whether all the changes in main eventually get pushed to stage and finally got tagged and deployed to prod

if all branches are kept in sync .. then yes .. stage and dev will be running the same image .. [regardless the build process ran twice ]

if you want to change the current workflow .. and deploy to dev and stage when a push is done to the same branch .. we can do so .

hope this answers your question :)

[stevejalim]

if you want to change the current workflow

Oh, no need to change it - if we retain what we have now, that's great. Thanks!

[bkochendorfer]

Do we want this to run on both nonprod and prod? Or is there some case somewhere that puts the prod build on prod and nonprod on nonprod?

[Basma1912]

you are right no need to include both .. since we are only using the workflow to build image .. I'll keep prod runner only ..is that ok?

[bkochendorfer]

Yep sounds good

[Basma1912]

@stevejalim when you can , please merge this request .. thank you

[stevejalim]

@Basma1912 Done! 👍