When I have worked with Jenkins and Maven, we also had a build trigger
on the trunk. But it does not trigger a release build, instead it
triggers a snapshot build. Snapshot build does not execute
release:prepare, so it does not cause a change in source control in the
trunk. You do get one techn
Do you really want to build a version every build? I've not used Maven
within Jenkins but I'd imagine you'd have a separate release job that did
that part?
Richard.
On Monday, September 16, 2013, Manoj Kumar Bardhan wrote:
> Hi,
>
> I am using Maven Release Plugin for automate the build & releas
Thanks for your reply.Yes.Actually its working.But when release:prepare
execute it re-increment the trunk pom.XML version.And successfully create
the tag with out snapshot.And when my Jenkins runs after 15 mins it found
that a new version in trunk , and it start build process again. Repeats
same ..
Not sure that could work correctly. If you always ignore pom.xml changes,
you'll sure have other issues soon.
Just had a look inside SVN config and found some interesting parameter
(which I don't find in the Git plugin, btw) : "Excluded Commit Messages".
Ignoring the "copy to tag" and so on messag
The git SCM plugin has a way to ignore changes to certain files, by
specifying those exclusion patterns with a regular expression. It is in
the "advanced" section of the plugin configuration items on the job
configuration page. Your SCM plugin may have a similar setting which would
allow you to i
I understand you're releasing a new version for almost every commit. Though
I like the idea of continuous delivery or equivalent I'm not sure it's
conceptually correct this way.
For your issue, if you really want to stay this way, I suppose I would just
try to update the working copy at the end of
Hi,
I am using Maven Release Plugin for automate the build & release
process.Its working fine but one problem I am facing.
I have created a job, which is checking trunk in every 15 mins, if any
changes found it starts the build & release process.And its working fine.
But , small problem is w