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,463,408
Community Members
 
Community Events
176
Community Groups

Error in your pipeline. Step is empty, null or missing

 

I have the following error when running my pipeline: 

Configuration error

There is an error in your bitbucket-pipelines.yml at [pipelines > branches > develop > 1]. To be precise: Step is empty, null, or missing.

 

Another user reported a similar issue earlier. The answer given there does not work for me as the issue was with indentation. My file does not have that error.

Here's my file: 

definitions:
steps:
- step: &deployToECS
name: Deploy to ECS
services:
- docker
script: # Modify the commands below to build your repository.
- pipe: atlassian/aws-ecs-deploy:1.0.4
variables:
AWS_ACCESS_KEY_ID: $AWS_ACCESS_KEY_ID
AWS_SECRET_ACCESS_KEY: $AWS_SECRET_ACCESS_KEY
AWS_DEFAULT_REGION: $AWS_REGION
CLUSTER_NAME: '$ECS_CLUSTER_NAME'
SERVICE_NAME: '$ECS_SERVICE_NAME'
TASK_DEFINITION: '$ECS_TASK_DEFINITION_FILE'
DEBUG: 'true'
pipelines:
branches:
develop:
- step:
<<: *deployToECS
deployment: development

 PS: The question editor here removes spacing when I paste my file contents so indentation might not be correct here.

 

However, the pipeline works if I change the step to reuse the anchor inline:

pipelines:
branches:
develop:
- step: *deployToECS
deployment: development

This "works" but I can not override variables with the deployment specific variables in this case. 

Any suggestions would be helpful.

2 answers

Same issue here. When using overrides the pipeline reports "Step is empty, null or missing"

@warmannj Solved it. It was a matter of indentation indeed.

Notice the extra indent inside - step:

pipelines:
branches:
develop:
- step:
<<: *deployToECS
deployment: development

 

Like Simone Scardoni likes this

I have the same problem anyone find a way to do this?  i have tried the <<: *deployToECS way it validates but then when pipelines build says its invalid...

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events