-
Notifications
You must be signed in to change notification settings - Fork 30
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 azure devops webhook support #401
Conversation
Process multiple git push events in azure and bitbucket.
eaf714e
to
bbe498e
Compare
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.
Looking good! With a couple of questions :)
ae90b41
to
41bcb20
Compare
41bcb20
to
31abd19
Compare
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.
LGTM, thanks!
@@ -0,0 +1,110 @@ | |||
// File copied from https://github.com/go-playground/webhooks/blob/master/azuredevops/azuredevops.go |
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.
nit: I think it could make sense to copy the corresponding test file over as well, just to be on the safe side. How do you see it?
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.
we would also need to copy all the testdata files.. https://github.com/go-playground/webhooks/blob/master/azuredevops/azuredevops_test.go#L63
I would avoid copying all those files. Should we leave it without the test or maybe we can just transfer my fork to the fleet org and use the fork instead?
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's leave it without the test for now; in the meantime, I'll be watching your PR so that we can switch back to using upstream ASAP. Thanks for clarifying :)
Add support for
Azure
DevOps
webhook.Azure
will notifygitjob
when a new commit has been pushed, then a Job will be created with the latest changes. It works the same way as the webhooks for other git providers.The https://github.com/go-playground/webhooks library we use for parsing the webhooks doesn't provide verification in Azure. I created a PR for adding basic auth verification in Azure. The file from this PR is copied in fleet in the meantime.
refers to rancher/fleet#1998