[JIRA] [bitbucket-plugin] (JENKINS-30166) Implement an SCMSource for BitBucket
Title: Message Title Antonio Muñiz created an issue Jenkins / JENKINS-30166 Implement an SCMSource for BitBucket Issue Type: Task Assignee: Antonio Muñiz Components: bitbucket-plugin Created: 27/Aug/15 8:44 AM Priority: Major Reporter: Antonio Muñiz When using the BitBucket plugin within some implementation of MultiBranchProject an implementation of SCMSource is needed. This implementation should be provided by BitBucket plugin. Add Comment This
[JIRA] [bitbucket-plugin] (JENKINS-30166) Implement an SCMSource for BitBucket
Title: Message Title Antonio Muñiz started work on JENKINS-30166 Change By: Antonio Muñiz Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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.
[JIRA] [bitbucket-plugin] (JENKINS-30166) Implement an SCMSource for BitBucket
Title: Message Title Antonio Muñiz commented on JENKINS-30166 Re: Implement an SCMSource for BitBucket There were two main goals of having an specific SCMSource for BitBucket: 1. Use the WS API to discover branches without having to perform a fetch (much faster) 2. Add the ability to discover PRs automatically After some code diving I sadly realized that any of the goals are achievable because: 1. In the process of branch discovery an SCMSourceCriteria.isHead which is responsible to say if a branch will be included or not basically checking for the existence of some marker file. Unfortunately there is no way to check that using the BB WS API. 2. The SCMSource API is designed to discover and manage branches in a single Git remote, but BB is managing PRs as independent repositories (not as refs in the same repository like GitHub does). So we can discover PRs (using the WS API) but they will be processed later as a branch in the SCMSource managed remote, which is wrong since the PR source branch lives in a separate repository. Any ideas on how we can manage this? Or it's simply not possible given the current design of scm-api-plugin (and probably branch-api-plugin)? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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.
[JIRA] [bitbucket-plugin] (JENKINS-30166) Implement an SCMSource for BitBucket
Title: Message Title
Antonio Muñiz edited a comment on JENKINS-30166
Re: Implement an SCMSource for BitBucket
There were two main goals of having an specific SCMSource for BitBucket:1. Use the WS API to discover branches without having to perform a fetch (much faster)2. Add the ability to discover PRs automaticallyAfter some code diving I sadly realized that any of the goals are achievable because:1. In the process of branch discovery an {{SCMSourceCriteria.isHead}} is applied, which is responsible to say if a branch will be included or not basically checking for the existence of some marker file. Unfortunately there is no way to check that using the BB WS API.2. The {{SCMSource}} API is designed to discover and manage branches in a single Git {{remote}}, but BB is managing PRs as independent repositories (not as refs in the same repository like GitHub does). So we can discover PRs (using the WS API) but they will be processed later as a branch in the {{SCMSource}} managed remote, which is wrong since the PR source branch lives in a separate repository.Any ideas on how we can manage this? Or it's simply not possible given the current design of {{scm-api-plugin}} (and probably {{branch-api-plugin}})?
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
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.
[JIRA] [bitbucket-plugin] (JENKINS-30166) Implement an SCMSource for BitBucket
Title: Message Title Jesse Glick commented on JENKINS-30166 Re: Implement an SCMSource for BitBucket Number one is unfortunate. Have you contacted Atlassian asking whether they intend to add functionality comparable to this? BB is managing PRs as independent repositories (not as refs in the same repository like GitHub does) Well, GitHub of course manages PRs as independent repositories, it just also offers them as refs in origin as a convenience. Number two does not seem like an issue. Your SCMHead implementation would merely need to encode the fork owner’s name, or the pull request number, etc., and return an appropriately-configured GitSCM when build is called. Nothing about SCMSource is forcing the SCM instances an implementation generates to have anything particular in common; certainly it knows nothing of hudson.plugins.git.UserRemoteConfig. Perhaps you are confused because you are extending AbstractGitSCMSource, which does currently assume that it is operating on a single remote. Either that needs to be generalized, or you just need to extend SCMSource directly. (The only valuable parts of AbstractGitSCMSource are the caching code, which ideally we would like to not use at all, though that depends on issue number one, so maybe it could be factored out into a static utility method; and SpecificRevisionBuildChooser, which is public static so it looks like it can be reused.) Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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.
[JIRA] [bitbucket-plugin] (JENKINS-30166) Implement an SCMSource for BitBucket
Title: Message Title Jesse Glick commented on JENKINS-30166 Re: Implement an SCMSource for BitBucket BTW even if the official REST API does not have special support for file contents, by spending a couple minutes browsing their web UI it seems you can get the equivalent: $ curl -Is https://bitbucket.org/jglick/yenta/raw/default/README.md | fgrep HTTP/ HTTP/1.1 200 OK $ curl -Is https://bitbucket.org/jglick/yenta/raw/default/Jenkins | fgrep HTTP/ HTTP/1.1 404 NOT FOUND Now how this would work on a private repository is another question. Can you send BASIC auth, etc.? Experiment. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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.
[JIRA] [bitbucket-plugin] (JENKINS-30166) Implement an SCMSource for BitBucket
Title: Message Title Antonio Muñiz stopped work on JENKINS-30166 Change By: Antonio Muñiz Status: In Progress Open Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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.
[JIRA] [bitbucket-plugin] (JENKINS-30166) Implement an SCMSource for BitBucket
Title: Message Title Antonio Muñiz started work on JENKINS-30166 Change By: Antonio Muñiz Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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.
[JIRA] [bitbucket-plugin] (JENKINS-30166) Implement an SCMSource for BitBucket
Title: Message Title Antonio Muñiz closed an issue as Won't Fix Jenkins / JENKINS-30166 Implement an SCMSource for BitBucket Change By: Antonio Muñiz Status: In Progress Closed Resolution: Won't Fix Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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.
