Folks; for my use case, I'd like to configure a setup / jenkins project that should work more or less like this:
* clone a defined set of maven modules from a local git server in a defined order into a set of named folders in the current jenkins projects workspace * iterate over these folders and do a "mvn clean install" on each one of them (and make the build fail if any of these maven builds fail), * run a shell script that takes the outcome of the last of these projects and launches it locally using either another shell script or a java -jar command (standalone dropwizard based service). So far, I tried various approaches to resolve this and, all the time, failed. Browsing the web, I read that the most common way of doing this is to have a parent pom somewhere in version control which gets checked out and built - however this is something I'd ideally like to avoid. Do you think such an approach is in some way possible? How, if so? TIA and all the best, Kristian -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/3c75cb87-f9d3-4555-9311-154685b360b7%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
