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

SCM Trigger configuration being overwritten by SYSTEM user in Pipeline

    XMLWordPrintable

Details

    • Bug
    • Status: Resolved (View Workflow)
    • Major
    • Resolution: Not A Defect
    • pipeline
    • Jenkins 2.8
      BlueOcean 1.0.0-b17
      CentOS 6.7
      java version "1.7.0_101"
      OpenJDK Runtime Environment (rhel-2.6.6.4.el6_8-x86_64 u101-b00)
      OpenJDK 64-Bit Server VM (build 24.95-b01, mixed mode)

    Description

      I setup a Pipeline job using a Pipeline script written in the job (not in SCM) and enabled SCM polling as a Build Trigger.

      The polling mechanism works and triggers a build after detecting changes, however whenever it polls there is a high chance that the config.xml will be modified, removing the SCM Trigger entirely.

      I used the Job Configuration History plugin and it shows the changes happening from SYSTEM user.

      Looking through jenkins.log doesn't provide much information either, as this is the only entry around the same time as the SYSTEM user updates the config.xml

      Jan 17, 2017 2:17:24 PM hudson.triggers.SCMTrigger$Runner run
      INFO: SCM changes detected in unified-trunk. Triggering #84

      Attachments

        Issue Links

          Activity

            jonathandyer Jonathan Dyer created issue -
            jonathandyer Jonathan Dyer made changes -
            Field Original Value New Value
            Description I setup a Pipeline job using a Pipeline script written in the job (not in SCM) and enabled SCM polling as a Build Trigger.

            The polling mechanism works and triggers a build after detecting changes, however whenever it polls there is a high chance that the config.xml will be modified, removing the SCM Trigger entirely.
             !image-2017-01-17-14-43-37-557.png|thumbnail!

            I used the Job Configuration History plugin and it shows the changes happening from SYSTEM user.
             !image-2017-01-17-14-41-29-596.png|thumbnail!





            I setup a Pipeline job using a Pipeline script written in the job (not in SCM) and enabled SCM polling as a Build Trigger.

            The polling mechanism works and triggers a build after detecting changes, however whenever it polls there is a high chance that the config.xml will be modified, removing the SCM Trigger entirely.
             !image-2017-01-17-14-43-37-557.png|thumbnail!

            I used the Job Configuration History plugin and it shows the changes happening from SYSTEM user.
             !image-2017-01-17-14-41-29-596.png|thumbnail!

            Looking through jenkins.log doesn't provide much information either, as this is the only entry around the same time as the SYSTEM user updates the config.xml
            {quote}
            Jan 17, 2017 2:17:24 PM hudson.triggers.SCMTrigger$Runner run
            INFO: SCM changes detected in unified-trunk. Triggering #84
            {quote}





            jamesdumay James Dumay made changes -
            Component/s blueocean-plugin [ 21481 ]
            hrmpw Patrick Wolf made changes -
            Link This issue is related to JENKINS-41072 [ JENKINS-41072 ]
            hrmpw Patrick Wolf made changes -
            Link This issue is related to JENKINS-41073 [ JENKINS-41073 ]
            hrmpw Patrick Wolf made changes -
            Link This issue is related to JENKINS-41074 [ JENKINS-41074 ]
            jglick Jesse Glick made changes -
            Resolution Not A Defect [ 7 ]
            Status Open [ 1 ] Resolved [ 5 ]
            jglick Jesse Glick made changes -
            Remote Link This issue links to "workflow-multibranch PR 52 (Web Link)" [ 15353 ]
            tknerr Torben Knerr made changes -
            Link This issue is related to JENKINS-45053 [ JENKINS-45053 ]

            People

              Unassigned Unassigned
              jonathandyer Jonathan Dyer
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: