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

"forgets" builds, workspace of renamed job

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Critical Critical
    • core
    • None

      I renamed a job yesterday on 1.491 and this morning, Jenkins showed it as having no builds - even though I could see them on the file system.

      Immediately after the renaming, Jenkins seemed to have "lost sight" of the existing workspace. So I fired another build and all was good. But this morning, it had "forgotten" both that build and the workspace again.

      Restarting Jenkins seems to have fixed it.

      (Hope I picked the right component...)

          [JENKINS-15979] "forgets" builds, workspace of renamed job

          G. Ann Campbell created issue -
          Andrew Bayer made changes -
          Component/s New: core [ 15593 ]
          Component/s Original: build-publisher [ 15529 ]
          Assignee Original: vjuranek [ vjuranek ] New: Kohsuke Kawaguchi [ kohsuke ]
          Priority Original: Minor [ 4 ] New: Critical [ 2 ]
          Andrew Bayer made changes -
          Link New: This issue duplicates JENKINS-15799 [ JENKINS-15799 ]
          Andrew Bayer made changes -
          Resolution New: Duplicate [ 3 ]
          Status Original: Open [ 1 ] New: Resolved [ 5 ]
          x29a made changes -
          Link New: This issue duplicates JENKINS-14030 [ JENKINS-14030 ]
          Oleg Nenashev made changes -
          Link New: This issue duplicates JENKINS-18678 [ JENKINS-18678 ]
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 146781 ] New: JNJira + In-Review [ 192084 ]

            kohsuke Kohsuke Kawaguchi
            ganncamp G. Ann Campbell
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: