[Warning] Topic Design-Details references an undefined anchor: "#IO_STATUS" in topic Constants
Also note that entering anchors with upper case characters won't cause actual errors within the output, but they can confuse humans and lead to them creating external links that won't work. This is because all anchor IDs are downcased on publishing, so in the HTML your anchor will be #io_status. It's thus best to use only lower case.
Regards,
Tim (EC Software Documentation & User Support)
Private support:
Please do not email or PM me with private support requests -- post to the forum directly.
If you're also getting this in the normal command console it would be helpful if you could send us a small demo project that reproduces the issue so that we can look into it. Pack everything in a zip and mail it to support AT ec-software.com (replace the AT with @) and we'll check it out.
Hi, I finally found the problem, it was actually related to user permissions. All is good now, but I have another question, which I will ask in a new thread.
Hello again,
now I setup my project like I wanted but still problems with building from the command line and Jenkins.
On my build server the help file is generated even if the command line still doesn't get back to the prompt.
...that is also an additional problem.
I activated all of the comments in HM but I don't get any message via Jenkins.
I do the same with msbuild but here I get a lot of messages.
I absolutely have no idea why that is not working with HM. Maybe I first have to try hhc.exe and look if that is generating some messages.
Sorry, but then I'm afraid we can't help you. Your only option there is to use a build system that does accept/display console messages correctly. Unfortunately, our developers say they don't currently have time to spend a few hours debugging one that doesn't.
Regards,
Tim (EC Software Documentation & User Support)
Private support:
Please do not email or PM me with private support requests -- post to the forum directly.
Hi Tim,
i think the problem is not on the build system. I changed the "helpman"-command to "hhc.exe". Also this generates a lot of messages.
And isn't it essential to work properly on a common build system like Jenkins?
Additional attempt:
I built the chm with "/keeptemp"-option locally on my build server. Then I changed my Jenkins script so that it uses the HTML Help Workshop tool "hhc.exe" with the temporary generated "output.hhp". That works fine even if hhc.exe returns also with an exit code of 1 (but internet says that seems to be a problem of hhc). I also get some build messages on my Jenkins console output.
So, i think HM console does something wrong.
By the way, creating a PDF via Jenkins also doesn't work. The same behaviour.
I don't know whether you are aware that Windows normally directs program output in both the stdout and stderr files to the console. Some programs write log output to one of these, and some to the other. So if you see console output from one program and not from the other in your build system it is perhaps because you have configured it to log only one of these files, and without eliminating this issue it cannot be concluded that one of the programs "doesn't work".
I had never heard of Jenkins other than in this thread, and having had a quick look at the documentation and all its Windows-alien concepts I can see why I would never want to use it! But there are many Stack Overflow postings on the subject of mixing stdout and stderr in Jenkins which may help you, even if Jenkins does not natively use these names. It seems clear that the cause of the problem is that the process exit code is seen as 1, so until you can get your build system to display the log which I and everyone else always seem to see written by Helpman.exe, you will not know what in your Jenkins script is causing this error exit. Much earlier in this thread I had an issue with the exit code, but the cause was quickly resolved after seeing the log output.