Not sure if this is really what fixed the problem but here goes:
Destroyed the Docker instance running my Jenkins installation and rebuilt
it using LTS instead of the "latest and greatest bleeding edge" version.
Docker is a good thing that way. :-)
Now have a stripped down version and my simple s
OK... seems this is somehow related to
https://issues.jenkins-ci.org/browse/JENKINS-45260
is there at least a work-around?
On Wed, Oct 17, 2018 at 10:16 AM Peter Berghold
wrote:
> Interestingly enough on a Jenkins server i manage where I have working
> shared libraries (multiple) I don't use t
Interestingly enough on a Jenkins server i manage where I have working
shared libraries (multiple) I don't use the @Library form at all. I tried
it on this other Jenkins server (the one I'm trying to *get* working) and
it didn't work.
In my first attempt I simply used:
@Library('lib3') _
which
Are you missing the @Library import in your pipeline? Or does your shared
library have a load implicitly declared?
https://jenkins.io/doc/book/pipeline/shared-libraries/
On Tue, Oct 16, 2018 at 14:49 Peter Berghold
wrote:
> Here is a tree of a very simple "library" I set up:
>
> ├── build.xm
Here is a tree of a very simple "library" I set up:
├── build.xml
├── manifest.mf
├── nbproject
│ ├── build-impl.xml
│ ├── genfiles.properties
│ ├── groovy-build.xml
│ ├── private
│ │ ├── config.properties
│ │ ├── private.properties
│ │ └── private.xml
│ ├── project.propertie
