search

netmelody / ci-eye

An infrastructure agnostic CI build radiator
http://netmelody.org/ci-eye/
Apache License 2.0
43 stars 26 forks source link

Teamcity build without builds #19

Open ushkinaz opened 12 years ago

ushkinaz commented 12 years ago

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
JosephGoulden commented 10 years ago

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.

Like this... TEAMCITY|http://teamcity.codebetter.com|CI-Eye|false

Still waiting for this to be merged to the master branch though.