R4R: build gaia docker image during CI

[mircea-c]

• Linked to github-issue with discussion and accepted design OR link to spec that describes this work. DevOps issue #147
• Wrote tests
• Updated relevant documentation (docs/)
• Added entries in PENDING.md with issue #
• rereviewed Files changed in the github PR explorer

---

For Admin Use:

• Added appropriate labels to PR (ex. wip, ready-for-review, docs)
• Reviewers Assigned
• Squashed all commits, uses message "Merge pull request #XYZ: [title]" (coding standards)

[jackzampolin]

A long running request of mine. Thank you very much for this PR @mircea-c !

[codecov]

Codecov Report

Merging #3282 into develop will increase coverage by 0.13%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##           develop    #3282      +/-   ##
===========================================
+ Coverage     55.2%   55.34%   +0.13%     
===========================================
  Files          134      135       +1     
  Lines         9526     9597      +71     
===========================================
+ Hits          5259     5311      +52     
- Misses        3936     3954      +18     
- Partials       331      332       +1

[jackzampolin]

Can we also make this push docker tags for git tags and update latest every time too? 🙏

[mircea-c]

Can we also make this push docker tags for git tags and update latest every time too?

I'll see if we can push tags easily.

As for latest I'm not convinced that's useful. Which version should it be pointing to? Latest develop build, a separate branch/tag specifically created for latest?

[cwgoes]

Do we want to do this on every branch? Was there a simulation requirement for that?

Otherwise just building on push to develop and master seems fine to me.

[alessio]

@mircea-c good point. In my view, we should have one tag for latest stable and one for latest develop. So how about stable and develop?

[alessio]

Do we want to do this on every branch?

@cwgoes Other than master and develop, I don't think we need tags for other branches.

[mircea-c]

OK, I've changed it so that it only builds on pushes to master and develop. The tags reflect the latest commit to either of those branches .

@jackzampolin any thoughts?

[alessio]

Looks good to me

[cwgoes]

LGTM but will let @jackzampolin give a final review.

[jackzampolin]

Yeah this works for me for now, Ideally we get artifacts for each commit tagged appropriately (i.e. for releases and tags, as well as develop and master), but this is a great start and we can easily add more here later. Going to go ahead and merge this.