Re: Pipelines in Jenkins...
Hello, I have similar case and I get the theory but cannot make it work. I have job A which is git poll job and as post build action it triggers build B using parametrized trigger plugin with predefined parameter: gitCommit=$GIT_COMMIT But I don't know how to read this parameter in job B. env command in shell script doesn't show it. I tried various combinations with e.g. gitCommit=someConstant and with Pass through git commit but just can't make it working. Would someone share the details of how to pass id (at best git commit id) down the pipeline? thanks Lukasz On Tuesday, February 21, 2012 12:55:32 AM UTC+1, Geoff Bullen wrote: 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
Re: Pipelines in Jenkins...
This is partially what the jenkins maven repository plugin [1] was built
for -- each build is exposed as a separate build repository, so you don't
need to go copying things around.
What we do is :
1) Install the plugin
2) Add the following to the jenkins settings.xml [2]:
3) In the downstream project, add -Pupstream into the maven settings
4) Check the 'Define upstream maven repository' checkbox (build
environment), and set the upstream build that you want to add as a build
repository.
There is a bug to do with snapshot IDs in the current version - there is a
patch that is in master, but I haven't had a chance to roll a release with
it yet. I'd use 0.6.1 until it's fixed if you rely on SNAPSHOT artifacts..
[1]
https://wiki.jenkins-ci.org/display/JENKINS/Jenkins+Maven+Repository+Server
[2]
profile
idupstream/id
repositories
repository
idupstream/id
url${env.Jenkins.Repository}/url
releases
enabledtrue/enabled
/releases
snapshots
enabledtrue/enabled
/snapshots
/repository
/repositories
pluginRepositories
pluginRepository
idupstream/id
url${env.Jenkins.Repository}/url
releases
enabledtrue/enabled
/releases
snapshots
enabledtrue/enabled
/snapshots
/pluginRepository
/pluginRepositories
/profile
On Thu, Feb 16, 2012 at 1:44 AM, 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
Re: Pipelines in Jenkins...
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
Re: Pipelines in Jenkins...
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 pgpWf75zKMiQP.pgp Description: PGP signature
