I am not sure this defect is raised for the correct component. I ran some tests and this only happens when I use the copy artifact and promoted builds plugins

      Steps to reproduce

      1. configure job a to require manual promotion via a star
      2. configure job a to archive an artifact
      3. configure job b to be triggered upon successful promotion to job b
      4. rename job a
      5. trigger job a to job c
      6. promote job a

      Expected results
      job b should be triggered

      Actual results
      Job b was not triggered
      Job b did not show job c as an upstream on the configure page - it showed job a

          [JENKINS-36122] Renaming a job does not get reflected

          ikedam added a comment -

          I suppose there are mistypes, and the following is the actual situation:

          1. configure job a to require manual promotion via a star
          2. configure job a to archive an artifact
            #configure job b to be triggered upon successful promotion to job b job a
          3. rename job a (to job c)
          4. trigger job a to job c
          5. promote job a job c

          ikedam added a comment - I suppose there are mistypes, and the following is the actual situation: configure job a to require manual promotion via a star configure job a to archive an artifact #configure job b to be triggered upon successful promotion to job b job a rename job a (to job c) trigger job a to job c promote job a job c

          ikedam added a comment -

          The issue sounds that job B fails to detect promotions of job A after job A is renamed, and the issue sounds of promoted-builds plugin.

          ikedam added a comment - The issue sounds that job B fails to detect promotions of job A after job A is renamed, and the issue sounds of promoted-builds plugin.

          Oleg Nenashev added a comment -

          No plan to work on it anytime soon. The plugin is up for adoption. Pull requests will be appreciated, reviewed and integrated if possible.

          Oleg Nenashev added a comment - No plan to work on it anytime soon. The plugin is up for adoption. Pull requests will be appreciated, reviewed and integrated if possible.

            Unassigned Unassigned
            eamonnfaherty eamonn faherty
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: