Comment 4 for bug 1904608
Revision history for this message
| Lucas Kanashiro (lucaskanashiro) wrote | #4 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
73416ba
(Get the code!)
The scenario with an unexpected behavior for me was:
1- Build is requested for all architectures (in our case amd64, arm64, ppc64el, and s390x).
2- 2 builds passed (amd64, arm64) and 2 failed (ppc64el, s390x) due to some flaky tests failing during build.
3- The successful builds are uploaded to DockerHub.
4- I retrigger builds for the failing architectures.
5- They build fine and get uploaded.
6- The tags for the architectures initially uploaded are gone.
What I was discussing with my teammates is that LP may upload tags in batches and it desconsiders the previous ones on DockerHub. Is this correct? I would not expect the need to request new builds even for the successfully ones. Moreover, I am not sure how this works exactly but if there is an architecture specific bug I would not expect to trigger builds for all architectures because of this fix, the digest hash of the image will change and users might think that there is something new but actually there is not.