Hi,
Your answer relates to Active Directory, I'm using LDAP 389 on Linux.
Any other idea?
Gil
בתאריך יום שלישי, 28 באוקטובר 2014 16:58:34 UTC+2, מאת Gil Br:
All,
I installed the latest LDAP Plugin for Jenkins.
When I use ldap://server.name I get *no* error under the LDAP Server
line,
Hello,
if a failed build follows follows on a successful build, the successful
build isn´t available anymore. Is there any possibility to save the last
successful build?
Thanks!
Monika
--
You received this message because you are subscribed to the Google Groups
Jenkins Users group.
To
As far as I know, Jenkins always keeps the last successful build, even if you
are using “discard old builds”. Are you observing something different?
From: moni.schaefer@googlemail.com [mailto:moni.schaefer@googlemail.com]
Sent: 29 October 2014 08:00
To: jenkinsci-users@googlegroups.com
Old post, I know, but I just came across this issue so thought I'd add my
findings. https://issues.jenkins-ci.org/browse/JENKINS-14771 looks to be
the same issue, the reason for the NPE is that while you've added the
trigger to the job you haven't told the trigger about the job. To work
That's a two year-old thread. There are other issues that are similar (
https://code.google.com/p/chromedriver/issues/detail?id=928) and current.
On 28 October 2014 17:28, Tamilarasan Rajendran tamil1...@gmail.com wrote:
Hi, I am also facing similar issue.
I am trying to execute my automation
Gil Br (2014-10-29 08:51):
Hi,
Your answer relates to Active Directory, I'm using LDAP 389 on Linux.
Any other idea?
Depending on your LDAP configuration you should use correct search base
and search filter... But I'm not sure how would you use NT password if
LDAP is on Linux? Or what do
Patrick van Dissel (2014-10-29 02:35):
[...]
About the jobs structure..
It really depends how you're going to use Jenkins.
Start simpel, and only add what is nessesary.
The amount of jobs does not really matter. For your idea, with my team
we currently have a Jenkins setup of 1 master with 3
alok kumar (2014-10-28 17:42):
Hi All,
I am using ZEN timestamp plugin to modify the BUILD_ID as per our
requirements.
It works well when I use it any build step, but when I try using the
changed BUILD_ID variable in the extended email build step it doesnt
show the modified BUILD_ID, but, the
Did you ever get a response? Is Jenkins ADA/508 compliant?
On Wednesday, September 24, 2014 11:40:15 AM UTC-4, laura1...@gmail.com
wrote:
I’m not sure if this is the right forum for this request, but I was hoping
someone might be able to point me in the right direction…
I was hoping
The JobDSL (currently) does not support having you global Jenkins config
files managed by the DSL. So, we have the global Jenkins configs in a
separate closed repository which we checked out manually once and is now
kept insync with a Jenkins job :). But solutions like
Puppet/Chef/Ansible could
I want groovy script for following scenario.
1. I am starting build with string parameterized build . When i run build
it will ask me value for that string parameter. Now i want to execute
groovy script in build step which will read this passed string parameter .
I want to create a a string type
Am 29.10.2014 um 13:40 schrieb niraj nandane:
1. I am starting build with string parameterized build . When i run
build it will ask me value for that string parameter. Now i want to
execute groovy script in build step which will read this passed string
parameter . I want to create a a string
Probably EnvInject plugin may help you..
Thanks,
JP
On Tue, Oct 28, 2014 at 10:12 PM, alok kumar alok.kuma...@gmail.com wrote:
Hi All,
I am using ZEN timestamp plugin to modify the BUILD_ID as per our
requirements.
It works well when I use it any build step, but when I try using the
Thanks...
So I think I've solved it...
The message : *Scheduling another build to catch up with XXX *crept into
the build logs.
This of course was scheduling a build (and doing it on _every_ build).
The branch to build is */master and this is what it has been for a while
but at some point
(replies inline)
On Wed, 24 Sep 2014, laura1fxj...@gmail.com wrote:
I?m not sure if this is the right forum for this request, but I was hoping
someone might be able to point me in the right direction?
I was hoping someone might be able to provide a Voluntary Product
Accessibility
No I never received a response.
On Oct 29, 2014, at 8:02 AM, doughansen08 doughanse...@gmail.com wrote:
Did you ever get a response? Is Jenkins ADA/508 compliant?
On Wednesday, September 24, 2014 11:40:15 AM UTC-4, laura1...@gmail.com
wrote:
I’m not sure if this is the right forum
Here you go :)
import javax.mail.Message
import hudson.model.*
import com.cloudbees.plugins.flow.*
import hudson.tasks.MailAddressResolver
def getUpstreamBuild(AbstractBuild curBuild)
{
upStreamBuild = null
if(curBuild != null)
{
// find a cause that will lead to an upstream
Hi All,
I did an unintentional upgrade of Jenkins from version 1.532.3 to 1.565.3
using the Long Term Support rpm's from jenkins.org. I tried to correct the
situation by downgrading to 1.532.1.
After the downgrade matrix-auth errors are written to jenkins.log :
WARNING: Failed to scout
Were you using multiple repositories in the job?
Had the job been through any special changes which might be relevant to
understand why the code which asks the question what needs to be built to
decide that more than one SHA1 needed to be built?
Mark Waite
On Wed, Oct 29, 2014 at 8:15 AM,
Hi,
thank you! Yes I can confirm that using the 3.4.x kernel on the master it
works!
Br,
Andras
On Wednesday, October 22, 2014 10:26:24 PM UTC-7, Guillaume Boucherie wrote:
For me it was link to linux kernel used. See this bug for more information
:
20 matches
Mail list logo
