|Re: Attempting to set up a Build Once Deploy Many job chain using several Hudson plugins, but ... [message #947923 is a reply to message #947069]
||Wed, 17 October 2012 15:25
| Winston Prakash
Registered: August 2011
Location: Fremont, CA USA
Hi Eric, as Steve mentioned, it would help if you explain what actually happens when you expect the chain to be CI->DEV->QA->UAT->PROD.|
You mentioned Job A has "Build other Projects" (downstream) checked and Job B has "Build after other projects are built" (upstream). You need either one of this, not both (unless your Job B has special setup to test the build artifacts of A).
Couple of Questions
- How does B do the deployment? Is it a deployment to some appserver
- What is the promotion process you adopted?
I can think of few options
Option1: only B does the deployment to DEV, QA, UAT, PROD based on A outcome. Automation may be little complicated, because it is a one-one with different deployment strategy.
Option 2: You can have more the one Job like Job A (CI) -> Job B (deploy to DEV) -> Job C (Deploy to QA) -> Job D (Deploy UAT) -> Job E (Deploy to PROD). This set up is one-to-one is a chanined fashion. In this case the promotion is manual and at each stage.
Option 3: Depending on some parameter in Job A, and its outcome, trigger
Job A (CI) -> Job B (deploy to DEV)
Job A (CI) -> Job C (deploy to QA)
Job A (CI) -> Job D (deploy to UAT)
Job A (CI) -> Job E (deploy to PROD)
This is one-to-many
I'm guessing Option 1 is complicated. Option 2 requires manual intervention. Option 3 may be a fit for you, but need to be setup correctly using both parameterized and promoted build plugin (wiki.hudson-ci.org/display/HUDSON/Promoted+Builds+Plugin)
Powered by FUDForum
. Page generated in 0.01737 seconds