Skip to content

Old version of Jenkins is used (library/jenkins vs jenkins/jenkins) resulting in invalid plugin configs #3

Description

@espoelstra

When attempting to run this the job wasn't available initially due to conflicts between plugins. When using the plugins.sh to install Jenkins plugins in Docker it ALWAYS uses the latest versions of plugins, and often this requires a newer version of Jenkins. It may be beneficial to switch over to jenkins/jenkins:lts if you want to keep things working without changes to Jenkins blowing things up.

I'm going to give that a shot and may submit a pull request, as I was able to just upgrade Jenkins from the alerts button in the UI and after a restart things mostly worked minus the workarounds in #1 and #2 that I had to use. There is also an issue with the Cobertura plugin not liking the < or > in the code and freaking out, but the build still completed.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions