[JIRA] (JENKINS-15202) Permanent building / consider removing latest changes

Tue, 18 Sep 2012 08:28:54 -0700

 
Waldek M edited a comment on Bug JENKINS-15202

Hello,

Well, perhaps the "plenty" was an overstatement. Sorry, I was a bit emotional, because those 2 existing issues have blocked a team of ~20 persons for a day. I'm simply concerned: if just after upgrade I've discovered 2 issues that have broken long-existing functionality, I'm not really eager to take the risk again and upgrade.

As for the automatic time rules: their description is in Advanced section of plugin configuration:

Use time rule in config spec
If checked, Hudson will use a time rule in the dynamic view's config spec, locking the view contents in as of the beginning of the build, even if files are changed on the branch during the build.

When using CC dynamic view, it's actually an essential option. Otherwise, content of the build may change during its compilation - which is very likely for team with a CI branch, the more probable, the bigger the team is.

It's mostly about adding a time rule at when updating the view's CS, eg:

time 17-sep-12.11:53:51utc+0000
[... config spec set by user - the original from Jenkins UI ]
end time

Please note also that the original CS may contain time rules, too.



I must though say that I like the new feature that allows setting config spec from file (I guess that was also part of the pull request?). I'm just very cautious and a bit afraid that perhaps there are some other changes that might not have been tested well enough: on snapshot and dynamic views, in standalone and master-slave, with Linux/Unix.



Waldek
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to