Re: Commit Access Request - svnmerge plugin
Done. Am 07.02.2014 um 02:02 schrieb Hugues Chabot hugues.cha...@gmail.com: Hi, If possible, I would like to contribute to the svnmerge plugin (https://github.com/jenkinsci/svnmerge-plugin). My GitHub username is hugueschabot (https://github.com/hugueschabot). I already submitted a patch a week ago which I already used successfully. Hugues -- 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/groups/opt_out. signature.asc Description: Message signed with OpenPGP using GPGMail
When releasing a plug-in does only release the snapshot version
Since this took me quite some hours to investigate I thought this might help others: If you want to release a new version of your plugin and maven somehow only commits and releases the snapshot version then your are probably also hit by http://jira.codehaus.org/browse/MRELEASE-812. Seems that the current release of the maven release plugin is broken (when using git): sometimes only the snapshot version is committed and released rather than the release version. Workaround until 2.5 of the release plug-in is available: pluginManagement plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-release-plugin/artifactId version2.4.2/version dependencies dependency groupIdorg.apache.maven.scm/groupId artifactIdmaven-scm-provider-gitexe/artifactId version1.9/version /dependency /dependencies /plugin /plugins /pluginManagement signature.asc Description: Message signed with OpenPGP using GPGMail
additional third party package link
Hi, On http://jenkins-ci.org/ there is a link to http://www.freshports.org/devel/jenkins for a FreeBSD package, but if you click over to the LTS tab, there isn't a link to http://www.freshports.org/devel/jenkins-lts. Since we're packaging both now, it would be nice to get a link to that added as well. Can anyone take a look please? (It would also be nice to have the logo updated too. :) ) Thanks, Steve -- 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/groups/opt_out.
How do I detect my upstream job?
Hi, I have the following use case: Jenkins installation inside firewall, and the builds themselves need to be hidden because logs / workspaces might contain secret keys (e.g. OAuth keys). On the other hand, the build status of some of those jobs shall be externally visible.. My current idea is to have a post-build action that uploads the badge of it upstream (the job with the secrets) to some externally visible web site. The only thing I don't know how to do is to determine in the uploader job which job was the trigger. Any ideas except the last-ditch solution of having one uploader job per normal job? Regards, Hakan -- 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/groups/opt_out.
JobProperty missing its descriptor
Hi, I've been trying to implement a JobProperty which is not visible to the user. Its only purpose is to store a String together with the job configuration. I created a class which extends JobProperty and in that class I created a public static class extending JobPropertyDescriptor. I put @Extension on this descriptor. The JobProperty I created only contain a String and a setter/getter for it. The problem I'm having is that it says my descriptor is missing! I tried replacing the JobProperty and JobPropertyDescriptor with AbstractDescribableImpl and DescriptorMyClass respectively, and this works, i.e. no missing descriptor warning. However, this the String I want to persist won't be saved in the job configuration, it will be saved in a separate XML file in the Jenkins home directory. Please help, this is so frustrating. -- 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/groups/opt_out.
Re: How do I detect my upstream job?
Hakan, Are The users in both sides of the firewall the same? If the users are different, you can disable the workspace permission for those outside the firewall and hide the passwords in the logs with https://wiki.jenkins-ci.org/display/JENKINS/Mask+Passwords+Plugin. Regards. Marcelo Rebasti On Mon, Feb 10, 2014 at 1:06 PM, Hakan Tandoğan hakan.tando...@gmail.comwrote: Hi, I have the following use case: Jenkins installation inside firewall, and the builds themselves need to be hidden because logs / workspaces might contain secret keys (e.g. OAuth keys). On the other hand, the build status of some of those jobs shall be externally visible.. My current idea is to have a post-build action that uploads the badge of it upstream (the job with the secrets) to some externally visible web site. The only thing I don't know how to do is to determine in the uploader job which job was the trigger. Any ideas except the last-ditch solution of having one uploader job per normal job? Regards, Hakan -- 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/groups/opt_out. -- 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/groups/opt_out.
Re: Call for starteam-plugin interest
Hi Paul, I'm glad to hear that Borland is planning to work on the Jenkins plugin for StarTeam. I've been thinking about updating the plugin to the newest Jenkins SCM plugin interface, as I've received some internal bug reports about build change sets being incomplete/incorrect and I am hoping that using the new interface will help, though I have done very little research at this point. I started a branch to update to SDK 13.0 last May. You can see my progress at https://github.com/patrick-higgins/starteam-plugin/tree/sdk13.0. It has been long enough that I don't recall the state of that branch. It may or may not be functioning. I've been thinking about the best way to handle the SDK upgrade. Do you have any internal metrics about how many StarTeam installations can use the new SDK? The options I have thought of are: 1. Requiring a new SDK for 0.7.0 (or whatever the next major version bump will be). 2. Forking the plugin to allow parallel development for the old and new SDK. 3. Support both new and old SDK within a single plugin code base. Option #1 seems like the most straightforward, but without usage numbers I'm not sure how realistic it is. Glad to have you! --Patrick On Thu, Feb 6, 2014 at 8:56 AM, Paul Adamson b...@pauladamson.co.uk wrote: Hi Folks, I work on starteam at Borland and my team has been given some time (and code) to contribute to the jenkins starteam-plugin. I've been talking to the plugin lead Jan Ruzicka and he's really enthusiastic about having us on board - so I want to put out a call for anyone else on the list who has an interest in the development of this plugin as we get it flying again. I noticed Patrick Higgins made a rare contribution to the starteam plugin recently - so a special 'Hi' to you! Regards, Paul -- 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/groups/opt_out.
Announcing implied labels plugin
Hi, I would like to announce the first release of Implied Labels Plugin. Its overall goal is to eliminate redundancy in label declarations using globaly configured label implications. More at wiki page https://wiki.jenkins-ci.org/display/JENKINS/Implied+Labels+Plugin -- 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/groups/opt_out.
Re: mvn release does not work, only publishes SNAPSHOT releases
Should we pull a new release of https://github.com/jenkinsci/pom
incoporating 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 javascript:
;-)
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.comjavascript:
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-providers-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:
I have seen this problem today using:
maven 3.1.1
maven-releas-plugin 2.2.2
git 1.8.5
Worked around downgrading git to 1.8.4.
http://jira.codehaus.org/browse/MRELEASE-812
--
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/groups/opt_out.
--
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/groups/opt_out.
--
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/groups/opt_out.
--
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/groups/opt_out.
--
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/groups/opt_out.
--
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/groups/opt_out.
