Getting duplicate build data for all build configurations in all project repositories

[wsherwoo]

I've tried implementing this plugin with Dashing, but am having confusing results.

• In teamcity.yml I have 4 repositories configured. These are all lowest level projects in our local teamcity environment, and all sub projects of the same team's project (one per deployment environment of prod, uat, qa, and dev).
• In the dashboard file, I have 4 different li items which with unique data_id's which match the teamcity.yml values
• When turned on, I'm getting valid responses from teamcity, which include all build configurations that live within each of the 4 lowest level projects I have requested. The names of these builds are accurate and distinct.
• However, the build status, username, and number are identical for ALL build configurations being displayed, regardless of project and build name.

After some digging, it appears that the item.last_build value is being updated with data from build_type_builds.first in line 39 of the jobs file teamcity.rb. The array of builds being returned (sorted by latest first) encompasses all builds in the entire teamcity environment, regardless of the parent project id.

Has anyone encountered this, or even better, found a way to fix it? I'm not sure what I've done wrong.

[FizzBuzz791]

Hi @wsherwoo, that's really odd! As you can see from this screenshot, I've got it up and working at our office and the usernames for each build are different. "V7 Git" is the lowest level sub-project, with multiple build configurations, but it sounds like that's what you're doing too.

TeamCity has an API (which is what the ruby script is using), it may be worth doing a little digging with that to see if it's reporting correctly. Maybe there's a certain configuration on the server that needs to be set and we just happened to get lucky and already have the required settings met.

Finally, what version TC are you using? I've only tested this with 9.1.4.

[wsherwoo]

Thanks for the quick reply @FizzBuzz791 . We are running 9.1.1. I will dig further into the settings today. We have experienced some issues in other areas because we haven't fully configured access control groups and roles/permissions in TC yet (it's fairly wide open). Hopefully that's not the issue...

[FizzBuzz791]

Ahh yep, I'm just using my own account in the config file, which happens to have Project Administrator permissions, so that's potentially where the issue lies.