title: How to override an attribute for a specific job when working with Jenkins Job Builder (JJB)
body: <p>We have got a Jenkins setup (at the moment not managed with the Jenkins Job Builder) where every web project has 5 very similar Jenkins jobs. This is a simplified Jenkins Job Builder yaml file which could work for our needs:</p>
  
  <pre><code>- defaults:
      name: global
      project-type: 'freestyle'
      disabled: false
      buildTargets: 'build'
  - job-template:
      name: '{jobNameFirstSegment}-{jobNameSecondSegment}'
      defaults: global
      builders:
        - ant:
            targets: '{buildTargets}'
            buildfile: 'build.xml'
  - project:
      name: lorem
      jobNameFirstSegment:
        - foo:
            displayNameFirstSegment: 'Foo'
            urlGitRepository: 'git@bitbucket.org:mycompany/foo.git'
        - bar:
            displayNameFirstSegment: 'Bar'
            urlGitRepository: 'git@bitbucket.org:mycompany/bar.git'
        - baz:
            displayNameFirstSegment: 'Baz'
            urlGitRepository: 'git@bitbucket.org:mycompany/baz.git'
      jobNameSecondSegment:
        - lorem:
            buildTargets: 'build-lorem'
        - ipsum:
            buildTargets: 'build-ipsum'
        - dolor:
            buildTargets: 'build-dolor'
        - sit:
            buildTargets: 'build-sit'
        - amet:
            buildTargets: 'build-amet'
      jobs:
        - '{jobNameFirstSegment}-{jobNameSecondSegment}'
  </code></pre>
  
  <p>This yaml file results in 15 Jenkins jobs - all are NOT disabled:</p>
  
  <ul>
  <li>foo-lorem</li>
  <li>foo-ipsum</li>
  <li>foo-dolor</li>
  <li>foo-sit</li>
  <li>foo-amet</li>
  <li>bar-lorem</li>
  <li>bar-ipsum</li>
  <li>bar-dolor</li>
  <li>bar-sit</li>
  <li>bar-amet</li>
  <li>baz-lorem</li>
  <li>baz-ipsum</li>
  <li>baz-dolor</li>
  <li>baz-sit</li>
  <li>baz-amet</li>
  </ul>
  
  <p>Is it possible with this kind of setup to disable a specific Jenkins job? I could not find out how to override the "disabled" attribute for e.g. the Jenkins job "foo-lorem". How can this be achieved?</p>
  
  <p>Infact we would need to have the possibility to be able to override any attribute of any Jenkins job if needed. Is this doable? How?</p>