Hello together,
I am making use of the vSphere cloud plugin to automatically generate
slaves from a VM image. This works perfectly fine for the first image but I
have to build my application for several platforms and therefore created
another VM with a different compiler installed and wanted to
We are reading the mail addresses from ldap. The assignment user from repo
commit user to mail address happens automagically in the background.
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving e
Hello!
I have a unit test that from time to time deadlocks. To work around that
and at least finish the build and collect the results available so far I
made use of a timeout in a try and caught the timeout. When this timeout
applies now, I get an overall green testrun which is not what I want.
Don't you actually want to use a ressource pool with two locks which use
the same label?
Am Donnerstag, 30. April 2020 15:46:28 UTC+2 schrieb Satya Muralidhar
Peddireddi:
>
> It's my test case I want run same job parallely in different locks.if one
> lock is busy go to another lock
>
> On Thu,
Hello!
Another weird issue I ran into:
For any reason it's not possible to clone from my repository without the
extension largefile and the commandline switch --stream (or --uncrompessed,
I tried both).
I therefore enabled this in the tools settings of mercurial:
When cloning from my jenkinsfile
Sorry for the delay, I've been on vacation.
With tracing I understood adding output to the code that helps you
understanding what happens e.g. variable content,
For sure that's not the most efficient way and in case your pipeline runs
for a time it might get boring
Am Donnerstag, 9. Apri
JFTR:
By using my personal user credentials everything started to work. So it
really seems to be a issue of my build user's access rights.
Thank you very much for the heads up!
Now I am trying to find out, why the start script is expecting the java
installation beyond the SLAVE_HOME instead of
For me that looks like an issue of your shell command and not of the
plugin. Can you try to store the actual file to your workspace and make the
plugin parse that?
For me the warnings.ng.plugin is just working in conjunction with cppcheck.
What I am doing looks like this:
The cppcheck-call:
cp
Hi Gianluca,
OK, the log was a good idea, thank you very much!
There I found:
Started provisioning VC9BuildSlave97yt3vpya79krvglcpcgevei4 from vSphereCloud
with 1 executors. Remaining excess workload: 0
Apr 01, 2020 5:13:01 PM WARNING
org.jenkinsci.plugins.vSphereCloud$VSpherePlannedNode$1 cal
Hi,
I have access to an Esxi-Server used by a vSphere instance. I set up a
vsphere cloud in my Jenkins installation properly ("Test connection" works).
I set up a template VM (Windows 10) with a Snapshot, Autologon and
Autostart according to
https://github.com/jenkinsci/vsphere-cloud-plugin/blo
Hello,
another question from me:
I am building an application with jenkins in 4 different variants: 2
compilers and debug and release. Currently I have a jenkinsfile where the
variants are implemented in the environment and I am building the
application with a long list of checkout, build and
Hi!
I have all my jobs currently realized as declarative jenkinsfiles. I
recently found the Extended workspace manager which could solve my issue
distributing test-jobs running on a previously built version to slave nodes.
Unfortunately I was not able to find any documentation or code examples h
Hello,
I have my jenkins running as service on a windows server 2016.
Whenever there is an update on any plugin or jenkins itself some of my jobs
are running severely slower (e.g. 150->340 minutes).
What I can say:
- it's only affecting (declarative) pipeline jobs, no freestyle-jobs
- it's only a
13 matches
Mail list logo