tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Richard Eckart de Castilho <...@apache.org>
Subject Re: UIMA-SDK build tied to tapestry-only node in Jenkins
Date Tue, 05 Nov 2013 15:26:14 GMT
Hello Uli,

actually, the UIMA-SDK build is tied to "ubuntu" already. I was recently trying to find a
rule for binding builds, starting with not tying it at all, then adding exclusions for those
where the build did not run. During that quest, at some point, a build was run on the tapestry
which was actually very helpful, because it showed us that a bug he thought to have fixed
long ago
hadn't been properly fixed at all. We fixed the issue again and a second build was run on
tapestry VM after that to verify it had gone. After this, the job was tied again to "ubuntu"
(I just checked, it says "ubuntu" in the job configuration).

I am not sure why the tapestry slave was chosen when I started excluding certain nodes. The
documentation at ASF says "If your build is not system-dependent (most simple Java builds,
you can leave your build untied to maximize the number of executors available for the build."
So I would assume, that certain reserved slaves are neither used when a job is not bound,
when it excludes specific nodes which are known to have issues (e.g. solaris1).

Sorry for the inconvenience. In any case, we did not have the intention of appropriating exclusive

Best regards,

-- Richard

On 04.11.2013, at 22:07, Ulrich Stärk <uli@apache.org> wrote:

> Hi UIMA devs,
> the Tapestry project has a donated built host exclusively for Tapestry builds. It seems
that despite
> the exclusiveness you are building UIMA builds on that node. I'd like to ask you to please
> your build so as not to use that node.
> Thanks,
> Uli

To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org

View raw message