Skip to content
Aborted

Changes

Summary

  1. jobs/test-override: update build description at the end (details)
  2. jobs/bodhi-trigger: wrap testing in cosa pod (details)
  3. jobs/bodhi-trigger: add reporting to ResultsDB (details)
  4. jenkins/config: add JCASC dropin for jms-messaging-plugin (details)
Commit 7d4747d29bac135c083e596619cbf3197f0ad9f1 by Jonathan Lebon
jobs/test-override: update build description at the end

It's funny to still have it say 'Running' even when it's done.
The file was modifiedjobs/test-override.Jenkinsfile (diff)
Commit 999c3d34c96be127fa743b8a40e963e72b37b846 by Jonathan Lebon
jobs/bodhi-trigger: wrap testing in cosa pod

Prep for reporting, which will use code from cosa.
The file was modifiedjobs/bodhi-trigger.Jenkinsfile (diff)
Commit 5e59cff3c491e86d0aa9aa15eab1f518fe8ee5d7 by Jonathan Lebon
jobs/bodhi-trigger: add reporting to ResultsDB

Call out to the new `resultsdb-report` script in cosa to report test
results back to ResultsDB. Report when first running and then again with
final test results.

Just this alone seems sufficient for the results to show up in Bodhi's
"Automated Tests" tab.

With this, we'll then be able to work on adding policies in Greenwave.
The file was modifiedjobs/bodhi-trigger.Jenkinsfile (diff)
The file was modifiedHACKING.md (diff)
Commit 984af45c7dadb43d24ca990d344e0ef7528ac42d by Jonathan Lebon
jenkins/config: add JCASC dropin for jms-messaging-plugin

This configures the JMS messaging plugin to connect to the public
endpoint of the Fedora messaging bus.

The tricky thing is passing in the keystores. The plugin does
not support using Jenkins credentials[[1]] so we can't leverage
kubernetes-credentials-provider.

We could do it the old way, which is to mount the secret into the
Jenkins pod, but since d6d1f61, CoreOS CI now uses the exact same
`jenkins.yaml` manifest as the production pipeline and we don't want to
bind mount it there.

Instead, we hack around this by just baking the keystores in the Jenkins
image at `$JENKINS_HOME/jms-messaging-stores`.

[1]: https://github.com/jenkinsci/jms-messaging-plugin/issues/263
The file was addedjenkins/config/jms.yaml