nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

plan build is not using the wrong artifact download.

Fred Kendall_tpd5bl

I have a plan build sequence. B and C have a dependency on Plan A.

Plan B and C should be using the last artifact set from A, but it is using 37 and not the fresh 38.

The plans are in sequence. B should not start until A is complete. The fresh Artifacts from A are not available yet, thus Plan B is using the previous set of artifacts.

This makes all of my sequential builds useless. B and C should be using the fresh new A artifacts, not the older previous set.

Bamboo Server is 6.5 build 60509

Accepted answers

Fred Kendall_tpd5bl

We may try to process a first build as the first dependency, followed by a insignificant (not having dependencies) plan between each of the subsequent builds with dependencies. This will allow us to kick off a set of builds in the evening a check them in the morning.

All comments

Eduardo Alvarenga

Hello @Fred Kendall

Thank you for reaching out!

Were you able to reproduce that behaviour on a recent Bamboo release such as 7, 8 or 9? Bamboo 6.5 has set as end-of-life years ago and is not supported anymore.

Regarding your Plan, are you using Build dependencies? Depending on how your dependent plans require the artifacts you may have to explore some Dependencies Block strategies (probably not available on Bamboo 6.5)

Thank you,

Eduardo Alvarenga
Atlassian Support APAC

--please don't forget to Accept the answer if the reply is helpful--

Fred Kendall_tpd5bl

We are a DoD facility and are not able to get updates safely. We are using version 6.5. I've checked the Dependencies Block strategies and I don't see how this would help us. We have the individual plan builds being executed in the correct sequence on a single agent. The agent will only process one plan at a time. I've gone back and checked previous sequential build and I see the same problem behavior.

We do not see the problem is we process each plan build individually and allow about 15 minutes between builds. It seems that the artifacts directories and not identified as available/existing until after the next sequenced plan is initiated automatically.

I tried to place a unique short 4 minute plan build between the dependency builds and still saw the problem. I tried the Clean working directory task at the top of each plan build to allow a break between the actual requirement for the dependent predecessor and the successor. This did not work.

The incident that bit me in the ass was a two week old dependency was used in a new build. Developers indicated that they had resolved the issue and that I must have use the incorrect dependencies. I'm informed them that I was not a idiot and that I would not let that happen. Well, I had too eat my hat. The Bamboo Artifacts had indeed been outdated.

Can you assure me that this is not an issues in updated versions of Bamboo? I can make an attempt for an upgrade.

Eduardo Alvarenga

Hello @Fred Kendall

It seems there is something going on in the way you are triggering the builds. Can you describe your internal queuing process and how you actually trigger the Plans in sequence?

As the dependent plans are downloading previous artifacts. It may be the case of the second build and onwards are getting triggered whilst the first plan is still running. The artifact list will only get updated once the Plan run is finished, not during it.

The dependent plans will build the artifact list when triggered, so if there still are no new artifacts present, it will consider the last one available.

When you use build dependencies, Bamboo will guarantee that the dependent Plans will be triggered only when the initial Plan is completed.

So, we need to understand in detail how your Plan trigger and dependencies process work in case you are using any non-standard/outside approach.

There is a fixed bug that may be related to your issue, so it would be important to validate if a newer release will solve the issue.

https://jira.atlassian.com/browse/BAM-19985

Best regards,

Eduardo Alvarenga
Atlassian Support APAC

--please don't forget to Accept the answer if the reply is helpful--

Fred Kendall_tpd5bl

I take 10 minutes to queue up the jobs on a single agent. The agent will only one plan build at at time. We are using this thread to control the single series process flow. It seems that the Artifacts are assigned at the time the plan is put in the queue. Not taking an effort to check on the newest (fresh) artifact.

The first dependency takes about 45 minutes to pull the source code and process the build. It was assumed that the next build in the sequence would find the new artifact and use it. This is not the case. I'm assuming that the plans are triggered after the previous build is completed and the agent can trigger the next, next, next....

Do you have another way to automate the triggering of each build. The single agent method is not working for us.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

server

bamboo