Dot commands using .load
Hi All,
We are using XML file to execute the steps. Usually we are create the environment variable called $BUILDFILE and then manually give the XML file from build forge console. How to get the XML file automatically, I tried using this command .load -s <command> but I am getting this below error no element found at line 1, column 0, byte -1: 18^ 4673888 at /PerlApp/XML/Parser.pm line 187 Some one help me to fix this issue. I am using 7.1.1.1 version Thanks Johnson |
3 answers
Hi All, Hi Johnson, It looks like from the error message that .load is having trouble parsing your XML file because of possibly a malformed or missing element. If there is a way to save the output of your command that is generating the XML for the .load, you might check that the resulting XML file has all the proper elements to be parsed by a XML processor. bju |
Bju,
Thanks for your response! I tried the same XML file loaded manually and it works. Used this command before .load $BUILDFILE - it works but it doesnt work with -s option. Do you have any other idea to get the XML file using different server and execute that XML file Thanks Jonnson Hi All, Hi Johnson, It looks like from the error message that .load is having trouble parsing your XML file because of possibly a malformed or missing element. If there is a way to save the output of your command that is generating the XML for the .load, you might check that the resulting XML file has all the proper elements to be parsed by a XML processor. bju |
Hi,
I have seen in some instances when using the .load -s `command to run` that the command that gets run includes lines or characters that were not expected and are not XML. For example, in one case I noticed that some environment variables were being echo'd out of the command and then the XML. This caused problems for the XML parser. You might try running the command between your backticks in just a regular Build Forge step and look at the output to verify that it is only XML. bju |
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.