-
Notifications
You must be signed in to change notification settings - Fork 58
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
Providing Unity selection as parameter #6
Comments
As an explanation to "be able to set the used version with a parameter": I thought about something like having the combo box replaced by a text box (with autocompletion mabye) that allows to use job variables like $myStringParam. That way I could simply pass the correct version name to that parameter of the job. |
This is exactly what we'd need as well. We have several projects using different Unity versions, and use a multi-configuration job with conditional build steps + Groovy scripts to keep all the different permutations in one job. This prevents us from specifying different Unity versions for different projects though, so it would be a very appreciated feature. Thanks so much,
|
+1 to this request, I have the same situation and need to be able to parametrize this choice. |
@JasonGowthorpe, I have made a pull request for this: #7 |
Hi,
currently the Unity version selection on a build step is done with a combo box. While this is nice in normal use cases we have a quite complex build setup and would like to be able to set the used version with a parameter of the job so it can be overridden with a parent build-flow. Is this possible / feasible?
Regards and thanks for this wonderful plugin,
Chris
The text was updated successfully, but these errors were encountered: