• Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
    Dedicated community for Japanese speakers
  • 한국 커뮤니티
    Dedicated community for Korean speakers
Exit
0

automating parents and children

New Here ,
Jan 14, 2009 Jan 14, 2009

Copy link to clipboard

Copied

We are looking to place our Help system in a new source control system (Team Foundation Server, e.g. "TFS") and have it auto-built on the Build Machine, probably on a weekly basis rather than daily.

Our help system consists of one "parent" CHM and a number of "child" CHMs. We have previous experience automating a small, single CHM help file using StarTeam, but no experience in how to automate a parent/child setup.

My working assumption of how this will work is we create a FinalBuilder command line for each help project, and that our parent CHM should be built last.

Am I being too simplistic? Is there anything we need to keep in mind or look out for?

Thanks!

Views

535

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Jan 14, 2009 Jan 14, 2009

Copy link to clipboard

Copied

And, as usual, I forget the basics! :)

We're using RH7, with separate copies installed on my machine (for editing changes in our Help) and on the build machine (this is the copy that will be used to check out, compile, and check in our Help on the build machine).

We're using Team Foundation Server as our source control, and Final Builder is the software used on our build machine.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Advisor ,
Jan 14, 2009 Jan 14, 2009

Copy link to clipboard

Copied

Have you looked into the batch file option in a command-line build? You can build multiple projects, multiple layouts, and multiple outputs; just enter one line for each.

In the example below, note that double quotes are used to encase any strings with spaces. Note also the relative location of our WebHelp merged folders in relation to the .bat file, and then the -l key for the layout and -o for the output. See the RH 7 Help for more details. Also make sure there are no line breaks for each build (in Notepad, turning off Word Wrap should show that - if not, remove them).


Good luck,
Leon

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Jan 14, 2009 Jan 14, 2009

Copy link to clipboard

Copied

We use the default names for our layouts, so using one of your examples, would it be:

c:\Program Files\Adobe\Adobe RoboHelp 7\RoboHTML\RHCL.exe" realtime\realtime.xpj -l "Microsoft HTML Help (Primary Layout)" -o c:v9_pdf_output\realtime

Is that correct?

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Advisor ,
Jan 15, 2009 Jan 15, 2009

Copy link to clipboard

Copied

Absalootle!

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
Feb 09, 2009 Feb 09, 2009

Copy link to clipboard

Copied

LATEST
One thing is a shame though. If you work with RSC (version control) you cannot GET the latest version through a commandline option. So you always have to get the latest version manually and then you can build automatically...

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Resources
RoboHelp Documentation
Download Adobe RoboHelp