Support exclusion of Build Ids

[RaphHaddad]

I know 'inclusion' is already there. But if 'exclusion' of build Ids sounds like a good idea I can send through a pull request.

[mavadat]

I'd up vote that feature. A close one is also inclusion of project rather
than build types. With TC now supporting sub projects it makes more sense
to categorise by projects and have build light monitor a category. This
reduces the need for both build-type specific inclusion and exclusions.

Logic is that if build light should monitor certain builds within project
but not other ones chances are a categorisation by sub-project is missing
in TeamCity that reflects the difference meaningfully.

On Wednesday, April 22, 2015, Raphael Haddad [email protected]
wrote:

I know 'inclusion' is already there. But if 'exclusion' of build Ids
sounds like a good idea i can send through a pull request.

—
Reply to this email directly or view it on GitHub
#19.

Cheers,
Jamal

[aaronpowell]

Sure, send a PR

[RaphHaddad]

@mavadat maybe make a new 'issue'?

@aaronpowell will do.

[mavadat]

Raphael, it certainly is new issue however I was hopping it might supersede
current issue in hopefully more elegant way.

On Wednesday, April 22, 2015, Raphael Haddad [email protected]
wrote:

@mavadat https://github.com/mavadat maybe make a new 'issue'?

@aaronpowell https://github.com/aaronpowell will do.

—
Reply to this email directly or view it on GitHub
#19 (comment).

Cheers,
Jamal

[RaphHaddad]

Hey JM. In this PR I will redactor some of the code that calls the TC API
in order to get this feature in with another PR.

Sent from Gmail Mobile
On 22 Apr 2015 11:42, "Jamal Mavadat" [email protected] wrote:

Raphael, it certainly is new issue however I was hopping it might supersede
current issue in hopefully more elegant way.

On Wednesday, April 22, 2015, Raphael Haddad [email protected]
wrote:

@mavadat https://github.com/mavadat maybe make a new 'issue'?

@aaronpowell https://github.com/aaronpowell will do.

—
Reply to this email directly or view it on GitHub
#19 (comment).

Cheers,
Jamal

—
Reply to this email directly or view it on GitHub
#19 (comment).