Are you using scripted or declarative? I will assume scripted since that's
all I know :)
There's a don't wait option. Or you could wrap the call in a try/catch. Or
you could save currentBuild.result before calling job B and restore it after
On Friday, August 21, 2020 at 5:09:57 AM UTC-4
Hi Jeremy,
Thanks a lot for your response. I am using a Declarative approach
(Jenkinsfile). Could you please provide some more details on the don't wait
option, if possible? JobA runs successfully and triggers JobB from Post
build. But if JobB fails, it marks JobA also as failed even though JobA
I only know scripted, which has 3 options:
wait for completion and propagate errors:
build job: 'lp_systemtest3/master'
no propagate errors
build propagate: false, job: 'lp_systemtest3/master'
don't wait
build wait: false, job: 'lp_systemtest3/master'
On Friday, August 21, 2020 at 1:05:08 PM
I use scripted pipelines with a library. The master and the slaves are
running in ubuntu 16.04 docker containers.
About a week ago we started getting occasional failures from this call:
junit testResults: ".build/ub18_debug/artifacts/systemtest/*xml"
There are about 60 junit xml files in
I have two different kinds of jobs:
one is installing all the requirements for a job from a storage, building
one package and collecting warnings and cppcheck results with warnings ng.
Here everything works fine, display of warnings and cppcheck-analysis works.
In another jobs I am building all
Hello, all
The configuration page has a setting named "Remote root
directory", but thoughout the documentation it is referred
to as the "Agent root directory". This setting shall point
to a local direcory in which the agent works. If you will
consider renaming the setting to match the better term
> Am 21.08.2020 um 12:02 schrieb 'christop...@googlemail.com' via Jenkins Users
> :
>
>
> I have two different kinds of jobs:
> one is installing all the requirements for a job from a storage, building one
> package and collecting warnings and cppcheck results with warnings ng. Here
>
sounds like the user is valid but not a member of any groups. Is that
possible?
On Thursday, August 20, 2020 at 1:28:21 PM UTC-4 Mk wrote:
> Hi Team,
>
> I am trying to configure LDAP(AD) Authentication in our Jenkins, Below is
> my configuration settings, But test LDAP connection is
Thanks a lot once again, Jeremy. Just curious. Are there any major
functional differences between Declarative and Scripted? I thought there
are only minor differences. So, if something works in Scripted approach, it
should work in Declarative approach as well, right?
With that said, you have
if you don't wait, then propagate is meaningless .. it can't be done.
I find scripted is more flexible, but any time a system gives you more rope,
you have to be careful not to hang yourself.
---
Jeremy Mordkoff
Director of Engineering Services
Hi Jeremy, Thanks for the reply. Actually *ldapsearch* command on jenkins
master server terminal works. Below is the response.
ldapsearch -x -h ad-ldap-server.com -p 389 -D
"CN=jenkins,OU=Users,OU=Division,OU=Team,DC=domain,DC=com" -b
"OU=Users,OU=Division,OU=Team,DC=domain,DC=com"
Hi,
I have a JobA defined in Jenkins Pipeline. When JobA builds successfully, I
trigger JobB from the Post step. But, if JobB fails in some step, it marks
JobA also as Failed.
Is there a way (some setting or option) to ignore the failure in JobB so
that it doesn't fail JobA (since it built
12 matches
Mail list logo
