Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Bitbucket Pipelines doesn't allow custom names for Deployments?


I have a bitbucket-pipelines.yml file that is throwing an error message in VS Code 'Value is not accepted. Valid values: "test", "staging", "production":

image: mydockerhub/myimage
- step:
name: Echo
- echo 'First step in default'
- step:
name: Deploy to ci1 sandbox
deployment: ci1-sandbox
trigger: manual

 I've created an environment called ci1-sandbox. Shouldn't this config file's "deployment" line reference that environment?


The example in the documentation at this link shows a sample pipelines config file that contains deployments with names other than 'test', 'staging' or 'production':



1 answer

0 votes
mkleint Atlassian Team Aug 12, 2019

please check the first paragraph of the documentation link. If you want to use custom names in the bitbucket-pipelines.yml file, you first need to define these values in the Bitbucket settings.  Under Settings / Pipelines/ Environments.

I've defined the values in the Bitbucket settings (there are environments existing in the settings that match the deployment names used in my configuration file) but still get an error highlight with message in VSCode:

error message.JPG

The error does not prevent the plans from running successfully, but it would be great to have the error highlighting removed for custom deployment names.


mkleint Atlassian Team Aug 13, 2019

I see. I could be an issue with VS Code plugin I assume. When I edit inline in bitbucket I get this error when entering a wrong deployment name:

Screen Shot 2019-08-14 at 9.09.26 am.png

I have the same issue with the vscode extension. It doesn't seem to pull down the deployment names from the repo my project is connected to. It's just using the default names of the deployments when you first enable pipelines.


I would recommend either removing the deployment name check or fixing it so it pulls the configured deployment names.


Disabling the Jira and Bitbucket extension prevents the deployment names from showing as an error, but then I lose the Jira Issue and Pipeline explorer.


Can you please fix this?

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Jira

Admins, notify your Jira instance of system-wide changes with the new admin announcement banner

Hi All! We’re excited to share the launch of an announcement banner that lets Jira site administrators communicate directly to their users across their  Jira Cloud instance.  ...

549 views 15 18
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you