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

After Jenkins upgrade pipeline script from SCM configuration is no longer visible on the GUI

    Details

    • Similar Issues:

      Description

      After upgrade of the jenkins server to Jenkins ver. 2.176.2 and all plugins to the latest version, all of our pipeline jobs are showing this (see screenshot) and we try to modify it to Pipeline script from SCM and save the configuration, and reopen the configuration of the job it reverts back the screenshot!

       

      what is weird that in the jenkins home directory, the configuration in the job is there in the xml files, it is just not parsed on the GUI!

       

      Even when we create new jobs and save it as pipeline script from SCM, the display always revert to Pipeline script! And there is nothing in the logs that can point us to what might be the issue

        Attachments

          Issue Links

            Activity

            Hide
            pwiseman Peter Wiseman added a comment -

            I tried Permissive Script Security 0.4. It does not have the issue.

            Show
            pwiseman Peter Wiseman added a comment - I tried Permissive Script Security 0.4. It does not have the issue.
            Hide
            olivergondza Oliver Gondža added a comment -

            permissive-script-security maintainer here, I failed to reproduce this with version 0.5 installed and enabled so I suspect there must be something else involved. Please share the config.xml of the affected job and org.jenkinsci.plugins.workflow.libs.GlobalLibraries.xml, where there is reported the stored config (of one or the other) is not rendered in UI.

            Show
            olivergondza Oliver Gondža added a comment - permissive-script-security maintainer here, I failed to reproduce this with version 0.5 installed and enabled so I suspect there must be something else involved. Please share the config.xml of the affected job and org.jenkinsci.plugins.workflow.libs.GlobalLibraries.xml , where there is reported the stored config (of one or the other) is not rendered in UI.
            Hide
            mkovarik Michal Kovarik added a comment -

            Prometheus plugin 2.0.6 without permissive-security-plugin works.

            Prometheus plugin 2.0.0 and permissive-security-plugin 0.5 works.

            Prometheus plugin 2.0.6 and permissive-security-plugin 0.5 does not work regardless permissive-script-security.enabled setting.

            During startup of Jenkins there are issues with prometheus - https://issues.jenkins-ci.org/browse/JENKINS-59675?focusedCommentId=377073

            Show
            mkovarik Michal Kovarik added a comment - Prometheus plugin 2.0.6 without permissive-security-plugin works. Prometheus plugin 2.0.0 and permissive-security-plugin 0.5 works. Prometheus plugin 2.0.6 and permissive-security-plugin 0.5 does not work regardless permissive-script-security.enabled setting. During startup of Jenkins there are issues with prometheus - https://issues.jenkins-ci.org/browse/JENKINS-59675?focusedCommentId=377073
            Hide
            pwiseman Peter Wiseman added a comment -

            Config.xml and org.jenkinsci.plugins.workflow.libs.GlobalLibraries.xml attached.

            config.xml

            org.jenkinsci.plugins.workflow.libs.GlobalLibraries.xml

            Show
            pwiseman Peter Wiseman added a comment - Config.xml and org.jenkinsci.plugins.workflow.libs.GlobalLibraries.xml attached. config.xml org.jenkinsci.plugins.workflow.libs.GlobalLibraries.xml
            Hide
            lkkovacs László Kovács added a comment -

            It seems like a recurring problem with security plugins no matter what Jenkins versions we are using. With 2.138.3 Jenkins version after updating script-security plugin to version to 1.68 and permissive-script-security plugin is 0.5.  We don't use Prometheus plugin, but the issue is still the same.

            As I see new permissive-script-security plugin version (0.5) has complications with several other plugin and there is no fix for it currently. So you have to downgrade plugins to solve the issue. 
             

            Show
            lkkovacs László Kovács added a comment - It seems like a recurring problem with security plugins no matter what Jenkins versions we are using. With 2.138.3 Jenkins version after updating script-security plugin to version to 1.68 and permissive-script-security plugin is 0.5.  We don't use Prometheus plugin, but the issue is still the same. As I see new permissive-script-security plugin version (0.5) has complications with several other plugin and there is no fix for it currently. So you have to downgrade plugins to solve the issue.   

              People

              • Assignee:
                Unassigned
                Reporter:
                melhossary Mohamed ELHOSSARY
              • Votes:
                5 Vote for this issue
                Watchers:
                12 Start watching this issue

                Dates

                • Created:
                  Updated: