[JENKINS-74431] Extract inline JS in ElectricFlowRunProcedure/config.jelly
#391
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Related PRs:
ElectricFlowTriggerRelease/config.jelly
#392ElectricflowDeployApplication/config.jelly
#393ElectricflowAssociateBuildToRelease/config.jelly
#394ElectricflowPipelinePublisher/config.jelly
#395https://www.jenkins.io/doc/developer/security/csp/
JENKINS-74431
This PR was created to extract the inline JS and legacy onClick handlers in
ElectricFlowRunProcedure/config.jelly
.Testing done
I tried to run a kubernetes cluster locally to run the demo server, however, my machine doesn't have sufficient resources to do so. Install CloudBees CD/RO within Kubernetes
@CJkrishnan @jsmith-cb Do you know if there is a better way to test this? Or perhaps if there is an existing test server I can use?
Submitter checklist