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.
jlebon
commented
11 months ago
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.yamlmanifest 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.