What about the CPU usage on a per core basis? I have seen Jenkins push a
single core to maximum for periods of time.
On Tuesday, November 18, 2014 12:21:41 PM UTC-6, Dunnigan, Terrence J wrote:
Hi All,
From time to time our Jenkins will become unresponsive for brief periods
of time.
I am posting here again since no one is responding to my problem anywhere.
I have a job in jenkins that has a build matrix that starts several jobs,
some of those jobs can only run one at a time. If I start the build matrix
job while another job is still running most of the time the jobs in the
matrix child builds running in parallel.
Scott
On Tue, Nov 4, 2014 at 10:40 AM, Jeffrey Parker thexd...@gmail.com
wrote:
I am posting here again since no one is responding to my problem
anywhere. I have a job in jenkins that has a build matrix that starts
several jobs, some of those jobs can
at
a time so we don't have matrix child builds running in parallel.
Scott
On Tue, Nov 4, 2014 at 10:40 AM, Jeffrey Parker thexd...@gmail.com
wrote:
I am posting here again since no one is responding to my problem
anywhere. I have a job in jenkins that has a build matrix that starts
several
I know what it is waiting for, that is not the problem. It is waiting for
another job of the same type to finish because only one can run at a time.
On Tue, Nov 4, 2014 at 11:38 AM, Les Mikesell lesmikes...@gmail.com wrote:
On Tue, Nov 4, 2014 at 11:11 AM, Jeffrey Parker thexd...@gmail.com
Yes, that is the problem that I am encountering.
On Tue, Nov 4, 2014 at 11:54 AM, Les Mikesell lesmikes...@gmail.com wrote:
On Tue, Nov 4, 2014 at 11:49 AM, Jeffrey Parker thexd...@gmail.com
wrote:
I know what it is waiting for, that is not the problem. It is waiting for
another job
I have several jobs in Jenkins that are kicked off by a job that uses the
build matrix plugin and I am encountering some problems with that plugin.
Basically when I kick off one of the build matrix jobs, then kick off
another before the first one completes some of the jobs in the build matrix
That is exactly what the problem is, but the bigger issue is running sudo
commands in a script like this is generally bad practice. The more correct
way to do it is to make sure that all files are already owned by the
correct user or that the user that is running the command has permission to
