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

job.Invoke does not pass parameters correctly. #111

Open
ArcticSnowman opened this issue Nov 2, 2017 · 4 comments
Open

job.Invoke does not pass parameters correctly. #111

ArcticSnowman opened this issue Nov 2, 2017 · 4 comments

Comments

@ArcticSnowman
Copy link

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.

@ghost
Copy link

ghost commented Jan 2, 2018

Hi, I have been having the same issue.

jenkins.BuildJob("macroservice-graph","id="+i)

@grabnerandi
Copy link

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?

@ifosch
Copy link

ifosch commented Aug 14, 2020

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.

@ifosch
Copy link

ifosch commented Aug 14, 2020

Even better to use Buildjob instead of InvokeSimple. However this doens't provide files inclusion o verifying if job is running either.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants