Create
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Products
See all
Community resources
Interests
See all
Community resources
Top groups
Explore all groups
Community resources
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Join now to unlock these features and more

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Get started Tell me more
Atlassian Community about banner
4,466,775
Community Members
 
Community Events
176
Community Groups

npm-client-login no longer working in BB pipelines

Max Elston
Max Elston Dec 21, 2021

I am trying to publish a package to NPM in BB pipelines. Everything was working fine however now it is failing due to 2FA errors. I have no 2FA set in NPM.

I am using npm-client-login to login in my bitbucket-pipelines.yml

Answer
Watch
Like Be the first to like this
142 views

1 answer

0 votes
Theodora Boudale
Theodora Boudale Atlassian Team Dec 27, 2021

Hi @Max Elston,

1. Just to confirm, are you using the following package?

https://www.npmjs.com/package/npm-cli-login

2. If so, is it the npm-cli-login command that is failing in your Pipelines build? If so, what is the output of the command? (Please make sure to sanitize any private/sensitive data from the output prior to sharing, if any)

3. Are you able to reproduce this error if you debug this locally with Docker, following the steps in the documentation below?

This is for testing purposes, to understand if the issue seems to be specific to Pipelines or not.

Kind regards,
Theodora

Reply

Suggest an answer

Log in or Sign up to answer
Bitbucket
Bitbucket
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
TAGS

Atlassian Community Events

See all events