IIUC the release plugin version 2.5.1 has the fix for non-root pom releases
(but I *might* be wrong about that)
On Friday, October 10, 2014, Ulli Hafner ullrich.haf...@gmail.com wrote:
Am 10.10.2014 um 21:19 schrieb Jesse Glick jgl...@cloudbees.com
javascript:;:
On Fri, Oct 10, 2014 at
This is what I understood as well. (about m-r-p 2.5.1)
Le 11 oct. 2014 10:07, Stephen Connolly stephen.alan.conno...@gmail.com
a écrit :
IIUC the release plugin version 2.5.1 has the fix for non-root pom
releases (but I *might* be wrong about that)
On Friday, October 10, 2014, Ulli Hafner
Hi Ullrich,
As correctly pointed by you I am having issue with releasing snapshots. I
looked at the suggestions listed in the link mentioned by you, but they
are not working for me. I am using the following commands for releasing the
plugin:
mvn
I see. The workaround does not work if your project is not in the root folder
of the git project. You need to move your sources one level up the folder
hierarchy.
I hope that this annoying bug will be fixed by the maven-release-plugin in the
near future…
Am 09.10.2014 um 17:51 schrieb
On Fri, Oct 10, 2014 at 2:23 PM, Ulli Hafner ullrich.haf...@gmail.com wrote:
The workaround
Sorry, which workaround are you referring to?
does not work if your project is not in the root folder of the git project.
What is the bug then? If you have a multimodule project, normally you
would
Am 10.10.2014 um 20:42 schrieb Jesse Glick jgl...@cloudbees.com:
On Fri, Oct 10, 2014 at 2:23 PM, Ulli Hafner ullrich.haf...@gmail.com wrote:
The workaround
Sorry, which workaround are you referring to?
specifying version 2.5 explicitly on the command line
does not work if your
On Fri, Oct 10, 2014 at 3:04 PM, Ulli Hafner ullrich.haf...@gmail.com wrote:
which workaround are you referring to?
specifying version 2.5 explicitly on the command line
Ah, well that is just using a new plugin version, which you would also
get by using a newer parent POM.
The release plugin
Am 10.10.2014 um 21:19 schrieb Jesse Glick jgl...@cloudbees.com:
On Fri, Oct 10, 2014 at 3:04 PM, Ulli Hafner ullrich.haf...@gmail.com wrote:
which workaround are you referring to?
specifying version 2.5 explicitly on the command line
Ah, well that is just using a new plugin version,
Hi Ullrich,
Using maven-scm-provider-gitexe 1.9.2 has worked for me. Thanks for your
solution and saving my weekend :)
Regards,
Kishore
On Saturday, 11 October 2014 01:13:02 UTC+5:30, Ullrich Hafner wrote:
Am 10.10.2014 um 21:19 schrieb Jesse Glick jgl...@cloudbees.com
javascript::
Hi Domi, Jenkins Dev team,
I am trying to release the teamconcert-git plugin by running the Maven
release commands (mvn -U release:prepare and mvn -U release:perform). I see
that the mvn -U release:perform completes successfully but plugin is not
available at
Hi Kishore,
no there is nothing more you have to do - just give it some time, check again
tomorrow. There are some background jobs which pick the new stuff up and
publish it.
Domi
On 09 Oct 2014, at 17:51, Krishna Kishore clkkish...@gmail.com wrote:
Hi Domi, Jenkins Dev team,
I am trying
You hit the mvn release bug that only releases snapshots, see
http://jenkins-ci.361315.n4.nabble.com/mvn-release-does-not-work-only-publishes-SNAPSHOT-releases-td4657620.html#a4657831
Am 09.10.2014 um 17:51 schrieb Krishna Kishore clkkish...@gmail.com:
Hi Domi, Jenkins Dev team,
I am trying
Hi Domi,
Thanks for creating the repository. I just signed up in the issue tracker
and my userid in JIRA is clkkishore, please created the required
component.
Thanks,
Kishore
On Friday, 3 October 2014 11:08:05 UTC+5:30, Dominik Bartholdi wrote:
done:
done, welcome a board!
Domi
On 06.10.2014, at 07:49, Krishna Kishore clkkish...@gmail.com wrote:
Hi Domi,
Thanks for creating the repository. I just signed up in the issue tracker
and my userid in JIRA is clkkishore, please created the required component.
Thanks,
Kishore
On
Hi Jenkins Dev Team,
Any update on my request to host a new plugin.
Thanks,
Kishore
On Monday, 29 September 2014 14:46:39 UTC+5:30, Krishna Kishore wrote:
Due to different dependencies we decided not to extend the functionality
of the existing plugin but write a new plugin. The existing
done: https://github.com/jenkinsci/teamconcert-git-plugin
but creating a component for you in the issue tracker failed, what is your
userid in JIRA?
...I don't have permission to create a CI job, can someone else create one?
Domi
On 03.10.2014, at 06:19, Krishna Kishore clkkish...@gmail.com
Due to different dependencies we decided not to extend the functionality of
the existing plugin but write a new plugin. The existing plugin implements
the SCM extension point of Jenkins and the new plugin is much more lighter
and uses the Build extension point. The target audience for the two
How is this one different to the existing teamconcert plugin? [1]
It seems very active.
Domi
[1] https://wiki.jenkins-ci.org/display/JENKINS/Team+Concert+Plugin
Am 28.09.2014 um 06:09 schrieb Krishna Kishore clkkish...@gmail.com:
Hi Jenkins Dev team,
I am with the Rational Team
Hi,
The existing plugin woks with the RTC Source control, it helps teams which
use RTC as SCC and Jenkins as CI engine. The new plugin will work with
projects which use Git as source control and integrate (i.e create
traceability links) Jenkins builds with RTC Work Items and Builds. This
How about extending the existing one with your functionality?
From a users point of view this is what I would love to see - as I guess you
would provite of some of the existing features too
Or maybe extract the parts the two plugins would have in common and create a
base plugin which can be
20 matches
Mail list logo
