• Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Blocker Blocker
    • None
    • Jenkins Version : 2.222.3
      Java version: "1.8.0_251"
      Installed in : Windows Server 2012

      I have Created Jenkins pipeline using pipeline script. After first run when i click on configure and see the pipeline code it shows empty.I have try to execute the pipeline it run but the code is empty. I am unable to update my pipeline or my code as it is empty. Jenkins Version i use 2.222.3. I have tried copying pipeline multiple time but it gets blank after i run the job.

      • I have clicked  save and apply in pipeline job
        *I have tried taking checkout of Jenkins file from git repository.Still it has same problem the settings get clears and it shows empty when i open it for the next time.
        *Tried keeping jenkins file in git and taking checkout still everthing getting vanshed 
        *I have tried in various browser Firefox,Chrome,Internet explorer every where its same
        *Normal other jobs are working fine only issue with the pipeline

        1. Installed_Plugins.txt
          8 kB
        2. Pipeline_Issue.PNG
          Pipeline_Issue.PNG
          89 kB
        3. wfE1S.png
          wfE1S.png
          16 kB

          [JENKINS-62228] Jenkins Pipeline Sourcecode Missing

          We are seeing the same behavior.

          If we save some value in the script box. We are able to see that the configuration as been saved properly using the $JOB_URL/config.xml and visualize the resulting XML of the job.

          When we go back to configure this job. The script box is now empty and if we hit the save button. The data that was previously saved is now gone....

          This is a major blocker!

          Running on Docker kubernetes.

          Jenkins :2.220

          workflow-job: 2.40

          Pascal Laporte added a comment - We are seeing the same behavior. If we save some value in the script box. We are able to see that the configuration as been saved properly using the $JOB_URL/config.xml and visualize the resulting XML of the job. When we go back to configure this job. The script box is now empty and if we hit the save button. The data that was previously saved is now gone.... This is a major blocker! Running on Docker kubernetes. Jenkins :2.220 workflow-job: 2.40

          Yann Rosema added a comment -

          Same here!

          jenkins v 2.336

          Yann Rosema added a comment - Same here! jenkins v 2.336

          Yann Rosema added a comment -

          It was a quick fix in my case: turned out it was the Mixing Security Realms plugin. It has some other major rendering issues, like badly rendering its own oprions.

          Yann Rosema added a comment - It was a quick fix in my case: turned out it was the Mixing Security Realms plugin. It has some other major rendering issues, like badly rendering its own oprions.

          Dorin Bogdan added a comment - - edited

          Hi jglick , svanoort , abayer, basil, dnusbaum 

          Do you have any suggestion about a workaround for this issue?
          The bug is still present.
          Jenkins 2.332.3, 2.346.1
          Windows 10 Enterprise
          Java 11.0.15

          workflow-job-plugin 1189.va_d37a_e9e4eda_

          Dorin Bogdan added a comment - - edited Hi jglick , svanoort , abayer , basil , dnusbaum   Do you have any suggestion about a workaround for this issue? The bug is still present. Jenkins 2.332.3, 2.346.1 Windows 10 Enterprise Java 11.0.15 workflow-job-plugin 1189.va_d37a_e9e4eda_

          Jesse Glick added a comment -

          No steps to reproduce from scratch, and given the stretch of time over two years it is possible that the reporter and distinct commenters are actually encountering unrelated bugs, possibly caused by other plugins not mentioned here.

          Jesse Glick added a comment - No steps to reproduce from scratch, and given the stretch of time over two years it is possible that the reporter and distinct commenters are actually encountering unrelated bugs, possibly caused by other plugins not mentioned here.

          Hilda added a comment -

          Hello jglick 

           

          We have observed that when we have installed Micro Focus Application Automation Tools plugin the Pipeline script is not visible in the UI in the job configuration.

          It is available in the config.xml file, and does not affect the functionality.

          Do you have any suggestions what could be the problem?

          This is the artifact to the latest version of MF plugin.

          https://ci.appveyor.com/project/HPEbot/hp-application-automation-tools-plugin/builds/44048577/artifacts

           

          Thank you,

          Hilda Both

          Hilda added a comment - Hello jglick     We have observed that when we have installed Micro Focus Application Automation Tools plugin the Pipeline script is not visible in the UI in the job configuration. It is available in the config.xml file, and does not affect the functionality. Do you have any suggestions what could be the problem? This is the artifact to the latest version of MF plugin. https://ci.appveyor.com/project/HPEbot/hp-application-automation-tools-plugin/builds/44048577/artifacts   Thank you, Hilda Both

          Mark Waite added a comment - - edited

          hildaboth I can't duplicate the problem. The steps that I took while attempting to duplicate it included:

          1. Create a plugins.txt file based on your Installed_Plugins.txt (use plugin ID instead of plugin name, remove the private appveyor plugin from the list)
          2. Start Jenkins with the following script in the directory with the plugins.txt file
            #!/bin/bash
            
            if [ ! -f ../jenkins-plugin-manager-2.12.7.jar ]; then
              wget https://github.com/jenkinsci/plugin-installation-manager-tool/releases/download/2.12.7/jenkins-plugin-manager-2.12.7.jar
              mv jenkins-plugin-manager-2.12.7.jar ..
            fi
            if [ ! -d plugins ]; then
              mkdir plugins
            fi
            java -jar ../jenkins-plugin-manager-2.12.7.jar --jenkins-version 2.346.1 --latest false --plugin-download-directory plugins --plugin-file plugins.txt
            
            if [ ! -f ../jenkins-2.346.1.war ]; then
              wget https://get.jenkins.io/war/2.346.1/jenkins.war
              mv jenkins.war ../jenkins-2.346.1.war
            fi
            JENKINS_HOME=. java -jar ../jenkins-2.346.1.war --httpPort=9090
            
          3. Complete the installation wizard by adding a user and choosing to install no plugins (since they are all installed through plugins.txt)
          4. Create a Pipeline job JENKINS-62228-Pipeline-source-code-empty-after-save that uses the "Hello world" example
          5. Save the Pipeline job
          6. Open the newly saved Pipeline job and confirm that the Hello world declarative Pipeline is still visible in the page

          When I include that private build of the appveyor plugin, I can duplicate the problem.

          When that private build of the plugin is running, the Jenkins log file includes the following message:

          WARNING hudson.model.Descriptor#verifyNewInstance: Father of org.jenkinsci.plugins.workflow.cps.CpsFlowDefinition@21aa5e1c and its getDescriptor() points to two different instances. Probably misplaced @Extension. See http://hudson.361315.n4.nabble.com/Help-Hint-needed-Post-build-action-doesn-t-stay-activated-td2308833.html

          I suspect that is highlighting that there is a bug in that private build of the appveyor plugin. You'll need to work with the provider of that plugin to resolve the bug in the plugin.

          Closing this bug because it was not originally created to document an issue in an unreleased version of that plugin.

          Mark Waite added a comment - - edited hildaboth I can't duplicate the problem. The steps that I took while attempting to duplicate it included: Create a plugins.txt file based on your Installed_Plugins.txt (use plugin ID instead of plugin name, remove the private appveyor plugin from the list) Start Jenkins with the following script in the directory with the plugins.txt file #!/bin/bash if [ ! -f ../jenkins-plugin-manager-2.12.7.jar ]; then wget https://github.com/jenkinsci/plugin-installation-manager-tool/releases/download/2.12.7/jenkins-plugin-manager-2.12.7.jar mv jenkins-plugin-manager-2.12.7.jar .. fi if [ ! -d plugins ]; then mkdir plugins fi java -jar ../jenkins-plugin-manager-2.12.7.jar --jenkins-version 2.346.1 --latest false --plugin-download-directory plugins --plugin-file plugins.txt if [ ! -f ../jenkins-2.346.1.war ]; then wget https://get.jenkins.io/war/2.346.1/jenkins.war mv jenkins.war ../jenkins-2.346.1.war fi JENKINS_HOME=. java -jar ../jenkins-2.346.1.war --httpPort=9090 Complete the installation wizard by adding a user and choosing to install no plugins (since they are all installed through plugins.txt) Create a Pipeline job JENKINS-62228 -Pipeline-source-code-empty-after-save that uses the "Hello world" example Save the Pipeline job Open the newly saved Pipeline job and confirm that the Hello world declarative Pipeline is still visible in the page When I include that private build of the appveyor plugin, I can duplicate the problem. When that private build of the plugin is running, the Jenkins log file includes the following message: WARNING hudson.model.Descriptor#verifyNewInstance: Father of org.jenkinsci.plugins.workflow.cps.CpsFlowDefinition@21aa5e1c and its getDescriptor() points to two different instances. Probably misplaced @Extension. See http://hudson.361315.n4.nabble.com/Help-Hint-needed-Post-build-action-doesn-t-stay-activated-td2308833.html I suspect that is highlighting that there is a bug in that private build of the appveyor plugin. You'll need to work with the provider of that plugin to resolve the bug in the plugin. Closing this bug because it was not originally created to document an issue in an unreleased version of that plugin.

          Mark Waite added a comment - - edited

          sandeep2602 this bug was reported 2 years ago. You reopened it without providing enough information so that others could help you. It is most unlikely that the cause of this issue match the cause of your issue. Since the original submitter did not provide enough details for others to duplicate the issue and you did not provide enough details for others to duplicate the issue, I'm closing the issue.

          If you would like help with the issue that you are seeing, please open a new issue report and provide the information requested in "How to report an issue". If you choose to ignore those guidelines, you should assume that others may not offer their help.

          Mark Waite added a comment - - edited sandeep2602 this bug was reported 2 years ago. You reopened it without providing enough information so that others could help you. It is most unlikely that the cause of this issue match the cause of your issue. Since the original submitter did not provide enough details for others to duplicate the issue and you did not provide enough details for others to duplicate the issue, I'm closing the issue. If you would like help with the issue that you are seeing, please open a new issue report and provide the information requested in "How to report an issue" . If you choose to ignore those guidelines, you should assume that others may not offer their help.

          I am seeing the same issue pipeline jobs script gets vanished for some reason

          omkar kakarparthi added a comment - I am seeing the same issue pipeline jobs script gets vanished for some reason

          Mark Waite added a comment -

          omkar143 this bug was reported over 2 years ago. You commented on it without providing enough information so that others could help you. It is most unlikely that the cause of this issue matches the cause of your issue. Since the original submitter did not provide enough details for others to duplicate the issue and you did not provide enough details for others to duplicate the issue, it is unlikely that others will be able to help you with the issue that you are reporting.

          If you would like help with the issue that you are seeing, please open a new issue report and provide the information requested in "How to report an issue".

          Mark Waite added a comment - omkar143 this bug was reported over 2 years ago. You commented on it without providing enough information so that others could help you. It is most unlikely that the cause of this issue matches the cause of your issue. Since the original submitter did not provide enough details for others to duplicate the issue and you did not provide enough details for others to duplicate the issue, it is unlikely that others will be able to help you with the issue that you are reporting. If you would like help with the issue that you are seeing, please open a new issue report and provide the information requested in "How to report an issue" .

            Unassigned Unassigned
            mukeshyougi Mukesh Venkatesh
            Votes:
            1 Vote for this issue
            Watchers:
            9 Start watching this issue

              Created:
              Updated:
              Resolved: