Hi!
I have jenkins on a single server and eight slaves on the other. Slaves are
sometimes far apart on a virtual server running VmWare ESXi. How to make
that simultaneously can build only two or three slaves, and other jobs are in
the queue?
Sorry for my english.
--
You received this
I think I ran into similar problems a while ago.
These open jenkins issues are related:
https://issues.jenkins-ci.org/browse/JENKINS-21424
https://issues.jenkins-ci.org/browse/JENKINS-19360
Attached to Jenkins-19360 is an xsl file that you can use to transform the
trx file that vstest produces
Hi,
I use the (free) Cloudbees folder plugin (4.5) on Jenkins (1.559). I have
several layers of nested folders. For most folders, the weather icon
correctly displays the aggregated status of recent builds, but for some
folders no icon is displayed. I cannot find a logical difference between
We have had several deployments to our Enterprise Service Bus where the
applications did not have proper connection strings for the environment. I'd
like to put a step into my deployment job where I can test the connection
string information (which has values keep in an external property file)
Hi
For our large C++ project, hosted in Subversion, we have a Jenkins job that
continuously builds the project on a Linux slave. We also have jobs that
periodically run regression tests on it (these tests are long and we don't want
to run them on every commit).
Currently, the regression
Any hints as o how to use the xsl file to transform the trx?
Is there a hook within the vstest runner or mstest plugins, where I can
plug in the xsl?
Or do I need to add a new step to do the conversion? Using what tool?
On Friday, June 20, 2014 1:45:47 AM UTC-5, Glenn V wrote:
I think I ran
Hi David,
you can use the Copy Artifact Plugin . This plugin allows Job B to copy any or
all of the published artifacts from Job A.
--
You received this message because you are subscribed to the Google Groups
Jenkins Users group.
To unsubscribe from this group and stop receiving emails from
When you add a slave in jenkins you specify a label for each slave.Set the
Restrict where this job can be run check box in your job configuration and
specify the name/label of your slave. based on the number of the executor in
your slave the jobs will run,and rest of the jobs with the same
David:
I pass the CI job's workspace into the downstream job using my build pipeline
via the clone workspace plugin. The CI job uses the Post-build Actions
-Archive for Clone Workspace SCM. The downstream job uses the cloned
workspace as a SCM plugin.
Eric
On Friday, June 20, 2014 9:49
