Skip to content
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

Single source for DEBs and RPMs #71530

Closed
dims opened this issue Nov 28, 2018 · 2 comments
Closed

Single source for DEBs and RPMs #71530

dims opened this issue Nov 28, 2018 · 2 comments
Labels
sig/release Categorizes an issue or PR as relevant to SIG Release.

Comments

@dims
Copy link
Member

dims commented Nov 28, 2018

We have duplicate code in k/release and k/k for deb(s) and rpm(s).

The code in k/release is built using:

./jenkins.sh --kube-version 1.12.0 --distros xenial` (debs)
./docker-build.sh` (rpms)

The code in k/k is built using:

bazel build //build/debs 
bazel build //build/rpms

Note that the code in k/release can sign the debs and rpms, while the one in k/k doesn't (AFAICT).

Since k/k is versioned and k/release is not, we need to drop the code in k/release and stick to the one in k/k. More specifically we need to change our release process to build the stuff from k/k and push them to where ever we publish artifacts. So there's a lot more digging to be done

Related issue : kubernetes/release#631

/sig release

cc @tpepper @calebamiles @justaugustus

@k8s-ci-robot k8s-ci-robot added the sig/release Categorizes an issue or PR as relevant to SIG Release. label Nov 28, 2018
@mauilion
Copy link

To add on here. There are also a number of things that have changed in the k/k/build repo that are not present in the k/release/ repo.
Among them the handling of the sysctl.d and modules.conf.d files for the kubeadm package.

@timothysc
Copy link
Member

closing in favor of #71677

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
sig/release Categorizes an issue or PR as relevant to SIG Release.
Projects
None yet
Development

No branches or pull requests

4 participants