Skip to content
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

What about bitbucket server? #2

Open
MartinMuzatko opened this issue Sep 3, 2018 · 3 comments
Open

What about bitbucket server? #2

MartinMuzatko opened this issue Sep 3, 2018 · 3 comments

Comments

@MartinMuzatko
Copy link

Bitbucket server does not support rest api 2.0 - is there an alternative?
I'm looking into @semantic-releas/exec as an alternative

@cmurczek-it
Copy link
Member

Hi @MartinMuzatko, in the project I created this plugin for we were using the hosted offering. I used the Atlassian docs to provide the alternative for an on-prem server hoping for the best since we did/do not have an on prem bitbucket server… According to the docs the plugin should be able to connect to a private bitbucket server. Can you post the output of running semantic-release with the --debug option?

@ryoung999
Copy link

Hi @cmurczek. I pulled this plugin and used it successfully for enterprise bitbucket server. I needed to edit two lines:
verifyConditions
and
publish
The construction of the URL for private Bitbucket servers is different from the hosted offering. It is possible that is not well documented.

`${bitbucketUrl}repositories/${owner}/${publishConfig.repositoryName}` #HOSTED URL
`${bitbucketUrl}${owner}/repos/${bitbucketPlugnConfig.repositoryName}` #PRIVATE URL

I suppose the fix is to detect HOSTED or PRIVATE and use the URL appropriate for the case. I am not a nodejs dev, but I can try to put together a fix if you like.

Rodney

@ryoung999
Copy link

@cmurczek I forked your repo and fixed the enterprise server urls. It is published here:
https://www.npmjs.com/package/@ryoung999/semantic-release-bitbucket
If you would like, pull the fixes to your repo and publish an update...I will remove my own fork.

Love the plugin...thank you for the work!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants