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
I'm sure I'm missing something conceptually, but with a modular
architecture, build artifacts may still be needed in the development
environments, particularly if one team is producing a module consumed by
another team and they want access to the SNAPSHOT build artifacts during
development.
Doesn'
Getting back to this...(BTW thanks for the responses)
How do you generate/control the unique ID? Is the SVN repository revision
a good ID to use? Seems that it would be good to correlate the builds
based on a known reference point. That may not work though with multiple
projects that are based
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 pr
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 St
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 al
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 b
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.
