[Jenkins] Pipeline Scripts are empty and cannot be viewed or edited in UI

[Dorin Bogdan]

Hello everybody,

 

This is Dorin Bogdan from Micro Focus, working on Micro Focus Application Automation Tools plugin.

We face a strange issue that seems to be caused by internal artifacts (most recent is v7.4 of the plugin going to be released very soon).

The steps to reproduce are very simple:

 

1. Create a Pipeline job
2. In Configure page, scroll down to script editor
3. Add the default Hello World script:

pipeline {

    agent any

 

    stages {

        stage('Hello') {

            steps {

                echo 'Hello World'

            }

        }

    }

}

4. Save the job
5. Reopen the Configure page and check the script

Actual result: the script content is empty (even it is correctly saved in config.xml)

Expected result: the script content is visible and can be edited

 

The behavior is identical to the one reported here:

https://issues.jenkins.io/browse/JENKINS-62228

 

The issue is not reproducible with v7.3 of hp-application-automation-tools-plugin.

 

Do you have any suggestions about how to diagnose it?

 

Please check the attached logs (workflow.log and system.log).

 

Environment:

• Jenkins 2.332.3
• Windows 10 Enterprise
• Java 11.0.15
• workflow-job-plugin 1189.va_d37a_e9e4eda_ (please check the attached file installed_plugins.txt)
• Micro Focus Application Automation Tools 7.4-SNAPSHOT (private-362fab4b-appveyor)

Or, you use the latest build / artifact  that is matching the actual sources from Micro Focus Application Automation Tools plugin

 

If you need more details please let me know.

I am also available for an online demo / meeting.

 

Thank you in advance,

Dorin.

[Basil Crow]

Hi Dorin,

I do not know what your problem is, but I know it must be coming from
either AlmServerSettingsGlobalConfiguration,
MCServerSettingsGlobalConfiguration,
OctaneServerSettingsGlobalConfiguration,
RunnerMiscSettingsGlobalConfiguration, or
SvServerSettingsGlobalConfiguration (or some combination of them),
because if I delete all of those classes and all references to them as
in https://github.com/basil/hpe-application-automation-tools-plugin/commit/30b60719a915476cea6c81d251b0e7d2b9291f51
then I can no longer reproduce your problem. So I would suggest
confirming that you can no longer reproduce the problem with that
commit, then adding the deleted code back one file or method at a time
until you identify the specific chunk of code that causes the problem.

Basil

[Dorin Bogdan]

Hi Basil,

Thank you very much for your prompt reply.

I will follow the suggestion as soon as I get free from other higher priorities, then will let you know the findings.

Dorin.

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAFwNDjrt3TG_GJyN5Z6Q9EBu7uKi0iPQ-U0n_7GimBXALnei3Q%40mail.gmail.com.

[Dorin Bogdan]

Hi Basil,

The issue was fixed using this PR:

https://github.com/jenkinsci/hpe-application-automation-tools-plugin/pull/517

Best regards,

Dorin.

[Basil Crow]

On Mon, Jul 11, 2022 at 5:19 AM Dorin Bogdan <dorin....@gmail.com> wrote:
> The issue was fixed using this PR:
> https://github.com/jenkinsci/hpe-application-automation-tools-plugin/pull/517

Great! Glad you were able to resolve this.