jenkins/config: add JCASC dropin for jms-messaging-plugin #51
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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]: jenkinsci/jms-messaging-plugin#263
jlebon
added a commit
to jlebon/fedora-coreos-pipeline
that referenced
this pull request
Nov 17, 2023
The JMS messaging plugin takes keystores for its credentials. We can't make them into proper Jenkins credentials nor mount them as Kubernetes secrets. Keystores are deprecated and super awkward to work with. Since there's nothing secret about the public endpoint, let's just add them directly to git (but with build instructions for posterity). This pairs with coreos/coreos-ci#51 which makes CoreOS CI leverage those files and which has more details.
|
Requires: coreos/fedora-coreos-pipeline#931 |
jlebon
added a commit
to coreos/fedora-coreos-pipeline
that referenced
this pull request
Nov 17, 2023
The JMS messaging plugin takes keystores for its credentials. We can't make them into proper Jenkins credentials nor mount them as Kubernetes secrets. Keystores are deprecated and super awkward to work with. Since there's nothing secret about the public endpoint, let's just add them directly to git (but with build instructions for posterity). This pairs with coreos/coreos-ci#51 which makes CoreOS CI leverage those files and which has more details.
aaradhak
pushed a commit
to aaradhak/fedora-coreos-pipeline
that referenced
this pull request
May 14, 2024
The JMS messaging plugin takes keystores for its credentials. We can't make them into proper Jenkins credentials nor mount them as Kubernetes secrets. Keystores are deprecated and super awkward to work with. Since there's nothing secret about the public endpoint, let's just add them directly to git (but with build instructions for posterity). This pairs with coreos/coreos-ci#51 which makes CoreOS CI leverage those files and which has more details.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.