Tag images with commit SHA

[pavolloffay]

Tag images with commit SHA.

It's necessary if there is an external CI/CD pipeline which is invoked per change in master. @objectiser can provide more info why it is needed.

Some open questions:

• should be old SHA tags removed (per number/time)?
• publish sha tags to a different repo?

https://docs.travis-ci.com/user/environment-variables/#default-environment-variables

Signed-off-by: Pavol Loffay ploffay@redhat.com

[codecov]

Codecov Report

Merging #1082 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff           @@
##           master   #1082   +/-   ##
======================================
  Coverage     100%    100%           
======================================
  Files         140     140           
  Lines        6622    6622           
======================================
  Hits         6622    6622

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 01ff822...b218cd6. Read the comment docs.

[black-adder]

I'd like to have a separate repo for these so we don't pollute the main repos.

[pavolloffay]

how do we call it jaeger-foo-stream|build|ci|sha?

[pavolloffay]

Just for the record I have tried to push ~600 different tags(with different layers) on docker hub. I was still able to access the first tags.

[yurishkuro]

how do we call it jaeger-foo-stream|build|ci|sha?

jaeger-foo-snapshot ?

[pavolloffay]

sounds good to me, @jpkrohling @objectiser? If not response I will continue with snapshot

[jpkrohling]

snapshot sounds alright to me.

[objectiser]

@pavolloffay snapshot is fine with me