Only ask for credentials when they're not set

[erickwilder]

I've set up this plugin and added both BITBUCKET_USER and BITBUCKET_PASSWORD as environment variables but every time I run semantic-release the plugin asks for credentials.

export BITBUCKET_USER=xxxx
export BITBUCKET_PASSWORD=zzzzz

npx semantic-release

Username for 'https://bitbucket.org':

Expected result:

Respect whatever values are defined by the environment variables and don't ask for credentials at all.

[cmurczek-it]

Hi @erickwilder, are you using the hosted offering or an on-prem server?
Also is your repo setup as a team repo? If the latter is the case, you need to set the teamName when configuring the plugin for releasing to BitBucket. There's on more thing with that scenario, though. Since the repo is not owned by you in that case, but by the team account, you'd also need to provide the team account's password, which is why you should think of setting up an app password. You can find an example config as well as the link to Atlassians docs regarding app passwords in the Config section of the readme.
If you still have problems, please provide more info, e.g. when is sematic-release-bitbucket asking for credentials? Try running semantic-release with the --debug switch and post the log here. It should contain some pointers to find out what's happening.

[erickwilder]

Hello Christoph. Thank you for your reply. The issue wasn't about authentication, but about recognizing the environment variables. I'm already using app passwords and set `teamName` following the documentation. Nevertheless I gave up on using this plugin and switched to `@semantic-release/git` as it already cover the same use cases as I wanted.

…

On Sat, Sep 15, 2018, 9:55 PM Christoph Murczek ***@***.***> wrote: Hi @erickwilder <https://github.com/erickwilder>, are you using the hosted offering or an on-prem server? Also is your repo setup as a team repo? If the latter is the case, you need to set the teamName when configuring the plugin for releasing to BitBucket. There's on more thing with that scenario, though. Since the repo is not owned by you in that case, but by the team account, you'd also need to provide the team account's password, which is why you should think of setting up an app password. You can find an example config as well as the link to Atlassians docs regarding app passwords in the Config section of the readme <https://github.com/iteratec/semantic-release-bitbucket#configuration>. If you still have problems, please provide more info, e.g. when is sematic-release-bitbucket asking for credentials? Try running semantic-release with the --debug switch and post the log here. It should contain some pointers to find out what's happening. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#3 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAlEHuDJfw2pJf4x4mCDmw4gB2SaaBY2ks5ubVsegaJpZM4Whd9f> .