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

All Descriptions throughout Jenkins, Change to AD_Login

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Minor
    • Resolution: Not A Defect
    • Component/s: ec2-plugin
    • Labels:
      None
    • Similar Issues:

      Description

      For a long time, basically since I installed Jenkins for my company to use, all "description" fields have been changing to AD_Login. We use the ec2 plugin so the description for which slave was instantiated for a specific build is always named AD_Login. This wouldn't be a huge deal and I kind of put it on the back burner, but now it's changing password fields for our Windows AMI profiles so it became a huge priority for us as no one can build on a Windows instance.

      I did as much digging around as me and one other person could. We googled everything we possibly could and found nothing, not even leads. We grep'd the entire server that master Jenkins is sitting on for any mention of AD_Login and sifted through almost 1 million lines to get nothing.

      It happens any time configuration is reloaded from disk, when you first go to /configure it will update every description to be AD_Login, if you change this and use the apply button you can get around it until configuration is reloaded. $JENKINS_HOME/config.xml shows correct values after this save but only until server restart or configuration reload.

      Once a correct value is saved and you refresh the /configure screen, the values are correct until a javascript window.onload runs and then changes it back, so if we need to change anything in /configure we have to re-change everything else on the page. I've spent hours trying to dig through all the code and multiple step-by-step debug processes with js. It always happens during the Behavior.apply(); call in window.onload, but this must be pulling the term AD_Login from somewhere and slapping it into the description field.

      I'm at a massive loss, anything at all would be a HUGE help. I've ensured that jenkins and all plugins are up to date. ensured that no customizations from my company are affecting it (there's only javascript and css customizations, I turned them off completely and still happens). Unfortunately our jenkins system is in our private network so I can't share much other than screenshots that are asked for.

        Attachments

          Activity

          Hide
          dadbod9000 Travis Neal added a comment -

          Forgot to mention it's also updating every job that has the "description-setter" plugin in use. It changes any field with the name `_.description` to AD_Login

          Show
          dadbod9000 Travis Neal added a comment - Forgot to mention it's also updating every job that has the "description-setter" plugin in use. It changes any field with the name `_.description` to AD_Login
          Hide
          oleg_nenashev Oleg Nenashev added a comment -

          Any chance that you have...

          1. Simple Theme Plugin and custom JavaScripts there
          2. Custom plugins installed (not ones from the Jenkins UC)
          3. Any jobs invoking system groovy Scripts to edit configurations
          4. Any users invoking invoking Groovy CLI or REST API
          5. Any System Groovy post-build hooks

          So far it looks like a custom tooling going crazy and applying changes improperly.

          Show
          oleg_nenashev Oleg Nenashev added a comment - Any chance that you have... Simple Theme Plugin and custom JavaScripts there Custom plugins installed (not ones from the Jenkins UC) Any jobs invoking system groovy Scripts to edit configurations Any users invoking invoking Groovy CLI or REST API Any System Groovy post-build hooks So far it looks like a custom tooling going crazy and applying changes improperly.
          Hide
          dadbod9000 Travis Neal added a comment -

          Hi Oleg,

          1) yes. They have all been removed but still happens. the Behavior.js script is the one applying it and it's getting the value from somewhere.
          2) we have no custom plugins installed. Only from the Jenkins project.
          3) there's 3 jobs that have groovy scripts. neither have been run since December and all of them pertain to retrieving some respective list (users, jobs, or folder contents)
          4) only 2 users have access to the jenkins CLI/script console, me and the person trying to help me resolve the issue
          5) We have only 3 groovy scripts as mentioned in #3

          Show
          dadbod9000 Travis Neal added a comment - Hi Oleg, 1) yes. They have all been removed but still happens. the Behavior.js script is the one applying it and it's getting the value from somewhere. 2) we have no custom plugins installed. Only from the Jenkins project. 3) there's 3 jobs that have groovy scripts. neither have been run since December and all of them pertain to retrieving some respective list (users, jobs, or folder contents) 4) only 2 users have access to the jenkins CLI/script console, me and the person trying to help me resolve the issue 5) We have only 3 groovy scripts as mentioned in #3
          Hide
          dadbod9000 Travis Neal added a comment - - edited

          we used the Hudson decrypt to determine that it was placing a credential from the credentials plugin into the space for windows passwords. so I've narrowed this down to the credentials-plugin as the description for that credential entry happens to be "AD_Login" I've change this description to see if anything else changes.

          Show
          dadbod9000 Travis Neal added a comment - - edited we used the Hudson decrypt to determine that it was placing a credential from the credentials plugin into the space for windows passwords. so I've narrowed this down to the credentials-plugin as the description for that credential entry happens to be "AD_Login" I've change this description to see if anything else changes.
          Hide
          dadbod9000 Travis Neal added a comment -

          Update:

          I duplicated our entire Jenkins stack and started deleting things. Deleted every single plugin except the Amazon EC2 Plugin and all of its dependencies, deleted all files related to deleted plugins and deleted all builds and jobs from the server. It was still happening.

          However, I decided to delete all but 1 AMI profile in the configuration and it stopped updating the field to say "AD_Login". I then deleted 1 by 1, restarted the server and checked. It stopped after deleting the last windows profile. I then put them all back copying that section from the "live" jenkins server we have and pasting it in. It started happening again. Removed all the windows profiles and only the windows profiles, and it no longer updates the field to say "AD_Login".

          I don't feel like this is a way to fix it, but it's a way to get around it for now and at least SOME lead to go on when trying to debug this. I'm going to update the components on this ticket to show the ec2 plugin and hope that this ticket hasn't been lost to the abyss.

          Show
          dadbod9000 Travis Neal added a comment - Update: I duplicated our entire Jenkins stack and started deleting things. Deleted every single plugin except the Amazon EC2 Plugin and all of its dependencies, deleted all files related to deleted plugins and deleted all builds and jobs from the server. It was still happening. However, I decided to delete all but 1 AMI profile in the configuration and it stopped updating the field to say "AD_Login". I then deleted 1 by 1, restarted the server and checked. It stopped after deleting the last windows profile. I then put them all back copying that section from the "live" jenkins server we have and pasting it in. It started happening again. Removed all the windows profiles and only the windows profiles, and it no longer updates the field to say "AD_Login". I don't feel like this is a way to fix it, but it's a way to get around it for now and at least SOME lead to go on when trying to debug this. I'm going to update the components on this ticket to show the ec2 plugin and hope that this ticket hasn't been lost to the abyss.
          Hide
          dadbod9000 Travis Neal added a comment -

          I solved this problem. Going to close this ticket.

          Show
          dadbod9000 Travis Neal added a comment - I solved this problem. Going to close this ticket.

            People

            • Assignee:
              francisu Francis Upton
              Reporter:
              dadbod9000 Travis Neal
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: