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

All builds are gone since I copied an existing project

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved (View Workflow)
    • Priority: Critical
    • Resolution: Incomplete
    • Component/s: core
    • Labels:
      None
    • Environment:
      Jenkins 1.500 / Tomcat 6 / JDK 1.6.0_18 / Debian 6 / x86
    • Similar Issues:

      Description

      Jenkins was set up and working stable.
      When it was idle I used "Copy existing job".
      Started the job.
      Then all my builds of some my projects where gone. In fact, there is no relationship between the copied / new project and the deleted ones.
      ;-(

        Attachments

          Issue Links

            Activity

            Hide
            schmke Kevin Schmidt added a comment -

            I'm also seeing this issue with 1.520. Happens with cloned projects, but not all cloned projects. There are a number of issues logged related to this, but the one with the most comments is closed as resolved but the problem still occurs it appears. Is this being worked on?

            Show
            schmke Kevin Schmidt added a comment - I'm also seeing this issue with 1.520. Happens with cloned projects, but not all cloned projects. There are a number of issues logged related to this, but the one with the most comments is closed as resolved but the problem still occurs it appears. Is this being worked on?
            Hide
            jwilso_27 Jon Wilson added a comment -

            Seeing this issue with 1.526. Some (but not all) cloned projects exhibit this behavior. This is a severe bug that is impacting production, as our projects are complex, yet similar, and benefit greatly from cloning older plans in order to minimize the chance of human error when configuring a new plan.

            Show
            jwilso_27 Jon Wilson added a comment - Seeing this issue with 1.526. Some (but not all) cloned projects exhibit this behavior. This is a severe bug that is impacting production, as our projects are complex, yet similar, and benefit greatly from cloning older plans in order to minimize the chance of human error when configuring a new plan.
            Hide
            tombrus Tom Brus added a comment -

            Seeing this issue with 1.529 as well.

            Show
            tombrus Tom Brus added a comment - Seeing this issue with 1.529 as well.
            Hide
            danielbeck Daniel Beck added a comment -

            Is anyone still experiencing this on recent Jenkins versions?

            Are the builds actually missing from disk, or just not shown in Jenkins? What happens when you reload configuration from disk? Is anything mentioned in the Jenkins log?

            Show
            danielbeck Daniel Beck added a comment - Is anyone still experiencing this on recent Jenkins versions? Are the builds actually missing from disk, or just not shown in Jenkins? What happens when you reload configuration from disk? Is anything mentioned in the Jenkins log?
            Hide
            danielbeck Daniel Beck added a comment -

            No response to comment asking for additional and updated information in two weeks, so resolving as Incomplete.

            Show
            danielbeck Daniel Beck added a comment - No response to comment asking for additional and updated information in two weeks, so resolving as Incomplete.

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              mkarg Markus KARG
              Votes:
              5 Vote for this issue
              Watchers:
              11 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: