unity-builder: The build doesn't build the scene
It builds ok in windows manually, but when i try to build with this action:

How can i know what’s happening?
I think its not building the scenes, because the build its 20mb and the one that i build in windows its > 60mb

/github/workspace/./ogirdor/game
-buildTarget
StandaloneWindows64
-customBuildTarget
StandaloneWindows64
-customBuildPath
/github/workspace/build/StandaloneWindows64/StandaloneWindows64.exe
-executeMethod
UnityBuilderAction.Builder.BuildProject
-versioning
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Comments: 18 (7 by maintainers)
ok i made it, it works with a new empty project. So i find out that i was setting wrong the projectPath, i was using {reporootname}/{subfolder} and it works with just setting the {subfolder}.
So let it as
projectPath: gameand it worked. @Jodebu try with it xD.Now i’m getting another problem more related to the project. maybe you may have an idea why.
4_Unity - Builder.txt
the only thing i can rescue inside the logs:
'' is an incorrect path for a scene file. BuildPlayer expects paths relative to the project folder.The root of your repository is the root of your github workspace during the action (if you don’t customize the checkout process).
So all you have to do if you Unity project is in the folder
myGameis use that as the project path. same for subpaths:my/nested/folder/game.If you’re just starting off it’s probably a good idea to have your project in the root of your repository and that you leave the settings to their defaults.
This should be fixed on master.
Could you please open a separate ticket for this?
This is a separate issue and it’s useful to separate issues to 1 topic per ticket. That way the history will be better searchable.
Ah yea, you’re right about that being the default build method. That build method should normally work fine. It may be related to something specific that not every project has, as this seems to be a new issue.
You could also try removing the
./in your relative path, as a relative path is assumed.So I’m fine to give you my input but I’m not going to debug every person’s project. I do this in my free time too.
I would recommend an approach where you start with an empty project (or the example project from this repo) which should not have these differences. Then incrementally add functionality of which you expect it to cause the issue. I have never experienced these kind of major differences. Perhaps it’s even related to some files being ignored in VCS.
Since you’re using a custom buildMethod I have no way of knowing what goes wrong in your build
Try using the built-in buildMethod (by not specifying this configuration option) and see if that works.
It should work, but in case it doesn’t, there might be another problem in which case I’d ask you to please be specific about what your logs tell you and what your configuration looks like.