Chandra:
The CI job is a maven job that pulls the code from the SCM (using the TFS
plugin) and it builds the java asset using maven. This job then uses the
post-build Actions step called Archive for Clone Workspace SCM) to archive its
workspces for consumption by a downstream job. Also, this
how is this configured?
On Tuesday, March 4, 2014 7:57:29 AM UTC-5, eric...@rocketmail.com wrote:
I use the build pipeline plugin for this purpose. The first link in the
chain is a CI build that polls the SCM repo and then subsequent downstream
jobs are used to promote the build
I use the build pipeline plugin for this purpose. The first link in the
chain is a CI build that polls the SCM repo and then subsequent downstream jobs
are used to promote the build DEV-.TEST-UAT-PROD
On Monday, March 3, 2014 2:53 PM, Stephen Connolly
stephen.alan.conno...@gmail.com wrote:
We've been using Jenkins for a year or so as our CI tool, but would like to
set it up somehow to also do our environment deployments. I've been testing
around with Atlassian Bamboo, which nicely integrates both CI and
Deployments; however, we'd like to stay with Jenkins since it's free.
Is
The promoted builds plugin is a good starting point.
After that it depends where you are deploying your app to.
In general, you set up your build to archive the artifacts... Then you set
up promotions to move the archived artifacts to their target servers...
Parameterized promotions can help if
