Issues with Snippet Generator in Jenkins 2.440.2 after Update

Using Jenkins
1

Hello everyone,

After updating Jenkins to version 2.440.2 and all our plugins to their latest versions, we have encountered issues with the Snippet Generator in Jenkins. Previously, everything worked fine, but now several plugins seem incompatible with the Snippet Generator.

Here are some examples of the issues we are encountering:
Acunetix360Scan:
step object of type com.acunetix.plugin.ACXScanBuilder
XrayScan:
no public field ‘serverId’ (or getter method) found in class org.jfrog.hudson.pipeline.declarative.steps.xray.XrayScanStep
updateReleaseBundle:
no public field ‘name’ (or getter method) found in class org.jfrog.hudson.pipeline.scripted.steps.distribution.UpdateReleaseBundleStep

These are just a few examples of the plugins with which the Snippet Generator is failing. Before the update, everything worked smoothly.

Has anyone else experienced these issues after updating Jenkins and plugins? Are there any known solutions or workarounds for these problems?

Thank you in advance for any help or suggestions.

Best regards,
Walter

2

Hello everyone,

I have been investigating and reading in various posts that the issue might stem from the reverse proxy configuration. However, I performed a test with a Docker setup without a proxy and it didn’t work either. Additionally, I installed the plugins cleanly but still couldn’t get it to work.

Could it be a Jenkins problem? Does anyone know if the pipeline plugins are reporting any recent issues?

Any help or suggestions would be greatly appreciated.

Thank you in advance.

3

Hello and welcome to this community, @walterh. :wave:

You may want to get in touch with some of the plugin maintainers (via an issue) for the plugins that don’t work anymore with the snippet generator. :person_shrugging:

4

Hello, thanks!
In this case, it doesn’t seem to be a plugin issue. It’s more of a problem or inconvenience with the pipeline generator. I have been looking through the community, and there are several reports of the same issue.

5

Where are these reports of issues with the Pipeline snippet syntax generator?

I’m aware of a user misunderstanding in JENKINS-73519 because the user was expecting something different from the Acunetix plugin than is stated in the Acunetix plugin documentation. I’m not aware of any other reports of issues with the Pipeline snippet syntax generator.

6

for example:

The problem is with different plugins, I already tried without any proxy and it didn’t work either.
Any recommendations?

7

The first example you noted was specifically described as an nginx reverse proxy configuration problem. The second example has no response to the suggestion that it may also be related to errors in the nginx reverse proxy configuration. Yet you state that you see the failure even without a reverse proxy.

You say

Which specific plugins? What steps do you take with those plugins that shows the issue?

Describe the detailed steps that you take to see the snippets on the working controller and the ways that those steps fail on the controller with the problem. Provide the precise list of plugins that you have installed and their versions as output by the script included in “How to report an issue”. Then hope that someone will find your plugin configuration interesting enough to try your configuration to see if they can duplicate the issue.