The [jenkins] section has a new timeout setting which would be nice to be able to configure via puppet.

http://docs.openstack.org/infra/jenkins-job-builder/execution.html#job-builder-section

A simple job as defined in the spec test of

{ 'test' => { 'name' => 'test' } }

Should produce

---
- job:
    name: "test"

but instead produces

---
 -job:
    test:
 -job:
     name: "test"

• Puppet: 4.3.2
• Ruby: 2.1.8
• Distribution: Centos 7
• Module version: 2.0.0

Currently the default parameters are:

  $git_url          = 'https://git.openstack.org/openstack-infra/jenkins-job-builder'

But when run it complains:

==> jenkins2: Error: Could not get latest version: HTTP-Error: 403 Must access using HTTPS instead of HTTP
==> jenkins2: Error: /Stage[main]/Jenkins_job_builder::Install/Package[jenkins-job-builder]/ensure: change from 1.6.1 to latest failed: Could not get latest version: HTTP-Error: 403 Must access using HTTPS instead of HTTP

We've seen job creation fail if/when Jenkins is unavailable - there should be a mechanism whereby the job creation is retried for a number attempts, and these tries should be configurable.

• Puppet: 4.3.2
• Ruby: 2.1.8
• Distribution: Centos 7
• Module version: 2.0.0

currently when installing from git the pip install puts in /usr/bin/jenkins-jobs not /usr/local/bin/jenkins-jobs

https://github.com/voxpupuli/puppet-jenkins_job_builder/blob/master/manifests/job.pp#L70

This needs to be conditionalized better or use actual exec with path

The discussion came up of this module should get archived. Should someone want to keep this module around, just comment here.
If no comments to keep this around arise in the new weeks, we will move forward with archiving.

Since we're using a refreshonly => true operation for the job update exec, this can lead to a situation where when a job update fails, and the job yaml file is not subsequently updated, the next puppet run will appear to be successful, even though the job update operation is in a broken state.

Affected Puppet, Ruby, OS and module versions/distributions

• Puppet: 3.8.7
• Ruby: 1.9.3p484
• Distribution: Ubuntu 14.04.5 LTS (affects all versions packages.ubuntu.com)
• Module version: 2.1.0 (also affects master)

What are you seeing

When using this module on Ubuntu, the following occurs every puppet run:

Notice: /Stage[main]/Jenkins_job_builder::Install/Package[python-argparse]/ensure: ensure changed 'purged' to 'present'

This is because the package is virtual, so Puppet doesn't see it as installed. It will always try to reinstall it:

# apt-cache show python-argparse
N: Can't select versions from package 'python-argparse' as it is purely virtual
N: No packages found

# apt-get install python-argparse
Reading package lists... Done
Building dependency tree
Reading state information... Done
Note, selecting 'libpython2.7-stdlib' instead of 'python-argparse'
libpython2.7-stdlib is already the newest version.

According to packages.ubuntu.com, this is virtual package is satisfied by libpython2.7-stdlib in all documented versions (trusty through zesty, and artful).

To save translating the docs for jenkins builder from yaml to ruby could the job define also have an option to take just the contents of a yaml file? Say as $config_yaml?

Hullo,

I'm using 1.1.0 of your Puppet module (thank you :) and when I provide Puppet hiera YAML for a Jenkins job genersys:

          publishers:
            - trigger-parameterized-builds:
              - project: "genersys-outgoing-promotion-filewriter. genersys-outgoing-promotion-ftp-reader, genersys-outgoing-promotion-ftp-writer, genersys-outgoing-promotion-service"
                condition: UNSTABLE_OR_BETTER
                predefined-parameters: PKG_VERSION=$PKG_VERSION

I get this output in /tmp/jenkins-genersys.yaml:

       publishers:
        - trigger-parameterized-builds:
           - condition: "UNSTABLE_OR_BETTER"
           - predefined-parameters: "PKG_VERSION=$PKG_VERSION"
           - project: "genersys-outgoing-promotion-filewriter. genersys-outgoing-promotion-ftp-reader, genersys-outgoing-promotion-ftp-writer, genersys-outgoing-promotion-service"

The jenkins-jobs run fails with KeyError: 'project' :(

I found that I need to manipulate the /tmp/jenkins-genersys.yaml to look like this in order for it to be processed successfully by jenkins-jobs

       publishers:
        - trigger-parameterized-builds:
           - project: "genersys-outgoing-promotion-filewriter, genersys-outgoing-promotion-ftp-reader, genersys-outgoing-promotion-ftp-writer, genersys-outgoing-promotion-service"
             predefined-parameters: PKG_VERSION=$PKG_VERSION
             condition: "UNSTABLE_OR_BETTER"

Is there a different way in Puppet hiera that I need to express the configuration to get the desired output?

Cheers,
Gavin.

The official jenkins module has added this support.

https://github.com/jenkinsci/puppet-jenkins#experimental-types-and-providers

Since there are now parameters for the exec, that implement retry options, the /bin/sleep part of the command executed is no longer required. We should deprecate this functionality, and remove it in a future release.

Fedora and EL7 both have support for installing JJB as RPMs. Is this something you'd be open for in this module?

When I define my config in hiera, the resulting YAML created on disk at /tmp/jenkins-job_name.yaml can differ considerably from the structure in hiera, and I sometimes have unexpected results when setting variables in hiera as well; for example, if I create a nested field with a literal ", it doesn't get created in the job correctly ..
Example:

my_amazing_job:
  delay: 15
  config:
    - job:
        name: my_amazing_job
        description: 'my_amazing_job'
        project-type: freestyle
        scm:
          - git:
              wipe-workspace: false
              credentials-id: 88888888-4444-4444-4444-888888888888
              url: "[email protected]:puppet-community/puppet-jenkins_job_builder.git"
              git-config-name: "User Deploy"
              git-config-email: "[email protected]"
              branches:
                - "*/master"
        wrappers:
          - ansicolor
        builders:
          - sbt:
              name: 'sbt'
              actions: "\"release with-defaults\""
              sbt-flags: '-Dsbt.log.noformat=true -Dsbt.override.build.repos=false'

results in a config file on disk with:

[root@jenkins ~]# cat /tmp/jenkins-my_amazing_job.yaml

---
  - job:
       builders:
        - sbt:
           actions: "release with-defaults\""
           name: "sbt"
           sbt-flags: "-Dsbt.log.noformat=true -Dsbt.override.build.repos=false"
       description: "my_amazing_job"
       name: "my_amazing_job"
       project-type: "freestyle"
       scm:
        - git:
           branches:
             - "*/master"
           credentials-id: "88888888-4444-4444-4444-888888888888"
           git-config-email: "[email protected]"
           git-config-name: "User Deploy"
           url: "[email protected]:puppet-community/puppet-jenkins_job_builder.git"
           wipe-workspace: "false"
       wrappers:
         - "ansicolor"

The config from hiera is being sorted .. and although this is not a bad thing in itself, the quoted string with escaped " is being incorrectly interpreted:

"\"release with-defaults\""

becomes:

"release with-defaults\""

and results in a string in the job with only a closing ", and not the entire string quoted

A proposed fix would be the one suggested by @choffee in #7 - to use to_yaml method in template, instead of the sort_yaml which is currently being used

I've run into an issue where a feature in jenkins_job_builder isn't available in the latest package on PyPi, and think it would be great to be able to install directly from git - do you think this would be a welcome addition?

Would it make sense to source in the jobs directory (could be it's own repo) and then have this plugin support building all the jobs in that directory?

similar to:
jenkins-jobs -l DEBUG --conf jenkins_job.ini --ignore-cache update -r jobs