search

brianfromoregon / caliper-ci

Automatically exported from code.google.com/p/caliper-ci
0 stars 0 forks source link

Asynchronous results #9

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
A suite of performance tests holding up the quick build feedback loop won't be 
practical at times. Need a story for this. A successful build might kick off 
another build or another process to run the tests, and when that other 
build/test finishes can we correlate those results to the upstream build? Like 
adding a "star" via promoted builds plugin? Likely too late to mark it as 
unstable.

Original issue reported on code.google.com by brianfromoregon on 21 Nov 2011 at 8:11

GoogleCodeExporter commented 9 years ago 
Without an offering here, I'd create a downstream job (which might run on a 
schedule instead of being triggered for each build) to synchronously run and 
collect the results, failing and sending mail. Bummer is that the Caliper 
reporting isn't alongside FindBugs,JUnit,etc in the upstream build.

Original comment by brianfromoregon on 21 Nov 2011 at 8:14