Jiri Petruzelka

Created July 24, 2020 08:14

Hi, we are currently using (a) + introducing common features using a shared maven dependency (in pom.xml), TeamCity downloads this dependency from provided location during configuration recompilati...

1. Community
2. TeamCity General Topics
3. Good Real World examples of Kotlin DSL

• 0 votes

Created June 25, 2020 12:05

Looks like it works, thank you!

1. Community
2. TeamCity General Topics
3. Rest API find projects by VCS settings root

• 0 votes

Created June 24, 2020 11:52

So an imperfect solution is to use snapshot and keep the same version + use the workaround above to force updates

1. Community
2. TeamCity General Topics
3. [SOLVED] Pom.xml dependency version

• 0 votes

Created June 23, 2020 11:34

Looks like there is a ticket https://youtrack.jetbrains.com/issue/TW-58754?_ga=2.9353973.1970866111.1592910988-1236548174.1551875989 and there is a workaround so it possibly can even be automated

1. Community
2. TeamCity General Topics
3. [SOLVED] Pom.xml dependency version

• 0 votes

Edited June 23, 2020 11:19

Now that I think about it ... if we achieve that we don't need to update all consumers whenever the dependency changes, now TeamCity will not fetch new changes if the base changes until a new build...

1. Community
2. TeamCity General Topics
3. [SOLVED] Pom.xml dependency version

• 0 votes

Created June 19, 2020 12:29

So this setup actually seems to work class SomeBuildTemplate constructor(    suppliedDependencies: Dependencies) : BuildType({    dependencies.apply {        items.addAll(suppliedDependencies.items...

1. Community
2. TeamCity General Topics
3. [SOLVED] Kotlin how to fill Dependencies object

• 0 votes

Edited June 19, 2020 12:05

Looks like it might work with Dependencies().apply {    snapshot(SomeOtherBuild) {}} Edit: looks like TC does not fail on this, but does not actually add the dependency either...

1. Community
2. TeamCity General Topics
3. [SOLVED] Kotlin how to fill Dependencies object

• 0 votes

Created June 19, 2020 07:41

Will give it a try, thank you!

1. Community
2. TeamCity General Topics
3. Password in Kotlin outside VCS settings

• 0 votes

Created June 18, 2020 14:37

Thank you for reply   All triggers are on B. A triggers via Snapshot dependency. Yes, it's via VCS changes, those particular files were included in folders visible to B, but excluded by Checkout ru...

1. Community
2. TeamCity General Topics
3. Enforce revisions synchronization + Checkout rules problems with revisions used (v2020.1)

• 0 votes