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

Run kubeadm job as a standalone job #2568

Merged
merged 1 commit into from
Apr 25, 2017
Merged

Run kubeadm job as a standalone job #2568

merged 1 commit into from
Apr 25, 2017

Conversation

fejta
Copy link
Contributor

@fejta fejta commented Apr 25, 2017

/assign @spxtr @pipejakob

@k8s-ci-robot k8s-ci-robot added the cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. label Apr 25, 2017
@spxtr
Copy link
Contributor

spxtr commented Apr 25, 2017

kubernetes-security :P

@fejta
Copy link
Contributor Author

fejta commented Apr 25, 2017

I should really learn to run these tests before creating the PR

@spxtr
Copy link
Contributor

spxtr commented Apr 25, 2017

/lgtm

It's tough to verify this sort of change, as @pipejakob knows, but this looks right.

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Apr 25, 2017
@fejta fejta merged commit 39293f2 into kubernetes:master Apr 25, 2017
@fejta fejta deleted the sq branch April 25, 2017 00:22
@krzyzacy
Copy link
Member

this seems murdered the job

@krzyzacy
Copy link
Member

nvm, the periodic version was not running normally before anyway

@pipejakob
Copy link
Contributor

Can you explain the motivation behind this move?

@fejta
Copy link
Contributor Author

fejta commented Apr 25, 2017

We don't want this job to run on every PR. And we don't want the delays in this job to slow down batches merges.

@spxtr
Copy link
Contributor

spxtr commented Apr 25, 2017

It doesn't make sense to have a job that runs_after_success of a presubmit but has always_run set to false.

@pipejakob
Copy link
Contributor

This probably isn't the best place to discuss what to do with this job, so I'll follow up elsewhere, but if I understand the change, this will effectively permanently break this pull job, since it was designed to only run after the bazel job (which builds/uploads CI .debs that are used by this kubeadm job).

I've had a separate PR open to fix this job for a while now (#2509), so maybe that's the best place to discuss how to move forward.

@spxtr
Copy link
Contributor

spxtr commented Apr 25, 2017

always_run set to false means its manually triggered. Just trigger it after the bazel job completes.

@pipejakob
Copy link
Contributor

Sure. Once the job is fully working and we actually want to trigger it more generally (either on every PR, or on PRs that change cmd/kubeadm/**), will it be appropriate to revert this change?

@spxtr
Copy link
Contributor

spxtr commented Apr 25, 2017

Yes, then it makes sense to do so.

@pipejakob
Copy link
Contributor

Got it, thanks!

pipejakob added a commit to pipejakob/test-infra that referenced this pull request Jun 6, 2017
This had been previously disabled by
kubernetes#2568. Adding the job back
to the bazel pipeline and reenabling.
pipejakob added a commit to pipejakob/test-infra that referenced this pull request Jun 6, 2017
This had been previously disabled by
kubernetes#2568. Adding the job back
to the bazel pipeline and reenabling.

Also, remove sporadic trailing whitespace.
pipejakob added a commit to pipejakob/test-infra that referenced this pull request Jun 17, 2017
This had been previously disabled by
kubernetes#2568. Adding the job back
to the bazel pipeline and reenabling.

Also, remove sporadic trailing whitespace.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. lgtm "Looks good to me", indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants