Command Line Publish not working

[Steve5EFE]

An attempt to publish a project on the build server using the command line fails because the nominated output preset does not exist, so it seems output presets are NOT considered part of the project.

We cannot create a preset on the build server, as we require a map file to be linked, and that IS part of the project.

This is surely a bug, as the only way we can build on the build server is to first manually load the project in question then manually create the required output preset with the link to the map file. This is so far out of the envlope for a CI server - expecially where mutiple build agents are in use, andy one of which could be called upon to run the build.

[Jeff_Coatsworth]

I suspect for both this thread & the other one you posted (https://community.adobe.com/t5/robohelp/command-line-build-does-not-update-linked-documents/m-p/1192...), you'll have to contact the RH folks - see https://helpx.adobe.com/contact/enterprise-support.other.html#robohelp for your support contact options.

[Peter Grainge]

See the first line of this page. Command Line Generation (grainge.org) The command line has to be run on a machine with a valid RoboHelp licence and RoboHelp does not run on servers.

The syntax to publish is on that page.

________________________________________________________
See www.grainge.org for free Authoring and RoboHelp Information

[Steve5EFE]

It is running with a valid license and it is running on a 2012R2 server. I can load the GUI there with no issues.

[Steve5EFE]

Also, the syntax is not the issue. The command I am using works perfectly on my machine, but not on any other machine unless I first manually create the output preset, then link it to the map file.

[Peter Grainge]

Whilst it may have installed, it is not a supported operating system. Versions of Windows and MS Word compatible with RoboHelp (adobe.com) That may not be relevant isn't the point that it is expecting to see the preset in instance of RoboHelp that you are using. Your comments seem to support that.

Jeff has already pointed out your support options so I think that's where you need to go. 

________________________________________________________
See www.grainge.org for free Authoring and RoboHelp Information

[Steve5EFE · Accepted solution]

After working with Adobe support, we found that when the GIT repo was created, a visual Studio default GGit.ignore file was used, which ignored 'publish/' on tbe basis it is part of one-click deployment. This, of course, resulted in NONE of the output presets being downloaded to the server.

Removing this from git ignore has resulted in server-side builds working correctly