Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Puppet improvements #225

Merged
merged 6 commits into from
Nov 19, 2019
Merged

Puppet improvements #225

merged 6 commits into from
Nov 19, 2019

Conversation

CyrilBrulebois
Copy link

Hi Mika,

You'll find a couple of small puppet improvements, a heavy simplification (factorizing the require on Package['jenkins']), and also a bugfix for Jenkins 2.176.2 regarding detached plugins.

Unfortunately, even with those patches, I'm getting some other issues due to plugin dependencies, that I'll document separately, in an issue.

Thanks for considering,
Cyril, with his DEBAMAX hat.

Either fix the missing {} around variable names, or drop quotes around
strings that only consist of a single variable.

Signed-off-by: Cyril Brulebois <cyril@debamax.com>
Signed-off-by: Cyril Brulebois <cyril@debamax.com>
Signed-off-by: Cyril Brulebois <cyril@debamax.com>
It shouldn't be needed when using apply.sh, but can help integrate this
jenkins_debian_glue.pp file inside a bigger Puppet infrastructure.

One would usually replace this with a call to stdlib's ensure_packages
function, but at least dependencies are documented and don't need to be
changed.

Signed-off-by: Cyril Brulebois <cyril@debamax.com>
There's little point in specifying this attribute in each and every
jenkins::plugin::install entry since all of them use it. So switch to
using a default value for all entries.

[ Best viewed with --patience ]

Signed-off-by: Cyril Brulebois <cyril@debamax.com>
From the LTS changelog of 2.176.2 (2019-07-17):

     Make sure detached plugins (plugins whose functionality used to be
     part of Jenkins itself) are installed upon Jenkins startup when
     needed as implied dependencies of other plugins which were already
     present. This simplifies compatibility for specialized installation
     scenarios not using the update center, such as when Jenkins is run
     from a Docker image prepackaged with some plugins. (issue 57528)

More details in: https://issues.jenkins-ci.org/browse/JENKINS-57528

Signed-off-by: Cyril Brulebois <cyril@debamax.com>
@CyrilBrulebois
Copy link
Author

If that's helpful, I can share logs from clean installations with:

  • nothing forced
  • only bouncycastle-api forced
  • both bouncycastle-api and junit forced

@mika
Copy link
Owner

mika commented Nov 19, 2019

Meh, really sorry that this took way longer than anticipated. :( But finally found time for it and once I fixed some further things with a) Debian/buster (gnupg not present) and b) git-client plugin dependency I could actually successfully test it. :)

Thanks a bunch for the PR and fixes, highly appreciated! 👍

@CyrilBrulebois CyrilBrulebois deleted the puppet-improvements branch November 24, 2019 11:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants