• 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

          Andrew Bayer added a comment -

          I'm seeing this with one set of matrix builds running on cloud slaves with 1.490 - there's something weird going on.

          Andrew Bayer added a comment - I'm seeing this with one set of matrix builds running on cloud slaves with 1.490 - there's something weird going on.

          x29a added a comment -

          The solution there was to reload the configuration from disk (which has the same effect like the restart mentioned in this issue). Since this is a popular Searchengine result, i wanted to mention the fairly easier solution.

          x29a added a comment - The solution there was to reload the configuration from disk (which has the same effect like the restart mentioned in this issue). Since this is a popular Searchengine result, i wanted to mention the fairly easier solution.

          Oleg Nenashev added a comment -

          The issue has been solved in JENKINS-18678

          Oleg Nenashev added a comment - The issue has been solved in JENKINS-18678

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

              Created:
              Updated:
              Resolved: