-
Notifications
You must be signed in to change notification settings - Fork 59
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create tool for push lockfiles around #205
Comments
probably would be good to have our pipeline publish a fedmsg for new builds so other things can queue off of it |
which actually ties pretty closely with #198 |
The So I think it's a matter of adding that plugin to our master, then plugging in the right configs and creds into Jenkins so it's set up. |
according to https://pagure.io/fedora-infrastructure/issue/7940#comment-579650 we need our own certs and can't re-use what the Fedora CI pipeline has done. I looked at rabbitmq publishers for jenkins today. I found one but I don't see where it supports TLS cert auth. Fortunately the fedora-messaging CLI is growing the ability to publish messages using the CLI. I tested that PR out and it seems to be working so maybe we can go with that. I'll try to test this out in a hacker pipeline run tomorrow. |
Is the first sentence related to the next ones? I'm not sure if you're saying that because we can't use the same cert as the Fedora CI pipeline, we can't use the same plugin either. Isn't it just a matter of plugging in a different cert in the settings for |
Anything left for this one? |
We still need to make it PR-based, though that's tracked by coreos/fedora-coreos-releng-automation#32, so yeah let's close this one. |
We need a tool that will:
bodhi-updates
buildsmanifest-lock.generated.json
tobodhi-updates
manifest-lock.json
totesting-devel
The text was updated successfully, but these errors were encountered: