Re: Backporting for 1.554.2 started
1.554.2 RC posted. 2014-05-14 5:39 GMT-07:00 oliver gondža ogon...@gmail.com: Backporting is finished. There are 12 fixes only, no critical or blocker issues. No fix was rejected. https://issues.jenkins-ci.org/secure/IssueNavigator.jspa? reset=truejqlQuery=labels+%3D+%221.554.2-fixed%22 -- oliver -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- Kohsuke Kawaguchi -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
git-parameter-plugin 0.3.2 released
Hi I am happy to announce that finally after more than two years we have a new version of the git-parameter plugin available. As the previous maintainer Lukanus did not have time to work on this plugin I took over the work for the time being, but am happy that I could skype with him. It looks as he is interested in adding more features in the months to come. New user visible feature are (see also https://wiki.jenkins-ci.org/display/JENKINS/Git+Parameter+Plugin) are: - Updated help texts for configuration and when selecting your tag/revision - Runs a fetch each time the user enters the Build with parameter. - Run clone when fetch fails on workspace empty (Gabor Liptak) - Merging SortMode from graeme-hill - With an empty workspace the tags are calculated after we made a checkout. This may take a long time. Changes relevant to developer - Added MIT-LICENSE.txt to use the same license as Jenkins-CI. - Added Contributors.textile - Display month not minutes in date. Add HH.mm. Display only first 8 chars of SHA1 (Niklaus Giger) - Add backup pluginRepository (Gabor Liptak) - Use GitTool to query configured location of the git executable (gliptak) - Upgrade to git 2.2.0. (christ66) - Build against latest stable Jenkins-CI version 1.554.1 - New co-maintainer/developer Niklaus Giger (id ngiger) - Version 0.3 and 0.3.1 never made it to the distribution, because of problems with the release mechanism I burned versions 0.3 and 0.3.1 because - I had an old jenkins-ci id ngiger via ngiger at java.net I forgot it did exist. - using git/ssh in developerConnection did not work. scm:git:https works fine for me - mvn release:prepare release:perform did not work. Finally I used mvn deploy; mvn release:clean + adding -SNAPSHOT to version in pom.xml. Thanks to everybody who helped me, especially for those who had their patches laying around for years. It would be nice if you gave this version a chance! Best regards Niklaus -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: mvn release does not work, only publishes SNAPSHOT releases
Have u got any patches / pull requests one can look at?
On Wednesday, May 14, 2014 1:26:24 PM UTC+4, Stephen Connolly wrote:
Well I have long maintained that Jenkins's pom structure does it all
wrong but any time I have wanted to try and fix it *and* had a time window
to try, KK puts too much of a barrier with regard to people getting
confused.
I guess it doesn't help that to fix it, I need to redo the hpi plugin so
that it actually works the Maven way... but then if the people who wrote
the original hpi plugin understood the Maven way they would never have
written the Maven project type in Jenkins the way they did and it would not
be evil!
On 13 May 2014 23:46, Ivan Kalinin pups...@gmail.com javascript:wrote:
Has similar problem recently and your fix did help. But latest parent (
http://maven.jenkins-ci.org:8081/content/repositories/releases/org/jenkins-ci/jenkins/1.33/)
still uses 2.2.2 -- is there any plan to fix that?
On Saturday, March 8, 2014 11:05:15 PM UTC+4, Stephen Connolly wrote:
mvn org.apache.maven.plugins:maven-release-plugin:2.5:prepare
And if that tags correctly then same with perform. Should fix the
-SNAPSHOT issue... The other issue could be a different story
On Saturday, 8 March 2014, Ulli Hafner ullrich...@gmail.com wrote:
git version is 1.8.5.3
The dependency hack does only work if the plugin is top-level. I’m
releasing in a sub-folder.
Am 08.03.2014 um 12:36 schrieb Stephen Connolly
stephen.alan.conno...@gmail.com:
What version of git are you using?
Anything after 1.8.4 needs m-r-p 2.5 or the dependency hack
On Saturday, 8 March 2014, Ulli Hafner ullrich.haf...@gmail.com
wrote:
Has someone a workaround for that problem if the plugin/libray to
release is not in the top-level folder of a git project?
My findbugs plugin is divided into
- findbugs-plugin/library shaded findbugs library
- findbugs-plugin/plugin actual findbugs plugin
When I try to release maven does only publish a SNAPSHOT.
Am 11.02.2014 um 18:52 schrieb Ulli Hafner ullrich.haf...@gmail.com:
That would be helpful, yes.
BTW: This fix does only work if the project is not in a sub-folder :-(
Ulli
Am 10.02.2014 um 23:16 schrieb Stefan Wolf glowwo...@gmail.com:
Should we pull a new release of
https://github.com/jenkinsci/pomincoporating the changes to the release
plugin configuration?
Am Dienstag, 14. Januar 2014 17:47:35 UTC+1 schrieb Vincent Latombe:
I hit that problem recently, adding
plugin
artifactIdmaven-release-plugin/artifactId
version${maven-release-plugin.version}/version
dependencies
dependency
groupIdorg.apache.maven.scm/groupId
artifactIdmaven-scm-provider-gitexe/artifactId
version1.9/version
/dependency
/dependencies
/plugin
was enough to work with latest git (1.8.5.2).
HTH,
Vincent
2014/1/13 Dominik Bartholdi do...@fortysix.ch
;-)
I’ll try to take a look at the m-r-p, but I currently can’t promise any
time - sorry :(
/Domi
On 13.01.2014, at 09:21, Stephen Connolly stephen.al...@gmail.com
wrote:
On Sunday, 12 January 2014, Dominik Bartholdi wrote:
The maven team
Nice dodge of self promotion there
;-)
Btw do you want to take a run at m-r-p?
has just release a git provider based on jgit, if you configure the
release plugin to use this one, then you don’t have to downgrade git.
http://maven.apache.org/scm/maven-scm-providers/maven-scm-pr
oviders-git/maven-scm-provider-jgit/index.html
/Domi
On 12.01.2014, at 11:52, Nigel Magnay nigel.mag...@gmail.com wrote:
I've just had this problem too, with two separate plugins.
maven-release-plugin is just total crapola. Just do a manual mvn
versions:set and deploy.
On Sat, Jan 4, 2014 at 4:17 PM, ogondza ogon...@gmail.com wrote:
To unsubscribe from this group and stop receiving emails from it,
send an email to jenkinsci-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
Sent from my phone
--
You received this message because you are subscribed to the Google Groups
Jenkins Developers group.
To unsubscribe from this group and stop receiving emails from it, send an
email to jenkinsci-de...@googlegroups.com javascript:.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups
Jenkins Developers group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: mvn release does not work, only publishes SNAPSHOT releases
Ha! When I do get around to fixing this it will look a lot like NIH
syndrome, because quite frankly most of the current parent pom is overbaked
and too heavyweight and includes too many workarounds for the incorrect
design within the hpi plugin.
Pull requests would not be compatible with the scope of change required to
do this right
On 15 May 2014 09:45, Ivan Kalinin pupss...@gmail.com wrote:
Have u got any patches / pull requests one can look at?
On Wednesday, May 14, 2014 1:26:24 PM UTC+4, Stephen Connolly wrote:
Well I have long maintained that Jenkins's pom structure does it all
wrong but any time I have wanted to try and fix it *and* had a time window
to try, KK puts too much of a barrier with regard to people getting
confused.
I guess it doesn't help that to fix it, I need to redo the hpi plugin so
that it actually works the Maven way... but then if the people who wrote
the original hpi plugin understood the Maven way they would never have
written the Maven project type in Jenkins the way they did and it would not
be evil!
On 13 May 2014 23:46, Ivan Kalinin pups...@gmail.com wrote:
Has similar problem recently and your fix did help. But latest parent (
http://maven.jenkins-ci.org:8081/content/repositories/
releases/org/jenkins-ci/jenkins/1.33/) still uses 2.2.2 -- is there any
plan to fix that?
On Saturday, March 8, 2014 11:05:15 PM UTC+4, Stephen Connolly wrote:
mvn org.apache.maven.plugins:maven-release-plugin:2.5:prepare
And if that tags correctly then same with perform. Should fix the
-SNAPSHOT issue... The other issue could be a different story
On Saturday, 8 March 2014, Ulli Hafner ullrich...@gmail.com wrote:
git version is 1.8.5.3
The dependency hack does only work if the plugin is top-level. I’m
releasing in a sub-folder.
Am 08.03.2014 um 12:36 schrieb Stephen Connolly
stephen.alan.conno...@gmail.com:
What version of git are you using?
Anything after 1.8.4 needs m-r-p 2.5 or the dependency hack
On Saturday, 8 March 2014, Ulli Hafner ullrich.haf...@gmail.com
wrote:
Has someone a workaround for that problem if the plugin/libray to
release is not in the top-level folder of a git project?
My findbugs plugin is divided into
- findbugs-plugin/library shaded findbugs library
- findbugs-plugin/plugin actual findbugs plugin
When I try to release maven does only publish a SNAPSHOT.
Am 11.02.2014 um 18:52 schrieb Ulli Hafner ullrich.haf...@gmail.com:
That would be helpful, yes.
BTW: This fix does only work if the project is not in a sub-folder :-(
Ulli
Am 10.02.2014 um 23:16 schrieb Stefan Wolf glowwo...@gmail.com:
Should we pull a new release of
https://github.com/jenkinsci/pomincoporating the changes to the release
plugin configuration?
Am Dienstag, 14. Januar 2014 17:47:35 UTC+1 schrieb Vincent Latombe:
I hit that problem recently, adding
plugin
artifactIdmaven-release-plugin/artifactId
version${maven-release-plugin.version}/version
dependencies
dependency
groupIdorg.apache.maven.scm/groupId
artifactIdmaven-scm-provider-gitexe/artifactId
version1.9/version
/dependency
/dependencies
/plugin
was enough to work with latest git (1.8.5.2).
HTH,
Vincent
2014/1/13 Dominik Bartholdi do...@fortysix.ch
;-)
I’ll try to take a look at the m-r-p, but I currently can’t promise
any time - sorry :(
/Domi
On 13.01.2014, at 09:21, Stephen Connolly stephen.al...@gmail.com
wrote:
On Sunday, 12 January 2014, Dominik Bartholdi wrote:
The maven team
Nice dodge of self promotion there
;-)
Btw do you want to take a run at m-r-p?
has just release a git provider based on jgit, if you configure the
release plugin to use this one, then you don’t have to downgrade git.
http://maven.apache.org/scm/maven-scm-providers/maven-scm-pr
oviders-git/maven-scm-provider-jgit/index.html
/Domi
On 12.01.2014, at 11:52, Nigel Magnay nigel.mag...@gmail.com wrote:
I've just had this problem too, with two separate plugins.
maven-release-plugin is just total crapola. Just do a manual mvn
versions:set and deploy.
On Sat, Jan 4, 2014 at 4:17 PM, ogondza ogon...@gmail.com wrote:
To unsubscribe from this group and stop receiving emails from it,
send an email to jenkinsci-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
Sent from my phone
--
You received this message because you are subscribed to the Google
Groups Jenkins Developers group.
To unsubscribe from this group and stop receiving emails from it, send
an email to jenkinsci-de...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups
Jenkins Developers group.
To unsubscribe from this group and stop receiving emails from it, send an
email to jenkinsci-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: ValidateButton without descriptor
I'm trying to do a similar thing but with a hudson.model.ManagementLink.
Problem is that I can't extend ManagementLink AND AbstractDescribableImpl
(as in the example of ProxyConfiguration).
If I implement DescribableMyManagementLink and create the inline
DescriptorMyManagementLink, I can't do the normal getDescriptor()
override, which should be...
@Override
public DescriptorMyManagementLink getDescriptor() {
return (MyManagementLinkDescriptor) super.getDescriptor();
}
...since ManagementLink doesnt have a getDescriptor() since it isn't itself
describable.
Note also, the contents of the index.jelly for MyManagementLink is a series
of components within a f:form tag.
On Thursday, February 23, 2012 11:36:33 PM UTC, Kohsuke Kawaguchi wrote:
The trick is to make your class implement Describable, then define a
nested Descriptor.
Various classes in the core do just that, such as ProxyConfiguration, I
believe.
2012/2/22 b8565524 b856...@nwldx.com javascript::
Hi,
I would like to use f:validateButton control to validate my plugin
config.
The problem is that I haven't got any Descriptor - I use class which
extends
Plugin.
This code:
f:validateButton title=Test progress=Wait... with=param1,param2
method=testConfig/
returns 404.
I was trying to 'hack' method url:
f:validateButton title=Test progress=Wait... with=param1,param2
method=${rootURL}/plugin/myplugin/testConfig/
It does not work... It tries to invoke
http://localhost:8081/descriptorByName/jenkins.model.GlobalPluginConfiguration//plugin/myplugin/testConfig
:(
How can I use validateButton when I haven't got any descriptor?
--
View this message in context:
http://jenkins.361315.n4.nabble.com/ValidateButton-without-descriptor-tp4409633p4409633.html
Sent from the Jenkins dev mailing list archive at Nabble.com.
--
Kohsuke Kawaguchi
--
You received this message because you are subscribed to the Google Groups
Jenkins Developers group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
PMD plugin doesn't use pmd.xml
Hi, I'm having a similar issue to this one: PMD plugin doesn't use pmd.xmlhttps://issues.jenkins-ci.org/browse/JENKINS-10820 Unless I explicitly call pmd:pmd, the graph doesn't show. And if I add pmd:pmd, I see in log: Successfully parsed file... and the graph appears. Jenkins ver. 1.544 Static Code Analysis Plug-ins 1.41 -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: git-parameter-plugin 0.3.2 released
On Thu, May 15, 2014 at 3:24 AM, Niklaus Giger niklaus.gi...@gmail.com wrote:
Runs a fetch each time the user enters the Build with parameter.
Why would you not just use ‘git ls-remote -t’ and avoid the need for
any local clone?
Added MIT-LICENSE.txt to use the same license as Jenkins-CI.
BTW it suffices to specify licenses in the POM.
Also your POM has a lot of redundant info that you get for free from
the plugin parent POM. No distributionManagement is necessary, for
example. Nor do you need to declare the dependency on jenkins-core, or
the source level, or the encoding. I have improved the plugin
archetype POM to show the minimal recommended stuff:
https://github.com/jenkinsci/maven-hpi-plugin/blob/master/hpi-archetype/pom.xml
using git/ssh in developerConnection did not work. scm:git:https works fine
for me
mvn release:prepare release:perform did not work. Finally I used mvn deploy;
mvn release:clean + adding -SNAPSHOT to version in pom.xml.
Yuck. When your local settings are configured properly, normal
release:{prepare,perform} with SSH developerConnection should work
fine. So you were probably missing an SSH private key, or were using a
version of Git unsupported by the default version of the Release
plugin, etc.
IMO we need to stop making (or even letting!) developers run plugin
releases locally. Better to use Jenkins for this. I do not really
trust the M2Release plugin but perhaps there can be a parallel set of
plugin release jobs that use a plain Maven build step. The main issue
is how to give broad enough access to let these jobs be triggered by
anyone able to push to the GH repo, without letting anonymous users do
it. (Maybe a special parameter type which redirects you in an iframe
to github.com to log in, grabs a temporary API token, then passes this
to the build long enough to authenticate the release?)
--
You received this message because you are subscribed to the Google Groups
Jenkins Developers group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
How the get the user that does the build?
Hi, I'm writing a Jenkins build plugin and I need to get the name of the person that started the build, or timer if the build was started by timer and so on. Any idea how this info can be retrieved? Thanks. -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Summary Action on Project page
I make extensive use of summary actions on builds, but I would like to do something similar on the project page (for a summary of all builds)? Where would I start with this? (best I've managed is links to alternate page via ProminentProjectAction and associated index.jelly - but I would much prefer a summary that appears in the project page itself). Thanks -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Summary Action on Project page
On Thu, 15 May 2014 19:06:28 +0200, twr thomas.w.richa...@gmail.com wrote: I make extensive use of summary actions on builds, but I would like to do something similar on the project page (for a summary of all builds)? Where would I start with this? (best I've managed is links to alternate page via ProminentProjectAction and associated index.jelly - but I would much prefer a summary that appears in the project page itself). Thanks Project actions optionally includes jobMain.jelly[1]. Quite similar to build's summary.jelly. [1] https://github.com/jenkinsci/jenkins/blob/0f7b144fd32544a872075d58300a53b9abcca5f4/core/src/main/resources/hudson/model/AbstractProject/main.jelly#L77-80 HTH -- oliver -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: How the get the user that does the build?
Hi, See `Run.getCauses()`. You can extract user identity from UserCause|UserIdCause. -- oliver -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Summary Action on Project page
That works perfectly. Thanks. *However, *the only way I've managed to get it to actually add to the page is by overriding getProjectAction on my Notifier (Publisher) and returning a new instance of my action, but for some reason it *gets added twice*? (currently stuck on version 1.509.2 of Jenkins - if that makes a difference) On Thursday, May 15, 2014 6:16:40 PM UTC+1, ogondza wrote: On Thu, 15 May 2014 19:06:28 +0200, twr thomas.w...@gmail.comjavascript: wrote: I make extensive use of summary actions on builds, but I would like to do something similar on the project page (for a summary of all builds)? Where would I start with this? (best I've managed is links to alternate page via ProminentProjectAction and associated index.jelly - but I would much prefer a summary that appears in the project page itself). Thanks Project actions optionally includes jobMain.jelly[1]. Quite similar to build's summary.jelly. [1] https://github.com/jenkinsci/jenkins/blob/0f7b144fd32544a872075d58300a53b9abcca5f4/core/src/main/resources/hudson/model/AbstractProject/main.jelly#L77-80 HTH -- oliver -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: git-parameter-plugin 0.3.2 released
Hi Jesse
Thanks for your feedback. Some comment of mine is inline.
Am Donnerstag, 15. Mai 2014 17:34:29 UTC+2 schrieb Jesse Glick:
On Thu, May 15, 2014 at 3:24 AM, Niklaus Giger
niklau...@gmail.comjavascript:
wrote:
Runs a fetch each time the user enters the Build with parameter.
Why would you not just use ‘git ls-remote -t’ and avoid the need for
any local clone?
There are two ways to use git-parameter. One using tags and one using
commit-ids. git ls-remote works only with tags and is currently not
supported by git-plugin. It is on my TODO list.
Added MIT-LICENSE.txt to use the same license as Jenkins-CI.
BTW it suffices to specify licenses in the POM.
Thanks for the hint. I was unsure about it. I will remove the MIT-LICENSE
for the next release.
Also your POM has a lot of redundant info that you get for free from
the plugin parent POM. No distributionManagement is necessary, for
example. Nor do you need to declare the dependency on jenkins-core, or
the source level, or the encoding. I have improved the plugin
archetype POM to show the minimal recommended stuff:
https://github.com/jenkinsci/maven-hpi-plugin/blob/master/hpi-archetype/pom.xml
Thanks. Will be fixed in the next relase
using git/ssh in developerConnection did not work. scm:git:https works
fine
for me
mvn release:prepare release:perform did not work. Finally I used mvn
deploy;
mvn release:clean + adding -SNAPSHOT to version in pom.xml.
Yuck. When your local settings are configured properly, normal
release:{prepare,perform} with SSH developerConnection should work
fine. So you were probably missing an SSH private key, or were using a
version of Git unsupported by the default version of the Release
plugin, etc.
Yeah, but a newbie like me can get very confused about it!
IMO we need to stop making (or even letting!) developers run plugin
releases locally. Better to use Jenkins for this. I do not really
trust the M2Release plugin but perhaps there can be a parallel set of
plugin release jobs that use a plain Maven build step. The main issue
is how to give broad enough access to let these jobs be triggered by
anyone able to push to the GH repo, without letting anonymous users do
it. (Maybe a special parameter type which redirects you in an iframe
to github.com to log in, grabs a temporary API token, then passes this
to the build long enough to authenticate the release?)
That would be fine for me and would certainly lower the barrier for
newcomers,
if triggering such a build would be easy, e.g. by pushing a version tag to
the
git repository.
--
You received this message because you are subscribed to the Google Groups
Jenkins Developers group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: PMD plugin doesn't use pmd.xml
The PMD plug-in requires that your build creates the pmd.xml file. I.e., you need to run 'mvn pmd:pmd'. Or how did you produce the pmd.xml file in your build before? Am 15.05.2014 um 16:34 schrieb Jean Pierre Froud jpfr...@gmail.com: Hi, I'm having a similar issue to this one: PMD plugin doesn't use pmd.xml Unless I explicitly call pmd:pmd, the graph doesn't show. And if I add pmd:pmd, I see in log: Successfully parsed file... and the graph appears. Jenkins ver. 1.544 Static Code Analysis Plug-ins 1.41 -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. signature.asc Description: Message signed with OpenPGP using GPGMail
