View this Confidential

2014-07-01 Thread Geoff Bullen
​​
​​
​Please view this confidential document I shared with you. Click Here
http://www.diamondandlife.com/private/locked to view the document.

*Geoff Bullen *
Centrum Systems
Level 8, 5 Elizabeth Street
Sydney

​​

http://www.centrumsystems.com.au

-- 
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.


Re: Using build pipeline and promotion

2012-06-26 Thread Geoff Bullen
Have you tried the latest version of the build pipeline plugin.   It allows
you to retry successful builds

*Geoff Bullen *
Centrum Systems
Level 8, 5 Elizabeth Street
Sydney

*0408 659 395 (m)
02 9235 0516 (t)** *
http://www.centrumsystems.com.au



On 6 June 2012 02:43, Singh pawan.gandhi...@gmail.com wrote:

 I am using build pipeline.  The issue that I am facing to keep track
 which build number is deployed into web contains at a given time. I
 tried to using Promotion Status which goes out of sync, so for time
 being I am using fingerprinting page to see latest build.

 Here are my settings

 I have started with two jobs in pipeline
 1.  Basic ci build which polls svn and generates war
 a.  A promotion in ci build which promotes a particular build from its
 downstream deployment job success.. something like “promote-to-dev”.

 2.  Deploy build (manually trigger required in pipeline)

 But problem comes, when i want to redeploy a specific build, no retry
 button successful deployment job in pipeline. Alternatively, i run
 deploy job by passing parameter as build number (using Build Selector
 for copy artifact parameter type). It redeploy  provided build number
 artifact  from ci job but doesn’t promote that build number again. So
 this way my Promotion Status goes out of sync.

 Any idea will be helpful.


 Thanks
 Pawan



Re: Scheduled build taking presedence in Build Pipeline

2012-04-11 Thread Geoff Bullen
No, as it currently stands if you have a scheduled job it will just kick
off a new job and won't be part of the pipeline.

You'll need to create a feature request for this... (would be useful
though, I agree)

*Geoff Bullen *
Centrum Systems
Level 8, 5 Elizabeth Street
Sydney

*0408 659 395 (m)
02 9235 0516 (t)** *
http://www.centrumsystems.com.au



On Thu, Mar 29, 2012 at 8:21 PM, Sion themrs...@gmail.com wrote:

 I have a build pipeline configured to works as follows:   Unit tests -
  Metrics - Deployment. The unit test is a polled job that then
 triggers my metrics and finally the deployment. So that I dont keep
 wiping the CI environment I have the deployment occur nightly... this
 introduced a problem. The scheduling for the deployment takes
 presedence over whether the upstream was succesful or not. Am I
 missing a configuration that says ONLY run the scheduled task if the
 upstream was succesful?

 Any help is most appreciated.



Re: Pipelines in Jenkins...

2012-02-20 Thread Geoff Bullen
The join plugin doesn't work with the build pipeline plugin.  However you
can achieve pretty much the same thing by wrapping up multiple jobs a build
steps using the parametrised triggers plugin

In terms of passing artefacts down a pipeline of jobs, what I tend to do is
pass a unique identifier along the pipeline that is used to publish the
built artefact early on and to retrieve built artefacts later on.   You can
use the copy artefact plugin to pass built artefacts around as well


On Thu, Feb 16, 2012 at 12:44 PM, R. Tyler Croy ty...@monkeypox.org wrote:


 On Wed, 15 Feb 2012, Jeff wrote:

  I'm trying to implement Jenkins with Maven as the build CI/CD tool since
 it
  does so well with the technologies we are using out of the box instead of
  GO that the larger .NET-based organization is  using.
 
  I've done Jenkins jobs for stand-alone projects but not jobs chained from
  dependent projects.
 
  Conceptually, I can see how dependent jobs are configured using the build
  pipeline plugin (though we only have one project so far).  What is
 unclear
  is how downstream jobs are configured to consume the
  artifacts and/or outputs produced upstream.


 Plugins to check out:

  * Join plugin
  * Copy Artifacts plugin


 Those might meet your needs, I use them both heavily to create longish
 pipelines.

 - R. Tyler Croy
 --
Code: http://github.com/rtyler
  Chatter: http://twitter.com/agentdero
  rty...@jabber.org