Dynamic Form Handling

[Brady Shober]

Hello,

I have recently adopted the EC2 Fleet plugin and have discovered a bug in the plugin which I would like to see if anyone else has encountered before and might have a solution.

The plugin provides the ability to configure 2 different Cloud types, and part of the configuration for the cloud includes Launcher configuration, which may include a credential field when configuring to use an SSH launcher. The issue is that when creating a new Cloud, the Add button to add a new credential does not work and I can see in the browser console an error from a web request to https://{jenkins-url}/manage/cloud/[object%20PointerEvent]. If you edit an existing Cloud, then the button works as expected and you can create a credential.

The field for the launcher configuration on the form is defined at https://github.com/jenkinsci/ec2-fleet-plugin/blob/master/src/main/resources/com/amazon/jenkins/ec2fleet/EC2FleetCloud/config.jelly#L52-L54

I've seen that other plugins that add Clouds like those provided by the EC2 plugin don't expose the ability to control the launcher configuration and just have a field specific for the SSH credentials and so don't have a dynamic form that can change based on launcher type, but I'd like to avoid refactoring to that pattern as a breaking change if there was another solution available.

Thank you,
Brady Shober

[Jesse Glick]

It think https://github.com/jenkinsci/credentials-plugin/blob/b47c9c300223f86a7fd0c34e132e013f6920ebaf/src/main/java/com/cloudbees/plugins/credentials/CredentialsSelectHelper.java#L122-L124 was always wrong because it is not using https://github.com/jenkinsci/workflow-step-api-plugin/blob/664bdaf9d0174c05140855af950b14c36c88ab18/src/main/java/org/jenkinsci/plugins/workflow/util/StaplerReferer.java#L59 which links to https://issues.jenkins.io/browse/JENKINS-19413 which links to to https://github.com/jenkinsci/jenkins/pull/6519 which appears to be working around the problem in core (but not other plugins using the same standard pattern, such as yours) rather than fixing it in the `credentials` plugin.

[Jesse Glick]

https://github.com/jenkinsci/credentials-plugin/pull/651 seems to fix this.

[Brady Shober]

Ah thanks, I will watch that PR and check to verify that it is working once it is merged and a new version is released.

On Wed, Sep 10, 2025, 7:24 PM 'Jesse Glick' via Jenkins Developers <jenkin...@googlegroups.com> wrote:

https://github.com/jenkinsci/credentials-plugin/pull/651 seems to fix this.

--
You received this message because you are subscribed to a topic in the Google Groups "Jenkins Developers" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-dev/MamDFUaYPMQ/unsubscribe.
To unsubscribe from this group and all its topics, send an email to jenkinsci-de...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr0BOheZs8LEE9UbE8aZy2RaG01Bf8exeCbUKFZr4Gv8dw%40mail.gmail.com.