|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
> My guess, it is licensing problem on unity3d plugin.
As said earlier, the plugin only invokes the unity3d command line. So if it fails from jenkins, it means the context in which it runs from the command line on your CMD and from jenkins is different in some way.
Can you try creating a new free-style Jenkins job, add a "Execute Windows bash command" build step and add 3 things
(you can start with just env and cat to make sure they are correct before adding the unity command that takes time)
Let's see what happens:
1. Let's see if this works or fail (note don't just look at the jenkins job result (it might report error/pass status incorrectly based on return codes of your batch script). Make sure the artifact created by your Build.Windows command was created properly - and check its timestamp and location.
2. Let's compare env output from jenkins and from your CMD.