Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
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

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.

Atlassian Community about banner
4,640,976
Community Members
 
Community Events
196
Community Groups

Bitbucket Pipline Visual Studio Code publish

Hello, 

 

I'm trying to configure my Pipline to automatically publish my Visual Studio Extension to Marketplace. Right now my bitbucket-pipelines.yml looks line this

 

image: node:16

pipelines:
  branches:
     master:
       - step:
           name: Setup VSCE
           script:
              - npm install -g vsce@latest
       - step:
          name: Install dependencies
          script:
            - npm install
        - step:
            name: Publish to Marketplace
            script:
               - vsce publish -p $TOKEN

But it failed because it 
don't see vsce on last step. Could someone help and direct me?
Thanks!
Best regards,
Alex

1 answer

0 votes
Syahrul
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Sep 30, 2022

 

Hey @alexander_danchenko 

Welcome to the community.

Can you share with me what is the error message you see on the last steps?

If you are getting commands not found error then the issue is most likely because your command VSCE is running on different steps then the one you install.

Each step in your pipeline runs a separate Docker container. So if you have the first steps installing VSCE you won't be able to use it on the next steps because it uses separate container.

You need to install VSCE in the same steps as example below:

      - step:
          name: 'Setup VSCE'
          script:
            - npm install -g vsce@latest
            - vsce publish

Cheers,
Syahrul

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
TAGS
AUG Leaders

Atlassian Community Events