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
Allow multiple pipelinerun for the same event #589
Conversation
cad521b
to
dfc6238
Compare
} | ||
|
||
if annotationRepo.Spec.URL != "" { | ||
repo = annotationRepo | ||
// TODO: We need to figure out secretCreation, it's buggy normally without multiplexing ie:bug #543 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
what if we create one secret for each pipeline?
anyway the secret is short lived till the life of pr
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
till we find a way to enable this again what would be side effect of this change?
multiple pipeline from private repo would fail right?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
let us work on this in a following PR, i may have a nice solution,
the e2e test error are legit, just finishing to fix it. |
@@ -94,7 +94,7 @@ spec: | |||
}, | |||
}, | |||
{ | |||
name: "test-annotations-inside-repo", | |||
name: "test-annotations-inside-Repo", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
was this a find and replace repo
-> Repo
change ? π
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
just un Alt-c too much :D
Signed-off-by: Chmouel Boudjnah <chmouel@redhat.com>
also how this is suppose to work with webhooks ? |
the same as before ? what do you mean by one message? (there was a bug in e2e with webhooks just before which i just fixed) |
we now gets all the matched condition from the matcher in the same struct we did a bunch of refactoring to break out .Run which got moved to its own Make event able to process multiple pipelineruns We run a goroutine in a workgroups which we wait for. This will be run in the main goroutine which started from the sinker. We disable secret auto creation for now when running multiples, it has many issues we need to fix regardless. We retries if we can't update the RepoStatus until we are able to do it. Signed-off-by: Chmouel Boudjnah <chmouel@redhat.com>
Signed-off-by: Chmouel Boudjnah <chmouel@redhat.com>
Signed-off-by: Chmouel Boudjnah <chmouel@redhat.com>
while using webhook we post a comment with breakdown |
yeah correct, or i believe it will, i have just enabled multiple prs e2e test for gitlab so will see how it goes π |
Signed-off-by: Chmouel Boudjnah <chmouel@redhat.com>
may be we should add which pipeline name in comment ? |
Co-authored-by: Shivam Mukhade <smukhade@redhat.com>
Changes
Allow multiple pipelinerun on the same event
Fixes #528
A bunch of of refactoring to break out .Run which got moved to its own.
We have a
sync.Map
of checkRunIds to track the checkRuns to which pipelineRun, we use github api "external_id" field for that .We run a goroutine in a workgroups waiting for all the pr to run This wait that all of them finishes before exiting to the adapter goroutine.
We retries if we can't update the RepoStatus until we are able to do it.
TODO (before merge):
TODO (post):
/test prname
supportScreenshot:
Submitter Checklist
make test lint
before submitting a PR (ie: with pre-commit, no need to waste CPU cycle on CI