Paul Molodowitch

Created February 01, 2023 20:01

The behavior I want is if TriggerA is run due to merge-requests/57 in from vcsRootA, I want: RealWork Build ConfigvcsRootA set to merge-requests/57vcsRootB set to <default>

1. Community
2. TeamCity General Topics
3. Multiple VCS roots: how to trigger against Merge/Pull Requests on EITHER root?

• 0 votes

Created February 01, 2023 19:56

My setup already has multiple triggering build configurations, one for each repo:                                        _______________________________________                                     ...

1. Community
2. TeamCity General Topics
3. Multiple VCS roots: how to trigger against Merge/Pull Requests on EITHER root?

• 0 votes

Created January 31, 2023 14:00

Hi - noticed this post is still pending approval.  Is there a problem I can address? I wanted to reference this description of the issue in another place, but I can't link to it until it's been app...

1. Community
2. TeamCity General Topics
3. Multiple VCS roots: how to trigger against Merge/Pull Requests on EITHER root?

• 0 votes

Created November 30, 2022 10:17

Both jobs need the content in both directories. Also, using separate checkout rules wouldn't give the desired behavior, where if files are changed in both directories, then only jobA runs.

1. Community
2. TeamCity General Topics
3. VCS Trigger - ensure NOT triggered if certain files changed

• 0 votes

Created November 08, 2022 00:37

The commit I'm querying about is definitely known by TeamCity, as it did, in fact, launch a build for it.  And the commit was only a few days old (but the particular build config is VERY active at ...

1. Community
2. TeamCity General Topics
3. How do I find if a specific build config has been run on a specific revision?

• 0 votes

Created October 26, 2022 19:31

Thanks for the response! Unfortunately, I tried this and it didn't work - I got 0 results:   And I know there actually is a job, because I copied the revision from it's build page:

1. Community
2. TeamCity General Topics
3. How do I find if a specific build config has been run on a specific revision?

• 0 votes

Created October 05, 2022 17:30

Found this related feature request:https://youtrack.jetbrains.com/issue/TW-67952/Versioned-settings-expose-latest-successfully-applied-commit-hash-via-Rest-API  

1. Community
2. TeamCity General Topics
3. How to find current versioned-settings commit/hash for a project, via REST API?

• 0 votes

Created October 05, 2022 00:07

I've been able to get what I need by web-scraping https://teamcity.nvidia.com/versionedSettingsStatus.html?projectId={projectId}&__fragmentId=versionedSettingsStatusInner ...but it's not pretty - j...

1. Community
2. TeamCity General Topics
3. How to find current versioned-settings commit/hash for a project, via REST API?

• 0 votes

Created March 17, 2022 13:41

As a workaround, I found that you can use an anonymous object declaration as a namespace: import jetbrains.buildServer.configs.kotlin.v2019_2.*version = "2021.2"object Constants { val MY_CONST ...

1. Community
2. TeamCity General Topics
3. Kotlin DSL - defining a constant that can be used inside init functions

• 1 vote

Created December 20, 2021 13:27

Actually - I think I may have found a workaround. By disabling versioned settings, then re-enabling (using the same VCS root and other settings as previously), you can then re-import "fresh".

1. Community
2. TeamCity General Topics
3. Rebasing when using versioned settings

• 2 votes