-
Notifications
You must be signed in to change notification settings - Fork 449
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
job.Invoke does not pass parameters correctly. #111
Comments
Hi, I have been having the same issue. jenkins.BuildJob("macroservice-graph","id="+i) |
HI. I think I run into the same issue. Trying to call Job.Invoke with a map[string]string but - while it executes the Job - it never passes my parameters. Any update on this? |
Hi! I got the same problem. I found InvokeSimple does work ok, though. Invoke seem to provide slightly different functionality, like checking if the job is running, or include files, and obviously, it's dealing with the parameters in a different way. I'm not sure what was the idea of that, but I think some parts of these methods should be separated and parametrized. Probably the object interface might be improved, but this could imply breaking changes. |
Even better to use Buildjob instead of InvokeSimple. However this doens't provide files inclusion o verifying if job is running either. |
Jenkins does NOT accept build parameters are a JSON body payload.. it only accepts them as query parameters.
job.Invoke needs to be modified to handle this.
The text was updated successfully, but these errors were encountered: