-
Notifications
You must be signed in to change notification settings - Fork 24
Description
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
views:
- name: CI-Eye Demo
servers:
- name: Product_Zappa
type: DEMO
- name: Product_Mappa
type: TEAMCITY
URL: http:/me.to
login: guest
password: pass
excludedBuilds:
- Local
- Fake
- name: Public Live
servers:
- name: Jenkins core
type: JENKINS
URL: http://ci.jenkins-ci.org