timer-triggered pipeline not using latest dependency

[Aquil...@gmx.de]

Hi everyone, 

I'm struggling a bit with understanding the fan-in especially when using timer-triggered pipelines. I hope that you can help me either to understand or even to solve the following issue.

There are 4 dependent pipelines as shown below, which are all timer-triggered:

• ui_full is triggered at 5pm
• plugins and core are triggered at 6pm
• apps is triggered at 7pm

The timeslots are huge enough to ensure that the previous build has been finished before the next dependent pipeline is started. The subversion materials are usually subfolders of three different subversion repositories (marked by color).

Unfortunately, the apps pipeline consumes the very same version of the plugins (e.g. 159) for every run, until the artifacts have been garbage collected by GoCD and the pipeline fails. Then I have to trigger the apps pipeline manually once, so that it uses the latest and greatest plugins (e.g. 189). 

Why doesn't the apps pipeline use the latest run of the plugins pipeline anyways, while this is working for e.g. the core pipeline. How can I force it to use the latest one? Why does it work when triggered manually, but not when using the timer?

There are no check-ins or manual triggers in between which would mess this up. Any hint is appreciated.

Regards,

Julia

Timer triggered:

Manually triggered:

[Jason Smyth]

Hi Julia,

The only thing I can think of that might cause an issue from what I can see in the Value Stream Maps that you posted is that the "ui_full" and "plugins" Pipelines seem to share a particular SVN source (coloured purple in the second photo). Are you sure that ui_full v2403 and plugins v189 both triggered using the same version of that Material?

Have you checked the logs on the GoCD server to see if there are any messages there relating to how the "apps" Pipeline is choosing the version of the plugins Pipeline to use?

I don't have any brilliant insights as to what the issue is at this point but hopefully this helps a little.

Regards,

Jason

[Aquil...@gmx.de]

Hi Jason, 

thanks for the response. So this purple materials is actually the same subfolder of the same repository which has the same revision for two years now. Nevertheless, since this is something that I don't need any longer I removed the dependency and will check if things are getting better now.

I also just checked the log files for the failed run, but there are no dedicated messages which dependency is used in which version or how the fan-in is processed. I can see that the timer is triggering the pipeline and that it is assigned correctly to an agent with the required resources. Afterwards, the agent is reporting that the pipeline status is "failed". That's all.

Regards,

Julia

[Aquil...@gmx.de]

Hello again, 

though the dependency on the same subversion material (subfolder) does no longer exist, an "old" version of the plugins are consumed. Any more ideas from someone?

Regards,

Julia