Bitbucket Branch Source Plugin & Endpoints

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

Bitbucket Branch Source Plugin & Endpoints

Richard Bywater-2
Hi

One of my colleagues is trying to get Jenkins 2 up and running with the Bitbucket Branch Source plugin using our Bitbucket Server infrastructure.

We've run into an issue with the plugin as it appears it expects the server URL defined in the Bitbucket endpoint configuration to be the same as the one to be used for cloning purposes even for SSH.

So for instance if you have defined https://bitbucketserver.example.com/bitbucket as the server URL, when cloning via SSH it attempts to use ssh://bitbucketserver.example.com:7999 (where 7999 is correctly read out of the clone link URLs returned by the Bitbucket API). In our case however, the web URL is different to the SSH url. For instance, based on the previous example, our SSH address is ssh://actualservername.example.com:7999/

My question is that, rather than reusing the server URL for cloning operations, is there a reason why the clone URLs returned by the API for a repository aren't used instead? This would seem to allow Bitbucket to tell the plugin exactly where to look in case any other corner cases like this come up.

Cheers
Richard.

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAMui945Sck2UTwhw8n7Ny0hbzc6CC_Aon8tDsXTBGa8cHzRFsw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Bitbucket Branch Source Plugin & Endpoints

stephenconnolly
Oversight. Please file a ticket in JIRA

On 4 October 2017 at 20:46, Richard Bywater <[hidden email]> wrote:
Hi

One of my colleagues is trying to get Jenkins 2 up and running with the Bitbucket Branch Source plugin using our Bitbucket Server infrastructure.

We've run into an issue with the plugin as it appears it expects the server URL defined in the Bitbucket endpoint configuration to be the same as the one to be used for cloning purposes even for SSH.

So for instance if you have defined https://bitbucketserver.example.com/bitbucket as the server URL, when cloning via SSH it attempts to use ssh://bitbucketserver.example.com:7999 (where 7999 is correctly read out of the clone link URLs returned by the Bitbucket API). In our case however, the web URL is different to the SSH url. For instance, based on the previous example, our SSH address is ssh://actualservername.example.com:7999/

My question is that, rather than reusing the server URL for cloning operations, is there a reason why the clone URLs returned by the API for a repository aren't used instead? This would seem to allow Bitbucket to tell the plugin exactly where to look in case any other corner cases like this come up.

Cheers
Richard.

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAMui945Sck2UTwhw8n7Ny0hbzc6CC_Aon8tDsXTBGa8cHzRFsw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CA%2BnPnMx3CsdxOe%3D1O53c%2B25HfVe%3DvJSRq6272%2BXz4RVryFpXRw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Bitbucket Branch Source Plugin & Endpoints

Richard Bywater-2
Will do!

Thanks
Richard.

On Thu, 5 Oct 2017 at 21:20 Stephen Connolly <[hidden email]> wrote:
Oversight. Please file a ticket in JIRA

On 4 October 2017 at 20:46, Richard Bywater <[hidden email]> wrote:
Hi

One of my colleagues is trying to get Jenkins 2 up and running with the Bitbucket Branch Source plugin using our Bitbucket Server infrastructure.

We've run into an issue with the plugin as it appears it expects the server URL defined in the Bitbucket endpoint configuration to be the same as the one to be used for cloning purposes even for SSH.

So for instance if you have defined https://bitbucketserver.example.com/bitbucket as the server URL, when cloning via SSH it attempts to use ssh://bitbucketserver.example.com:7999 (where 7999 is correctly read out of the clone link URLs returned by the Bitbucket API). In our case however, the web URL is different to the SSH url. For instance, based on the previous example, our SSH address is ssh://actualservername.example.com:7999/

My question is that, rather than reusing the server URL for cloning operations, is there a reason why the clone URLs returned by the API for a repository aren't used instead? This would seem to allow Bitbucket to tell the plugin exactly where to look in case any other corner cases like this come up.

Cheers
Richard.

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAMui945Sck2UTwhw8n7Ny0hbzc6CC_Aon8tDsXTBGa8cHzRFsw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CA%2BnPnMx3CsdxOe%3D1O53c%2B25HfVe%3DvJSRq6272%2BXz4RVryFpXRw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAMui9440Rw18_vmatSgj_qA-72iRwxt_3BhQJgM4v3Wu7LTRDw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Bitbucket Branch Source Plugin & Endpoints

stephenconnolly

On 5 October 2017 at 01:52, Richard Bywater <[hidden email]> wrote:
Will do!

Thanks
Richard.

On Thu, 5 Oct 2017 at 21:20 Stephen Connolly <[hidden email]> wrote:
Oversight. Please file a ticket in JIRA

On 4 October 2017 at 20:46, Richard Bywater <[hidden email]> wrote:
Hi

One of my colleagues is trying to get Jenkins 2 up and running with the Bitbucket Branch Source plugin using our Bitbucket Server infrastructure.

We've run into an issue with the plugin as it appears it expects the server URL defined in the Bitbucket endpoint configuration to be the same as the one to be used for cloning purposes even for SSH.

So for instance if you have defined https://bitbucketserver.example.com/bitbucket as the server URL, when cloning via SSH it attempts to use ssh://bitbucketserver.example.com:7999 (where 7999 is correctly read out of the clone link URLs returned by the Bitbucket API). In our case however, the web URL is different to the SSH url. For instance, based on the previous example, our SSH address is ssh://actualservername.example.com:7999/

My question is that, rather than reusing the server URL for cloning operations, is there a reason why the clone URLs returned by the API for a repository aren't used instead? This would seem to allow Bitbucket to tell the plugin exactly where to look in case any other corner cases like this come up.

Cheers
Richard.

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAMui945Sck2UTwhw8n7Ny0hbzc6CC_Aon8tDsXTBGa8cHzRFsw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CA%2BnPnMx3CsdxOe%3D1O53c%2B25HfVe%3DvJSRq6272%2BXz4RVryFpXRw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAMui9440Rw18_vmatSgj_qA-72iRwxt_3BhQJgM4v3Wu7LTRDw%40mail.gmail.com.

For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CA%2BnPnMwN%3DdGZ8Udh3EYXX%2BncV7ventdzEL9jqaS2hrpHp0C7xA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Bitbucket Branch Source Plugin & Endpoints

Richard Bywater-2
Thanks for the pointer - I'll see if I can fit in some time to whip something up.

Richard.

On Thu, 5 Oct 2017 at 21:57 Stephen Connolly <[hidden email]> wrote:

On 5 October 2017 at 01:52, Richard Bywater <[hidden email]> wrote:
Will do!

Thanks
Richard.

On Thu, 5 Oct 2017 at 21:20 Stephen Connolly <[hidden email]> wrote:
Oversight. Please file a ticket in JIRA

On 4 October 2017 at 20:46, Richard Bywater <[hidden email]> wrote:
Hi

One of my colleagues is trying to get Jenkins 2 up and running with the Bitbucket Branch Source plugin using our Bitbucket Server infrastructure.

We've run into an issue with the plugin as it appears it expects the server URL defined in the Bitbucket endpoint configuration to be the same as the one to be used for cloning purposes even for SSH.

So for instance if you have defined https://bitbucketserver.example.com/bitbucket as the server URL, when cloning via SSH it attempts to use ssh://bitbucketserver.example.com:7999 (where 7999 is correctly read out of the clone link URLs returned by the Bitbucket API). In our case however, the web URL is different to the SSH url. For instance, based on the previous example, our SSH address is ssh://actualservername.example.com:7999/

My question is that, rather than reusing the server URL for cloning operations, is there a reason why the clone URLs returned by the API for a repository aren't used instead? This would seem to allow Bitbucket to tell the plugin exactly where to look in case any other corner cases like this come up.

Cheers
Richard.

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAMui945Sck2UTwhw8n7Ny0hbzc6CC_Aon8tDsXTBGa8cHzRFsw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CA%2BnPnMx3CsdxOe%3D1O53c%2B25HfVe%3DvJSRq6272%2BXz4RVryFpXRw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].

For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CA%2BnPnMwN%3DdGZ8Udh3EYXX%2BncV7ventdzEL9jqaS2hrpHp0C7xA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAMui945bUZAWT%2BO2fAjgpGi3XeV%3DfNKsy7jMzshZinhY-uT6Vg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.