-
Notifications
You must be signed in to change notification settings - Fork 70
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
Add integration test to check linchpin.latest output #789
Conversation
One thing to consider with this test is should we be running it with every relevant PR, or just the release PRs? |
ci-linchpin-messageBus-trigger build #525: FAILURE: https://jenkins-continuous-infra.cloud.continuous-infra.upshift.redhat.com/job/ci-linchpin-messageBus-trigger/525/ |
Can one of the admins verify this patch? |
d1b3428
to
956e1f0
Compare
ci-linchpin-messageBus-trigger build #526: FAILURE: https://jenkins-continuous-infra.cloud.continuous-infra.upshift.redhat.com/job/ci-linchpin-messageBus-trigger/526/ |
956e1f0
to
9d66f16
Compare
ci-linchpin-messageBus-trigger build #527: FAILURE: https://jenkins-continuous-infra.cloud.continuous-infra.upshift.redhat.com/job/ci-linchpin-messageBus-trigger/527/ |
9d66f16
to
b698db7
Compare
ci-linchpin-messageBus-trigger build #528: FAILURE: https://jenkins-continuous-infra.cloud.continuous-infra.upshift.redhat.com/job/ci-linchpin-messageBus-trigger/528/ |
b698db7
to
f9480a0
Compare
ci-linchpin-messageBus-trigger build #529: FAILURE: https://jenkins-continuous-infra.cloud.continuous-infra.upshift.redhat.com/job/ci-linchpin-messageBus-trigger/529/ |
f9480a0
to
f7d1749
Compare
ci-linchpin-messageBus-trigger build #530: FAILURE: https://jenkins-continuous-infra.cloud.continuous-infra.upshift.redhat.com/job/ci-linchpin-messageBus-trigger/530/ |
f7d1749
to
f8d8566
Compare
ci-linchpin-messageBus-trigger build #531: FAILURE: https://jenkins-continuous-infra.cloud.continuous-infra.upshift.redhat.com/job/ci-linchpin-messageBus-trigger/531/ |
f8d8566
to
4a4d2a0
Compare
ci-linchpin-messageBus-trigger build #532: FAILURE: https://jenkins-continuous-infra.cloud.continuous-infra.upshift.redhat.com/job/ci-linchpin-messageBus-trigger/532/ |
4a4d2a0
to
5bb57b1
Compare
ci-linchpin-messageBus-trigger build #533: FAILURE: https://jenkins-continuous-infra.cloud.continuous-infra.upshift.redhat.com/job/ci-linchpin-messageBus-trigger/533/ |
23e08f0
to
a9de951
Compare
[test] |
8344a29
to
c259644
Compare
I'll rebase this against #792 once that gets merged |
ci-linchpin-messageBus-trigger build #535: FAILURE: https://jenkins-continuous-infra.cloud.continuous-infra.upshift.redhat.com/job/ci-linchpin-messageBus-trigger/535/ |
ci-linchpin-messageBus-trigger build #540: FAILURE: https://jenkins-continuous-infra.cloud.continuous-infra.upshift.redhat.com/job/ci-linchpin-messageBus-trigger/540/ |
c259644
to
ab491c0
Compare
ab491c0
to
79ee97f
Compare
ci-linchpin-messageBus-trigger build #543: SUCCESS: https://jenkins-continuous-infra.cloud.continuous-infra.upshift.redhat.com/job/ci-linchpin-messageBus-trigger/543/ |
Check linchpin.latest output to make sure that the data we receive from the various providers is up to date