Suresh, FWIW the precommit build fails fast in such cases (by design). nige
On Jan 14, 2011, at 10:12 AM, Suresh Srinivas wrote: > It may not be as simple as triggering retest, as Some of the patches could be > old and may not apply. > > > On 1/14/11 8:44 AM, "Nigel Daley" <[email protected]> wrote: > > Todd, please file a Jira in Common against test component. FWIW, I fear the > precommit integration with Jira will need some amount of work as Apache moves > to Jira 4.2 in the coming weeks. > > Nige > > On Jan 14, 2011, at 12:57 AM, Todd Lipcon wrote: > >> Hey Nigel, >> >> Would there be any way to add a feature where we can make some special >> comment on the JIRA that would trigger a hudson retest? There are a lot of >> really old patches out on the JIRA that would be worth re-testing against >> trunk, and it's a pain to download and re-attach. >> >> I'm thinking a comment with a special token like "@Hudson.Test" >> >> Failing that, Ian, can you add me to the Hudson list? >> >> -Todd >> >> On Wed, Jan 12, 2011 at 4:33 PM, Nigel Daley <[email protected]> wrote: >> >>>> Jakob Homan commented on HDFS-884: >>>> ---------------------------------- >>>> >>>>> Konstantin, if you're trying to kick a new patch build for this you no >>> longer move it to "Open" and back to "Patch Available". Instead, you must >>> upload a new patch. Or, if you have permission, you can kickhttps:// >>> hudson.apache.org/hudson/job/PreCommit-HDFS-Build/ and enter the issue >>> number. >>>> >>>> That makes me sad. Is this a new feature or regression? >>> >>> [For everyone's benefit, moving this to general@] >>> >>> Jakob, I referenced the change here: http://tinyurl.com/4crxlvy >>> The new system is much more robust partial because it no longer relies on >>> watching Jira generated emails to determined when issues move into Patch >>> Available state. There is limited info I can get from the Jira API, thus the >>> triggering mechanism had to change. >>> >>> Cheers, >>> Nige >>> >> >> >> >> -- >> Todd Lipcon >> Software Engineer, Cloudera > >
