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

Next challenges

Recent achievements

  • Global
  • Personal


  • Give kudos
  • Received
  • Given


  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

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

Extra artifacts

I'm building some unsigned RPM files in my first Stage- Job-Task and that completes and the artifacts are properly defined and collected by the task. Then my plan goes on to the next stage were the RPMs from the previous stage are signed. I have my unsigned RPMs defined as dependent artifacts that are link to the signing job. The thing is, when my signing job completes, it has signed all of the RPMs from this and every previous successful RPM build (that first stage) and not just the RPMs that were created from the previous stage. Any reason why this is happening?


Bamboo version: 5.9.4 

4 answers

1 accepted

0 votes
Answer accepted

I think found my issue. It seems that having linked artifact dependencies was dumping all(current and previous builds) of the artifacts into the ${} directory at the start of the job. If delete everything and then explicitly define an artifact download task, I get just the artifacts that are associated to the current build. 

0 votes

It looks like you need to cleanup working dir of your build before start. Add simple script to cleanup work folder before start of first job

@Alexey Chystoprudov Already added that. Didn't help. I'm flabbergasted on where these files are coming form. 

Can you add a Script task with ls command before running your scripts. Just to confirm folder is empty.

Then look at artifact definition maybe it's too wide and looks at bamboo home folders (might be the case if you use local agent for all your jobs)

I think @Alexey Chystoprudov may be right but I would suggest doing a force clean build in checkout repository task instead of script


Also can you share some more info on signing stage as to how you are doing it? If you're doing it in right directory and if you are using any wildcard characters.

Suggest an answer

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

Bamboo 7.1 is here and is packed with value!

I'm happy to announce that Bamboo 7.1 has been released and it’s overflowing with awesome new features. Top-voted issues First and foremost, a bunch of JAC top voted issues has been delivered - y...

703 views 1 6
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