Please let me know what you think is the right way to parse maven logs.
I broke my build into three steps: core, clientUI, installer. Each is a multi project maven build. I use "Script" tasks and a script file with targets to handle each step so I ensure the how-to-build is captured in source control. I setup clientUI and Installer to always run so I'll always get an installer even if the clientUI tests fail that one step
now, I have bamboo logs which are difficult to read. I plan to add a parsing step that captures the bamboo log analyze it and write a summary. Were I using ant, I'd set ant to use XML output, slurp it into a structure, extract my data and write a summary. Since I'm using maven, I'm looking at writing a plain text parser for maven.
The effort involved is non trivial and I'm wondering if I'm making this harder than it needs to be.
Do any of ypu run multi-step maven builds in bamboo plans and how to handle extracting the relevant bits out of the inner build steps?
In Java-world, what you could do is to inherit from the class com.atlassian.bamboo.plugins.maven.task.Maven2BuildTask (or Maven3BuildTask). Some options then:
add some marker to the log file that would let you find out where the task starts
redirect the Maven logs to a separate file by using buildLogger.getInterceptorStack().add() method.
have the interceptor generate the summary on the fly - that's what it's for ;-)
Hi all Lets make this Friday fun really fun and post one (or more) of your best jokes! The joke can be about an Atlassian product, or just a really fun joke you want to share! I’m not the best j...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot