You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have a build configuration by the name "local" that doesn't have any "public" finished builds. It's used for testing feature branches, as described here: http://confluence.jetbrains.net/display/TCD7/Branch+Remote+Run+Trigger
The build configuration contains only personal build runs and will never have public runs.
CI-Eye reports status of that build as unknown, which is technically correct, but does not reflect reality.
Actually, since that kind builds are of no interest to the entire team, it would be right to exclude them from ci-eye radiator.
In current structure of views.txt it's rather difficult to add a list of excluded builds to configuration. Perhaps, it's a time to rethink views.txt structure.
I would vote for YAML for it's simplicity
Hi. I think that I have resolved this in issue #26. We had the same problem with personal builds on our team. I've added the ability to filter out these personal builds with a boolean flag in the config.
We have a build configuration by the name "local" that doesn't have any "public" finished builds. It's used for testing feature branches, as described here: http://confluence.jetbrains.net/display/TCD7/Branch+Remote+Run+Trigger
The build configuration contains only personal build runs and will never have public runs.
CI-Eye reports status of that build as unknown, which is technically correct, but does not reflect reality.
Actually, since that kind builds are of no interest to the entire team, it would be right to exclude them from ci-eye radiator.
In current structure of views.txt it's rather difficult to add a list of excluded builds to configuration. Perhaps, it's a time to rethink views.txt structure.
I would vote for YAML for it's simplicity
The text was updated successfully, but these errors were encountered: