|"Trigger even if the build is unstable" fails [message #911755]
||Wed, 12 September 2012 05:03
| Bernhard Hiller
Registered: September 2012
Our software suite consists of some 20 C# solutions. A change in a shared component may affect many of those solutions.|
Consequently, I set up many projects ("Free style Projects" each consisting of a few "Execute Windows Batch Command" for building, testing and cleaning the solution) to be build one after the other. And I checked "Trigger even if the build is unstable" - I want to see all the projects which fail due to a change in a shared component! Reparing one solution after the other takes unnecessary lots of time and makes the process non-continuous.
This bug seems to have been reported several times, with minimal variations:
(again the other bug: "You can only use links to eclipse.org sites while you have fewer than 25 messages." - I must not provide links to hudson-ci.org... Please add the http:// )
In the last case, it was marked as "Not a defect" - obviously, the developer did not understand the business case behind that use!
I'll try to find out if the "parameterized trigger plugin" mentioned in the last post could be useful.
Powered by FUDForum
. Page generated in 0.09279 seconds