I have multiple jobs - each job triggers zero or more "child" jobs - and I have 
a trigger to kick off a full build chain by starting the first job as a 
parameterized build

For example: Trigger -> call Job 1 with "clean deploy" -> Job 1 completes and 
calls Job 2 with the current build parameters, etc, etc

So I can run my trigger with a goal as a parameter and everything will build 
using the parameter I feed into the Trigger.

What I want to be able to do is run thru the Job build cycle twice (with 
different parameters) and after the 2nd cycle kick off a final job:

*         Cycle #1: run with "mvn deploy" parameters

o   This must complete in full before Cycle #2 starts

*         Cycle #2: run  with "mvn dependency:copy-dependencies ..." parameters

o   This copies provided dependencies for each job to a specific folder

*         Last Step: Run final job

o   This scp's the contents of the dependencies folder up to our server

I can't imagine I am doing anything unique or new so hopefully someone can give 
me some pointers


*I cannot run both sets of parameters at the same time or within the same cycle 
- this is not an option* For some reason when I run as "deploy 
dependency:copy-dependencies -DincludeScope=provided 
-DoutputDirectory=$HOME/ghlib -Dmdep.stripClassifier=true 
-Dmdep.stripVersion=true" my artifacts are not created correctly, but if I just 
call "deploy" they do. Since I can't figure that out I figure I can just run 2 
build cycles - once for deploy and once for the dependency copy


Thanks in advance
s


-- 
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/7FB4F0EC1916C84CBA95F6E5A360E40A013E5DCDFFBB%40ghex01.hq.ghds.net.
For more options, visit https://groups.google.com/d/optout.

Reply via email to