Hi Keshav,
sorry for interfering, but I think Gianluca’s pseudo code and hint should
actually help you:
* Job A will wait for both job B and job C to be finished
* and only if both were successful, then and only then continue with
triggering job D in the next stage
HTH Reinhold
From:
I have fixed it. Each time when we change/update the *"Display Name LDAP
attribute" *value in LDAP configuration section, We need to delete the user
from people category and need to login. Post that it displays the
configured settings.
On Wednesday, September 2, 2020 at 9:57:31 AM UTC+5:30, Mk
Are you running in a corporate environment that uses a proxy to talk to the
Internet? If so then you'll need to ensure that the certificate used by the
proxy (assuming it intercepts TLS traffic) is loaded in the "cacerts" file
for the given version of Java. Unfortunately I'm not sure where that
res
master is running current JRE 8
java.version
1.8.0_261
I was able to upgrade from jenkins-2.222.3 to jenkins-2.235.1 at 06/30/20.
I am puzzled by this error.
On Tuesday, September 1, 2020 at 6:54:23 PM UTC-7 Mark Waite wrote:
> That may indicate that the Java installation used by your Jenkins
Team, Is it possible to display only *First name + Sur-name* in Jenkins?
On Friday, August 28, 2020 at 9:56:39 AM UTC+5:30, Mk wrote:
>
> Dear Team,
>
> Now our LDAP Authentication working fine. I have question regarding "*Display
> Name LDAP attribute*: *displayname*" i have configured like thi
That may indicate that the Java installation used by your Jenkins on
WIndows does not recognize the SSL certificates that Let's Encrypt provides
for the Jenkins update center.
Check the Java version from the "System Information" page in "Manage
Jenkins". Java 8u262 is the most recent version of J
I am running Jenkins 2.235.1 on Windows. I am not able to Update Jenkins
and Plugin failed to update. I have tried to installed self sign SSL Cert
and does not solve the issue. What is the cause and how to fix?
Failure -
sun.security.provider.certpath.SunCertPathBuilderException: unable to
I already used the following declarative cleanup pipeline for Jenkin,
according to the feature of my code, I have to convert into the scripted
pipeline, how I can convert it to the scripted pipeline?
stage ('Cleanup Feature Releases') {
steps {
script {
envParameters
Hi Gianluca,
I can't trigger Job D directly from Job A. Actually in my project we are
running integration tests in Job B and UI tests in Job C. So if both the
builds are green then only i can merge the code to master in Job D. But
thanks for your answer I will try it.
Thanks,
Keshav.
On Wed, S
Hi, for some obscure reason, the machine Window update were not totally up to
date. Performing the all the update seem to have fix the issue. So it seem like
old Windows 10 build aren’t working. Sorry for all the noise. Did try with and
without the anti-virus, no difference. There was nothing me
Hi,
why not triggering Job D directly from job A ? In this way, if you put that
in a stage after job B and job C is triggered ... it will only be triggered
if both succedded:
stage("Run B and C") {
steps {
parallel(
"job B": { buildJob ... },
"job C:" { build Job ... },
}
stag
>Does it require the user to be admin?
no, a regular user should work if has access to the workdir
>Maybe this unresolved issue is still there!?
https://issues.jenkins-ci.org/browse/JENKINS-48850
this issue has a different stack trace and fails in another place.
The issue here happens after t
Hi,
i have stuck with a small issue... i have a job A which triggers job B and
job C. for job B and job C downstream job is job D i need this job D is
to be triggered when job B and job C both are success. i have tried with
"Build after other projects are build" with "trigger only if build
Maybe this unresolved issue is still there!?
https://issues.jenkins-ci.org/browse/JENKINS-48850
From: jenkinsci-users@googlegroups.com On
Behalf Of Jérôme Godbout
Sent: September 1, 2020 2:12 PM
To: jenkinsci-users@googlegroups.com
Subject: RE: Windows client ssh connection error
Did try withou
Did try without the firewall and it doesn’t work either, !?!? Anyone got an
idea what it is actually doing that might not work?!? Both machine are on the
same network, no ip conflict. If I delete the remoting.jar and the folders into
c:\JenkinsSlave it get created again, so the connection is hap
Hi,
Is there any special requirements? (ssh does work from both Linux and Windows
to this machine, also from the Jenkins master user account too). Seem like
starting the slave fails, anything to do with firewall or something like that?
here the node that work (Windows 10 64 bits):
[09/01/20 09:
Yes, I created the folder and give the user (I made a local user for this
called Jenkins). The user has full control over that folder. Does it require
the user to be admin?
The following are created:
c:\JenkinsSlave\
remoting.jar
remoting\
No nothing
From: jenkinsci-users@googlegroups.com On
Behalf Of Ivan Fernandez Calvo
Sent: September 1, 2020 12:20 PM
To: Jenkins Users
Subject: Re: Windows client ssh connection error
when you enter on that Windows machine though SSH manually, Do you have a long
banner at the beginning that y
We also updated the FAQ:
https://github.com/jenkinsci/pipeline-maven-plugin/blob/master/FAQ.adoc
It is linked from the bottom of the README (AFAIK for now the plugins site
cannot handle the usage of inclusions)
On Tue, Sep 1, 2020 at 5:11 PM Arnaud Héritier wrote:
> Thanks to we now have convert
when you enter on that Windows machine though SSH manually, Do you have a
long banner at the beginning that you do not have in the other machine?
El martes, 1 de septiembre de 2020 a las 18:04:53 UTC+2, Ivan Fernandez
Calvo escribió:
> Has the user that connect permissions on c:\JenkinsSlave? I
Has the user that connect permissions on c:\JenkinsSlave? Is the folder
c:\JenkinsSlave\remoting created? Are there some err_pid* files or log
files in c:\JenkinsSlave folder?
El martes, 1 de septiembre de 2020 a las 17:48:39 UTC+2, Jérôme Godbout
escribió:
> Hi,
>
>
>
> I did solve my issue
Hi,
I did solve my issue with the ssh agent I had earlier, but when I try to do the
same on another Windows client machine I get this weird error below. The log on
the slave are empty (c:\JenkinsSlave\remoting). The error is a bit vague and I
have no clue what is wrong. I can connect with ssh,
Thanks to we now have converted the documentation from Confluence to
Asciidoc :
https://github.com/jenkinsci/pipeline-maven-plugin/blob/master/README.adoc
I hope the rendering won't be too bad on the plugins site
All feedbacks (and PRs) are welcome
On Mon, Aug 31, 2020 at 7:54 PM Arnaud Héritier
Hello, all
How is `matrix' supposed to interact with `checkout'? If I
have several axes, of which some require change of agent (OS
version), and some do not (Debug or Release mode), where
shall place the `checkout' step? Currently, I have it at
this path in my Jenkinsfile:
pipeline -> st
The problem was with the folder name `iText%207%20.NET`, which is an
urlencoded version of `iText 7 .NET`. Apparently Jenkins can't handle
urlencoded spaces in folder names.
I renamed the folder to `itext_7_dotnet` and then used
build job: "itext_7_dotnet/sharpen/${java.net.URLEncoder.encod
25 matches
Mail list logo
