Some builds don't show up on dependencies list

Answered

Hi

I have two jobs, one for building assemblies, and one for building installers that use the assemblies built by the first job. We use Git and feature branches and normally, when we build the installers, we simply pick the master assemblies. Sometimes I have to override this default behavior, at which point I use the custom run build dialog, select the specific assemblies I want from the dependencies dropdown, and run the build.

I encountered two related issues in this dropdown:
1. It is very short. Since we are using feature branches, the assemblies I want to pick are often not shown because other developers committed changes to their feature branches. The list has no edit capabilities so I cannot pick a specific build number or branch.
2. It looks like the list omits builds with no changes. I discovered this when trying to deal with issue #1. I manually triggered a build for a feature branch so I can pick its assemblies from the list, but they never showed up. I had to commit a dummy change, just so an auto-build would be triggered for this branch, at which point the assemblies showed up in the dependencies dialog. Maybe the dependencies list is only updated for triggered builds?

I might be missing a setting somewhere, but I could not find a way to change the dependencies list behavior. If there is one, I would like to know where it is.If not, is it possible to fix one of these issues, so I can avoid using dummy commits?

Thank you

Rami

7 comments
Comment actions Permalink

Hi Rami,

1. To increase the number of builds loaded in the dropdown of the custom run build dialog please use internal property teamcity.runCustomBuild.buildsLimit=100 (see the section).
2. All finished builds should be listed in the dropdown. Please try to increase the number of loaded builds (as noted above) and check wether the build with no changes appeares.

0
Comment actions Permalink

Alina,

Thank you for the reply. I will adjust the internal property to increase the number of builds showing in the list.
As for #2, you are correct. It looks like the list is semi-sorted so some builds are pushed down.

Rami

0
Comment actions Permalink

Sorry to try to resurrect an old thread here, but this is the only post I've found that seems relevant to the issue I am seeing locally. I've tried the same troubleshooting steps you suggest, but am still left with no dependencies available for a particular build that was a rebuild of a previous dependency with slightly different arguments.

 

We have somewhat complex build hierarchy set up that basically utilizes two starter jobs to set some variables in configuration files that are persisted into the build's artifacts. We do this so that we can later target these same artifacts and rebuild sub-configurations to target similar environments / settings but with different code built.

What we see is that when we try to re-run the build directly from the previous run (the run that had a no-change rebuild) we can see the dependencies as expected. But when we go to a specific change in the change log and choose to rebuild using that commit, we are unable to see the dependencies of builds that were run with no actual changes from the VCS Root. 

This is quite hindering as we are controlling some things outside of VCS specifically to enable extended functionality within Infrastructure as Code systems and credential storage tools.

 

If it is meant to act as you state, to always show ALL built dependencies, then this sounds like a bug.

0
Comment actions Permalink

The list should always show the built dependencies, but there is a number of conditions and filters that can be applied to it. We have gone through several reworks of this dialog recently and are planning some extra changes going forward, so also knowing which version you are in is relevant.

 

If you have a complex setup where you set custom variables, we would need the details of said setup and how exactly you attempt the triggers to try to check where this can go wrong. 

0
Comment actions Permalink

Sorry, thought I had shared the version. WE're on 2018.2.1 currently (upgrading this weekend to 2020.1)

We're not using the parameterization to control which dependencies are available to a particular build. We're using the same snapshot and artifact dependencies across the whole project space. 

 

The credential management and infrastructure as code systems are populating variable values to then be used by build scripts directly, generally they are not impacted by the lack of available dependencies. 

Are you suggesting that using a plugin to do rest-ful population of parameters could cause dependncies to not be visible in the build dialog?

0
Comment actions Permalink

Sorry for the delay, your first response was so quick that I missed its notification

 

Is the issue still going on on 2020.1.x? If it's the case, I'd like to ask you to either open a new thread or send us a request via the Submit a request button on top of the page if you need to send private data. Then detail a step by step guide to replicate the issue, since I'm afraid that your description did not really give me enough information to know exactly which steps you take and what is missing and what is present.

 

Using a plugin to do a rest-ful population of parameters can do a lot of modifications in behavior, including dependencies not be listed, but it does not have to be the case. Again, since I'm not sure how you are doing most of the actions you described, I cannot confirm whether it's the case or not. We would need to dive into the details to be able to troubleshoot it.

0

Please sign in to leave a comment.