-
Notifications
You must be signed in to change notification settings - Fork 12
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
no default value causes remote jobs to fail #26
Comments
Not sure what |
it's a pipeline command that allows you to trigger a remote jenkins job (a different jenkins server). |
Never used that plugin. Also the issue description does not include a stack trace, or any indication of exactly how the upstream and downstream jobs are configured (such as Pipeline script text). Please provide complete, minimal steps to reproduce from scratch. |
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
not sure how out-of-the-box this is, but i am using this to have an "optional" file to pass in (a user can pass in a file, or all the parameters can be filled out when the job is executed). i use this mainly for an remote jenkins server to call this job (in this way, the calling jenkins server does not pass in a base64file)
in essence, in my job, the base64file is optional to pass in. and this works fine when calling it locally from the GUI (I don't have to choose a file). however, when the job is called via the remote jenkins server (remoteTrigger) it seems that the job is (in essence) requiring the file, as the jenkins server logs show:
this same job works fine being called from the remoteTrigger if the base64file parameter isn't part of the config.
i am unsure if this is a jenkins issue or this plugin issue, but figured i would start here since the job will in fact launch fine w/o this file-parameter.
The text was updated successfully, but these errors were encountered: