Skip to content
This repository has been archived by the owner on Nov 6, 2020. It is now read-only.

stop breaking docker hub builds #9833

Closed
debris opened this issue Oct 30, 2018 · 3 comments
Closed

stop breaking docker hub builds #9833

debris opened this issue Oct 30, 2018 · 3 comments
Labels
F2-bug 🐞 The client fails to follow expected behavior. F3-annoyance 💩 The client behaves within expectations, however this “expected behaviour” itself is at issue. M1-ci 🙉 Continuous integration.
Milestone

Comments

@debris
Copy link
Collaborator

debris commented Oct 30, 2018

Our docker hub release process is broken, cause changes on master branch of this repo affect how stable branch is being released on docker hub (e.g. pr #9689)

How it works now:

to release master, we use master/scripts/docker/hub/Dockerfile
to release beta, we use master/scripts/docker/hub/Dockerfile
to release stable, we use master/scripts/docker/hub/Dockerfile

How it should work:

to release master, we should use master/scripts/docker/hub/Dockerfile
to release beta, we should use **beta**/scripts/docker/hub/Dockerfile
to release stable, we should use **stable**/scripts/docker/hub/Dockerfile

cc @paritytech/ci
thanks @fubhy for the report

@debris debris added F2-bug 🐞 The client fails to follow expected behavior. F3-annoyance 💩 The client behaves within expectations, however this “expected behaviour” itself is at issue. M1-ci 🙉 Continuous integration. labels Oct 30, 2018
@ddorgan
Copy link
Collaborator

ddorgan commented Nov 7, 2018

@debris but this is expected right? This was backported to both stable and beta.

Stable: #9648

Beta: #9649

@debris
Copy link
Collaborator Author

debris commented Nov 26, 2018

@ddorgan, can you elaborate? Does our docker hub deployment work exactly as I described in how it should work?

If yes, than we made a mistake, cause we should never backport #9689 as it is a breaking change

@5chdn 5chdn added this to the 2.3 milestone Nov 26, 2018
@5chdn
Copy link
Contributor

5chdn commented Dec 5, 2018

How it works now

Not from what I can tell, the pipeline uses the scripts/gitlab/publish-docker.sh on the branch it is running, and the -f scripts/docker/hub/Dockerfile from the branch it is running on.

Please give pointers if you think this works differently.

@5chdn 5chdn closed this as completed Dec 5, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
F2-bug 🐞 The client fails to follow expected behavior. F3-annoyance 💩 The client behaves within expectations, however this “expected behaviour” itself is at issue. M1-ci 🙉 Continuous integration.
Projects
None yet
Development

No branches or pull requests

3 participants