• Describe what you need us to do:

This request is for a Jenkins master instance to be used for Container Linux development/testing builds until its retirement (currently theorized to be mid-2020). There is an ongoing effort to decommission legacy CoreOS infrastructure by migrating services off it.

Since this is dev/testing, we're not concerned with the hosting details (URLs, IPs, etc.). You can pick your preferred Jenkins image if there is precedent for using a specific one; we just need to install a few plugins and create pipeline jobs. This is only a master, so we don't expect particularly high resource utilization, but some persistent storage would be needed. We currently have 100GiB on /var/jenkins_home, but it's using 14GiB of it. The workers doing the actual builds are handled externally, so they are unrelated to this request.

Optionally, I think it would be nice to have FAS SSO (e.g. with the oic-auth plugin) if this service will run on Fedora OpenShift. I saw an infra page saying to request client secrets though infra tickets. If that could be set up as part of this, great, if not, we can worry about special authentication later.

• When do you need this? (YYYY/MM/DD)

I don't know of any hard dates related to this, but migrating off the old infrastructure sooner will make everyone happier.

• When is this no longer needed or useful? (YYYY/MM/DD)

Check on the state of the Container Linux life cycle with the CoreOS teams (maybe just e-mail aos-devel) on July 1st 2020. This dev Jenkins will no longer be needed if EOL is on schedule, but its life would need to be extended if plans slip.

• If we cannot complete your request, what is the impact?

I'll just run it on some random cloud platform.