View this Confidential

[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

[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  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: Build Pipeline Plugin: does not correctly define the upstream build?

[Geoff Bullen]

I haven't been able to recreate this.

Could you create a test instance and some test jobs and see if you get the
same behaviour?

*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 22, 2012 at 1:58 AM, Nicky Ramone  wrote:

> Hello.
>
> I created a simple pipeline. I noticed that it seems to be doing something
> wrong for a build that is not the last one.
> Take this pipeline view, for instance:
>
>   foo-1.0 <http://localhost:8080/view/foo_pipeline/job/foo-1.0/>
>   foo-deploy-qa<http://localhost:8080/view/foo_pipeline/job/foo-deploy-qa/>
>   Svn: 37
> <http://localhost:8080/view/foo_pipeline/#>
>  foo-1.0 #14
>  <http://localhost:8080/view/foo_pipeline/job/foo-1.0/14/>
> Mar 20, 2012
> 4:50:51 PM ART
> Duration: 35 sec
>   foo-deploy-qa #47
>  <http://localhost:8080/view/foo_pipeline/job/foo-deploy-qa/47/>
> Mar 20, 2012
> 4:51:32 PM ART
> Duration: 5.8 sec
>   Svn: 37
> <http://localhost:8080/view/foo_pipeline/#>
>  foo-1.0 #13
>  <http://localhost:8080/view/foo_pipeline/job/foo-1.0/13/>
> Mar 20, 2012
> 12:30:41 PM ART
> Duration: 25 sec
>   foo-deploy-qa #90
>  <http://localhost:8080/view/foo_pipeline/job/foo-deploy-qa/90/>
> Mar 21, 2012
> 11:38:26 AM ART
> Duration: 4.5 sec
>   Svn: 35
> <http://localhost:8080/view/foo_pipeline/#>
>  foo-1.0 #12
>  <http://localhost:8080/view/foo_pipeline/job/foo-1.0/12/>
> Mar 20, 2012
> 12:02:30 PM ART
> Duration: 35 sec
>   foo-deploy-qa #91
>  <http://localhost:8080/view/foo_pipeline/job/foo-deploy-qa/91/>
> Mar 21, 2012
> 11:40:57 AM ART
> Duration: 4.6 sec
>   Svn: 35
> <http://localhost:8080/view/foo_pipeline/#>
>  foo-1.0 #11
>  <http://localhost:8080/view/foo_pipeline/job/foo-1.0/11/>
> Mar 20, 2012
> 12:01:08 PM ART
> Duration: 22 sec
>   Pending build of project: foo-deploy-qa
> Trigger
>
> If I decide to trigger the foo-deploy-qa build on the bottom (the one
> that's pending), I would expect the upstream build for it to be foo-1.0#11.
> However, this doesn't seem to happen. I created a simple system script
> with the Groovy Plugin to show the upstream build:
> build = Thread.currentThread().executable
> upstreamBuilds = build.getUpstreamBuilds()
> println "upstream builds: " + upstreamBuilds
>
> So, after the build is run, I can see this in the console:
>
> upstream builds: [hudson.maven.MavenModuleSet@680525[foo-1.0]:14]
>
> As you can see, it always returns the last upstream build (foo-1.0#14 in
> this case), not the one that corresponds to that pipeline (foo-1.0#11 in
> this case).
>
> Has anyone come across this problem too?
>
> Thanks.
> Cheers.
>

Re: Scheduled build taking presedence in Build Pipeline

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

[Geoff Bullen]

Jeff,

We have a pretty similar set up to what you describe.

We use a unique ID based on the build# of the first job in the pipeline.
 This is used to publish to the maven repo in the 1st step and retrieve
artifacts in the subsequent steps.


*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, Feb 16, 2012 at 7:15 AM, 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.
>
> Off the top of my head, how would jobs be created/configured to perform
> the steps in the pipeline sequence below:
>
>1. (JOB) Build shared library
>   1. Run Unit tests
>   2. Upload SNAPSHOT to Maven repository (e.g.,
>   Shared-1.6.3-SNAPSHOT-12.jar)
>2. (JOB) Trigger build of WebApp
>   1. Build WebApp and include latest SNAPSHOT shared library (e.g.,
>   Shared-1.6.3-SNAPSHOT-12.jar)
>   2. Run Unit tests for WebApp
>   3. Upload WAR to repository (e.g., WebApp-1.4.2-SNAPSHOT-6.war)
>3. (JOB) Deploy WebApp-1.4.2-SNAPSHOT-6.war
>   1. Grab WebApp-1.4.2-SNAPSHOT-6.war
>   2. Deploy to DEV server (tomcat container)
>  1. use DEV config.properties file (*not sure how to switch out
>  properties based on deploy env*)
>   4. (JOB) Run Integration tests
>5. (JOB) Deploy to STAGE environment
>   1. Grab (somehow) WebApp-1.4.2-SNAPSHOT-6.war
>   2. Deploy to ALL STAGE server (tomcat container) nodes (load
>   balanced - two to 4 nodes)
>  1. use STAGE config.properties file (*not sure how to switch out
>  properties based on deploy env)*
>   6. (JOB) Run Integration Tests (Validation only?)
>7. (JOB) Run Load tests
>8. (JOB) Deploy to LIVE
>
>
> I've read through the Jenkins Build pipeline plugin page, but could really
> use some additional perspectives/resources, particularly with steps 3-8.
>
> Any tips/resources that I should read or insight into how you do this
> would be appreciated.
>
> --
> Jeff Vincent
> predato...@gmail.com
> See my LinkedIn profile at:
> http://www.linkedin.com/in/rjeffreyvincent
> I ♥ DropBox <http://db.tt/9O6LfBX> !!
>
>

Re: Pipelines in Jenkins...

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

Re: Build Pipeline plugin doesn't interact with Promoted Builds plugin?

[Geoff Bullen]

Hi Chris,

Yes, unfortunately the pipeline plugin doesn't support the features of the
promoted build plugin.   All you can currently do is have a manual trigger
versus an automated trigger.

If you were able to implement this feature we will include it.

Cheers,

Geoff


On Fri, Feb 10, 2012 at 7:25 PM, Chris Withers wrote:

> Hi All,
>
> I'm still struggling with this.
>
> Am I right in thinking that the Build Pipeline plugin doesn't do anything
> with the information provided by the Promoted Builds plugin?
>
> Any chance it will do any time soon?
>
> As I explained in a previous post^, I'd ideally like to have the Pipeline
> View put jobs triggered by promotion put in a column to the right of all
> the downstream jobs of the build doing the promotion.
>
> Moreover, it'd be great if the pipeline view correctly showed manual
> manual promotion steps and only let them be triggered when all other
> promotion criteria had been met...
>
> ...or am I just totally missing something here?
>
> Chris
>
> ^ http://groups.google.com/**group/jenkinsci-users/browse_**thread/thread/
> **103c4c1669aa22b5#
>
> --
> Simplistix - Content Management, Batch Processing & Python Consulting
>- http://www.simplistix.co.uk
>