Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

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

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

 

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
Community showcase
Published in Bitbucket Pipelines

Bitbucket Pipelines Runners is now in open beta

We are excited to announce the open beta program for self-hosted runners. Bitbucket Pipelines Runners is available to everyone. Please try it and let us know your feedback. If you have any issue...

502 views 10 8
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