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,456,701
Community Members
 
Community Events
176
Community Groups

Schdeuler Trigger Daily and lastest Artifact Deployment

Edited

Hi Team, 

 

I set up daily Triggered to run a scan job but its not taking latest Artifacts present and when deploy job is running taking 

'${bamboo.inject.FixVersion}.${bamboo.inject.BuildDay}.${bamboo.inject.BuildTime}_(19)

 

 How can i set in Scheduled trigger last release created ?

 I am using Bamboo Specs to create Pipelines. So observed if the last plan run is spec Update in that case scheduled job fails as it's not able to find the artifacts. But if last build before scheduled job ran is actual plan build it works fine. 

So if i create bamboo pipeline without spec scheduled job works fine but if create through specs and there is update in specs it fails. 

How can i handle this scenario ? 

1 answer

1 accepted

0 votes
Answer accepted

Hi @RajVerma7099

I'm not really sure if I understand your request. Could you give us more details on what configuration you have (plan/deployment) and what is the issue?

Is your trigger in the build plan or in the deployment one?

What is this variable standing for?

${bamboo.inject.FixVersion}.${bamboo.inject.BuildDay}.${bamboo.inject.BuildTime}_(19)

Okay some more details - I am using Bamboo Specs to create Pipelines. So observed if the last plan run is spec Update in that case scheduled job fails as it's not able to find the artifacts. But if last build before scheduled job ran is actual plan build it works fine. 

So if i create bamboo pipeline without spec scheduled job works fine but if create through specs and there is update in specs it fails. 

How can i handle this scenario ? 

Hi @RajVerma7099 
Can you share the Bamboo version so I can run a test to check if this is a bug?

Using 6.8.0 Version 

@Daniel Santos  - Please let me know your observation?

Hi @RajVerma7099

Sorry for the delay. I still have to run some tests, but I think you are affected by this bug: https://jira.atlassian.com/browse/BAM-19770. As soon as I have them run I'll share my findings here.

Hi @RajVerma7099

I was able to reproduce the issue both in Bamboo 6.8.0 and 6.8.1. I've opened a new bug to report this thanks to you:

Unfortunately, the only workaround I can possibly think is to set a scheduled trigger for your build to run a few munites before the deployment is triggered. This should drastically reduce the chances of a specs update to happen as the latest result.

We will now need to wait for our development team to fix that bug so this issue can be avoided. In case you want to know, this is our Server Bug Fix Policy and thank you for bringing it to our attention.

thanks Daniel !

Like Daniel Santos likes this

Hi @RajVerma7099

If you think this answer can help others, please click this helped me at the top of it.

See you in the next thread!

Other wise go stuck our thumb!

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events