Mark Waite commented on Bug JENKINS-21309

I had looked inside the source code to see if I could locate the issue from the source code. I was unsuccessful. I hadn't attempted to duplicate the problem from the user interface previously. Today, I tried to duplicate the problem from the user interface. I could not duplicate the problem from the user interface.

Could you provide step by step instructions which show how you define the Jenkins job and the clicks you perform to navigate to the URL which contains the extra "s" character?

I failed to duplicate the bug with the following steps:

  1. Create a new free-style job "JENKINS-21309-bitbucket-url-wrong"
  2. Select Git as Source Code Management
  3. Insert repository URL https://markewa...@bitbucket.org/git-client-plugin.git
  4. Enable SCM polling (so that I can use curl to trigger a poll), no polling schedule is required
  5. Cause the repo to poll with "curl http://127.0.0.1:8080/git/notifyCommit?url="">
  6. Confirm the job built based on that poll
  7. Submit a change to the repository master branch
  8. Cause the repo to poll again with "curl http://127.0.0.1:8080/git/notifyCommit?url="">
  9. Confirm that the job built again and shows the change in the "Recent Changes"
  10. I was unable to find any location which linked to a bitbucket diff at all. What link do you click to see a bitbucket diff link, without configuring the bitbucket repository URL in the browser?
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to