Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] RestListParameterValue Not Exported To Remote Access API #174

Open
bugreportsonly opened this issue Nov 28, 2022 · 1 comment
Open
Labels
bug Something isn't working

Comments

@bugreportsonly
Copy link

Describe the bug
The value for a RestListParameterValue Parameter is missing in Remote Access API ("../api/") responses. The parameter 'name' is shown but no 'value' element is present.

To Reproduce
Steps to reproduce the behavior:

  1. Configure a project to use a RestListParameter parameter.
  2. Generate a run/Build the project.
  3. Check the Remote Access API response (<jenkins_url>/<project>/<build#>/api/xml , <jenkins_url>/<project>/<build#>/api/json, etc.)
  4. Note the absence of a value in the response.

Expected behavior
The value of the parameter to be exposed to API requests.

Screenshots
Excerpt from the /api/xml response for a run of an example project; note the absence of a value:
image

Versions (please complete the following information):

  • Jenkins: 2.361.4
  • Plugin: 1.6.3
  • Browser: Firefox, Chrome (any really)

Additional context
Given that the information is saved to the build.xml and is shown properly on the /parameters page, this should be an oversight(?)
Guessing now...Is it possible the issue is the fact the @Exported annotation is still on the value field rather than the getValue method? As part of #85, value was shifted to private and the value.jelly file was adjusted to use the getValue method, but the annotation was not moved/changed.

@bugreportsonly bugreportsonly added the bug Something isn't working label Nov 28, 2022
@h1dden-da3m0n
Copy link
Contributor

Hi there!

Thank you for the bug report! Interesting use case, and certainly nothing I had on my radar.
Also very appreciate the your extra reteach and analysis!
Not sure when I will get to fixing it, especially since I want to re-write the plugin from scratch eventually.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants