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 job specifies the additional post-build Actions step "Build other projetcs (manual step)" to specify the downstrean job.
The downstream job uses the "Clone Workspace" for the Source Code Management sections. My deploy takes place using some ANT code calling a REST API for Mule as we are deploying a Mule asset to an in-house enterprise service bus. All deployment jobs (DEV->TEST->UAT->PROD) in turn use the same "clone archive" and "Build other projects (manual step)" to pass the workspace down the pipeline. Of course prod does not as it end the pipeline. The Build pipeline plugin is a visualization tool where you indicate the starting job and it visualizes the job relationsheip of upstream/downstream jobs. It allows you to manually trigger downstream jobs based upon the sucess of the upstream job. On Monday, June 2, 2014 6:01 PM, Chanda Norton <chanda.nor...@gmail.com> wrote: 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 DEV-.>TEST->UAT->PROD > > > >On Monday, March 3, 2014 2:53 PM, Stephen Connolly <stephen.al...@gmail. com> >wrote: > >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 you have to change the target from >deployment to deployment. > > >For larger deployments, you are deploying to a file share from which >chef/puppet does the actual deployment... But for small deployments you just >push direct to the server eg by the ssh/sftp publisher or by a container >specific plugin (eg tomcat) or by a PaaS specific deployer plugin (eg >cloudbees-deployer-plugin for deployment to cloudbees/cloudfoundry/AWS elastic >beanstalk/google app engine) > >On Monday, 3 March 2014, Caleb Tote <caleb...@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 there a plugin for this type of thing? Any suggestions on how to manage >>deployments? Should we just switch to Bamboo? -- >>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 jenkinsci-users+unsubscribe@ googlegroups.com. >>For more options, visit https://groups.google.com/ groups/opt_out. >> > >-- >Sent from my phone >-- >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 jenkinsci-use...@ googlegroups.com. > >For more options, visit https://groups.google.com/ groups/opt_out. > > > > -- 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 jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
