Command Line Build with CocosCreator 3.8.6

Cocos Creator
1

Hey everyone.

Needs some help getting the a newer version of the engine to build from the CLI. Before my team was using version 2.3.4 and it worked fine, but now that the engine is tied into the Dashboard it doesn’t seem to want to run headless. Any thoughts.

Output from the CLI:

init **** success
Load profile failed: local://editor/packages.json
Load profile failed: local://editor/package.json
Load profile failed: project://editor/package.json
Load profile failed: local://packages/ui-kit.json
start **** info
start **** info
Arguments:
  C:\ProgramData\cocos\editors\Creator\3.8.6\CocosCreator.exe: true
  path: (ProjectPath)
  build: configPath=(FilePath)\GameBuildConfig.json
  dev: false
  home: (FilePath)\.CocosCreator

Please manage your project through CocosDashboard

startup...

This line seems suspicious to me like the Creator is not being called corrected. (Arguments:
C:\ProgramData\cocos\editors\Creator\3.8.6\CocosCreator.exe: true) Just not sure how to fix that.

Any thoughts?

2

If you have not downloaded CocosDashboard, please download it first.

3

I had it downloaded. The problem I am facing is we want to run build via continuous integration/Azure Pipeline so the build is running on a server vs a local device. So there is no user interaction for the build.

Any thoughts for that?

4

I have no ideas about Azure Pipeline. But normally you should install the Cocos and Cocos Dashboard on the server for the Command Line Building. Here is the link of Command Line Build for your reference: Publish from the Command Line | Cocos Creator

5

I have tried several of the things in that article. Generally all with the same results. When I run the command it just opens the Dashboard rather than build the game.

Seems like it might just not be supported in the way it needs to be for continuous integration. With AzurePipeline I really just need a way to run a build without having to open the engine or the dashboard applications.

6

Try the command line with CMD. If it is OK, I must be available to integrate into jenkins or Azure. If it is not OK with CMD, please have a check with you command.

7

I was able to get this to run locally.

The command wanted --project not --path. Simple mistake, but working now.

1 Like