Is there some way to send an admin an email when the master notices that a
slave has gone offline?
Thanks,
John Bobinyec
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails fro
The apparent interference might have been due to other things.
But does no one else have ghosts?
jb
On Thursday, January 26, 2017 at 3:27:12 PM UTC-5, John Bobinyec wrote:
>
>
> We have a pool of slaves. When a job is dispatched to one of them it is
> assigned to an executor on
We have a pool of slaves. When a job is dispatched to one of them it is
assigned to an executor on that machine. Oftentimes there is a very
similar job running on another machine but it's not assigned to an
executor. I call these ghosts. What do they do? How are they
dispatched? It seems
We want to take Jenkins down for maintenance and give several days notice
to the users. Is there an easy way to send an administrative email to that
effect?
Thanks,
John Bobinyec
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users"
I have several perl scripts which develop information which is to be used
as environmental variables in subsequent parts of the build.
How do I:
1. Pass the information back from the perl script to the main build
program?
2. Once the main program has the information, set up environme
The format of the data is
PARAM1=VAL1:PARAM2=VAL2
What do you do if VAL1 has a colon in it, like C:\Tools ? Jenkins seems to
think the colon is the beginning of another variable/value pair.
Thanks,
jb
--
You received this message because you are subscribed to the Google Groups
"Jenkins Use
Using Project Based security, I can start a job using a script file (perl,
LWP), only if the Anonymous id has Build/Read access to the job. There is
another id which has "everything" access to the job. With the Anonymous
having access, I don't need to specify an ID/password or the ID/API . No
Consider a job which consists of many sequential steps. When the
processing in a particular step encounters an error, execution of the step
and consequently the job, stops. If the error condition can be corrected,
what's the best way to resume/restart the job from the point of failure?
It is
We're thinking of migrating to jenkins. The build machines run rexx
scripts on Windows machines. In the project I'm trying to set up a command
which will execute the rexx script on the slave. The command is to be
executed in an "Execute a Windows batch command" window:
"c:\Program Files\ObjR