Yeah, I noticed the cite jobs are failing, my guess is that i didn't set up
the new server properly. It is on my list to look into. I'll try to do that
soon in the next few days.
As for the job trigger, i would say a simple nightly trigger should do?
On Mon, Oct 14, 2013 at 8:06 PM, Ben Caradoc-Davies <
ben.caradoc-dav...@csiro.au> wrote:
> Justin,
>
> another issue that came up at Monday's meeting is the CITE test breakage
> and lack of triggers for the jobs. I have been kicking them manually but
> still encountering some failures (looks like a Jenkins problem not a
> config). Also do you have any opinion about the best approach for
> triggering (see below)?
>
> Kind regards,
> Ben.
>
> On 14/10/13 21:43, ben.caradoc-dav...@csiro.au wrote:
>
>> CITE breakage
>> -------------
>>
>> Q: Held up CITE breakage?
>> A: Seem it has not been run in 26 days, perhaps not configured correctly
>> 2.4-cite-all triggers the other builds, but it does not have a build
>> trigger itself -> How to fix? Once a day, or triggered by the nightly build
>> maybe?
>>
>
> --
> Ben Caradoc-Davies <ben.caradoc-dav...@csiro.au>
> Software Engineer
> CSIRO Earth Science and Resource Engineering
> Australian Resources Research Centre
>
--
*Justin Deoliveira*
Vice President, Engineering | Boundless
jdeol...@boundlessgeo.com
@j_deolive <https://twitter.com/j_deolive>
------------------------------------------------------------------------------
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60135031&iu=/4140/ostg.clktrk
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
