You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by Richard Eckart de Castilho <ri...@gmail.com> on 2013/06/01 10:47:17 UTC
Re: Build failed in Jenkins: UIMA-SDK #309
Am 07.05.2013 um 16:55 schrieb Marshall Schor <ms...@schor.com>:
> There are 2 errors. One is "out-of-space" on disk. I've reduced the # of
> builds to keep to 3 and the # of days to keep the build to 7.
You changed the keeping times for the full builds. Increasing these values
again to say 120 days and 20 builds and just reduce the keeping times for
the artifacts of these builds (accessible via the "Advanced" button, which
may actually have a different label since I see it in German). Like just
keeping 1 or 2 builds with artifacts. These values are currently unset.
That way we'd have more meaningful historic view on changes, build failure
causes, etc. in Jenkins.
Cheers,
-- Richard
Re: Build failed in Jenkins: UIMA-SDK #309
Posted by Richard Eckart de Castilho <ri...@gmail.com>.
Changed to in UIMA-SDK build:
Keep builds 120 days, max 20 builds in total.
Keep artifacts for the 2 latest builds.
-- Richard
Am 01.06.2013 um 10:47 schrieb Richard Eckart de Castilho <ri...@gmail.com>:
> Am 07.05.2013 um 16:55 schrieb Marshall Schor <ms...@schor.com>:
>
>> There are 2 errors. One is "out-of-space" on disk. I've reduced the # of
>> builds to keep to 3 and the # of days to keep the build to 7.
>
> You changed the keeping times for the full builds. Increasing these values
> again to say 120 days and 20 builds and just reduce the keeping times for
> the artifacts of these builds (accessible via the "Advanced" button, which
> may actually have a different label since I see it in German). Like just
> keeping 1 or 2 builds with artifacts. These values are currently unset.
>
> That way we'd have more meaningful historic view on changes, build failure
> causes, etc. in Jenkins.
>
> Cheers,
>
> -- Richard
Re: Build failed in Jenkins: UIMA-SDK #309
Posted by Marshall Schor <ms...@schor.com>.
+1 - I didn't know about this feature :-) . -Marshall
On 6/1/2013 4:47 AM, Richard Eckart de Castilho wrote:
> Am 07.05.2013 um 16:55 schrieb Marshall Schor <ms...@schor.com>:
>
>> There are 2 errors. One is "out-of-space" on disk. I've reduced the # of
>> builds to keep to 3 and the # of days to keep the build to 7.
> You changed the keeping times for the full builds. Increasing these values
> again to say 120 days and 20 builds and just reduce the keeping times for
> the artifacts of these builds (accessible via the "Advanced" button, which
> may actually have a different label since I see it in German). Like just
> keeping 1 or 2 builds with artifacts. These values are currently unset.
>
> That way we'd have more meaningful historic view on changes, build failure
> causes, etc. in Jenkins.
>
> Cheers,
>
> -- Richard
>