Changes

Summary

  1. jobs: delete ignition-dracut (details)
  2. jobs: rename fcct to butane (details)
  3. jobs: don't create jobs in folders (details)
Commit b0b856d73cd6f4d77d110e6b0d84838bdb26b9ec by Jonathan Lebon
jobs: delete ignition-dracut

It's been archived for a while now.
The file was modified jobs/seed-github-ci.Jenkinsfile (diff)
Commit 049ba64a37449daf13aec2fa20d8c57c55bdd2cb by Jonathan Lebon
jobs: rename fcct to butane

Follows the upstream repo rename.
The file was modified jobs/seed-github-ci.Jenkinsfile (diff)
Commit 142efd987ea39f357361c6d993aa297544475397 by Jonathan Lebon
jobs: don't create jobs in folders

There's a bug in BlueOcean where a link to a job containing slashes will
not work:

https://issues.jenkins.io/browse/JENKINS-47604

Let's hack around this by not creating folders and just having the jobs
live at the top-level.
The file was modified jobs/seed-github-ci.Jenkinsfile (diff)

Summary

  1. pod: use `coreos-ci-sa` serviceAccount when using `runAsUser` (details)
  2. pod: use serviceAccountName instead of serviceAccount (details)
  3. pod: set serviceAccount in podTemplate instead of YAML (details)
Commit 89159ffb40253be9ae29e44eb96a5051e8167d12 by Jonathan Lebon
pod: use `coreos-ci-sa` serviceAccount when using `runAsUser`

That service account has `RunAsAny` caps.

This is a bit hacky. Ideally, this shared lib wouldn't hardcode things
specific to either CoreOS CI or the pipeline here and instead we'd store
this config in https://github.com/coreos/coreos-ci. This works though
because the FCOS pipeline doesn't use `runAsUser` at all.
The file was modified vars/pod.groovy (diff)
Commit a4d2b514b7e2edeca40d4acbe1cb4a5f659a716e by Jonathan Lebon
pod: use serviceAccountName instead of serviceAccount

The latter is deprecated. It should still work at the k8s level, but
it's possible there's something going on with the Jenkins kubernetes
plugin not handling this correctly.
The file was modified vars/pod.groovy (diff)
Commit 0759da977470e5a8bf9d4a134887dc1117eb9458 by Jonathan Lebon
pod: set serviceAccount in podTemplate instead of YAML

Setting the `serviceAccountName` field in the pod YAML itself is not
working with the kubernetes plugin. I noticed that `podTemplate` also
supports specifying the `serviceAccount` directly. It's possible that
that key is used and any service account set in the pod YAML directly is
always overridden.

Let's try using that instead.
The file was modified vars/pod.groovy (diff)