Am Dienstag, den 23.08.2016, 01:43 +0200 schrieb Baptiste Mathus: > Not sure I get what you're trying to do, but using pipeline it'd > probably be easy to write that logic you're expressing. >
I'll have a look at pipelines then - thanks for your hint. Well, to maybe explain a bit clearer what we're trying to achieve: We do have a couple of service applications in our environment that include various local maven artifacts providing common core functionalities (database access, authentication, ...). >From a maven project point of view, they are pom "compile" scope dependencies that could come from a central maven repository (and actually they already do, for releases). That's also why the services and the shared modules don't have a common parent / multi-module pom - they logically don't belong to each other that much. >From a development process however, some of the stories our team is working on include changes in several modules (say, the frontend layer, some business logic, as well as even changes in the database model). >From a code versioning point of view they're separate projects living in separated git repositories, in worst case living in tags or subbranches. What we basically want to do using jenkins is to automate the process that, in order to deploy to our testing environment, for this work-in- progress modules, someone needs to take all the relevant branches of all the projects involved, build them in the right order, unzip the final artifact to somewhere on the testing system and launch it. The most straightforward way of doing so (and, actually, the way we do it right now) is to have a shell script that does... - git clone and git checkout -b for all projects and branches to have them as subfolders in a shared workspace structure like /database-api | | | /pom.xml | /auth | | | /pom.xml . . . /service | /pom.xml - have a script run across this structure to do "mvn clean install" in each of the subfolders - have a script enter <service>/target and unzip whatever has been built in there to somewhere on disk. This might not be the best approach to building such structures but so far it works; I'm more than open to better ideas how to solve the same problem. ;) 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 jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/1471932168.4478.13.camel%40gmail.com. For more options, visit https://groups.google.com/d/optout.
