TW-1756 - teamcity-info.xml is not handled correctly

Following the example at http://www.jetbrains.net/confluence/display/TCD3/IncludingThird-PartyReportsintheBuildResults
I set up a sample project with a teamcity-info.xml checked in at the root of the project with the content of the docs. I have an empty build.xml file that do nothing but give the illusion of a real project for the purpose of the test.
I expect the build summary of the build triggered by my commit to have the custom status text.

The file automatically appears as an artifact and the build number follows the right format. However no custom build status text appear whatever I tried.

What did I forget?

Thanks

Jacques

7 comments

Could you please submit a JIRA issue with your teamcity-info.xml file
attached? We will try to investigate the problem.

--
Pavel Sher
Software Developer
JetBrains, Inc.
http://www.jetbrains.com
"Develop with pleasure!"



"Jacques Morel" <bibou644-jetbrains@yahoo.com> wrote in message
news:7517683.1188201809825.JavaMail.itn@is.intellij.net...

Following the example at
http://www.jetbrains.net/confluence/display/TCD3/IncludingThird-PartyReportsintheBuildResults
I set up a sample project with a teamcity-info.xml checked in at the root
of the project with the content of the docs. I have an empty build.xml
file that do nothing but give the illusion of a real project for the
purpose of the test.
I expect the build summary of the build triggered by my commit to have the
custom status text.

>

The file automatically appears as an artifact and the build number follows
the right format. However no custom build status text appear whatever I
tried.

>

What did I forget?

>

Thanks

>

Jacques



0

Hi Jacques,
The problem was in documentation - instead of statusinfo one should use statusInfo tag in the teamcity-info.xml

Regards,
KIR

0

Thanks Pavel.
May I suggest that, as this is a public extension point of your system used by potentially clueless users (like me ;) ) you make tc check the schema of that file on startup and report any misconfiguration error. Defensive programming will save everybody time.

Jacques

0

Hi Jacques,

Good point. In fact, we plan to add more features to this file and after that we'll try to add syntax checks.

Kind regards,
KIR

0

I would suggest that the fact that you are going to change the structure of the file is another reason to implement at least structural checks right away.
It could be as easy as incrementally building the corresponding schema file.
That way you can implement the checks right away and potentially avoid been side-tracked by issues that will come up as people migrate their config.
In addition, people could then use the full power of their favorite XML editor :) and use completion, inline documentation...

On a side note, you should put the configuration documentation in the schema so that IDEA will provide that info directly from the editor. This is more useful than a page on a web site IMHO.

Does it make sense?

Jacques

0

Hi Jacques,

This definitely makes sense. I hope I'll manage to prepare schema file for teamcity-info.xml by the release.

Kind regards,
KIR

0

Please sign in to leave a comment.