Your browser was unable to load all of the resources. They may
have been blocked by your firewall, proxy or browser configuration.
Press Ctrl+F5 or Ctrl+Shift+R to have your browser try again.
We've run into an issue where it would be very useful to know if an agent ended up running a Sync step on a build configuration outside of its normal resource. Is there an easy way to query QB for all Build Jobs (still in the history) where that particular agent ran the master step?
This would be the equivalent of running a query for build history for all configurations, filtering by a specific node running the master step. This feature exists in the history query for a specific configuration only, as far as I can tell.
If this is possible, please let me know.
Thanks in advance,
At right top of the screen, you can search for builds, and at bottom of build search option, you may specify agent to query against.
How about the ability to identify on what nodes a given step ran (not necessarily the master step)?
Or any step at all..
You may open the step status page and it will show on what node the step ran on
That wouldn't work if I wanted to query for all such jobs.
Unfortunately this info can not be queried per step, as there is no separate step table.
Actually, and perhaps related, is this why I cannot see any history in the Build Step statistics?
For "Build Stats", I can see duration, success rate, etc. going back to the beginning of time.
But for "Step Stats", no matter what step I pick, it shows only the most recent number; all previous runs show as zero.
I occasionally run "Rebuild Statistics" job, but it doesn't seem to make a difference.
The step stats should be available, as it collects data for each build overtime, writes result to its own file database, and draws the graph. Can you please let me know the reproducing procedure?
I am not sure how I can do that, except to bring you my entire database. I can try to set up a tiny test case.
Yes, please set up a tiny test case at your side to see if it works.
Thank you, I had this problem too, but I managed to solve it thanks to this post
How did you solve it?
In setting up my test case, I discovered that it works in some configurations and not others. I haven't found a pattern yet.
Seems that the account "evaldp2" is spamming.