Artifact paths update not detected after Load settings from VCS

Answered

Hi, we have a setup with common Kotlin library (dependency via pom.xml) + a project with versioned Kotlin settings

The library contains a BuildType descendant with a dependency and artifact path. The project then instantiates the class, providing some specific values needed

I made a change to the artifact path target and used Load settings from VCS in the project -> artifact path update WAS successfully reflected _in UI_

However new builds (on various agents) still used the old path

After making a random commit (removed an empty line from settings.kts) it started to work

I think at least some changes do not require an explicit commit and Load settings is enough for the change to take effect ... can this be something particular? Or a bug?

0
2 comments

It seems there's the same issue for Parameters, I've overriden env variable and I can see the new value in Edit settings AND in Run dialog but the actually build will get passed old values

0

Hi Jiří. Did you make the initial change through a commit to your Versioned Settings repository? Please see the commit has and compare it with what TeamCity checked out when it ran the build. Look for "Compute revision for 'your-versioned-settings-VCS-Root'" in the build log. Did TeamCity check out an earlier revision? Was it checked out from the right branch?

0

Please sign in to leave a comment.