Skip to main content
S
Steve5EFE
Inspiring
March 29, 2021
Answered

Command Line Publish not working

  • March 29, 2021
  • 3 replies
  • 307 views

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.

    This topic has been closed for replies.
    Correct answer Steve5EFE

    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

    3 replies

    Peter Grainge
    Community Expert
    Peter GraingeCommunity Expert
    Community Expert
    March 29, 2021

    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

    Use the menu (bottom right) to mark the Best Answer or Highlight particularly useful replies. Found the answer elsewhere? Share it here.
    S
    Steve5EFEAuthorCorrect answer
    Inspiring
    March 29, 2021

    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

    Peter Grainge
    Community Expert
    Peter GraingeCommunity Expert
    Community Expert
    March 29, 2021

    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

    Use the menu (bottom right) to mark the Best Answer or Highlight particularly useful replies. Found the answer elsewhere? Share it here.
    S
    Steve5EFEAuthor
    Inspiring
    March 29, 2021

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

    Jeff_Coatsworth
    Community Expert
    Jeff_CoatsworthCommunity Expert
    Community Expert
    March 29, 2021

    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/11925718), you'll have to contact the RH folks - see https://helpx.adobe.com/contact/enterprise-support.other.html#robohelp for your support contact options.

    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices