-
-
Notifications
You must be signed in to change notification settings - Fork 300
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
How to pass job variables to job.play() #2731
Comments
Hmm, that should work. I've had trouble in the past with the way the Gitlab API handles array though, since they didnt seem to be consistent. Ill give it a look and follow up when I have the time. |
If I get time this weekend I’ll look into contributing with a PR. This is a
pretty solid API wrapper. Making it align to the Gitlab API more closely
will only make it better.
Thanks.
|
Fixed for the next release! |
Wow! That is awesome. I failed to find time. I’ll upgrade when it’s
available and test it out!
|
@jdalrymple I see this is tagged for the next major release. When are you intending to release? |
End of the month! 🤞 At least the rc will be available then for people to test out. Currently just need to fix the CI pipeline for the automated release and testing. |
@Prophet32j Give the latest canary a try, it should be fixed! |
🚀 Issue was released in |
Description
There doesn't appear to be an ability to pass variables to a pipeline when playing from the gitbeaker API. The Gitlab Jobs API shows it as the payload in the call: https://gitlab.com/gitlab-org/gitlab/-/blob/master/doc/api/jobs.md#run-a-job
I need to pass in a couple variables which will simplify my entire process.
Something like this is what I would expect with this API:
Checklist
The text was updated successfully, but these errors were encountered: