Closed coreycsteele closed 7 years ago
The person reporting this issue to me found that this actually does work. Issue filed in error.
Thanks for closing the issue. As a reminder, we've moved our issue tracking to JIRA, please file any new issues here:
I went off your marketplace page, the submit support request is pointing at github. I’ll make a note of the new issue tracking page. Thanks.
corey
On Sep 25, 2017, at 3:49 PM, Mohammed Davoodi notifications@github.com wrote:
Thanks for closing the issue. As a reminder, we've moved our issue tracking to JIRA, please file any new issues here:
https://mohamicorp.atlassian.net/servicedesk/ https://mohamicorp.atlassian.net/servicedesk/ — You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub https://github.com/mohamicorp/stash-jenkins-postreceive-webhook/issues/205#issuecomment-332035987, or mute the thread https://github.com/notifications/unsubscribe-auth/ACQBcXIhRLD3W-b9-5jrl7FbnHe6OPzrks5smC3sgaJpZM4PjDse.
Thanks for the heads up, we've changed the URL now.
I’m trying to get a password reset link from your site but I’m not receiving anything. Is that working? Your docs indicated you can setup multiple jenkins url’s but the button to do that doesn’t exist.
corey
On Sep 25, 2017, at 6:41 PM, Mohammed Davoodi notifications@github.com wrote:
Thanks for the heads up, we've changed the URL now.
— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub https://github.com/mohamicorp/stash-jenkins-postreceive-webhook/issues/205#issuecomment-332061211, or mute the thread https://github.com/notifications/unsubscribe-auth/ACQBcaFHasyz1l9jS5yNjJ6hLn6Tp_hbks5smFZIgaJpZM4PjDse.
Hi Corey,
The password reset should be handled by Atlassian (they host our service desk and jira), not sure why it's not working at the moment.
As for the multi-server support, we're releasing a new version of the plugin today which will include that. We published the new documentation a little early. You'll be able to get it today.
Mohammed
Bitbucket Server Webhook to Jenkins, the Advanced Configuration used to have an option to trigger jenkins for all pull requests. Recently this option disappeared. Please bring it back.
My preferred config, which worked until recently, is to have Bitbucket only trigger Jenkins on pull request changes and on special branches (“Build from”). Now only the latter is an option.
Looks like the only workaround is to “Build all”, but that will cause extra load on our jenkins bots performing work on branches not ready to be reviewed.