I have a 3 step sequence of 4 jobs, (1) TriggerBld, (2) DoBuild,
(3a)Test1 and (3b)Test2. These are linked by a fingerprinted file
passed down from TriggerBld (which is triggered by a Subversion
change) to DoBuild to Test1 and Test2. When using the dashboard to
examine a TriggerBld build, it shows
I am a bit blown that you can run LDAP authentication on Jenkins without
assigning a DC. How can that work properly?
I'm not using LDAP, but Active Directory. A lot of Active Directory is
built upon LDAP, but one of Active Directory's features is that I
don't have to specify a domain
If you examine a TriggerBld build, click on See Fingerprints on the
sidebar, you see the fingerprinted file? When you click on the More
info link next to it, what do you get? Jenkins should tell you it has
seen the fingerprint in TriggerBld, DoBuild, Test1 and Test2. If it
doesn't, then you are
Thanks for the reply Sami, the fingerprinted file is being propagated
down to the test jobs. When I use the See Fingerprints on
TriggerBld, and then more details, I get This file has been used
in ... and all 4 jobs (with the correct build numbers).
The same happens when I use the See
Issue 13531 (https://issues.jenkins-ci.org/browse/JENKINS-13531) is ready to be
closed once https://github.com/jenkinsci/s3-plugin/pull/4 is merged into the
main line.
I've been using a self-built snapshot with the patch supplied for the last week
now.
Thanks,
Grant Limberg
I'm sorta wedged at this same place now.
While I can log in, the manage' page (among others) is NOT being displayed
because there is now an error about First name, Last name having an invalid
character in there.
How do I even upgrade if I can't reach the plugin pages?
