I am looking to get involved in the Gradle community, am a user, advocate, fan and share it through all the channels available to me. I do have a passion for delivery (which was one of the reason Gradle appeals) but having just checked out the CI server have some questions to ask - and hope that I am asking them in the correct place.
>From a deveoper viewpoint I find the Team City builds to lack what I would expect. I have not used Team City so forgive me if it is a tool capability/familiarity issue. When using Jenkins/Hudson in conjunction with Sonar for trending I see trends, visual test status, visual violations etc. I like to see groups of tests, module metrics to determine/maintain internal quality. It does not matter which tools, just that quality is maintained and measured - I am NOT for one moment questioning the quality of the code, am just advocating its visualization. I could contribute here if people feel it would be worthwhile. As for the build pipeline - the whole Continuous Delivery relies to some extent on limiting the time builds are in the red. I noticed that the builds on the CI take upwards of 50 minutes! Thats is a long time to wait for feedback on a build - are there ways to break the build down into stages that would provide faster feedback (or are the public CI builds merely the final stage of such a pipeline?). Could some of the developers share there experiences of the Gradle build pipeline and some of the complexities/issues it deals with - e.g need to be tested on different OS's and Java VMs etc. Would they like to see some improvements in the pipeline? Could I be of assistance in this process? Apart from that am keen to pick up some maintenance tasks if anyone has a particular favourite for me to start with then point me in the right direction. Cheers Pete -- View this message in context: http://gradle.1045684.n5.nabble.com/The-Gradle-Build-Visualization-Pipeline-tp5096265p5096265.html Sent from the gradle-dev mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
