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

Providing Unity selection as parameter #6

Open
Alloc86 opened this issue Apr 5, 2016 · 4 comments
Open

Providing Unity selection as parameter #6

Alloc86 opened this issue Apr 5, 2016 · 4 comments

Comments

@Alloc86
Copy link

Alloc86 commented Apr 5, 2016

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

@Alloc86
Copy link
Author

Alloc86 commented Apr 6, 2016

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.

@tommikiviniemi-srs
Copy link

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,

  • Tommi

@JasonGowthorpe
Copy link

+1 to this request, I have the same situation and need to be able to parametrize this choice.
Thanks,
Jason

@tommikiviniemi-srs
Copy link

tommikiviniemi-srs commented Jul 25, 2016

@JasonGowthorpe, I have made a pull request for this: #7

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