Hi Sami, hi Anthony,
what I need to do is actually what Sami says. I do not want to always
archive the artifacts of all builds, since I don't have so much space. That
instance of Jenkins is meant to be populated with dozen projects and it
might be used to build "test" builds or to make "release"
Does it work for maven based jobs?
Looks like you can't set more memory for maven then you gave to jenkins
process, because maven executes in parent jenkins java process.
2012/7/26 Markward Schubert
> Hi Group!
>
> Is there some known issue with JVM Parameters being ignored for Maven
> build ste
Can you normally SSH to the slave machine from Master? I got some weird
errors that disappeared after Firewall is relaxed ...
Krishna Chaitanya
On Sun, Jul 29, 2012 at 11:55 AM, Sami Tikka wrote:
> From which package does "java" on the slave come from?
>
> -- Sami
>
> Rich Pixley kirjoitti 2
From which package does "java" on the slave come from?
-- Sami
Rich Pixley kirjoitti 28.7.2012 kello 0.24:
> I'm trying to set up my first slave and I'm running into a problem I don't
> understand or know how to debug.
>
> Both machines are ubuntu-12.04, standard ubuntu jenkins install, con
Rich Pixley kirjoitti 28.7.2012 kello 0.28:
> You just have to understand that jenkins doesn't really do much in the way of
> work space management so hosed builds mean you'll have to clear the workspace
> and start all over from scratch.
Jenkins does have the option of clearing the workspace
Further observation: it seems to happen only when running multiple
concurrent builds
of the same job on the same slave (but not when running multiple builds on
separate
slaves, at least it seems that way currently).
On Saturday, July 28, 2012 3:04:41 PM UTC+2, Lukas Rytz wrote:
>
> Hi all,
>
