Arvados

Official Jenkins documentation:

Configuration as code - This is a higher-level overview of the plugin Lucas found. You can install this plugin, export your configuration, edit it, and load it back in. This could maybe provide a migration path for us.

Pipeline as code

By default, pipeline as code looks for a Jenkinsfile at the root of the project's repository. You can at least tell it to look in a different path. And maybe that would be sufficient for us. But what's less clear to me what is the right way to define a project that wants to work with more than one repository (e.g., arvados and arvados-dev for our package-building jobs, since they build from Arvados source but know some details about our in-house infrastructure). This needs a little bit more investigation.

At some point I did get referred to RJPP, which seems promising, except it seems to be based on an older version of pipelines that we maybe shouldn't be targeting. This also needs a little bit more investigation.