ISSUE TYPE

• Bug Report

COMPONENT NAME

jenkins_job

ANSIBLE VERSION

ansible 2.3.0 (devel a236cbf3b4) last updated 2016/12/08 13:23:10 (GMT +200)

CONFIGURATION

N/A

OS / ENVIRONMENT

N/A

SUMMARY

The jenkins_job module cannot handle creating jobs of type jenkins.branch.OrganizationFolder.

Background:
If we use the plugins

• bitbucket
• cloudbees-bitbucket-branch-source

to integrate with Bitbucket, then there's the option to create a kind of wrapper job that only has the purpose of scanning Bitbucket projects for repositories (and therein a 'Jenkinsfile'). Something similar exists for GitHub and possibly other providers.

If we use the jenkins_job to create such a wrapper job it fails, because it cannot determine whether this job is disabled or not. The JSON response for such job doesn't include the 'color' attribute which the module looks for and there is in general no option for disabling such job apart from disabling its polling.

TL;DR:
The module does

def get_job_status(self):
    try:
        return self.server.get_job_info(self.name)['color'].encode('utf-8')
    except Exception:
        e = get_exception()
        self.module.fail_json(msg='Unable to fetch job information, %s' % str(e))

and throws this exception because there is no color attribute in the response.

The good news - the rest of the module just works if you hack around this check like

def get_job_status(self):
    return "enabled"

Now my suggestion is to make the module ignore this check for this kind of job.

STEPS TO REPRODUCE

An example job template which I created for a generic job role can be found here:
https://gist.github.com/tumbl3w33d/a1a986fa73da6adc0078532a5578782a

This should allow you to choose the right identifiers for such kind of wrapper jobs, so you could skip the failing check.

An example of a JSON response of the jenkins api for such a wrapper job:
https://gist.github.com/tumbl3w33d/04379f013e1e58dff13da60d46234975

EXPECTED RESULTS

The wrapper job gets created.

ACTUAL RESULTS

fatal: [targethost]: FAILED! => {"changed": false, "failed": true, "msg": "Unable to fetch job information, 'color'"}

I'd be happy to support you with testing a possible pull request because it's quite hard for you to reproduce this setup.