Each module will automatically publish its own module artifacts, for example: https://builds.apache.org/job/OpenMeetingsMaven/3/org.apache.openmeetings$openmeetings-core/
We only might need to add something to also publish the assembled Tomcat server including red5 as a build artifact. Sebastian 2014-05-08 9:48 GMT+12:00 [email protected] <[email protected]>: > Hi Maxim, > > our current build is using some hand build Jenkins configuration. > Jenkins does actually provide its own Maven template. When you create a > new Job you can see that option. > > By using that it results in having this kind of build overview: > https://builds.apache.org/job/OpenMeetingsMaven/ > > With a graph of the test results. > > Also it shows details of the module builds: > https://builds.apache.org/job/OpenMeetingsMaven/3/ > > and generates automatically the Test Result overview: > https://builds.apache.org/job/OpenMeetingsMaven/3/testReport/ > > All of that stuff is kind of available in our current build but we all did > that by manually scripting and configuring Jenkins. > I think we should use the Maven template of Jenkins and get rid of our > custom config. We might benefit from improvements that are done to it in > the future with zero effort. And it also looks a bit more cleaner. > > What do you think ? > > Sebastian > > > > > > -- > Sebastian Wagner > https://twitter.com/#!/dead_lock > http://www.webbase-design.de > http://www.wagner-sebastian.com > [email protected] > -- Sebastian Wagner https://twitter.com/#!/dead_lock http://www.webbase-design.de http://www.wagner-sebastian.com [email protected]
