Writing Bamboo Plugin for Test Runners and Parsers

[Ryan Strope]

I'm looking for someone to give me some guidance or point me to some good resources in creating Bamboo plugins that SPECIFICALLY target the Testing section of a Build Plan.

I can see looking through my Bamboo settings that the pre-packaged Plugins have modules for Test Runners, and Test Parsers e.g. NUnit, MSTest, VSTest etc so clearly there is a set of Standards, practices and algorithms for creating test runners and parsers just like there is for creating standard do some action modules as described in the many how to create a [Insert Atlassian product here] Plugin.

I've already played around and created a few standard plugins but I can't figure out what to do to make a plugin show up under the Testing selection of Build Plan The ultimate goal of course to have my unit and integration test results show up in the Test Results tab.

Little background on me

I'm primarily a C# Developer, and an intermediate to advanced PowerShell developer, but I can also hold my own in VBA, VBScript when necessary. I've done a lot of work in C, C++ but that was 10 plus years since i last seriously picked up those languages. As for Java I've only ever dabbled in it so i'm definitely in unfamiliar waters especially coming from a tightly integrated user friendly build environment like Visual Studio to how Java Builds are put together and managed (been playing with Eclipse to some measure of success i.e the plugins I had mentioned creating above)

So the question is where can I find out more about making my own test runners and parsers to use in my Bamboo Builds.

Thanks in advance for any help, advice or pointing me in the right direction

[Gonchik Tsymzhitov]

Hi! 

If you want to start write plugins (apps) -> let's check this docs:

https://developer.atlassian.com/server/bamboo/

Also, you can review source code different plugins e.g.

https://bitbucket.org/iuliushutuleac/bamboo-logparser-plugin

About your use case, I am parsing generic logs into Junit report. Hence everything starting to universal.  

Cheers,

Gonchik Tsymzhitov

[Ryan Strope]

I've already been through the documentation on the community and as many places as i could find them including building a few of my own plugins what i can't find though is how to get the tasks parts of my plugins to go into the proper Task Type as shown below

I need them to show up here and there is nothing out there that clearly spells out what makes something a Builder, a Test parser or runner, source control, etc

[Gonchik Tsymzhitov]

Hi @Ryan Strope! 

Please, put in your  atlassian-plugin.xml 

in taskType scope add this parameter:

<category name="test"/> 

Cheers,

Gonchik Tsymzhitov