deployment - Jenkins - Promoting a build to different environments -


i hoping guidance on best way promote build through environments.

we have 3 environments, dev, staging, prod.

the dev jenkins build running in continuous integration set-up, code checked in subversion, jenkins run new build (clean, compile, test, deploy).

the tricky bit when comes staging , prod.

the idea able manually promote successful dev build staging. staging build check out dev's svn revision number, build, test, deploy staging , create branch in svn.

lastly release manager manually promote staging build prod. prod build check out branch previous staging build, deploy prod , tag branch release.

i have tried use combination of promotion builds plugin , paramterized trigger plugin no luck. subversion revision number doesn't seem passed between dev build staging build.

does have guidance on process promote build through multiple environments?

in scenario, why need go , label branch in svn? don't use svn, w/ tfs, when hudson/jenkins gets code, changeset number has retrieved in build log. know code build came from, , @ time.

then promote build environment environment using hudson, source control system doesn't need know code deployed.


Comments

Popular posts from this blog

linux - Using a Cron Job to check if my mod_wsgi / apache server is running and restart -

actionscript 3 - TweenLite does not work with object -

jQuery Ajax Render Fragments OR Whole Page -