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

Builds disappear some time after renaming job

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved (View Workflow)
    • Priority: Blocker
    • Resolution: Fixed
    • Component/s: core
    • Environment:
      Any
      Observed in LTS 1.509.2, LTS 1.509.3, 1.528, 1.532-SNAPSHOT (private-09/12/2013 13:02 GMT-jenkins)
    • Similar Issues:

      Description

      Builds disappear from Jenkins some time after a project has been renamed.

      We upgraded from 1.492 on July 4th and then renamed one build. Four days later we realized the renamed build had lost some or all of its builds. We recovered the builds by reloading from disk this morning. Later in the afternoon, another project was renamed, and some of its builds went missing too.

      Here are the builds of the renamed job on disk:

      $ ls -l
      total 25
      lrwxrwxrwx 1 jenkins jenkins  19 Mar  1 13:29 1 -> 2013-03-01_13-29-26
      lrwxrwxrwx 1 jenkins jenkins  19 Mar  1 13:31 2 -> 2013-03-01_13-31-20
      drwxrwxr-x 3 jenkins jenkins 141 Jul  9 08:24 2013-03-01_13-29-26
      drwxrwxr-x 3 jenkins jenkins 141 Jul  9 08:24 2013-03-01_13-31-20
      drwxrwxr-x 3 jenkins jenkins 141 Jul  9 08:24 2013-03-01_13-32-42
      drwxrwxr-x 3 jenkins jenkins 141 Jul  9 08:24 2013-03-28_09-56-31
      drwxrwxr-x 3 jenkins jenkins 141 Jul  9 08:24 2013-03-28_10-02-11
      lrwxrwxrwx 1 jenkins jenkins  19 Mar  1 13:32 3 -> 2013-03-01_13-32-42
      lrwxrwxrwx 1 jenkins jenkins  19 Mar 28 09:56 4 -> 2013-03-28_09-56-31
      lrwxrwxrwx 1 jenkins jenkins  19 Mar 28 10:02 5 -> 2013-03-28_10-02-11
      lrwxrwxrwx 1 jenkins jenkins   1 Jul  9 14:23 lastFailedBuild -> 4
      lrwxrwxrwx 1 jenkins jenkins   1 Jul  9 14:23 lastStableBuild -> 5
      lrwxrwxrwx 1 jenkins jenkins   1 Jul  4 11:18 lastSuccessfulBuild -> 5
      lrwxrwxrwx 1 jenkins jenkins   2 Jul  9 14:23 lastUnstableBuild -> -1
      lrwxrwxrwx 1 jenkins jenkins   1 Jul  9 14:23 lastUnsuccessfulBuild -> 4
      

      The disk shows 5 builds, 1 through 5, but the GUI only shows 4 and 5, it is missing 1, 2, and 3.

      JENKINS-19650 contains steps to reliably reproduce the problem.

      How do I debug this? One thing looks odd: the dates on the symbolic links differ from the dates in the build history, and differ from the directories they actually link.

        Attachments

          Issue Links

            Activity

            deepchip Martin d'Anjou created issue -
            deepchip Martin d'Anjou made changes -
            Field Original Value New Value
            Description Builds disappear from build history in Jenkins LTS 1.509.2.

            We upgraded from 1.492 on Thursday before a long weekend, so not much happened over the weekend. Four days later, that is today, we lost some builds. We recovered them by reloading from disk this morning. Later in the afternoon of the same day, a project was renamed, and some of its builds went missing.

            Here are the builds of the renamed job on disk:
            {noformat}
            $ ls -l
            total 25
            lrwxrwxrwx 1 jenkins jenkins 19 Mar 1 13:29 1 -> 2013-03-01_13-29-26
            lrwxrwxrwx 1 jenkins jenkins 19 Mar 1 13:31 2 -> 2013-03-01_13-31-20
            drwxrwxr-x 3 jenkins jenkins 141 Jul 9 08:24 2013-03-01_13-29-26
            drwxrwxr-x 3 jenkins jenkins 141 Jul 9 08:24 2013-03-01_13-31-20
            drwxrwxr-x 3 jenkins jenkins 141 Jul 9 08:24 2013-03-01_13-32-42
            drwxrwxr-x 3 jenkins jenkins 141 Jul 9 08:24 2013-03-28_09-56-31
            drwxrwxr-x 3 jenkins jenkins 141 Jul 9 08:24 2013-03-28_10-02-11
            lrwxrwxrwx 1 jenkins jenkins 19 Mar 1 13:32 3 -> 2013-03-01_13-32-42
            lrwxrwxrwx 1 jenkins jenkins 19 Mar 28 09:56 4 -> 2013-03-28_09-56-31
            lrwxrwxrwx 1 jenkins jenkins 19 Mar 28 10:02 5 -> 2013-03-28_10-02-11
            lrwxrwxrwx 1 jenkins jenkins 1 Jul 9 14:23 lastFailedBuild -> 4
            lrwxrwxrwx 1 jenkins jenkins 1 Jul 9 14:23 lastStableBuild -> 5
            lrwxrwxrwx 1 jenkins jenkins 1 Jul 4 11:18 lastSuccessfulBuild -> 5
            lrwxrwxrwx 1 jenkins jenkins 2 Jul 9 14:23 lastUnstableBuild -> -1
            lrwxrwxrwx 1 jenkins jenkins 1 Jul 9 14:23 lastUnsuccessfulBuild -> 4
            {noformat}

            How do I debug this? One thing looks odd: the dates on the symbolic links differ from the dates in the build history, and differ from the directories they actually link.
            Builds disappear from build history in Jenkins LTS 1.509.2.

            We upgraded from 1.492 on Thursday before a long weekend, so not much happened over the weekend. Four days later, that is today, we lost some builds. We recovered them by reloading from disk this morning. Later in the afternoon of the same day, a project was renamed, and some of its builds went missing.

            Here are the builds of the renamed job on disk:
            {noformat}
            $ ls -l
            total 25
            lrwxrwxrwx 1 jenkins jenkins 19 Mar 1 13:29 1 -> 2013-03-01_13-29-26
            lrwxrwxrwx 1 jenkins jenkins 19 Mar 1 13:31 2 -> 2013-03-01_13-31-20
            drwxrwxr-x 3 jenkins jenkins 141 Jul 9 08:24 2013-03-01_13-29-26
            drwxrwxr-x 3 jenkins jenkins 141 Jul 9 08:24 2013-03-01_13-31-20
            drwxrwxr-x 3 jenkins jenkins 141 Jul 9 08:24 2013-03-01_13-32-42
            drwxrwxr-x 3 jenkins jenkins 141 Jul 9 08:24 2013-03-28_09-56-31
            drwxrwxr-x 3 jenkins jenkins 141 Jul 9 08:24 2013-03-28_10-02-11
            lrwxrwxrwx 1 jenkins jenkins 19 Mar 1 13:32 3 -> 2013-03-01_13-32-42
            lrwxrwxrwx 1 jenkins jenkins 19 Mar 28 09:56 4 -> 2013-03-28_09-56-31
            lrwxrwxrwx 1 jenkins jenkins 19 Mar 28 10:02 5 -> 2013-03-28_10-02-11
            lrwxrwxrwx 1 jenkins jenkins 1 Jul 9 14:23 lastFailedBuild -> 4
            lrwxrwxrwx 1 jenkins jenkins 1 Jul 9 14:23 lastStableBuild -> 5
            lrwxrwxrwx 1 jenkins jenkins 1 Jul 4 11:18 lastSuccessfulBuild -> 5
            lrwxrwxrwx 1 jenkins jenkins 2 Jul 9 14:23 lastUnstableBuild -> -1
            lrwxrwxrwx 1 jenkins jenkins 1 Jul 9 14:23 lastUnsuccessfulBuild -> 4
            {noformat}

            The disk shows 5 builds, 1 through 5, but the GUI only shows 4 and 5, it is missing 1, 2, and 3.

            How do I debug this? One thing looks odd: the dates on the symbolic links differ from the dates in the build history, and differ from the directories they actually link.
            deepchip Martin d'Anjou made changes -
            Description Builds disappear from build history in Jenkins LTS 1.509.2.

            We upgraded from 1.492 on Thursday before a long weekend, so not much happened over the weekend. Four days later, that is today, we lost some builds. We recovered them by reloading from disk this morning. Later in the afternoon of the same day, a project was renamed, and some of its builds went missing.

            Here are the builds of the renamed job on disk:
            {noformat}
            $ ls -l
            total 25
            lrwxrwxrwx 1 jenkins jenkins 19 Mar 1 13:29 1 -> 2013-03-01_13-29-26
            lrwxrwxrwx 1 jenkins jenkins 19 Mar 1 13:31 2 -> 2013-03-01_13-31-20
            drwxrwxr-x 3 jenkins jenkins 141 Jul 9 08:24 2013-03-01_13-29-26
            drwxrwxr-x 3 jenkins jenkins 141 Jul 9 08:24 2013-03-01_13-31-20
            drwxrwxr-x 3 jenkins jenkins 141 Jul 9 08:24 2013-03-01_13-32-42
            drwxrwxr-x 3 jenkins jenkins 141 Jul 9 08:24 2013-03-28_09-56-31
            drwxrwxr-x 3 jenkins jenkins 141 Jul 9 08:24 2013-03-28_10-02-11
            lrwxrwxrwx 1 jenkins jenkins 19 Mar 1 13:32 3 -> 2013-03-01_13-32-42
            lrwxrwxrwx 1 jenkins jenkins 19 Mar 28 09:56 4 -> 2013-03-28_09-56-31
            lrwxrwxrwx 1 jenkins jenkins 19 Mar 28 10:02 5 -> 2013-03-28_10-02-11
            lrwxrwxrwx 1 jenkins jenkins 1 Jul 9 14:23 lastFailedBuild -> 4
            lrwxrwxrwx 1 jenkins jenkins 1 Jul 9 14:23 lastStableBuild -> 5
            lrwxrwxrwx 1 jenkins jenkins 1 Jul 4 11:18 lastSuccessfulBuild -> 5
            lrwxrwxrwx 1 jenkins jenkins 2 Jul 9 14:23 lastUnstableBuild -> -1
            lrwxrwxrwx 1 jenkins jenkins 1 Jul 9 14:23 lastUnsuccessfulBuild -> 4
            {noformat}

            The disk shows 5 builds, 1 through 5, but the GUI only shows 4 and 5, it is missing 1, 2, and 3.

            How do I debug this? One thing looks odd: the dates on the symbolic links differ from the dates in the build history, and differ from the directories they actually link.
            Builds disappear from build history in Jenkins LTS 1.509.2.

            We upgraded from 1.492 on July 4th and then renamed some builds. Four days later we realized the renamed builds had gone missing. We recovered them by reloading from disk this morning. Later in the afternoon, another project was renamed, and some of its builds went missing too.

            Here are the builds of the renamed job on disk:
            {noformat}
            $ ls -l
            total 25
            lrwxrwxrwx 1 jenkins jenkins 19 Mar 1 13:29 1 -> 2013-03-01_13-29-26
            lrwxrwxrwx 1 jenkins jenkins 19 Mar 1 13:31 2 -> 2013-03-01_13-31-20
            drwxrwxr-x 3 jenkins jenkins 141 Jul 9 08:24 2013-03-01_13-29-26
            drwxrwxr-x 3 jenkins jenkins 141 Jul 9 08:24 2013-03-01_13-31-20
            drwxrwxr-x 3 jenkins jenkins 141 Jul 9 08:24 2013-03-01_13-32-42
            drwxrwxr-x 3 jenkins jenkins 141 Jul 9 08:24 2013-03-28_09-56-31
            drwxrwxr-x 3 jenkins jenkins 141 Jul 9 08:24 2013-03-28_10-02-11
            lrwxrwxrwx 1 jenkins jenkins 19 Mar 1 13:32 3 -> 2013-03-01_13-32-42
            lrwxrwxrwx 1 jenkins jenkins 19 Mar 28 09:56 4 -> 2013-03-28_09-56-31
            lrwxrwxrwx 1 jenkins jenkins 19 Mar 28 10:02 5 -> 2013-03-28_10-02-11
            lrwxrwxrwx 1 jenkins jenkins 1 Jul 9 14:23 lastFailedBuild -> 4
            lrwxrwxrwx 1 jenkins jenkins 1 Jul 9 14:23 lastStableBuild -> 5
            lrwxrwxrwx 1 jenkins jenkins 1 Jul 4 11:18 lastSuccessfulBuild -> 5
            lrwxrwxrwx 1 jenkins jenkins 2 Jul 9 14:23 lastUnstableBuild -> -1
            lrwxrwxrwx 1 jenkins jenkins 1 Jul 9 14:23 lastUnsuccessfulBuild -> 4
            {noformat}

            The disk shows 5 builds, 1 through 5, but the GUI only shows 4 and 5, it is missing 1, 2, and 3.

            How do I debug this? One thing looks odd: the dates on the symbolic links differ from the dates in the build history, and differ from the directories they actually link.
            deepchip Martin d'Anjou made changes -
            Description Builds disappear from build history in Jenkins LTS 1.509.2.

            We upgraded from 1.492 on July 4th and then renamed some builds. Four days later we realized the renamed builds had gone missing. We recovered them by reloading from disk this morning. Later in the afternoon, another project was renamed, and some of its builds went missing too.

            Here are the builds of the renamed job on disk:
            {noformat}
            $ ls -l
            total 25
            lrwxrwxrwx 1 jenkins jenkins 19 Mar 1 13:29 1 -> 2013-03-01_13-29-26
            lrwxrwxrwx 1 jenkins jenkins 19 Mar 1 13:31 2 -> 2013-03-01_13-31-20
            drwxrwxr-x 3 jenkins jenkins 141 Jul 9 08:24 2013-03-01_13-29-26
            drwxrwxr-x 3 jenkins jenkins 141 Jul 9 08:24 2013-03-01_13-31-20
            drwxrwxr-x 3 jenkins jenkins 141 Jul 9 08:24 2013-03-01_13-32-42
            drwxrwxr-x 3 jenkins jenkins 141 Jul 9 08:24 2013-03-28_09-56-31
            drwxrwxr-x 3 jenkins jenkins 141 Jul 9 08:24 2013-03-28_10-02-11
            lrwxrwxrwx 1 jenkins jenkins 19 Mar 1 13:32 3 -> 2013-03-01_13-32-42
            lrwxrwxrwx 1 jenkins jenkins 19 Mar 28 09:56 4 -> 2013-03-28_09-56-31
            lrwxrwxrwx 1 jenkins jenkins 19 Mar 28 10:02 5 -> 2013-03-28_10-02-11
            lrwxrwxrwx 1 jenkins jenkins 1 Jul 9 14:23 lastFailedBuild -> 4
            lrwxrwxrwx 1 jenkins jenkins 1 Jul 9 14:23 lastStableBuild -> 5
            lrwxrwxrwx 1 jenkins jenkins 1 Jul 4 11:18 lastSuccessfulBuild -> 5
            lrwxrwxrwx 1 jenkins jenkins 2 Jul 9 14:23 lastUnstableBuild -> -1
            lrwxrwxrwx 1 jenkins jenkins 1 Jul 9 14:23 lastUnsuccessfulBuild -> 4
            {noformat}

            The disk shows 5 builds, 1 through 5, but the GUI only shows 4 and 5, it is missing 1, 2, and 3.

            How do I debug this? One thing looks odd: the dates on the symbolic links differ from the dates in the build history, and differ from the directories they actually link.
            Builds disappear from build history in Jenkins LTS 1.509.2.

            We upgraded from 1.492 on July 4th and then renamed one build. Four days later we realized the renamed build had lost some or all of its history. We recovered the history by reloading from disk this morning. Later in the afternoon, another project was renamed, and some of its build history went missing too.

            Here are the builds of the renamed job on disk:
            {noformat}
            $ ls -l
            total 25
            lrwxrwxrwx 1 jenkins jenkins 19 Mar 1 13:29 1 -> 2013-03-01_13-29-26
            lrwxrwxrwx 1 jenkins jenkins 19 Mar 1 13:31 2 -> 2013-03-01_13-31-20
            drwxrwxr-x 3 jenkins jenkins 141 Jul 9 08:24 2013-03-01_13-29-26
            drwxrwxr-x 3 jenkins jenkins 141 Jul 9 08:24 2013-03-01_13-31-20
            drwxrwxr-x 3 jenkins jenkins 141 Jul 9 08:24 2013-03-01_13-32-42
            drwxrwxr-x 3 jenkins jenkins 141 Jul 9 08:24 2013-03-28_09-56-31
            drwxrwxr-x 3 jenkins jenkins 141 Jul 9 08:24 2013-03-28_10-02-11
            lrwxrwxrwx 1 jenkins jenkins 19 Mar 1 13:32 3 -> 2013-03-01_13-32-42
            lrwxrwxrwx 1 jenkins jenkins 19 Mar 28 09:56 4 -> 2013-03-28_09-56-31
            lrwxrwxrwx 1 jenkins jenkins 19 Mar 28 10:02 5 -> 2013-03-28_10-02-11
            lrwxrwxrwx 1 jenkins jenkins 1 Jul 9 14:23 lastFailedBuild -> 4
            lrwxrwxrwx 1 jenkins jenkins 1 Jul 9 14:23 lastStableBuild -> 5
            lrwxrwxrwx 1 jenkins jenkins 1 Jul 4 11:18 lastSuccessfulBuild -> 5
            lrwxrwxrwx 1 jenkins jenkins 2 Jul 9 14:23 lastUnstableBuild -> -1
            lrwxrwxrwx 1 jenkins jenkins 1 Jul 9 14:23 lastUnsuccessfulBuild -> 4
            {noformat}

            The disk shows 5 builds, 1 through 5, but the GUI only shows 4 and 5, it is missing 1, 2, and 3.

            How do I debug this? One thing looks odd: the dates on the symbolic links differ from the dates in the build history, and differ from the directories they actually link.
            Hide
            deepchip Martin d'Anjou added a comment - - edited

            I am observing that the Jenkins GUI only shows the 2 most recent builds in the build history. I am up to build 16, and Jenkins only shows builds 15 and 16 in the build history.

            Show
            deepchip Martin d'Anjou added a comment - - edited I am observing that the Jenkins GUI only shows the 2 most recent builds in the build history. I am up to build 16, and Jenkins only shows builds 15 and 16 in the build history.
            Hide
            integer Kanstantsin Shautsou added a comment -

            do you have any errors in jenkins.log?

            Show
            integer Kanstantsin Shautsou added a comment - do you have any errors in jenkins.log?
            Hide
            oleg_nenashev Oleg Nenashev added a comment -

            In the my case, there's no builds in history after renaming.
            Configuration reload works well, but bug is really annoying.

            Symlinks are corrupted as well:
            lrwxrwxrwx 1 jenkins synopsys 2 Aug 19 00:55 lastFailedBuild -> -1
            lrwxrwxrwx 1 jenkins synopsys 2 Aug 23 07:25 lastStableBuild -> -1
            lrwxrwxrwx 1 jenkins synopsys 2 Aug 23 00:50 lastSuccessfulBuild -> -1
            lrwxrwxrwx 1 jenkins synopsys 2 Aug 19 00:55 lastUnstableBuild -> -1
            lrwxrwxrwx 1 jenkins synopsys 2 Aug 19 00:55 lastUnsuccessfulBuild -> -1

            Show
            oleg_nenashev Oleg Nenashev added a comment - In the my case, there's no builds in history after renaming. Configuration reload works well, but bug is really annoying. Symlinks are corrupted as well: lrwxrwxrwx 1 jenkins synopsys 2 Aug 19 00:55 lastFailedBuild -> -1 lrwxrwxrwx 1 jenkins synopsys 2 Aug 23 07:25 lastStableBuild -> -1 lrwxrwxrwx 1 jenkins synopsys 2 Aug 23 00:50 lastSuccessfulBuild -> -1 lrwxrwxrwx 1 jenkins synopsys 2 Aug 19 00:55 lastUnstableBuild -> -1 lrwxrwxrwx 1 jenkins synopsys 2 Aug 19 00:55 lastUnsuccessfulBuild -> -1
            Hide
            samppa Samuli Saarinen added a comment -

            I'm seeing this on 1.528 as well. Has something to do with renaming jobs. After reloading configuration from disk build history shows all missing builds.

            Show
            samppa Samuli Saarinen added a comment - I'm seeing this on 1.528 as well. Has something to do with renaming jobs. After reloading configuration from disk build history shows all missing builds.
            Hide
            idapperdanman David Ishee added a comment - - edited

            I'm seeing this in LTS 1.509.3 too. When I look at the jobs directory for this job, I see some bad symbolic links:

            lastFailedBuild -> -1
            lastStableBuild -> -1
            lastSuccessfulBuild -> -1
            lastUnstableBuild -> -1
            lastUnsuccessfulBuild -> -1
            

            Reloading the configuration from disk made the history come back.

            Show
            idapperdanman David Ishee added a comment - - edited I'm seeing this in LTS 1.509.3 too. When I look at the jobs directory for this job, I see some bad symbolic links: lastFailedBuild -> -1 lastStableBuild -> -1 lastSuccessfulBuild -> -1 lastUnstableBuild -> -1 lastUnsuccessfulBuild -> -1 Reloading the configuration from disk made the history come back.
            danielbeck Daniel Beck made changes -
            Link This issue is duplicated by JENKINS-19650 [ JENKINS-19650 ]
            danielbeck Daniel Beck made changes -
            Link This issue is related to JENKINS-18694 [ JENKINS-18694 ]
            Hide
            danielbeck Daniel Beck added a comment -

            Edited to avoid confusion with the separate 'Build History' view and add additional information from JENKINS-19650.

            Show
            danielbeck Daniel Beck added a comment - Edited to avoid confusion with the separate 'Build History' view and add additional information from JENKINS-19650 .
            danielbeck Daniel Beck made changes -
            Description Builds disappear from build history in Jenkins LTS 1.509.2.

            We upgraded from 1.492 on July 4th and then renamed one build. Four days later we realized the renamed build had lost some or all of its history. We recovered the history by reloading from disk this morning. Later in the afternoon, another project was renamed, and some of its build history went missing too.

            Here are the builds of the renamed job on disk:
            {noformat}
            $ ls -l
            total 25
            lrwxrwxrwx 1 jenkins jenkins 19 Mar 1 13:29 1 -> 2013-03-01_13-29-26
            lrwxrwxrwx 1 jenkins jenkins 19 Mar 1 13:31 2 -> 2013-03-01_13-31-20
            drwxrwxr-x 3 jenkins jenkins 141 Jul 9 08:24 2013-03-01_13-29-26
            drwxrwxr-x 3 jenkins jenkins 141 Jul 9 08:24 2013-03-01_13-31-20
            drwxrwxr-x 3 jenkins jenkins 141 Jul 9 08:24 2013-03-01_13-32-42
            drwxrwxr-x 3 jenkins jenkins 141 Jul 9 08:24 2013-03-28_09-56-31
            drwxrwxr-x 3 jenkins jenkins 141 Jul 9 08:24 2013-03-28_10-02-11
            lrwxrwxrwx 1 jenkins jenkins 19 Mar 1 13:32 3 -> 2013-03-01_13-32-42
            lrwxrwxrwx 1 jenkins jenkins 19 Mar 28 09:56 4 -> 2013-03-28_09-56-31
            lrwxrwxrwx 1 jenkins jenkins 19 Mar 28 10:02 5 -> 2013-03-28_10-02-11
            lrwxrwxrwx 1 jenkins jenkins 1 Jul 9 14:23 lastFailedBuild -> 4
            lrwxrwxrwx 1 jenkins jenkins 1 Jul 9 14:23 lastStableBuild -> 5
            lrwxrwxrwx 1 jenkins jenkins 1 Jul 4 11:18 lastSuccessfulBuild -> 5
            lrwxrwxrwx 1 jenkins jenkins 2 Jul 9 14:23 lastUnstableBuild -> -1
            lrwxrwxrwx 1 jenkins jenkins 1 Jul 9 14:23 lastUnsuccessfulBuild -> 4
            {noformat}

            The disk shows 5 builds, 1 through 5, but the GUI only shows 4 and 5, it is missing 1, 2, and 3.

            How do I debug this? One thing looks odd: the dates on the symbolic links differ from the dates in the build history, and differ from the directories they actually link.
            Builds disappear from Jenkins some time after a project has been renamed.

            We upgraded from 1.492 on July 4th and then renamed one build. Four days later we realized the renamed build had lost some or all of its builds. We recovered the builds by reloading from disk this morning. Later in the afternoon, another project was renamed, and some of its builds went missing too.

            Here are the builds of the renamed job on disk:
            {noformat}
            $ ls -l
            total 25
            lrwxrwxrwx 1 jenkins jenkins 19 Mar 1 13:29 1 -> 2013-03-01_13-29-26
            lrwxrwxrwx 1 jenkins jenkins 19 Mar 1 13:31 2 -> 2013-03-01_13-31-20
            drwxrwxr-x 3 jenkins jenkins 141 Jul 9 08:24 2013-03-01_13-29-26
            drwxrwxr-x 3 jenkins jenkins 141 Jul 9 08:24 2013-03-01_13-31-20
            drwxrwxr-x 3 jenkins jenkins 141 Jul 9 08:24 2013-03-01_13-32-42
            drwxrwxr-x 3 jenkins jenkins 141 Jul 9 08:24 2013-03-28_09-56-31
            drwxrwxr-x 3 jenkins jenkins 141 Jul 9 08:24 2013-03-28_10-02-11
            lrwxrwxrwx 1 jenkins jenkins 19 Mar 1 13:32 3 -> 2013-03-01_13-32-42
            lrwxrwxrwx 1 jenkins jenkins 19 Mar 28 09:56 4 -> 2013-03-28_09-56-31
            lrwxrwxrwx 1 jenkins jenkins 19 Mar 28 10:02 5 -> 2013-03-28_10-02-11
            lrwxrwxrwx 1 jenkins jenkins 1 Jul 9 14:23 lastFailedBuild -> 4
            lrwxrwxrwx 1 jenkins jenkins 1 Jul 9 14:23 lastStableBuild -> 5
            lrwxrwxrwx 1 jenkins jenkins 1 Jul 4 11:18 lastSuccessfulBuild -> 5
            lrwxrwxrwx 1 jenkins jenkins 2 Jul 9 14:23 lastUnstableBuild -> -1
            lrwxrwxrwx 1 jenkins jenkins 1 Jul 9 14:23 lastUnsuccessfulBuild -> 4
            {noformat}

            The disk shows 5 builds, 1 through 5, but the GUI only shows 4 and 5, it is missing 1, 2, and 3.

            JENKINS-19650 contains steps to reliably reproduce the problem.

            How do I debug this? One thing looks odd: the dates on the symbolic links differ from the dates in the build history, and differ from the directories they actually link.
            Environment Linux Observed in LTS 1.509.2, LTS 1.509.3, 1.532-SNAPSHOT (private-09/12/2013 13:02 GMT-jenkins)
            Summary Builds disappear from build history in LTS 1.509.2 Builds disappear
            danielbeck Daniel Beck made changes -
            Environment Observed in LTS 1.509.2, LTS 1.509.3, 1.532-SNAPSHOT (private-09/12/2013 13:02 GMT-jenkins) Any
            Observed in LTS 1.509.2, LTS 1.509.3, 1.528, 1.532-SNAPSHOT (private-09/12/2013 13:02 GMT-jenkins)
            danielbeck Daniel Beck made changes -
            Link This issue is related to JENKINS-19720 [ JENKINS-19720 ]
            danielbeck Daniel Beck made changes -
            Summary Builds disappear Builds disappear some time after renaming job
            danielbeck Daniel Beck made changes -
            Labels lts-candidate
            jglick Jesse Glick made changes -
            Link This issue is duplicated by JENKINS-19885 [ JENKINS-19885 ]
            jglick Jesse Glick made changes -
            Labels lts-candidate lazy-loading lts-candidate
            Hide
            oleg_nenashev Oleg Nenashev added a comment -

            The issue appears in 1.509.4 as well. Subjectively, the issue is less frequent being compared to 1.509.3

            Show
            oleg_nenashev Oleg Nenashev added a comment - The issue appears in 1.509.4 as well. Subjectively, the issue is less frequent being compared to 1.509.3
            Hide
            andersmarsten Anders Marsten added a comment -

            I have been running 1.424.2 ,1.509.2 and 1.509.3 without discovered this before. Last week’s this has happens three times on jobs that have been recently renamed. One of the last changes I have done in Jenkins prior to the first occurrence of this problem was to upgrade to 1.509.2, 1.509.3 and add the Job Config History plug-in, maybe the plug-in is related to the problem, or increasing number of existing Jenkins jobs?

            Renaming of jobs work without this problem before upgrade from 1.424.2 to 1.509.2

            Currently running 1.509.3, no info is stated in log files.

            I find this problem very Critical

            Show
            andersmarsten Anders Marsten added a comment - I have been running 1.424.2 ,1.509.2 and 1.509.3 without discovered this before. Last week’s this has happens three times on jobs that have been recently renamed. One of the last changes I have done in Jenkins prior to the first occurrence of this problem was to upgrade to 1.509.2, 1.509.3 and add the Job Config History plug-in, maybe the plug-in is related to the problem, or increasing number of existing Jenkins jobs? Renaming of jobs work without this problem before upgrade from 1.424.2 to 1.509.2 Currently running 1.509.3, no info is stated in log files. I find this problem very Critical
            Hide
            samppa Samuli Saarinen added a comment -

            We are not using Job config history plugin so it's likely not the cause.

            Show
            samppa Samuli Saarinen added a comment - We are not using Job config history plugin so it's likely not the cause.
            Hide
            danielbeck Daniel Beck added a comment -

            Anders: See related JENKINS-18694 and Jesse Glick's comment there. It occurs due to build records being stored in soft references ( http://docs.oracle.com/javase/6/docs/api/java/lang/ref/SoftReference.html ) since 1.485 to not require as much memory. So anything influencing when and how the JVM garbage collects data to free memory can cause this. Chances are, one of your config changes pushed you just over the threshold.

            To force this issue to occur, you can discard the build data from memory after renaming a job by running the following in the script console:

            jenkins.model.Jenkins.instance.getItemByFullName('jobname')._getRuns().purgeCache()
            
            Show
            danielbeck Daniel Beck added a comment - Anders: See related JENKINS-18694 and Jesse Glick's comment there. It occurs due to build records being stored in soft references ( http://docs.oracle.com/javase/6/docs/api/java/lang/ref/SoftReference.html ) since 1.485 to not require as much memory. So anything influencing when and how the JVM garbage collects data to free memory can cause this. Chances are, one of your config changes pushed you just over the threshold. To force this issue to occur, you can discard the build data from memory after renaming a job by running the following in the script console: jenkins.model.Jenkins.instance.getItemByFullName( 'jobname' )._getRuns().purgeCache()
            Hide
            mcklaus Klaus Azesberger added a comment - - edited

            got the same in 1.509.2...

            a quite dangerous side effect is, that jenkins spams an exception for not finding a proper build.xml for build folders (the timestamp folders within the build-folder of the job exists but no files are contained)

            i attached the exception

            Show
            mcklaus Klaus Azesberger added a comment - - edited got the same in 1.509.2... a quite dangerous side effect is, that jenkins spams an exception for not finding a proper build.xml for build folders (the timestamp folders within the build-folder of the job exists but no files are contained) i attached the exception
            mcklaus Klaus Azesberger made changes -
            Attachment exception.log [ 24637 ]
            Hide
            danielbeck Daniel Beck added a comment -

            Klaus: I think you're experiencing a different issue. In your case, it seems the build.xml is never even created, which can happen in my experience when Jenkins stops during a build.

            Show
            danielbeck Daniel Beck added a comment - Klaus: I think you're experiencing a different issue. In your case, it seems the build.xml is never even created, which can happen in my experience when Jenkins stops during a build.
            Hide
            mcklaus Klaus Azesberger added a comment -

            you might be right - can't tell yet.
            so just to be clear: you say, when others experience missing builds, there still are build.xml files?

            Show
            mcklaus Klaus Azesberger added a comment - you might be right - can't tell yet. so just to be clear: you say, when others experience missing builds, there still are build.xml files?
            Hide
            danielbeck Daniel Beck added a comment -

            Yes. See also original issue description: "We recovered the builds by reloading from disk this morning.". This also works for me. Without the XML files on disk, this wouldn't work.

            Show
            danielbeck Daniel Beck added a comment - Yes. See also original issue description: "We recovered the builds by reloading from disk this morning.". This also works for me. Without the XML files on disk, this wouldn't work.
            Hide
            rbaradari Ramin Baradari added a comment -

            Still happening in 1.538.

            Show
            rbaradari Ramin Baradari added a comment - Still happening in 1.538.
            jglick Jesse Glick made changes -
            Link This issue is related to JENKINS-15156 [ JENKINS-15156 ]
            arvindramalingam Arvind Ramalingam made changes -
            Priority Critical [ 2 ] Blocker [ 1 ]
            Hide
            arvindramalingam Arvind Ramalingam added a comment -

            Changing Priority as Blocker..
            This is also happening in Jenkins ver. 1.509.4.

            Show
            arvindramalingam Arvind Ramalingam added a comment - Changing Priority as Blocker.. This is also happening in Jenkins ver. 1.509.4.
            Hide
            danielbeck Daniel Beck added a comment -

            Arvind: You can safely 'Reload configuration from disk' after renaming jobs to prevent builds from disappearing. Already disappeared builds will reappear.

            Also FYI: 1.509.4 is obsolete and no longer supported, 1.532.1 has been released over three weeks ago. (Also suffers from this though).

            Show
            danielbeck Daniel Beck added a comment - Arvind: You can safely 'Reload configuration from disk' after renaming jobs to prevent builds from disappearing. Already disappeared builds will reappear. Also FYI: 1.509.4 is obsolete and no longer supported, 1.532.1 has been released over three weeks ago. (Also suffers from this though).
            Hide
            arvindramalingam Arvind Ramalingam added a comment -

            Hi Daniel,

            Thank you for the quick response.

            1.509.4 LTS is the latest stable version so that is the reason we are using it.The restart did help us to bring back the history but should we be doing it everytime the builds disappear.The build history disappears every day for us.

            Show
            arvindramalingam Arvind Ramalingam added a comment - Hi Daniel, Thank you for the quick response. 1.509.4 LTS is the latest stable version so that is the reason we are using it.The restart did help us to bring back the history but should we be doing it everytime the builds disappear.The build history disappears every day for us.
            Hide
            danielbeck Daniel Beck added a comment -

            Arvind:
            Could you please clarify: Do builds disappear from Jenkins without you renaming their projects? Or do they only disappear after you rename a project as described in the issue above? If it's the former, you might be experiencing a different issue – this one's about builds disappearing from renamed projects. If it's the latter, you shouldn't need to restart. Select 'Reload Configuration From Disk' in 'Manage Jenkins' (which isn't a full restart, as builds keep running and plugins aren't reloaded). Afterwards, the renamed project should no longer lose its builds.

            [ Note that Jenkins 1.532.1 is the latest LTS release and has been released on Nov 25, it's just that nobody bothered to update the web site.
            Changelog: http://jenkins-ci.org/changelog-stable / Download: http://mirrors.jenkins-ci.org/war-stable/1.532.1/ ]

            Show
            danielbeck Daniel Beck added a comment - Arvind: Could you please clarify: Do builds disappear from Jenkins without you renaming their projects? Or do they only disappear after you rename a project as described in the issue above? If it's the former, you might be experiencing a different issue – this one's about builds disappearing from renamed projects. If it's the latter, you shouldn't need to restart. Select 'Reload Configuration From Disk' in 'Manage Jenkins' (which isn't a full restart, as builds keep running and plugins aren't reloaded). Afterwards, the renamed project should no longer lose its builds. [ Note that Jenkins 1.532.1 is the latest LTS release and has been released on Nov 25, it's just that nobody bothered to update the web site. Changelog: http://jenkins-ci.org/changelog-stable / Download: http://mirrors.jenkins-ci.org/war-stable/1.532.1/ ]
            Hide
            arvindramalingam Arvind Ramalingam added a comment -

            Daniel:
            The issue I am facing is that latter one.
            I understand what reload configuration does but I dont prefer doing it as there are issues with gerrit trigger plugin re running all the patch sets again.But thanks for you confirmation that it is a one time activity and the renamed jobs should have build history.

            Cool I will test out the new LTS

            Show
            arvindramalingam Arvind Ramalingam added a comment - Daniel: The issue I am facing is that latter one. I understand what reload configuration does but I dont prefer doing it as there are issues with gerrit trigger plugin re running all the patch sets again.But thanks for you confirmation that it is a one time activity and the renamed jobs should have build history. Cool I will test out the new LTS
            oleg_nenashev Oleg Nenashev made changes -
            Assignee Oleg Nenashev [ oleg_nenashev ]
            Hide
            oleg_nenashev Oleg Nenashev added a comment -

            Finally, the issue has not been solved in the new LTS.

            The issue's cause:

            • Builds cache (RunMap.java) has its own reference to builds directory
            • This directory is being set upon job's creation, but AbstractProject don't modify the location on renaming

            I've created a PR with a draft fix, but we need to implement a unit test (see Daniel's reproduction step in JENKINS-19650)
            https://github.com/jenkinsci/jenkins/pull/1075

            Show
            oleg_nenashev Oleg Nenashev added a comment - Finally, the issue has not been solved in the new LTS. The issue's cause: Builds cache (RunMap.java) has its own reference to builds directory This directory is being set upon job's creation, but AbstractProject don't modify the location on renaming I've created a PR with a draft fix, but we need to implement a unit test (see Daniel's reproduction step in JENKINS-19650 ) https://github.com/jenkinsci/jenkins/pull/1075
            jglick Jesse Glick made changes -
            Status Open [ 1 ] In Progress [ 3 ]
            Hide
            scm_issue_link SCM/JIRA link daemon added a comment -

            Code changed in jenkins
            User: Oleg Nenashev
            Path:
            core/src/main/java/hudson/model/AbstractProject.java
            core/src/main/java/jenkins/model/lazy/AbstractLazyLoadRunMap.java
            http://jenkins-ci.org/commit/jenkins/568ccba8187cfa859deeefb397983e049a9d942b
            Log:
            [FIXED JENKINS-18678] - Update builds location in RunMap after the job's renaming
            This change resolve the issue with missing builds after the jobs renaming and further cleanup of cache.
            Finally, the cache's directory location will be updated after the each job renaming.
            https://issues.jenkins-ci.org/browse/JENKINS-18678

            Signed-off-by: Oleg Nenashev <nenashev@synopsys.com>

            Show
            scm_issue_link SCM/JIRA link daemon added a comment - Code changed in jenkins User: Oleg Nenashev Path: core/src/main/java/hudson/model/AbstractProject.java core/src/main/java/jenkins/model/lazy/AbstractLazyLoadRunMap.java http://jenkins-ci.org/commit/jenkins/568ccba8187cfa859deeefb397983e049a9d942b Log: [FIXED JENKINS-18678] - Update builds location in RunMap after the job's renaming This change resolve the issue with missing builds after the jobs renaming and further cleanup of cache. Finally, the cache's directory location will be updated after the each job renaming. https://issues.jenkins-ci.org/browse/JENKINS-18678 Signed-off-by: Oleg Nenashev <nenashev@synopsys.com>
            scm_issue_link SCM/JIRA link daemon made changes -
            Resolution Fixed [ 1 ]
            Status In Progress [ 3 ] Resolved [ 5 ]
            Hide
            scm_issue_link SCM/JIRA link daemon added a comment -

            Code changed in jenkins
            User: Jesse Glick
            Path:
            test/src/test/groovy/hudson/model/AbstractProjectTest.groovy
            http://jenkins-ci.org/commit/jenkins/1943801ba725bff83e1afaea5f4c7670754c5c61
            Log:
            JENKINS-18678 Reproduced problem in test.

            Show
            scm_issue_link SCM/JIRA link daemon added a comment - Code changed in jenkins User: Jesse Glick Path: test/src/test/groovy/hudson/model/AbstractProjectTest.groovy http://jenkins-ci.org/commit/jenkins/1943801ba725bff83e1afaea5f4c7670754c5c61 Log: JENKINS-18678 Reproduced problem in test.
            Hide
            scm_issue_link SCM/JIRA link daemon added a comment -

            Code changed in jenkins
            User: Jesse Glick
            Path:
            changelog.html
            core/src/main/java/hudson/model/AbstractProject.java
            core/src/main/java/jenkins/model/lazy/AbstractLazyLoadRunMap.java
            http://jenkins-ci.org/commit/jenkins/833c423268635ba79672ccdf6d17977a2a4d4181
            Log:
            JENKINS-18678 Tweaking API, adding @since & changelog for #1075, fixing purgeCache so that test can pass.

            Compare: https://github.com/jenkinsci/jenkins/compare/7b83852b6685...833c42326863

            Show
            scm_issue_link SCM/JIRA link daemon added a comment - Code changed in jenkins User: Jesse Glick Path: changelog.html core/src/main/java/hudson/model/AbstractProject.java core/src/main/java/jenkins/model/lazy/AbstractLazyLoadRunMap.java http://jenkins-ci.org/commit/jenkins/833c423268635ba79672ccdf6d17977a2a4d4181 Log: JENKINS-18678 Tweaking API, adding @since & changelog for #1075, fixing purgeCache so that test can pass. Compare: https://github.com/jenkinsci/jenkins/compare/7b83852b6685...833c42326863
            Hide
            dogfood dogfood added a comment -

            Integrated in jenkins_main_trunk #3132
            [FIXED JENKINS-18678] - Update builds location in RunMap after the job's renaming (Revision 568ccba8187cfa859deeefb397983e049a9d942b)
            JENKINS-18678 Reproduced problem in test. (Revision 1943801ba725bff83e1afaea5f4c7670754c5c61)
            JENKINS-18678 Tweaking API, adding @since & changelog for #1075, fixing purgeCache so that test can pass. (Revision 833c423268635ba79672ccdf6d17977a2a4d4181)

            Result = SUCCESS
            nenashev : 568ccba8187cfa859deeefb397983e049a9d942b
            Files :

            • core/src/main/java/jenkins/model/lazy/AbstractLazyLoadRunMap.java
            • core/src/main/java/hudson/model/AbstractProject.java

            Jesse Glick : 1943801ba725bff83e1afaea5f4c7670754c5c61
            Files :

            • test/src/test/groovy/hudson/model/AbstractProjectTest.groovy

            Jesse Glick : 833c423268635ba79672ccdf6d17977a2a4d4181
            Files :

            • core/src/main/java/hudson/model/AbstractProject.java
            • changelog.html
            • core/src/main/java/jenkins/model/lazy/AbstractLazyLoadRunMap.java
            Show
            dogfood dogfood added a comment - Integrated in jenkins_main_trunk #3132 [FIXED JENKINS-18678] - Update builds location in RunMap after the job's renaming (Revision 568ccba8187cfa859deeefb397983e049a9d942b) JENKINS-18678 Reproduced problem in test. (Revision 1943801ba725bff83e1afaea5f4c7670754c5c61) JENKINS-18678 Tweaking API, adding @since & changelog for #1075, fixing purgeCache so that test can pass. (Revision 833c423268635ba79672ccdf6d17977a2a4d4181) Result = SUCCESS nenashev : 568ccba8187cfa859deeefb397983e049a9d942b Files : core/src/main/java/jenkins/model/lazy/AbstractLazyLoadRunMap.java core/src/main/java/hudson/model/AbstractProject.java Jesse Glick : 1943801ba725bff83e1afaea5f4c7670754c5c61 Files : test/src/test/groovy/hudson/model/AbstractProjectTest.groovy Jesse Glick : 833c423268635ba79672ccdf6d17977a2a4d4181 Files : core/src/main/java/hudson/model/AbstractProject.java changelog.html core/src/main/java/jenkins/model/lazy/AbstractLazyLoadRunMap.java
            Hide
            marquito77 Marko Stefanovic added a comment - - edited

            I had a similar problem where build would "disappear". Reason was a missing build.xml in the build folders.

            After some research I found out that the problem was using the Warnings plugin for a msbuild project while the Maven plugin was deactivated. After I activated the Maven plugin the build.xml was correctly created and the following builds were shown correctly in the history.

            Show
            marquito77 Marko Stefanovic added a comment - - edited I had a similar problem where build would "disappear". Reason was a missing build.xml in the build folders. After some research I found out that the problem was using the Warnings plugin for a msbuild project while the Maven plugin was deactivated. After I activated the Maven plugin the build.xml was correctly created and the following builds were shown correctly in the history.
            Hide
            oleg_nenashev Oleg Nenashev added a comment -

            @Marko
            AFAIK, Maven plugin is an optional dependency for Warnings plugin. Hence Warnings plugin should work properly without it.

            I recommend to create a separate issue for your case.

            Show
            oleg_nenashev Oleg Nenashev added a comment - @Marko AFAIK, Maven plugin is an optional dependency for Warnings plugin. Hence Warnings plugin should work properly without it. I recommend to create a separate issue for your case.
            Hide
            jglick Jesse Glick added a comment -

            @marquito77 yes that sounds really unrelated.

            Show
            jglick Jesse Glick added a comment - @marquito77 yes that sounds really unrelated.
            Hide
            marquito77 Marko Stefanovic added a comment -

            @Oleg, Jesse
            Sorry for off topic posting. I created a new issue. See JENKINS-21268 for further discussion.

            Show
            marquito77 Marko Stefanovic added a comment - @Oleg, Jesse Sorry for off topic posting. I created a new issue. See JENKINS-21268 for further discussion.
            Hide
            scm_issue_link SCM/JIRA link daemon added a comment -

            Code changed in jenkins
            User: Jesse Glick
            Path:
            test/src/test/groovy/hudson/model/AbstractProjectTest.groovy
            http://jenkins-ci.org/commit/jenkins/554be78b9b79eb662d8426f0ace2115a509f7406
            Log:
            JENKINS-18678 JENKINS-18028 Confirming (as suggested in #1069 by @oleg-nenashev) that build history is retained after a move into a folder.

            Show
            scm_issue_link SCM/JIRA link daemon added a comment - Code changed in jenkins User: Jesse Glick Path: test/src/test/groovy/hudson/model/AbstractProjectTest.groovy http://jenkins-ci.org/commit/jenkins/554be78b9b79eb662d8426f0ace2115a509f7406 Log: JENKINS-18678 JENKINS-18028 Confirming (as suggested in #1069 by @oleg-nenashev) that build history is retained after a move into a folder.
            Hide
            dogfood dogfood added a comment -

            Integrated in jenkins_main_trunk #3154
            JENKINS-18678 JENKINS-18028 Confirming (as suggested in #1069 by @oleg-nenashev) that build history is retained after a move into a folder. (Revision 554be78b9b79eb662d8426f0ace2115a509f7406)

            Result = SUCCESS
            Jesse Glick : 554be78b9b79eb662d8426f0ace2115a509f7406
            Files :

            • test/src/test/groovy/hudson/model/AbstractProjectTest.groovy
            Show
            dogfood dogfood added a comment - Integrated in jenkins_main_trunk #3154 JENKINS-18678 JENKINS-18028 Confirming (as suggested in #1069 by @oleg-nenashev) that build history is retained after a move into a folder. (Revision 554be78b9b79eb662d8426f0ace2115a509f7406) Result = SUCCESS Jesse Glick : 554be78b9b79eb662d8426f0ace2115a509f7406 Files : test/src/test/groovy/hudson/model/AbstractProjectTest.groovy
            Hide
            scm_issue_link SCM/JIRA link daemon added a comment -

            Code changed in jenkins
            User: Jesse Glick
            Path:
            changelog.html
            core/src/main/java/hudson/model/AbstractProject.java
            test/src/test/groovy/hudson/model/AbstractProjectTest.groovy
            http://jenkins-ci.org/commit/jenkins/cb623640ccd820ad0540efc3b50cc596626e43a2
            Log:
            [FIXED JENKINS-18694] Generalizing fix of JENKINS-18678 to include also rename of parent folders, taking advantage of JENKINS-18028 API.

            Show
            scm_issue_link SCM/JIRA link daemon added a comment - Code changed in jenkins User: Jesse Glick Path: changelog.html core/src/main/java/hudson/model/AbstractProject.java test/src/test/groovy/hudson/model/AbstractProjectTest.groovy http://jenkins-ci.org/commit/jenkins/cb623640ccd820ad0540efc3b50cc596626e43a2 Log: [FIXED JENKINS-18694] Generalizing fix of JENKINS-18678 to include also rename of parent folders, taking advantage of JENKINS-18028 API.
            Hide
            scm_issue_link SCM/JIRA link daemon added a comment -

            Code changed in jenkins
            User: Oleg Nenashev
            Path:
            core/src/main/java/hudson/model/AbstractProject.java
            core/src/main/java/jenkins/model/lazy/AbstractLazyLoadRunMap.java
            http://jenkins-ci.org/commit/jenkins/65502e1cd928e5f3bdaff505313ab8e7cb64350c
            Log:
            [FIXED JENKINS-18678] - Update builds location in RunMap after the job's renaming
            This change resolve the issue with missing builds after the jobs renaming and further cleanup of cache.
            Finally, the cache's directory location will be updated after the each job renaming.
            https://issues.jenkins-ci.org/browse/JENKINS-18678

            Signed-off-by: Oleg Nenashev <nenashev@synopsys.com>
            (cherry picked from commit 568ccba8187cfa859deeefb397983e049a9d942b)

            Show
            scm_issue_link SCM/JIRA link daemon added a comment - Code changed in jenkins User: Oleg Nenashev Path: core/src/main/java/hudson/model/AbstractProject.java core/src/main/java/jenkins/model/lazy/AbstractLazyLoadRunMap.java http://jenkins-ci.org/commit/jenkins/65502e1cd928e5f3bdaff505313ab8e7cb64350c Log: [FIXED JENKINS-18678] - Update builds location in RunMap after the job's renaming This change resolve the issue with missing builds after the jobs renaming and further cleanup of cache. Finally, the cache's directory location will be updated after the each job renaming. https://issues.jenkins-ci.org/browse/JENKINS-18678 Signed-off-by: Oleg Nenashev <nenashev@synopsys.com> (cherry picked from commit 568ccba8187cfa859deeefb397983e049a9d942b)
            Hide
            scm_issue_link SCM/JIRA link daemon added a comment -

            Code changed in jenkins
            User: Jesse Glick
            Path:
            test/src/test/groovy/hudson/model/AbstractProjectTest.groovy
            http://jenkins-ci.org/commit/jenkins/9c7b5a1373bf0bf88a95c18afe166da3841fa42e
            Log:
            JENKINS-18678 Reproduced problem in test.

            (cherry picked from commit 1943801ba725bff83e1afaea5f4c7670754c5c61)

            Show
            scm_issue_link SCM/JIRA link daemon added a comment - Code changed in jenkins User: Jesse Glick Path: test/src/test/groovy/hudson/model/AbstractProjectTest.groovy http://jenkins-ci.org/commit/jenkins/9c7b5a1373bf0bf88a95c18afe166da3841fa42e Log: JENKINS-18678 Reproduced problem in test. (cherry picked from commit 1943801ba725bff83e1afaea5f4c7670754c5c61)
            Hide
            scm_issue_link SCM/JIRA link daemon added a comment -

            Code changed in jenkins
            User: Jesse Glick
            Path:
            core/src/main/java/hudson/model/AbstractProject.java
            core/src/main/java/jenkins/model/lazy/AbstractLazyLoadRunMap.java
            http://jenkins-ci.org/commit/jenkins/133f63332680bb750eca822ee21d3145b7482ddf
            Log:
            JENKINS-18678 Tweaking API, adding @since & changelog for #1075, fixing purgeCache so that test can pass.

            (cherry picked from commit 833c423268635ba79672ccdf6d17977a2a4d4181)

            Conflicts:
            changelog.html

            Show
            scm_issue_link SCM/JIRA link daemon added a comment - Code changed in jenkins User: Jesse Glick Path: core/src/main/java/hudson/model/AbstractProject.java core/src/main/java/jenkins/model/lazy/AbstractLazyLoadRunMap.java http://jenkins-ci.org/commit/jenkins/133f63332680bb750eca822ee21d3145b7482ddf Log: JENKINS-18678 Tweaking API, adding @since & changelog for #1075, fixing purgeCache so that test can pass. (cherry picked from commit 833c423268635ba79672ccdf6d17977a2a4d4181) Conflicts: changelog.html
            olivergondza Oliver Gondža made changes -
            Labels lazy-loading lts-candidate 1.532.2-fixed lazy-loading
            Hide
            vladichko Vlad Aginsky added a comment -

            Thanks for the effort to fix this, what is Jenkins version that includes this fix?

            Show
            vladichko Vlad Aginsky added a comment - Thanks for the effort to fix this, what is Jenkins version that includes this fix?
            Show
            oleg_nenashev Oleg Nenashev added a comment - The fix is available in jenkins-1.546 http://jenkins-ci.org/commit/jenkins/568ccba8187cfa859deeefb397983e049a9d942b http://jenkins-ci.org/commit/jenkins/833c423268635ba79672ccdf6d17977a2a4d4181
            Hide
            amargono amargono added a comment -

            When will the LTS version 1.532.2 be released? I noticed the issue has been fixed in this release.

            Show
            amargono amargono added a comment - When will the LTS version 1.532.2 be released? I noticed the issue has been fixed in this release.
            Hide
            amargono amargono added a comment -

            The LTS 1.532.2 is now available, however after upgrading, I can't authenticate with LDAP.
            It turned out the whole ldap plugins classes missing.
            Copying the the ldap classes from the previous version to:
            <JENKINS_HOME>/plugins/ldap/WEB-INF/classes solved the authentication issue.

            I have logged the issue at:
            https://issues.jenkins-ci.org/browse/JENKINS-21865

            Show
            amargono amargono added a comment - The LTS 1.532.2 is now available, however after upgrading, I can't authenticate with LDAP. It turned out the whole ldap plugins classes missing. Copying the the ldap classes from the previous version to: <JENKINS_HOME>/plugins/ldap/WEB-INF/classes solved the authentication issue. I have logged the issue at: https://issues.jenkins-ci.org/browse/JENKINS-21865
            Hide
            mishael Mishael Kim added a comment -

            Has anyone successfully tested this fix in the latest LTS build after migrating the older problem jobs/configs over? I'm still seeing my builds disappear in LTS version 1.532.2 when using jobs carried over from my backup. Does it possibly require the creation of a new job to get past this bug?

            @amargono
            BTW, I haven't run into any LDAP issues with this build.

            Show
            mishael Mishael Kim added a comment - Has anyone successfully tested this fix in the latest LTS build after migrating the older problem jobs/configs over? I'm still seeing my builds disappear in LTS version 1.532.2 when using jobs carried over from my backup. Does it possibly require the creation of a new job to get past this bug? @amargono BTW, I haven't run into any LDAP issues with this build.
            Hide
            jglick Jesse Glick added a comment -

            @mishael you may be seeing a different bug that happens to have similar symptoms but for a completely different reason. File it separately with steps to reproduce if you have them.

            Does it possibly require the creation of a new job to get past this bug?

            No; and this bug would only ever manifest itself within a single Jenkins session, so after a restart the job would look fine.

            Show
            jglick Jesse Glick added a comment - @mishael you may be seeing a different bug that happens to have similar symptoms but for a completely different reason. File it separately with steps to reproduce if you have them. Does it possibly require the creation of a new job to get past this bug? No; and this bug would only ever manifest itself within a single Jenkins session, so after a restart the job would look fine.
            Hide
            gecon27 Ioannis Oikonomou added a comment -

            We also have the same problem on 1.542.
            @jglick: I haven't tried upgrading to 1.546 yet, however I noticed that somebody else is still facing the same problem even with 1.547:
            https://issues.jenkins-ci.org/browse/JENKINS-17265?focusedCommentId=193358&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-193358
            Are you aware of this? Any feedback will be highly appreciated ...

            Thanks,
            Ioannis

            Show
            gecon27 Ioannis Oikonomou added a comment - We also have the same problem on 1.542. @jglick: I haven't tried upgrading to 1.546 yet, however I noticed that somebody else is still facing the same problem even with 1.547: https://issues.jenkins-ci.org/browse/JENKINS-17265?focusedCommentId=193358&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-193358 Are you aware of this? Any feedback will be highly appreciated ... Thanks, Ioannis
            oleg_nenashev Oleg Nenashev made changes -
            Link This issue is duplicated by JENKINS-15979 [ JENKINS-15979 ]
            oleg_nenashev Oleg Nenashev made changes -
            Link This issue is duplicated by JENKINS-14030 [ JENKINS-14030 ]
            oleg_nenashev Oleg Nenashev made changes -
            Link This issue is duplicated by JENKINS-18927 [ JENKINS-18927 ]
            oleg_nenashev Oleg Nenashev made changes -
            Link This issue is related to JENKINS-18827 [ JENKINS-18827 ]
            danielbeck Daniel Beck made changes -
            Link This issue is duplicated by JENKINS-18778 [ JENKINS-18778 ]
            oleg_nenashev Oleg Nenashev made changes -
            Link This issue is related to JENKINS-19303 [ JENKINS-19303 ]
            rtyler R. Tyler Croy made changes -
            Workflow JNJira [ 150026 ] JNJira + In-Review [ 193387 ]
            Hide
            dd_jenkins Deepthi D added a comment -

            We are using jenkins 2.7.4 and faced this problem.The build history does exist on the server but are not displayed in the UI

            Show
            dd_jenkins Deepthi D added a comment - We are using jenkins 2.7.4 and faced this problem.The build history does exist on the server but are not displayed in the UI

              People

              Assignee:
              oleg_nenashev Oleg Nenashev
              Reporter:
              deepchip Martin d'Anjou
              Votes:
              15 Vote for this issue
              Watchers:
              29 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: