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

Downstream projects links disappeared

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Major Major
    • core
    • None
    • Cent0S - 64bit - 2.6.18-238.9.1.el5
      tomcat-6.0.32
      java 1.6.0_17-b17

       

      Some downstream jobs links were randomly removed from its upstream job.
      From the job config history, it showed the user apparently made some changes on the job config and removed the downstream jobs link, however the person does not have a permission to update the job configuration (based on project security).

      The users however made some changes on other un-related jobs that he has the permission and the job config showed a correct report of what changes he made on a project that he has the permission to modify the job config.

      Here is the scenarios:
      Upstream project: Proj1
      Downstream projects: Proj2, Proj3
      User A does not have permission to modify any of Proj1, Proj2 or Proj3 job config.

      User A made some job config changes on Proj4 which has no relation with Proj1, Proj2 or Proj3.
      For some reason, User A appeared on the job config history on the Proj1 and the history showed that he removed the Downstream Proj2 and Proj3 (which he does not have any permission to do that).

      Not sure if this is a bug related to the JobConfigHistory Plugin (ver 1.11)? or problem with the jenkins 1.404.
      Could it be the same bug as reported on https://issues.jenkins-ci.org/browse/JENKINS-5265?

      Any feedback is very much appreciated.

      Thanks,
      amargono

          [JENKINS-12009] Downstream projects links disappeared

          a margono created issue -
          a margono made changes -
          Component/s New: jobconfighistory [ 15683 ]
          Description Original: A similar issue was reported as jenkins bug and it was claimed to have been fixed.
          https://issues.jenkins-ci.org/browse/JENKINS-5265.

          A downstream jobs was randomly removed when people with no jenkins job config permission (per project base permission) changed configuration of a job.

          However the job workspace still exists, it looks like the job config was messed up.
                      		New: Some downstream jobs links were randomly removed from its upstream job.
          From the job config history, it showed the user apparently made some changes on the job config and removed the downstream jobs link, however the person does not have a permission to update the job configuration (based on project security).

          The users however made some changes on other un-related jobs that he has the permission and the job config showed a correct report of what changes he made on a project that he has the permission to modify the job config.

          Here is the scenarios:
          Upstream project: Proj1
          Downstream projects: Proj2, Proj3
          User A does not have permission to modify any of Proj1, Proj2 or Proj3 job config.

          User A made some job config changes on Proj4 which has no relation with Proj1, Proj2 or Proj3.
          For some reason, User A appeared on the job config history on the Proj1 and the history showed that he removed the Downstream Proj2 and Proj3 (which he does not have any permission to do that).

          Not sure if this is a bug related to the JobConfigHistory Plugin (ver 1.11)? or problem with the jenkins 1.404.
          Could it be the same bug as reported on https://issues.jenkins-ci.org/browse/JENKINS-5265?

          Any feedback is very much appreciated.

          Thanks,
          amargono




           





           
          Summary Original: Downstream project disappeared due to permission issue. New: Downstream projects links disappeared

          Daniel Beck added a comment -

          This is probably duplicated by 13502. Could you verify my analysis there, i.e. that it's related to missing read permissions for the downstream jobs?

          Daniel Beck added a comment - This is probably duplicated by 13502. Could you verify my analysis there, i.e. that it's related to missing read permissions for the downstream jobs?

          Kathi Stutz added a comment -

          Removed JobConfigHistory from the list of components since it just recorded the changes but did not cause them.

          Kathi Stutz added a comment - Removed JobConfigHistory from the list of components since it just recorded the changes but did not cause them.
          Kathi Stutz made changes -
          Component/s Original: jobconfighistory [ 15683 ]
          Daniel Beck made changes -
          Link New: This issue duplicates JENKINS-13502 [ JENKINS-13502 ]
          Daniel Beck made changes -
          Component/s New: core [ 15593 ]
          Component/s Original: downstream-buildview [ 15699 ]

          Daniel Beck added a comment -

          Assuming this is a duplicate of JENKINS-13502 after no responses were forthcoming.

          Any similar issue in 1.551+ or 1.532.3 can be assumed to be unrelated and caused by SECURITY-109.

          Daniel Beck added a comment - Assuming this is a duplicate of JENKINS-13502 after no responses were forthcoming. Any similar issue in 1.551+ or 1.532.3 can be assumed to be unrelated and caused by SECURITY-109.
          Daniel Beck made changes -
          Resolution New: Duplicate [ 3 ]
          Status Original: Open [ 1 ] New: Resolved [ 5 ]
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 142281 ] New: JNJira + In-Review [ 190052 ]

            shinodkm shinodkm
            amargono1 a margono
            Votes:
            5 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: