Hi, We use Jenkins and have recently started to use Maven and Artifactory instead of Ant and IVY.
What we are trying to achieve is to compile and unit test a multi-module project, then create a distribution and then test that distribution with smoke tests to give quick developer feedback. Once the test passes we would like to promote the original build and use Maven release allowing for further testing and as a basis for customer releases. To make this as fast as possible I’d like to use a native Jenkins build so that we only rebuild changed modules and remain sure that we are testing the correct versions. It seemed that the Artifactory plugin would make sure that I was testing the expected versions; however I’m running into an issue: The Parent job is a native Maven job using Artifactory plugin, executing mvn install and snapshots versions. A direct child native Maven job then creates a distribution deliverable from modules in the parent. It works fine if the parent job builds all modules, but if the parent job doesn’t have to build everything then the child job can’t find the modules not built. Do you need to build all modules every time, have I miss configured my jobs or is there a better way of achieving what I want? Thanks, Dan -- View this message in context: http://forums.jfrog.org/Question-on-Artifactory-plugin-and-native-Maven-builds-on-Jenkins-tp6603166p6603166.html Sent from the Artifactory - Users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ 10 Tips for Better Web Security Learn 10 ways to better secure your business today. Topics covered include: Web security, SSL, hacker attacks & Denial of Service (DoS), private keys, security Microsoft Exchange, secure Instant Messaging, and much more. http://www.accelacomm.com/jaw/sfnl/114/51426210/ _______________________________________________ Artifactory-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/artifactory-users
