• Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Critical Critical
    • None
    • Windows 10; Jenkins 2.148+; pipeline plugins: latest

      Repro steps:

      1. Create a new pipeline job
      2. Scroll down to Pipeline section
      3. Default "Pipeline script" is selected in drop down.
      4. Script text area is missing.

          [JENKINS-54233] Pipeline Script textarea missing

          Andrew Gray added a comment -

          Andrew Gray added a comment - jglick

          Jesse Glick added a comment -

          Working for me on Linux after running 2.148 and installing Pipeline from setup wizard. Steps to reproduce from scratch? Errors in Jenkins log or browser console?

          Jesse Glick added a comment - Working for me on Linux after running 2.148 and installing Pipeline from setup wizard. Steps to reproduce from scratch? Errors in Jenkins log or browser console?

          Jesse Glick added a comment -

          CC current maintainers, starting with svanoort.

          Jesse Glick added a comment - CC current maintainers, starting with svanoort .

          Andrew Gray added a comment - - edited

          Thanks Jesse.  I have Windows boxes at home and work.

          Repro: All I did was update the Groovy plugin from 2.20 to latest.

          Above screenshot is from my home laptop running 2.148 (now 2.149).

           

          Work build server is 2.138.2 (LTS release) on Windows 2012. As it is critical infrastructure (we are yet to stand up a test instance so we can test these plugin updates) I am reticent to update this plugin but we don't want to fall behind.

           

          Does this problem also happen on 2.138.2 on Windows 2012?

          Andrew Gray added a comment - - edited Thanks Jesse.  I have Windows boxes at home and work. Repro: All I did was update the Groovy plugin from 2.20 to latest. Above screenshot is from my home laptop running 2.148 (now 2.149).   Work build server is 2.138.2 (LTS release) on Windows 2012. As it is critical infrastructure (we are yet to stand up a test instance so we can test these plugin updates) I am reticent to update this plugin but we don't want to fall behind.   Does this problem also happen on 2.138.2 on Windows 2012?

          Jesse Glick added a comment -

          Also working fine for me with the same installation (2.148, latest Pipeline) on Windows 10 using Internet Explorer.

          Try reinstalling Jenkins from scratch. If that works, then you can bisect your way to the problem.

          Jesse Glick added a comment - Also working fine for me with the same installation (2.148, latest Pipeline ) on Windows 10 using Internet Explorer. Try reinstalling Jenkins from scratch. If that works, then you can bisect your way to the problem.

          Andrew Gray added a comment -

          Reinstalling Jenkins is not an option.  I am more interested in whether the issue occurs on the LTS release (2.138.2) as that is what we are using at work and I can't afford to test it as it is the only instance we currently have.

          Andrew Gray added a comment - Reinstalling Jenkins is not an option.  I am more interested in whether the issue occurs on the LTS release (2.138.2) as that is what we are using at work and I can't afford to test it as it is the only instance we currently have.

          Jesse Glick added a comment -

          I do not see any such issue on 2.138.2.

          By “reinstall” I did not mean delete your existing installation, but to create a new one to compare behavior. My best guess offhand is that some unreported JavaScript error caused by a misbehaving plugin (outside the standard list of Pipeline plugins) is responsible. But without more information, this issue is not diagnosable.

          Jesse Glick added a comment - I do not see any such issue on 2.138.2. By “reinstall” I did not mean delete your existing installation, but to create a new one to compare behavior. My best guess offhand is that some unreported JavaScript error caused by a misbehaving plugin (outside the standard list of Pipeline plugins) is responsible. But without more information, this issue is not diagnosable.

          Jesse Glick added a comment -

          If this started in 2.148 then theoretically the change by tscherler for JENKINS-53462 could be responsible.

          Jesse Glick added a comment - If this started in 2.148 then theoretically the change by tscherler for JENKINS-53462 could be responsible.

          Kevin Wilson added a comment -

          I was using AJP for my HTTPD-Tomcat connection. I switched to HTTP, and the script editor came back.
          Directories, IP addresses and port numbers were removed.

          The tip off was this error in my logs:
          27-Dec-2018 14:19:35.166 WARNING [Handling GET /cloudbees/configure from xxx.xxx.xxx.xxx : ajp-apr-yyy.yyy.yyy.yyy-zzzz-exec-1] hudson.init.impl.InstallUncaughtExceptionHandler.lambda$init$0 null
          {{ javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:.../tomcat8/webapps/cloudbees/WEB-INF/lib/jenkins-core-2.138.4-cb-2.jar!/lib/form/dropdownListBlock.jelly:51:59: <j:when> java.io.IOException: Failed to send AJP message}}
          {{ at org.kohsuke.stapler.jelly.JellyFacet$1.dispatch(JellyFacet.java:111)}}
          {{ at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:739)}}
          {{ at org.kohsuke.stapler.Stapler.invoke(Stapler.java:870)}}
          {{ at org.kohsuke.stapler.Stapler.invoke(Stapler.java:668)}}
          {{ at org.kohsuke.stapler.Stapler.service(Stapler.java:238)}}
          {{ at javax.servlet.http.HttpServlet.service(HttpServlet.java:729)}}

          Kevin Wilson added a comment - I was using AJP for my HTTPD-Tomcat connection. I switched to HTTP, and the script editor came back. Directories, IP addresses and port numbers were removed. The tip off was this error in my logs: 27-Dec-2018 14:19:35.166 WARNING [Handling GET /cloudbees/configure from xxx.xxx.xxx.xxx : ajp-apr-yyy.yyy.yyy.yyy-zzzz-exec-1] hudson.init.impl.InstallUncaughtExceptionHandler.lambda$init$0 null {{ javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar: file:.../tomcat8/webapps/cloudbees/WEB-INF/lib/jenkins-core-2.138.4-cb-2.jar!/lib/form/dropdownListBlock.jelly:51:59: <j:when> java.io.IOException: Failed to send AJP message}} {{ at org.kohsuke.stapler.jelly.JellyFacet$1.dispatch(JellyFacet.java:111)}} {{ at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:739)}} {{ at org.kohsuke.stapler.Stapler.invoke(Stapler.java:870)}} {{ at org.kohsuke.stapler.Stapler.invoke(Stapler.java:668)}} {{ at org.kohsuke.stapler.Stapler.service(Stapler.java:238)}} {{ at javax.servlet.http.HttpServlet.service(HttpServlet.java:729)}}

          Kevin Wilson added a comment -

          Ok, that was strange. It worked only once after the change.

          Kevin Wilson added a comment - Ok, that was strange. It worked only once after the change.

            Unassigned Unassigned
            apgray Andrew Gray
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: