Skip to content
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

Closed
jlebon opened this issue Jun 21, 2019 · 8 comments
Closed

Create tool for push lockfiles around #205

jlebon opened this issue Jun 21, 2019 · 8 comments

Comments

@jlebon
Copy link
Member

jlebon commented Jun 21, 2019

We need a tool that will:

  1. watch for new bodhi-updates builds
  2. push manifest-lock.generated.json to bodhi-updates
  3. on some configurable interval, open PR to update manifest-lock.json to testing-devel
@dustymabe
Copy link
Member

1. watch for new `bodhi-updates` builds

probably would be good to have our pipeline publish a fedmsg for new builds so other things can queue off of it

@dustymabe
Copy link
Member

1. watch for new `bodhi-updates` builds

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

@jlebon
Copy link
Member Author

jlebon commented Jun 24, 2019

Related: https://github.com/CentOS-PaaS-SIG/ci-pipeline/blob/59b4cb3cefdabca41844ea6a2c1bbfc221d90148/src/org/centos/pipeline/PipelineUtils.groovy#L304

The sendCIMessage step is provided by https://github.com/jenkinsci/jms-messaging-plugin.

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.

@dustymabe
Copy link
Member

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.

@jlebon
Copy link
Member Author

jlebon commented Jun 27, 2019

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.

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 jms-messaging-plugin?

@jlebon
Copy link
Member Author

jlebon commented Jul 5, 2019

@dustymabe
Copy link
Member

Anything left for this one?

@jlebon
Copy link
Member Author

jlebon commented Sep 25, 2019

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.

@jlebon jlebon closed this as completed Sep 25, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants