Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-28030

The .chef folder is not written on the first build of a job

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      I've had a report that on the first time a job runs, the .chef folder is not being created in the workspace.

      It appears to be related to jobs that are checking out a git repo (or maybe code checkout in general) in the first build.

        Attachments

          Activity

          Descending order - Click to sort in ascending order
          Hide
          Permalink
          tfitch Tyler Fitch added a comment -

          Marking as closed.

          Show
          tfitch Tyler Fitch added a comment - Marking as closed.
          Hide
          Permalink
          tfitch Tyler Fitch added a comment -

          Fixed in release 0.1.4 of the Chef Identity plugin.

          Show
          tfitch Tyler Fitch added a comment - Fixed in release 0.1.4 of the Chef Identity plugin.
          Hide
          Permalink
          scm_issue_link SCM/JIRA link daemon added a comment -

          Code changed in jenkins
          User: Tyler Fitch
          Path:
          src/main/java/io/chef/jenkins/ChefIdentityBuildWrapper.java
          http://jenkins-ci.org/commit/chef-identity-plugin/a19a22631924197975c68521bd6305d2dfc3d147
          Log:
          JENKINS-28030 I was using the preCheckout method to write the .chef folder when I should have been using setUp. Now .chef folder won't be erased by SCM checkout on first job run.

          Show
          scm_issue_link SCM/JIRA link daemon added a comment - Code changed in jenkins User: Tyler Fitch Path: src/main/java/io/chef/jenkins/ChefIdentityBuildWrapper.java http://jenkins-ci.org/commit/chef-identity-plugin/a19a22631924197975c68521bd6305d2dfc3d147 Log: JENKINS-28030 I was using the preCheckout method to write the .chef folder when I should have been using setUp. Now .chef folder won't be erased by SCM checkout on first job run.
          Hide
          Permalink
          tfitch Tyler Fitch added a comment -

          Actually, ended up being much simpler and just an API error on my side using preCheckout() instead of setUp(). Will have this change deployed shortly.

          Show
          tfitch Tyler Fitch added a comment - Actually, ended up being much simpler and just an API error on my side using preCheckout() instead of setUp(). Will have this change deployed shortly.
          Hide
          Permalink
          tfitch Tyler Fitch added a comment -

          This is basically identical to this issue from another "Build Environment" plugin. https://issues.jenkins-ci.org/browse/JENKINS-12770

          Looks like I'll be refactoring the Chef Identity plugin to be a "Build Step" instead of a "Build Environment" setting. Thus ensuring it runs after the SCM checkout phase and makes the first run of jobs succeed.

          Show
          tfitch Tyler Fitch added a comment - This is basically identical to this issue from another "Build Environment" plugin. https://issues.jenkins-ci.org/browse/JENKINS-12770 Looks like I'll be refactoring the Chef Identity plugin to be a "Build Step" instead of a "Build Environment" setting. Thus ensuring it runs after the SCM checkout phase and makes the first run of jobs succeed.

            People

            Assignee:
            tfitch Tyler Fitch
            Reporter:
            tfitch Tyler Fitch
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: