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

UI is flickering when i save a job using 2 execute shells

    • 2.435

      Versions i saw this issue 2.387.3 and lts also.

      So, when i create a Jenkins job including 2 execute shells saving them and deleting the 1st one(execute shell), the other one when comes up starts flickering the screen. And it is unreadable when i want to make any changes in the job.

      I suspected the plugins first, but later when i freshly created a Jenkins server with the Jenkins recommended plugins also i encountered the same.

      I have attached the photos before and after, please check it.

       

      Thank you,

      Abhishek

          [JENKINS-72196] UI is flickering when i save a job using 2 execute shells

          abhishek created issue -
          Mark Waite made changes -

          Mark Waite added a comment -

          Thanks for the report. I've been able to duplicate the problem on my Jenkins 2.426 test instance. Steps that I took to duplicate the issue:

          1. Create a new freestyle job
          2. Add an execute shell step with the text "echo this is the first shell step"
          3. Add a second execute shell step with the text "echo this is the second shell step"
          4. Save the job definition
          5. Edit the job definition and remove the first execute shell step
          6. Confirm the web page looks wrong

          Mark Waite added a comment - Thanks for the report. I've been able to duplicate the problem on my Jenkins 2.426 test instance. Steps that I took to duplicate the issue: Create a new freestyle job Add an execute shell step with the text "echo this is the first shell step" Add a second execute shell step with the text "echo this is the second shell step" Save the job definition Edit the job definition and remove the first execute shell step Confirm the web page looks wrong

          Mark Waite added a comment -

          abhishek_02 are you interested in performing the git bisect to identify the commit that introduced the problem?

          Mark Waite added a comment - abhishek_02 are you interested in performing the git bisect to identify the commit that introduced the problem?
          Mark Waite made changes -
          Labels Original: jenkins

          Mark Waite added a comment - - edited

          abhishek_02 the behavior exists in some form all the way back to Jenkins 2.164.3, released 4 years ago. You'll need to use the workaround of saving the job after deleting the execute shell step, then open the job again with the configure link.

          Mark Waite added a comment - - edited abhishek_02 the behavior exists in some form all the way back to Jenkins 2.164.3, released 4 years ago. You'll need to use the workaround of saving the job after deleting the execute shell step, then open the job again with the configure link.
          Mark Waite made changes -
          Priority Original: Major [ 3 ] New: Trivial [ 5 ]

          abhishek added a comment -

          Thanks Mark for finding the timeline of that cause, appreciate the effort for the findings. I think it is the only way to do as you said save the job and again configure it.

          abhishek added a comment - Thanks Mark for finding the timeline of that cause, appreciate the effort for the findings. I think it is the only way to do as you said save the job and again configure it.
          abhishek made changes -
          Priority Original: Trivial [ 5 ] New: Major [ 3 ]

          abhishek added a comment -

          Is there a way to patch this issue?, because we have a few Jenkins servers where we have more than 1 subsequent  execute shells in use. will be a pain if this continues.

          abhishek added a comment - Is there a way to patch this issue?, because we have a few Jenkins servers where we have more than 1 subsequent  execute shells in use. will be a pain if this continues.

            Unassigned Unassigned
            abhishek_02 abhishek
            Votes:
            1 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: