-
Notifications
You must be signed in to change notification settings - Fork 161
[19.03 backport] Backport master latest commits to 19.03 #433
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
| $(RM) -r debbuild | ||
| [ ! -d sources ] || $(CHOWN) -R $(shell id -u):$(shell id -g) sources | ||
| $(RM) -r sources | ||
| $(RM) engine-image |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We need to discuss if we can already backport these changes
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sure, that the main objective of this PR, what should we pick up to be close as possible of the nightly build without breaking the existing release process for previous version.
|
Can you sign-off the cherry-pick commits? Some checks expect the cherry-pick commits to have a sign-off (which should be the last line in the commit); when cherry-picking, the You can amend the existing commits, or use both |
4c44962 to
5f3ca6b
Compare
|
Given that there's some bigger changes in this (removal of publishing the "engine" images); I suggest holding off merging this until after 19.03.7 has been done. (I'm ok with a separate PR with a more limited number of changes if there's fixes in this one that are trivial and/or important to have) |
5f3ca6b to
088c10d
Compare
|
hmm; why is static failing on this branch, but not on master? |
|
If only we had these things called containers so we could reproduce CI issues locally... #NotAFanOfJenkins |
|
I think what's happening is we chown the workspace to jenkins user, but then the generated binaries are not chowned as jenkins user (probably root) so it can't remove it. |
|
Yes, there's some "chown-ing" happening in some parts; mostly curious why it fails in this branch but not on master |
|
@thaJeztah is it normal that CI is using docker/engine ? I lost track of where we are with that. |
Currently, yes, but I have a PR to change that; #457 (let me extract the first commit to a separate PR for easier review/merge) |
1. A symbol % is not working as expected in PHONY targets, so e.g. ubuntu-cosmic was not being rebuild each time, because ubuntu-cosmic directory exists. The fix is to explicitly mark every ubuntu-whatever target as phony. 2. Remove code duplication for making packages for different distros. 3. Add missing ubuntu (cosmic, disco) and debian (buster) to the appropriate targets. 4. As a side effect, bash completion now lists all the distros to be build. 5. Exclude raspbian from deb target as it can only be built on ARM. Signed-off-by: Kir Kolyshkin <kolyshkin@gmail.com> (cherry picked from commit c048fc8) Signed-off-by: Guillaume Lours <guillaume.lours@docker.com>
1. A symbol % is not working as expected in PHONY targets, so e.g. fedora-30 was not being rebuild each time, because fedora-30 directory exists. The fix is to explicitly mark every fedora-NN target as phony. 2. Remove code duplication for making packages for different distros. 3. As a side effect, bash completion now lists all the distros to be build. Signed-off-by: Kir Kolyshkin <kolyshkin@gmail.com> (cherry picked from commit 62a8258) Signed-off-by: Guillaume Lours <guillaume.lours@docker.com>
Instead of dynamically getting list of distros to build for, rely on the corresponding targets in sub-Makefiles. This also ensures that deb/Makefile and rpm/Makefile will have up-to-date list of distros included. This also fixes the following bug: > $ make deb > for p in raspbian-stretch ubuntu-bionic ubuntu-disco ubuntu-xenial debbuild/ubuntu-disco ubuntu-cosmic debian-buster debian-stretch; do \ > ... As you can see, `debbuild/ubuntu-disco` should not be included but it is. Could be prevented by using `-maxdepth 1` argument to `find`. While at it, amend the sub-Makefiles to print out the distro that we build for. Signed-off-by: Kir Kolyshkin <kolyshkin@gmail.com> (cherry picked from commit 8ac858c) Signed-off-by: Guillaume Lours <guillaume.lours@docker.com>
Signed-off-by: Sebastiaan van Stijn <github@gone.nl> (cherry picked from commit 2350856) Signed-off-by: Guillaume Lours <guillaume.lours@docker.com>
Signed-off-by: Sebastiaan van Stijn <github@gone.nl> (cherry picked from commit 689992d) Signed-off-by: Guillaume Lours <guillaume.lours@docker.com>
Signed-off-by: Jintao Zhang <zhangjintao9020@gmail.com> (cherry picked from commit fedbde9) Signed-off-by: Guillaume Lours <guillaume.lours@docker.com>
Signed-off-by: Zuhayr Elahi <elahi.zuhayr@gmail.com> (cherry picked from commit 1b52d15) Signed-off-by: Guillaume Lours <guillaume.lours@docker.com>
Signed-off-by: Zuhayr Elahi <elahi.zuhayr@gmail.com> (cherry picked from commit c1a42f9) Signed-off-by: Guillaume Lours <guillaume.lours@docker.com>
Signed-off-by: Eli Uriegas <eli.uriegas@docker.com> (cherry picked from commit 3ed5f77) Signed-off-by: Guillaume Lours <guillaume.lours@docker.com>
Re-use these build-args, so that there's only one place to set them per Dockerfile.
To verify this change:
Check if the env-vars are set on the image:
```bash
make UBUNTU_VERSIONS=ubuntu-bionic DEBIAN_VERSIONS="" RASPBIAN_VERSIONS="" CLI_DIR=$GOPATH/src/github.com/docker/cli ENGINE_DIR=$GOPATH/src/github.com/docker/docker deb
docker image inspect debbuild-ubuntu-bionic/x86_64 --format '{{json .Config.Env }}' | jq .
```
Which should output something like;
```json
[
"PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/local/go/bin:/go/bin",
"GOPROXY=direct",
"GO111MODULE=off",
"GOPATH=/go",
"DOCKER_BUILDTAGS=apparmor seccomp selinux",
"RUNC_BUILDTAGS=apparmor seccomp selinux",
"DISTRO=ubuntu",
"SUITE=bionic"
]
```
Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
(cherry picked from commit a996681)
Signed-off-by: Guillaume Lours <guillaume.lours@docker.com>
Signed-off-by: Sebastiaan van Stijn <github@gone.nl> (cherry picked from commit 5b8545f) Signed-off-by: Guillaume Lours <guillaume.lours@docker.com>
Signed-off-by: Sebastiaan van Stijn <github@gone.nl> (cherry picked from commit ca70795) Signed-off-by: Guillaume Lours <guillaume.lours@docker.com>
Signed-off-by: Sebastiaan van Stijn <github@gone.nl> (cherry picked from commit 863ec11) Signed-off-by: Guillaume Lours <guillaume.lours@docker.com>
Signed-off-by: Sebastiaan van Stijn <github@gone.nl> (cherry picked from commit f5975a7) Signed-off-by: Guillaume Lours <guillaume.lours@docker.com>
Signed-off-by: Sebastiaan van Stijn <github@gone.nl> (cherry picked from commit f2d6d9c) Signed-off-by: Guillaume Lours <guillaume.lours@docker.com>
088c10d to
399b434
Compare
|
I simply rebased |
|
opened #462 and cherry-picked it here to see if that resolves the problem |
Signed-off-by: Sebastiaan van Stijn <github@gone.nl> (cherry picked from commit d2395a3) Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
a1f9018 to
593dcd2
Compare
|
All green now, with #462 cherry-picked (we should merge that one first though) |
Backporting commits from
masterto be close as possible with the nightly docker-ce packaging in the19.03branchbackport of: