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

Downstream project removed when configuration saved

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Major Major
    • core
    • None
    • Platform: All, OS: Windows XP

      I have two projects (A and B). Project A is a freestyle project that is
      configured to build project B in the "Build other projects" as a post build
      action. If I attempt to edit the configuration for project B, project B will
      no longer be a downstream project of project A.

      Hudson Version: 1.209
      OS : Win2K3 Server

          [JENKINS-1617] Downstream project removed when configuration saved

          Clint Wong added a comment -

          fix typo

          Clint Wong added a comment - fix typo

          I couldn't reproduce the problem as of 1.221. I wonder if you can try the newer
          version to see if you still see the problem?

          The only plausible theory that I can come up with is that you open two
          configuration pages, then add B as the downstream in A config, submit that, then
          submit B config page later.

          The submission of the B config page would overwrite your earlier submission
          about the dependency relationship, so that could cause what you are describing.

          Kohsuke Kawaguchi added a comment - I couldn't reproduce the problem as of 1.221. I wonder if you can try the newer version to see if you still see the problem? The only plausible theory that I can come up with is that you open two configuration pages, then add B as the downstream in A config, submit that, then submit B config page later. The submission of the B config page would overwrite your earlier submission about the dependency relationship, so that could cause what you are describing.

          Clint Wong added a comment -

          I have installed 1.225, and I am still able to reproduce this issue. The
          process that I used to recreate this issue was to use a single tab on FireFox
          3.0. I opened the configuration page for project A, and I set project B as the
          downstream project. After project B was set as a downstream project, I saved
          the configuration of project A. I proceeded to open the configuration page of
          project B. After saving the configuration of project B, I opened the
          configuration of project A again, and project B was no longer a downstream project.

          The portion of your theory that is not correct is the part about opening two
          configuration pages at the same time. All of my actions take place in a serial
          fashion.

          Clint Wong added a comment - I have installed 1.225, and I am still able to reproduce this issue. The process that I used to recreate this issue was to use a single tab on FireFox 3.0. I opened the configuration page for project A, and I set project B as the downstream project. After project B was set as a downstream project, I saved the configuration of project A. I proceeded to open the configuration page of project B. After saving the configuration of project B, I opened the configuration of project A again, and project B was no longer a downstream project. The portion of your theory that is not correct is the part about opening two configuration pages at the same time. All of my actions take place in a serial fashion.

          Alan Harder added a comment -

          looks like this was fixed recently.. reopen if that fix doesn't solve this one.

              • This issue has been marked as a duplicate of 2778 ***

          Alan Harder added a comment - looks like this was fixed recently.. reopen if that fix doesn't solve this one. This issue has been marked as a duplicate of 2778 ***

            Unassigned Unassigned
            crwong Clint Wong
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: