Inedo Community Forums Forums
    • Recent
    • Tags
    • Popular
    • Login

    Welcome to the Inedo Forums! Check out the Forums Guide for help getting started.

    If you are experiencing any issues with the forum software, please visit the Contact Form on our website and let us know!

    BuildMaster fails to return TeamCity build configs

    Scheduled Pinned Locked Moved Support
    10 Posts 4 Posters 36 Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • K Offline
      kquinn_2909
      last edited by

      We're attempting to setup Buildmaster to have it serve as a deployment and test arm of our builds based on build artifacts.
      The connection to TC seems to work. We do get the list of projects from the server.
      a451b640-0be8-4fc5-a075-c0734d8232f2-image.png
      BM also says that TC has been synchronized.
      99e13f1e-d50d-41ec-895c-caa46724c254-image.png
      But when we go to import builds so we can see the artifacts, the dropdown never populates.
      a01f93d6-871d-49a5-8064-238e0390a6d5-image.png
      What API calls are you using that is supposed to return that info?
      TeamCity version is TeamCity Professional 2025.11 Build 207946
      and BuildMaster is version Version 2025.5 (Build 14).

      We're kind of at a standstill until we can get the artifacts list.

      atrippA 1 Reply Last reply Reply Quote 0
      • atrippA Offline
        atripp inedo-engineer @kquinn_2909
        last edited by

        Hi @kquinn_2909 ,

        The "Recent TeamCity Builds" page should show a list of builds in the selected TeamCity project; it's a bit tricky to troubleshoot, but BuildMaster is essentially querying for builds using this locator string: defaultFilter:false,project:{Uri.EscapeDataString(project)}&fields=build(id,number,status,state,webUrl,startDate,buildTypeId)

        Might be easier to see in the source code:
        https://github.com/Inedo/inedox-teamcity/blob/master/TeamCity/InedoExtension/TeamCityClient.cs#L63

        I believe the Project ID is being used, which in your case would be WebProjects_Replicator. I think the name would be "WebProjects Replicator". Though I'm not totally sure.

        What builds do you see on the TeamCity side of things?

        Thanks,
        Alana

        K 2 Replies Last reply Reply Quote 0
        • K Offline
          kquinn_2909 @atripp
          last edited by

          @atripp Thanks for the reply. Let me try a few things and get back to you.

          1 Reply Last reply Reply Quote 0
          • K Offline
            kquinn_2909 @atripp
            last edited by

            @atripp OK.
            Using the url - /app/rest/builds?locator=defaultFilter:false,project:WebProjects_Replicator&fields=build(id,number,status,state,webUrl,startDate,buildTypeId)

            I get this when calling the API:
            9489ce46-afd2-4156-9b79-f4269c951477-image.png
            and this when looking at the TC UI:
            f392fc1e-9e4a-417a-b800-2887f911d35e-image.png
            So, that lines up.
            Not quite sure why I dont get a build list in BuildMaster.

            stevedennisS 1 Reply Last reply Reply Quote 0
            • stevedennisS Offline
              stevedennis inedo-engineer @kquinn_2909
              last edited by

              Hi @kquinn_2909 ,

              We haven't forgotten about this; the issue is trying to figure out steps to reproduce it based on the information we have... considering it works on our test instance and all. We may consider putting some more debugging code in, though figuring out how to expose that in this context is a little challenging.

              Just as a sanity check though, do you have a project that doesn't have a "space" in the name? I want to make sure this isn't something really simple as WebProjects%20Replicator vs WebProjects_Replicator.

              The other idea is authentication/authorization, though I would imagine you would get an error accessing the project instead of no builds.

              Thanks,
              Steve

              1 Reply Last reply Reply Quote 0
              • K Offline
                kquinn_2909
                last edited by

                @stevedennis no worries.
                We have most of our builds in sub-projects.
                In this case, 'WebProjects' is a top-level project and 'Replicator' is a sub-project of that. In that sub-project, we could have any number of different build configs.
                I moved the WebProjects_Replicator project to the root level and renamed it to just 'Replicator'. I then recreated the TC connection and attempted to import builds. I get the same result. The CI Build dropdown does not populate.
                I even removed an other build config in that project so it ends up being 1 top-level project with 1 build config in it. No dice.

                As for credentials, if they were wrong, the connection would probably show me Error instead of Synced
                2729b583-65c1-49ff-8f45-7eb2fb306107-image.png

                1 Reply Last reply Reply Quote 0
                • rhessingerR Offline
                  rhessinger inedo-engineer
                  last edited by

                  Hi @kquinn_2909,

                  I'm working to recreate this issue, but I'm struggling to recreate it. Would you be able to send us the results of the following API?

                  app/rest/projects/WebProjects_Replicator?fields=buildTypes(buildType)
                  

                  The thought I currently have is that the Build Type list is returning something different that is filtering out those builds (https://github.com/Inedo/inedox-teamcity/blob/7d447a5f4f3c3e38c98012c65e9db40afec224b6/TeamCity/InedoExtension/TeamCityClient.cs#L84)

                  Thanks,
                  Rich

                  Products Engineer, Inedo

                  K 1 Reply Last reply Reply Quote 0
                  • K Offline
                    kquinn_2909 @rhessinger
                    last edited by kquinn_2909

                    @rhessinger. Hi. Here's the result:

                    <project>
                       <buildTypes>
                          <buildType id="WebProjectsReplicatorBuildOnChange" name="BuildOnChange" description="Now Building 22.1" projectName="Web Projects / Replicator" projectId="Replicator" href="/app/rest/buildTypes/id:WebProjectsReplicatorBuildOnChange" webUrl="http://10.0.14.200:8111/buildConfiguration/WebProjectsReplicatorBuildOnChange?mode=builds"/>
                       </buildTypes>
                    </project>
                    
                    1 Reply Last reply Reply Quote 0
                    • rhessingerR Offline
                      rhessinger inedo-engineer
                      last edited by

                      Hi @kquinn_2909

                      That is why you are not seeing the builds. That build types API is returning the Id as WebProjectsReplicatorBuildOnChange, where the builds API is returning WebProjects_Replicator_BuildOnChange as the Id. Are you using any sort of shared build type?

                      Thanks,
                      Rich

                      Products Engineer, Inedo

                      K 1 Reply Last reply Reply Quote 0
                      • K Offline
                        kquinn_2909 @rhessinger
                        last edited by

                        @rhessinger While that kind of makes sense, I dont think that is the issue.
                        In the past, I've imported projects from production TC servers to the test server. Thinking this may have been part of the problem, I instead created a brand new project on the test server called "WebProjects_SessionManagement". After creating the project, I created the build config "WebProjects_SessionManagement_BuildChanges". I created 3 dummy steps and then ran those builds 3 times.
                        After that was done, I created a new Application in BuildMaster. When I went to import the 3 builds I created, it resulted in the same behavior that I saw before.
                        When I check the API (/app/rest/projects/WebProjects_SessionManagement?fields=buildTypes(buildType)), I get this for projects:

                        <project>
                           <buildTypes>
                              <buildType id="WebProjects_SessionManagement_BuildChanges" name="BuildChanges" projectName="Web Projects / Session Management" projectId="WebProjects_SessionManagement" href="/app/rest/buildTypes/id:WebProjects_SessionManagement_BuildChanges" webUrl="http://10.0.14.200:8111/buildConfiguration/WebProjects_SessionManagement_BuildChanges?mode=builds"/>
                           </buildTypes>
                        </project>
                        

                        And then when I check the builds for this project (/app/rest/builds?locator=defaultFilter:false,project:WebProjects_SessionManagement&fields=build(id,number,status,state,webUrl,startDate,buildTypeId)), I get this:

                        <builds>
                           <build id="10342" buildTypeId="WebProjects_SessionManagement_BuildChanges" number="26.20.0117.3" status="SUCCESS" state="finished" webUrl="http://10.0.14.200:8111/buildConfiguration/WebProjects_SessionManagement_BuildChanges/10342">
                              <startDate>20260117T214753-0500</startDate>
                           </build>
                           <build id="10341" buildTypeId="WebProjects_SessionManagement_BuildChanges" number="25.20.1317.2" status="SUCCESS" state="finished" webUrl="http://10.0.14.200:8111/buildConfiguration/WebProjects_SessionManagement_BuildChanges/10341">
                              <startDate>20260117T214729-0500</startDate>
                           </build>
                           <build id="10340" buildTypeId="WebProjects_SessionManagement_BuildChanges" number="25.20.1317.1" status="SUCCESS" state="finished" webUrl="http://10.0.14.200:8111/buildConfiguration/WebProjects_SessionManagement_BuildChanges/10340">
                              <startDate>20260117T214719-0500</startDate>
                           </build>
                        </builds>
                        

                        and yet, no builds in the dropdown in BuildMaster

                        1 Reply Last reply Reply Quote 0

                        Hello! It looks like you're interested in this conversation, but you don't have an account yet.

                        Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

                        With your input, this post could be even better 💗

                        Register Login
                        • 1 / 1
                        • First post
                          Last post
                        Inedo Website Home • Support Home • Code of Conduct • Forums Guide • Documentation