Use stable names for GH workflow jobs

[hakman]

We will need to pass the job names to Tide to make them blocking, so stable names would be required.

[johngmyers]

We can probably skip making nodeup on MacOS.

[hakman]

Good point. Done.

[hakman]

Any idea why we only build nodeup and not all ?

[justinsb]

I suspect this is just historical about the way these tests were introduced (they're still fairly new); I suspect we were just trying to replace tests in travis.

From that point of view I really like splitting out the tests explicitly. What we really want on macos is coverage of the kops CLI (I don't think we want nodeup tests to run on macos; there's a case for windows in the future but I don't know of anyone trying to get kubelet to run on macos)

For linux, I think trying everything seems reasonable! We should probably be trending towards running tests in bazel, as more and more of our release pipeline is using bazel (I have some exciting news on this front for our next office hours :-) )

I think it's fine to rearrange what these do a bit in a separate PR.

[hakman]

Looking forward to that :).

[johngmyers]

This removes Go 1.13. Is that because it's currently redundant with the Prow jobs and we expect to drop it as a requirement when we move Prow to 1.14?

[hakman]

This removes Go 1.13. Is that because it's currently redundant with the Prow jobs and we expect to drop it as a requirement when we move Prow to 1.14?

Yes. Also, when Go 1.15 is released we can add an optional build-next job.

[rifelpet]

this looks good to me. I agree we can have optional jobs for the next or previous go versions. I know i've asked this before, but to confirm here, are we safe to merge this with prow configured as-is and will it affect other open PRs? and what will the rollout to enforce these jobs look like exactly?

[hakman]

@rifelpet open PRs would behave like current release branches, expecting these tests, but will not block for now.
Having stable names, means that we can backport these to release branches also and satisfy Prow and Tide requirements.
Once we are happy with how things work, we can see what should be done to make them blocking and remove the equivalent TravisCI jobs.

[justinsb]

/approve
/lgtm

Github testing isn't entirely happy, so this is also a nice test of whether we're going to break other PRs (I think!)

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: hakman, justinsb

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [justinsb]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[hakman]

/retest