Re: New plugin - Text finder run condition
github repo https://github.com/jenkinsci/text-finder-run-condition-plugin CI job https://jenkins.ci.cloudbees.com/job/plugins/job/text-finder-run-condition/ 2012/7/13 cjo cjo.john...@gmail.com Please can someone fork this new run condition plugin and add JIRA component for it. https://github.com/cjo9900/text-finder-run-condition-plugin Github and Jenkins-ci user name cjo9900 Wiki page to be moved under Plugins https://wiki.jenkins-ci.org/display/~cjo9900/Text+Finder+Run+Condition+Plugin Thanks Chris
Re: jiraComponent
good catch, thanks
2012/7/13 cjo cjo.john...@gmail.com
Looks like you are missing the pluginId= before the component name,
which should be the
so should be
{jenkins-plugin-info:pluginId=build-flow-plugin|jiraComponent=build-flow}
you might also need to add the
source dir if it is different in github
|sourceDir= build-flow-plugin
see
https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins#HostingPlugins-AddingaWikipage
Chris
On Friday, July 13, 2012 2:11:26 PM UTC+1, nicolas de loof wrote:
Hi,
I've edited https://wiki.jenkins-**ci.org/display/JENKINS/Build+**
Flow+Pluginhttps://wiki.jenkins-ci.org/display/JENKINS/Build+Flow+Pluginto
set jenkins-plugin-info
**jiraComponent to the adequate component name, but the link still
points to build-flow-plugin
Did I miss something ?
Re: Re: New Plugin
+ CI job https://jenkins.ci.cloudbees.com/job/plugins/job/lotus-connections/ 2012/7/12 Vojtech Juranek vjura...@redhat.com Hi, forked as lotus-connections-plugin [1]. I got some error when setting up teams, so please verify that you have the commit rights. Welcome aboard! Vojta [1] https://github.com/jenkinsci/lotus-connections-plugin On Thursday 12 July 2012 10:32:20 Phil Rumble wrote: Done. the repo is called LotusConnectionsPlugin On Wed, Jul 11, 2012 at 1:11 PM, Vojtech Juranek vjura...@redhat.com wrote: Hi, could you push your plugin into github (under your account), so that we can fork it under jenkinsci? Thanks Vojta On Tuesday 10 July 2012 22:03:43 Rumble wrote: Hi, I'd like to add a new plugin LotusConnections which will post a build status message to Lotus Connections. My github id is 'philrumble' Thanks
Re: new CustomHistory plugin
oups ... Failed to fork a repository: https://api.github.com/repos/jenkinsci/CustomHistory/teams anyway repo has been forked : https://github.com/jenkinsci/custom-history-plugin and CI job : https://jenkins.ci.cloudbees.com/job/plugins/job/custom-history/ 2012/7/12 Roman rgrigor...@gmail.com It published there https://github.com/ryg-/**CustomHistoryhttps://github.com/ryg-/CustomHistory Thanks, Roman nicolas de loof nicolas.del...@gmail.com писал(а) в своём письме Thu, 12 Jul 2012 11:47:07 +0400: Can you please publish your plugin on your own github account so that we can fork it on jenkinsci organisation ? 2012/7/12 Roman rgrigor...@gmail.com Hi, I'd like to add a new plugin CustomHistory which provides custom history(any text data) attachment for builds. It could be used for cases when standard jenkins version control tools cannot be used because of build process. My github id is 'ryg-' Thanks, Roman
Re: jBPM workflow plugin fork request
would like to, but jenkins-admin bot is dead 2012/7/10 Jiří Sviták svitak.j...@gmail.com Hello all, could you please fork jBPM workflow plugin and grant me commit access? https://github.com/jsvitak/jbpm-workflow-plugin jBPM workflow plugin uses jBPM 5, which is the current version and is based on BPMN 2.0 standard. Old plugin for jBPM https://wiki.jenkins-ci.org/display/JENKINS/JBPM+Plugin is 3 years dead project and uses older jBPM 3, which uses its own format for business processes and so it's incompatible with jBPM 5. Thanks Jiri Svitak
Re: RE: Backports to LTS 1.446.1
I also would like to backport JENKINS-14113 (from 1.472 : 4e7a43c5863b5e7ad637a5034f75d3c144c45129https://github.com/jenkinsci/jenkins/commit/4e7a43c5863b5e7ad637a5034f75d3c144c45129 ) to fix github webhook 2012/7/9 Vojtech Juranek vjura...@redhat.com Hi James, it's there more then week, so back ported. Vojta On Thursday 05 July 2012 09:28:00 Nord, James wrote: Hi Vojta, I would like to nominate the following, new in 1.473 (2012/07/01) Updating job config.xml shouldn't clobber in-progress builds. (issue 12318) It's not a candidate yet as it hasn't been in a release for more than 2 weeks - but I'm hoping by the time the decision is taken that this would not be the case (given a new latest release is due in a few days.). /James -Original Message- From: jenkinsci-dev@googlegroups.com [mailto:jenkinsci- d...@googlegroups.com] On Behalf Of Vojtech Juranek Sent: 05 July 2012 08:10 To: jenkinsci-dev@googlegroups.com Subject: Backports to LTS 1.446.1 Hi, as agrees on last Jenkins meeting, next LTS will be based on 1.466 [1]. I identified following two critical issues needs to be backported: * JENKINS-11251 - Cannot parse coverage results Premature end of file [2] * JENKINS-13625 - ERR_CONTENT_DECODING_FAILED returned on testResults and console output after Jenkins reload [3] Please let me know if there are any other critical or blocker issues need to be backported to 1.466.1 Thanks Vojta [1] http://meetings.jenkins-ci.org/jenkins/2012/jenkins.2012-06-27-18.01.html [2] https://issues.jenkins-ci.org/browse/JENKINS-11251 [3] https://issues.jenkins-ci.org/browse/JENKINS-13625 ** This message is confidential and intended only for the addressee. If you have received this message in error, please immediately notify the postmas...@nds.com and delete it from your system as well as any copies. The content of e-mails as well as traffic data may be monitored by NDS for employment and security purposes. To protect the environment please do not print this e-mail unless necessary. NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, United Kingdom. A company registered in England and Wales. Registered no. 3080780. VAT no. GB 603 8808 40-00 *** ***
Re: Fork new plug-in for running R scripts
need a github owner to act here to fix the plugin member team
2012/7/7 Bruno P. Kinoshita brunodepau...@yahoo.com.br
Hi Nicolas, thanks!
Unfortunately I believe due to that error I have no rights to write to the
repository.
Would there be a way to give the write rights to my user (kinow), please?
Or I can create a repository using my user account, rather than the company
account.
Thanks again
Bruno P. Kinoshita
http://kinoshita.eti.br
http://tupilabs.com
--
*From:* nicolas de loof nicolas.del...@gmail.com
*To:* jenkinsci-dev@googlegroups.com
*Sent:* Saturday, 7 July 2012 2:02 PM
*Subject:* Re: Fork new plug-in for running R scripts
done :
repo = https://github.com/jenkinsci/r-plugin
ci = https://jenkins.ci.cloudbees.com/job/plugins/job/r/
got this error during fork, don't know the impact :
Failed to fork a repository: {message:Validation
Failed,errors:[{field:user,resource:TeamMember,code:org}]}
2012/7/7 Bruno P. Kinoshita brunodepau...@yahoo.com.br
Hi all,
I was running some R scripts that a friend of mine sent me, and that will
be used during a talk about BioUno. It turned out to be useful and saved me
some time, so I thought it would be useful for other users too (maybe using
r-plugin and plot-plugin together :)
Could someone fork it please? And would it be possible to create a JIRA
component and add me as maintainer, please?
Here's the repository URL: https://github.com/tupilabs/r-plugin
This plug-in was created using python-plugin as reference (actually I
copied most of the code), so I owe the maintainer a beer :-)
Thank you in advance!
Bruno P. Kinoshita
http://kinoshita.eti.br
http://tupilabs.com
Re: Another plugin to fork please
done 2012/6/24 Frederik Fromm frederik.fr...@googlemail.com Please give me commit access for https://github.com/jenkinsci/build-blocker-plugin. I have made some changes that need to be committed. Thanks! I had a deeper look inside the locks and latches plugin. It works on a deeper level, directly on the threads as I understand it. It also uses a the tasks ResourceList to provide the the correct CauseOfBlockage text. This is something I didn't manage to get working until now. Do you think that working with the QueueTaskDispatcher is not as stable as the thread bases thing of the locks and latches plugin. Hmmm... I really would like you opinion about this. have no idea about this implementation detail, just wanted to ensure we don't duplicate efforts ;) The main difference is, that my plugin can monitor jobs that don't need to be change. It is not neccessarily a two way monitoring. Using the locks and latches plugin, both jobs need to have the same lock configured. Thanks again. Frederik 2012/6/23 nicolas de loof nicolas.del...@gmail.com Just wanted to ensure you looked at this plugin, that indeed seems unmaintained. Please check if your plugin supports same feature so we maybe can deprecate locklatches in favor of your plugin (especially if you provide configuration migration) 2012/6/23 Frederik Fromm frederik.fr...@googlemail.com Thanks! As I said, I searched in a lot of code. The locks and latches Plugin is quite old and doesn't use the QueueTaskDispatcher. My tests with my new Build blocker Plugin was working fine. And I need it for my current project. But anyway, have a look at my code. If there are performance or concurreny or any other issues that didn't think of, let me know about them. Thanks! Regards, Frederik Am 23.06.2012 um 20:57 schrieb nicolas de loof nicolas.del...@gmail.com : done repository : https://github.com/jenkinsci/build-blocker-plugin ci job : https://jenkins.ci.cloudbees.com/job/plugins/job/build-blocker I wonder how this plugin overlap with lock and latches plugin https://wiki.jenkins-ci.org/display/JENKINS/Locks+and+Latches+plugin or maybe could supersede ? 2012/6/23 ffromm frederik.fr...@googlemail.com Hi! I just created a simple plugin prevent a job from building while configured other jobs are running. Please fork from here: https://github.com/ffromm/build-blocker-plugin I spent some time searching for a similar functionality but could not find anything like this. I use a QueueTaskDiskpatcher that monitors the currently running jobs. If one of the jobs matches to one of the configured regular expressions in the job to build, then the job stay in the queue. Please put this plugin also under Jenkins-on-Jenkins CI. Thanks!
Re: Another plugin to fork please
done repository : https://github.com/jenkinsci/build-blocker-plugin ci job : https://jenkins.ci.cloudbees.com/job/plugins/job/build-blocker I wonder how this plugin overlap with lock and latches plugin https://wiki.jenkins-ci.org/display/JENKINS/Locks+and+Latches+plugin or maybe could supersede ? 2012/6/23 ffromm frederik.fr...@googlemail.com Hi! I just created a simple plugin prevent a job from building while configured other jobs are running. Please fork from here: https://github.com/ffromm/build-blocker-plugin I spent some time searching for a similar functionality but could not find anything like this. I use a QueueTaskDiskpatcher that monitors the currently running jobs. If one of the jobs matches to one of the configured regular expressions in the job to build, then the job stay in the queue. Please put this plugin also under Jenkins-on-Jenkins CI. Thanks!
Re: Another plugin to fork please
Just wanted to ensure you looked at this plugin, that indeed seems unmaintained. Please check if your plugin supports same feature so we maybe can deprecate locklatches in favor of your plugin (especially if you provide configuration migration) 2012/6/23 Frederik Fromm frederik.fr...@googlemail.com Thanks! As I said, I searched in a lot of code. The locks and latches Plugin is quite old and doesn't use the QueueTaskDispatcher. My tests with my new Build blocker Plugin was working fine. And I need it for my current project. But anyway, have a look at my code. If there are performance or concurreny or any other issues that didn't think of, let me know about them. Thanks! Regards, Frederik Am 23.06.2012 um 20:57 schrieb nicolas de loof nicolas.del...@gmail.com: done repository : https://github.com/jenkinsci/build-blocker-plugin ci job : https://jenkins.ci.cloudbees.com/job/plugins/job/build-blocker I wonder how this plugin overlap with lock and latches plugin https://wiki.jenkins-ci.org/display/JENKINS/Locks+and+Latches+plugin or maybe could supersede ? 2012/6/23 ffromm frederik.fr...@googlemail.com Hi! I just created a simple plugin prevent a job from building while configured other jobs are running. Please fork from here: https://github.com/ffromm/build-blocker-plugin I spent some time searching for a similar functionality but could not find anything like this. I use a QueueTaskDiskpatcher that monitors the currently running jobs. If one of the jobs matches to one of the configured regular expressions in the job to build, then the job stay in the queue. Please put this plugin also under Jenkins-on-Jenkins CI. Thanks!
monitoring plugin svn - github sync broken
https://svn.jenkins-ci.org/trunk/hudson/plugins/monitoring/ - 1.39 SNAPSHOT https://github.com/jenkinsci/monitoring-plugin - 1.35 makes me thing : do we have the svn - github sync mecanism documented somewhere ? we have user doc at https://wiki.jenkins-ci.org/display/JENKINS/Moving+from+Subversion+%28svn%29+to+Github, but can't find anything on the way this svn git branch is maintained
Re: Sources of subversion-plugin?
it seems you released and committed to svn but the sync to github didn't occurred https://svn.jenkins-ci.org/tags/subversion-1.40/ 2012/6/16 Kohsuke Kawaguchi k...@kohsuke.org Let me check. 2012/6/9 Christoph Kutzinski ku...@gmx.de: Hi, I've seen that the subversion-plugin was migrated to GitHub https://github.com/jenkinsci/subversion-plugin/commits/master However, the commits of the latest release (1.40) seem to be missing. Anyone knows what went wrong? cheers Kutzi -- Kohsuke Kawaguchi
Re: New plugin
my jenkins-admin command to fork the repo failed as irc bot is using github api v2 that has been shut down yesterday 2012/6/14 Louis louis...@gmail.com Along the same lines, could I add a plugin? Github ID: louisrli Github repo: https://github.com/louisrli/arbitrary-parameters-plugin Thanks! Louis On Saturday, June 9, 2012 2:17:31 AM UTC-4, Matthew Riley wrote: Hi, I'm creating my first Jenkins plugin. Following the advice at: https://wiki.jenkins-ci.org/** display/JENKINS/Hosting+**Pluginshttps://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins My GitHub ID is mattriley, I already have a repo on GitHub which you can fork at: https://github.com/mattriley/**yammer-plugin-for-jenkinshttps://github.com/mattriley/yammer-plugin-for-jenkins Thanks, Matt
Re: New plugin
I'll follow up, this is now in my TODO ;) 2012/6/14 Louis Li loui...@college.harvard.edu I see. Should I follow up once the bot has been updated, or will there be a queue of plugins until the changes are made? Thanks a lot again. Louis On Thu, Jun 14, 2012 at 12:04 AM, nicolas de loof nicolas.del...@gmail.com wrote: my jenkins-admin command to fork the repo failed as irc bot is using github api v2 that has been shut down yesterday 2012/6/14 Louis louis...@gmail.com Along the same lines, could I add a plugin? Github ID: louisrli Github repo: https://github.com/louisrli/arbitrary-parameters-plugin Thanks! Louis On Saturday, June 9, 2012 2:17:31 AM UTC-4, Matthew Riley wrote: Hi, I'm creating my first Jenkins plugin. Following the advice at: https://wiki.jenkins-ci.org/** display/JENKINS/Hosting+**Pluginshttps://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins My GitHub ID is mattriley, I already have a repo on GitHub which you can fork at: https://github.com/mattriley/**yammer-plugin-for-jenkinshttps://github.com/mattriley/yammer-plugin-for-jenkins Thanks, Matt
Re: [build-flow-plugin] some experiment with jsplumb styling (057c4ba)
indeed, I didn't remembered when I first heard about this. 2012/6/12 domi d...@fortysix.ch I know - you, KK and me where talking about it in Brussels… :) the idea was also to provide new icons via this plugin On 12.06.2012, at 19:03, nicolas de loof wrote: I think KK had such a resource plugin in mind -- Forwarded message -- From: Dominik Bartholdi reply+c-1447997-344b8a6f65eb7315bfe89f48f1a5e28ff7cbefc2-132...@reply.github.com Date: 2012/6/12 Subject: Re: [build-flow-plugin] some experiment with jsplumb styling (057c4ba) To: Nicolas De loof nico...@apache.org @ndeloof I'll gona use jsPlump in an other plugin too - do you think we should externalize it into a separate plugin? maybe we should start a general resource plugin? --- Reply to this email directly or view it on GitHub: https://github.com/jenkinsci/build-flow-plugin/commit/057c4ba2277b646cc4255a725aa31fe05b787d60#commitcomment-1447997
Re: New plugin
done : git: https://github.com/jenkinsci/yammer-plugin ci : https://jenkins.ci.cloudbees.com/job/plugins/job/yammer 2012/6/9 Matthew Riley matt...@matthewriley.name Hi, I'm creating my first Jenkins plugin. Following the advice at: https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins My GitHub ID is mattriley, I already have a repo on GitHub which you can fork at: https://github.com/mattriley/yammer-plugin-for-jenkins Thanks, Matt
Re: New plugin
I tried:
jenkins-admin: Make cloudsmith a committer of stackhammer-plugin
but got response Failed to create a repository: {message:Server Error}
anyone ?
2012/6/9 Thomas Hallgren iron...@gmail.com
I'm not able to push to the https://github.com/jenkinsci/**
stackhammer-plugin https://github.com/jenkinsci/stackhammer-plugin
repository.
Is there something more that I must do in order to get commit rights?
On Saturday, June 9, 2012 12:05:13 PM UTC+2, nicolas de loof wrote:
done
https://github.com/jenkinsci/**stackhammer-pluginhttps://github.com/jenkinsci/stackhammer-plugin
https://jenkins.ci.cloudbees.**com/job/plugins/job/**stackhammer/https://jenkins.ci.cloudbees.com/job/plugins/job/stackhammer/
Re: Re: Plugin for JaCoCo (new)
right, your the best ;) ci job created on https://jenkins.ci.cloudbees.com/job/plugins/job/jacoco/ (pull request validator plugin to be installed soon) 2012/6/1 Jesse Farinacci jie...@gmail.com Greetings, On Fri, Jun 1, 2012 at 12:49 PM, Vojtech Juranek vjura...@redhat.com wrote: I don't know how to convince githut to fork it. Brute force would be to detele the repo and create it from scratch, but there are probably some more elegant solutions.Any idea? There was definitely some weirdness there.. but I think I crudely have imported the project with history. Check out https://github.com/jenkinsci/jacoco-plugin -Jesse -- There are 10 types of people in this world, those that can read binary and those that can not.
Re: Back ports to LTS 1.447.2
2012/5/22 Vojtech Juranek vjura...@redhat.com Hi, once again sorry for LTS delay. I find following issues to be back ported to LTS 1.447.2: Blockers or critical issues: * JENKINS-8663 - Parsing of POM happens before SNAPSHOT-Parents are updated * JENKINS-12994 - Quiet period is blocking other jobs in queue * JENKINS-13129 - Updating built-in plugins doesn't work, the file doesn't get pinned and is overwritten on the next startup * JENKINS-13448 - Guice injector failure can cause failure of whole Jenkins Major issues (explicitly requested on dev list or IMHO possibly critical issues): * JENKINS-1152, JENKINS-3983 - Mail server rejecting emails from hudson, SMTP authentication not working * JENKINS-9882 - Jenkins runs out of file descriptors (winstone problem) * JENKINS-12674 - Too many files open causes Jenkins to stop responding * JENKINS-13238 - Loading All Build History Fails * JENKINS-13649 - Invalid environment variable values when running hierarchical jobs on windows slaves Any other proposals for back ports? JENKINS-13435 Auto Install jdk from oracle downloads html instead of bin Thanks Vojta
Re: [RFC] BuildHive for Jenkins on Jenkins Plugin CI
What's the overlap with jenkins.ci.cloudbees.com we already proposed on governance meeting ? please note we (cloudbees) can install the adequate plugins there to get pull-request checking as buildhive does. 2012/5/18 Jesse Farinacci jie...@gmail.com Greetings, Now that BuildHive has been announced, I think we should start using it as the primary place for all Jenkins' plugin CI needs. It's kind of a pain to manage these things for each plugin ourselves at JonJ - http://ci.jenkins-ci.org I think it also lends itself to us having to be more stable on official JonJ since more and more plugin developers are depending on it to build and test their plugins. This has an inverse effect that JonJ can't be a place to test out more experimental work, as well as other expectations about availability and stability. In addition to being extremely easy to use, BuildHive also will automatically test out pull requests and comment in the GitHub pull request whether the change broke the build. This is totally awesome! I think we may also be able to easily exploit Validated Merge functionality which does roughly the same thing but without the hassle of creating a pull request. The proposal for discussion is to take a snapshot of all our plugin jobs on ci.jenkins-ci.org as an archive. Then delete them from ci.jenkins-ci.org. Utilize BuildHive as the canonical place for Jenkins on Jenkins testing for plugins-only. Continue current usage of ci.jenkins-ci.org for core and forked libs. Comments? -Jesse -- There are 10 types of people in this world, those that can read binary and those that can not.
Re: I created IPMessenger plugin
forked as https://github.com/jenkinsci/ipmessenger-plugin welcome onboard 2012/5/3 nabedge nabe...@gmail.com Of course, I have already read https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins anyway, please give me commit access priviledge or fork from my repository below. 2012年5月4日金曜日 2時09分15秒 UTC+9 nabedge: Hi All. I created a plugin. I would like to host this plugin on jenkins-ci.org but I don't konow how to do it. Does anyone coach me? source is here. https://github.com/nabedge/**ipmessenger-pluginhttps://github.com/nabedge/ipmessenger-plugin IPMessenger(http://ipmsg.org/**index.html.enhttp://ipmsg.org/index.html.en) is simple IM, popular on Japan. So, I implemented Notification plugin for jenkins. regards. nabedge http://twitter.com/nabedge http://mixer2.org/
Re: Fork, please
done https://github.com/jenkinsci/cronProjectAction-plugin https://github.com/jenkinsci/startup-scm-poll-plugin https://github.com/jenkinsci/user-builds-started-plugin 2012/5/2 G. Ann Campbell ann.campb...@shawinc.com https://github.com/ganncamp/cronProjectAction https://github.com/ganncamp/startup-scm-poll https://github.com/ganncamp/user-builds-started Privileged and/or confidential information may be contained in this message. If you are not the addressee indicated in this message (or are not responsible for delivery of this message to that person) , you may not copy or deliver this message to anyone. In such case, you should destroy this message and notify the sender by reply e-mail. If you or your employer do not consent to Internet e-mail for messages of this kind, please advise the sender. Shaw Industries does not provide or endorse any opinions, conclusions or other information in this message that do not relate to the official business of the company or its subsidiaries. Privileged and/or confidential information may be contained in this message. If you are not the addressee indicated in this message (or are not responsible for delivery of this message to that person) , you may not copy or deliver this message to anyone. In such case, you should destroy this message and notify the sender by reply e-mail. If you or your employer do not consent to Internet e-mail for messages of this kind, please advise the sender. Shaw Industries does not provide or endorse any opinions, conclusions or other information in this message that do not relate to the official business of the company or its subsidiaries.
Re: Plugin for JaCoCo (new)
Would you like me to create a repo on github/jenkinci to host this plugin and give you commit access ? 2012/4/30 Ognjen Bubalo ognjen.bub...@gmail.com Hello! There is a long waited plugin we are working on. This project has been accepted as a Google Summer of Code project, so it will be implemented during the summer. First I would like to ask for commit access :). My GitHub id is: ognjenb The URL: https://groups.google.com/**forum/?fromgroups#!forum/** jenkins-jacoco-plugin-mailing-**listhttp://?fromgroups#%21forum/jenkins-jacoco-plugin-mailing-list The Mailing list: jenkins-jacoco-plugin-mailing-**l...@googlegroups.comjenkins-jacoco-plugin-mailing-l...@googlegroups.com Other refs: https://community.jboss.org/thread/194984 https://issues.jenkins-ci.org/browse/JENKINS-10835 Please if you are interested join the Mailing list. Ideas, comments are welcomed! :) Br, Ogi
Re: Subversion plugin support for svn 1.7?
Fully agree about patched libraries, in the meantime, I've been inspired by the merge done by centic on JENKINS-11933 and I'm finalizing a merge for svnkit 1.7.4 to our fork 2012/4/26 Olivier Lamy oliver.l...@gmail.com What about having an other subversion plugin (not bundled with core for license reason) called svn-1.7-plugin and which use svnkit 1.7 ? 2012/4/26 Christoph Kutzinski ku...@gmx.de: Hi, in case no one else has mentioned, there are currently a lot of complaints and a lively discussion in https://issues.jenkins-ci.org/browse/JENKINS-11381 why Jenkins still doesn't support svn 1.7 now that SVNKit 1.7 is released. I would fix this myself, but I don't know what the Jenkins specific patches to SVNKit are and how to apply them to SVNKit 1.7 I'd like to take this opportunity to point out again that using a patched library is *NOT* a good idea and we should try to see how the Hudson guys solved it in this case. cheers Christoph -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy
Re: Subversion plugin support for svn 1.7?
Olivier explained me the licensing issue with svnkit 1.7, with TmateSoft License is not compatible with Jenkins MIT as it requires all derivative to follow complete source code for your application must be available and freely redistributable under reasonable conditions MIT let you do whatever you like with jenkins, this would require a license change, mostly GPL This wouldn't apply if subversion is handled by another plugin, separated from jenkins core distribution. Would be also a good opportunity to get rid of those forks (during merge, I had to tweak the svnkit fork due to our for on trilead-ssh !) Maybe it's time for us to deprecate the subversion plugin. Not sure how to handle backward compat, maybe core could keep a fake subversion plugin to automatically install the (new) svn-plugin on first usage, like OSX Lion does for java runtime wdyt ? 2012/4/26 nicolas de loof nicolas.del...@gmail.com Fully agree about patched libraries, in the meantime, I've been inspired by the merge done by centic on JENKINS-11933 and I'm finalizing a merge for svnkit 1.7.4 to our fork 2012/4/26 Olivier Lamy oliver.l...@gmail.com What about having an other subversion plugin (not bundled with core for license reason) called svn-1.7-plugin and which use svnkit 1.7 ? 2012/4/26 Christoph Kutzinski ku...@gmx.de: Hi, in case no one else has mentioned, there are currently a lot of complaints and a lively discussion in https://issues.jenkins-ci.org/browse/JENKINS-11381 why Jenkins still doesn't support svn 1.7 now that SVNKit 1.7 is released. I would fix this myself, but I don't know what the Jenkins specific patches to SVNKit are and how to apply them to SVNKit 1.7 I'd like to take this opportunity to point out again that using a patched library is *NOT* a good idea and we should try to see how the Hudson guys solved it in this case. cheers Christoph -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy
Re: Windows equivalent for publish-over-ssh plugin?
seems you need https://wiki.jenkins-ci.org/display/JENKINS/Publish+Over+CIFS+Plugin 2012/4/25 Salut karthik.krishnag...@gmail.com Hi All, I am trying to send files/execute commands in a remote windows machine (which is not a jenkins slave). I worked similar kind of stuff for *x environments using publish-over-ssh plugin. How to achieve this for a windows server? Please also assume FTP is not enabled in the remote machine. Thanks in advance.
Re: I would like to host my plugin on jenkins-ci.org
fyi, also created the corresponding job on https://jenkins.ci.cloudbees.com/job/plugins/job/sladiator , waiting for approval to migrate plugins job there 2012/4/17 Jesse Farinacci jie...@gmail.com Greetings, On Tue, Apr 17, 2012 at 3:15 AM, Ullrich Hafner ullrich.haf...@gmail.com wrote: Created https://github.com/jenkinsci/sladiator-plugin Welcome aboard! http://ci.jenkins-ci.org/job/plugins_sladiator/ Welcome aboard, -Jesse -- There are 10 types of people in this world, those that can read binary and those that can not.
Re: glassfish repo must die
2012/4/12 Nord, James jn...@nds.com My bad – I took an action a long time ago to investigate this and I did but never really got back to anyone or progressed it to its conclusion.*** * ** ** Getting an artifact that is not under our control whose project has no interest in pushing it isn’t a problem. ** ** What’s more of a stumbling block – and what I have just asked the maven list is what we do with all the patched jars we have (svnkit/winstone) afaik this is not a problem as long as we distribute it under our own groupId ** ** ** ** /James ** ** *From:* jenkinsci-dev@googlegroups.com [mailto: jenkinsci-dev@googlegroups.com] *On Behalf Of *nicolas de loof *Sent:* 05 April 2012 14:22 *To:* Stephen Connolly *Cc:* jenkinsci-dev@googlegroups.com *Subject:* Re: glassfish repo must die ** ** synch to central will fix dependency to jenkins artifacts (so most of plugins) but we still have some plugins to depend to artifacts that aren't available on central, - guice-2.0.1, or de.regnis.q.sequence:sequence-library (for svn-stuff) for sample ** ** 2012/4/5 Stephen Connolly stephen.alan.conno...@gmail.com On 4 April 2012 23:13, Kohsuke Kawaguchi kkawagu...@cloudbees.com wrote: On 04/04/2012 01:38 PM, nicolas de loof wrote: jenkins-ci.org http://jenkins-ci.org is under our control so we can point it to whatever we like also, plugin can't build without a repo declaration as jenkins artifacts aren't available on central I don't thing this to be a bad practice. Would you expect all developers to configure settings with adequate repo to build your project ? This *only* is a requirement for deployment on central just my 2 cents :P Yes, the goal here is to make it easier for people to check out plugins and build them, so that they can apply patches. Many of them are Maven newbies. ** ** Then let's sync to central. Every added step (like ~/.m2/settings.xml tweaking) is a hurdle. We should have repository definition in POM to avoid this. ** ** Nope... we should just sync to central As Nicolas wrote, repo.jenkins-ci.org is our domain that we control, so the same thing won't happen again. (There is a separate effort to make more of our artifacts available in central, which would eliminate this problem in a long run, but we shouldn't wait for that.) ** ** Why not just hurry that effort along ;-) ** ** 2012/4/4 Jeff MAURY jeffma...@jeffmaury.com mailto:jeffma...@jeffmaury.com You should rather delete this repo definition as it is not a good Maven practice and may lead to the same problem in the future. Jeff On Wed, Apr 4, 2012 at 8:58 PM, nicolas de loof nicolas.del...@gmail.com mailto:nicolas.del...@gmail.com wrote: Hi folks, as you know, glassfish maven repo (aka m.g.o-public) is definitively off, but we depend on it for many plugins dependencies, and this is hardcoded in plugin parent pom (so, to get it fixed, plugin would need to upgrade to a recent jenkins-core dependency). some of you may already encounter dependency resolution issues trying to build a plugin form scratch I volunteer to migrate the 400+ plugins to replace repository pointing to m.g.o-public and replace/add repo.jenkins-ci.org/public http://repo.jenkins-ci.org/public where missing, so that each plugin explicitly defines repository to our infra (I plan to write a tool for that). We discussed this on governance meeting, but I wan't to ensure everybody agree here, so please let me know if you see any drawback or have another suggestion. Nicolas -- Jeff MAURY Legacy code often differs from its suggested alternative by actually working and scaling. - Bjarne Stroustrup http://www.jeffmaury.com http://riadiscuss.jeffmaury.com http://www.twitter.com/jeffmaury ** ** -- Kohsuke Kawaguchi | CloudBees, Inc. | http://cloudbees.com/ Try Nectar, our professional version of Jenkins ** ** ** ** -- ** This message is confidential and intended only for the addressee. If you have received this message in error, please immediately notify the postmas...@nds.com and delete it from your system as well as any copies. The content of e-mails as well as traffic data may be monitored by NDS for employment and security purposes. To protect the environment please do not print this e-mail unless necessary. NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, United Kingdom. A company registered in England and Wales. Registered no. 3080780. VAT no. GB 603 8808 40-00 **
Re: glassfish repo must die
2012/4/5 Jesse Farinacci jie...@gmail.com
Greetings,
On Thu, Apr 5, 2012 at 4:04 AM, Arnaud Héritier aherit...@gmail.comwrote:
* Yes it is the bad practice to put repos in POMs
* Yes it many more developers/contributors friendly to add repo in POMs
(as far as we don't add not controlled repos and our artifacts aren't
supposed to be reused)
* Yes it was a bad idea and more generally all this part of projects
infra description, users/groups settings
It's only bad because the location might change. Since it is really just a
CNAME record, I don't think the root cause of why specifying
{r,pluginR}epositories applies.
+1 to coding our own {r,pluginR}epositories section for our CNAME record
+1 to coding a m-enforcer-p rule which fails builds for
additional {r,pluginR}epositories
As I said to Nicolas KK at the last hackergarten in Paris I drived a
contribution for such mass change : https://gist.github.com/2305867 (by
@jeanhelou)
Nicolas might probably starts from it.
Please remember that there are close to 200 plugins which are in SVN
still. They would need to be migrated to GitHub before applying this kind
of broad and automatic conversion.
Indeed, committing such a pom change to github will automatically stop the
svn - github sync, without plugin author to be involved, and this is bad.
I'll have to check on pom.xml for scm and commit at the right place
https://wiki.jenkins-ci.org/display/JENKINS/Moving+from+Subversion+%28svn%29+to+Github
-Jesse
--
There are 10 types of people in this world, those
that can read binary and those that can not.
Re: glassfish repo must die
synch to central will fix dependency to jenkins artifacts (so most of plugins) but we still have some plugins to depend to artifacts that aren't available on central, - guice-2.0.1, or de.regnis.q.sequence:sequence-library (for svn-stuff) for sample 2012/4/5 Stephen Connolly stephen.alan.conno...@gmail.com On 4 April 2012 23:13, Kohsuke Kawaguchi kkawagu...@cloudbees.com wrote: On 04/04/2012 01:38 PM, nicolas de loof wrote: jenkins-ci.org http://jenkins-ci.org is under our control so we can point it to whatever we like also, plugin can't build without a repo declaration as jenkins artifacts aren't available on central I don't thing this to be a bad practice. Would you expect all developers to configure settings with adequate repo to build your project ? This *only* is a requirement for deployment on central just my 2 cents :P Yes, the goal here is to make it easier for people to check out plugins and build them, so that they can apply patches. Many of them are Maven newbies. Then let's sync to central. Every added step (like ~/.m2/settings.xml tweaking) is a hurdle. We should have repository definition in POM to avoid this. Nope... we should just sync to central As Nicolas wrote, repo.jenkins-ci.org is our domain that we control, so the same thing won't happen again. (There is a separate effort to make more of our artifacts available in central, which would eliminate this problem in a long run, but we shouldn't wait for that.) Why not just hurry that effort along ;-) 2012/4/4 Jeff MAURY jeffma...@jeffmaury.com mailto:jeffmaury@jeffmaury.**com jeffma...@jeffmaury.com You should rather delete this repo definition as it is not a good Maven practice and may lead to the same problem in the future. Jeff On Wed, Apr 4, 2012 at 8:58 PM, nicolas de loof nicolas.del...@gmail.com mailto:nicolas.deloof@gmail.**comnicolas.del...@gmail.com wrote: Hi folks, as you know, glassfish maven repo (aka m.g.o-public) is definitively off, but we depend on it for many plugins dependencies, and this is hardcoded in plugin parent pom (so, to get it fixed, plugin would need to upgrade to a recent jenkins-core dependency). some of you may already encounter dependency resolution issues trying to build a plugin form scratch I volunteer to migrate the 400+ plugins to replace repository pointing to m.g.o-public and replace/add repo.jenkins-ci.org/public http://repo.jenkins-ci.org/**publichttp://repo.jenkins-ci.org/public where missing, so that each plugin explicitly defines repository to our infra (I plan to write a tool for that). We discussed this on governance meeting, but I wan't to ensure everybody agree here, so please let me know if you see any drawback or have another suggestion. Nicolas -- Jeff MAURY Legacy code often differs from its suggested alternative by actually working and scaling. - Bjarne Stroustrup http://www.jeffmaury.com http://riadiscuss.jeffmaury.**com http://riadiscuss.jeffmaury.com http://www.twitter.com/**jeffmaury http://www.twitter.com/jeffmaury -- Kohsuke Kawaguchi | CloudBees, Inc. | http://cloudbees.com/ Try Nectar, our professional version of Jenkins
glassfish repo must die
Hi folks, as you know, glassfish maven repo (aka m.g.o-public) is definitively off, but we depend on it for many plugins dependencies, and this is hardcoded in plugin parent pom (so, to get it fixed, plugin would need to upgrade to a recent jenkins-core dependency). some of you may already encounter dependency resolution issues trying to build a plugin form scratch I volunteer to migrate the 400+ plugins to replace repository pointing to m.g.o-public and replace/add repo.jenkins-ci.org/public where missing, so that each plugin explicitly defines repository to our infra (I plan to write a tool for that). We discussed this on governance meeting, but I wan't to ensure everybody agree here, so please let me know if you see any drawback or have another suggestion. Nicolas
Re: glassfish repo must die
jenkins-ci.org is under our control so we can point it to whatever we like also, plugin can't build without a repo declaration as jenkins artifacts aren't available on central I don't thing this to be a bad practice. Would you expect all developers to configure settings with adequate repo to build your project ? This *only* is a requirement for deployment on central just my 2 cents :P 2012/4/4 Jeff MAURY jeffma...@jeffmaury.com You should rather delete this repo definition as it is not a good Maven practice and may lead to the same problem in the future. Jeff On Wed, Apr 4, 2012 at 8:58 PM, nicolas de loof nicolas.del...@gmail.comwrote: Hi folks, as you know, glassfish maven repo (aka m.g.o-public) is definitively off, but we depend on it for many plugins dependencies, and this is hardcoded in plugin parent pom (so, to get it fixed, plugin would need to upgrade to a recent jenkins-core dependency). some of you may already encounter dependency resolution issues trying to build a plugin form scratch I volunteer to migrate the 400+ plugins to replace repository pointing to m.g.o-public and replace/add repo.jenkins-ci.org/public where missing, so that each plugin explicitly defines repository to our infra (I plan to write a tool for that). We discussed this on governance meeting, but I wan't to ensure everybody agree here, so please let me know if you see any drawback or have another suggestion. Nicolas -- Jeff MAURY Legacy code often differs from its suggested alternative by actually working and scaling. - Bjarne Stroustrup http://www.jeffmaury.com http://riadiscuss.jeffmaury.com http://www.twitter.com/jeffmaury
Re: Bitbucket Repository Browser
git-plugin 1.1.16 added support for bitbucket, but I must admit I didn't tested it by myself 2012/3/17 Andrew Gray andrew.paul.g...@gmail.com Hi All, Is there a repository browser plugin for Bitbucket that does the same thing as GitHubWeb link on the Recent changes page? Looks like *git-pluginhttps://github.com/hudson-plugins/git-plugin/tree/603c07c72de5f206836b6311fb9694b0ef5476fe * / srchttps://github.com/hudson-plugins/git-plugin/tree/603c07c72de5f206836b6311fb9694b0ef5476fe/src/ mainhttps://github.com/hudson-plugins/git-plugin/tree/603c07c72de5f206836b6311fb9694b0ef5476fe/src/main/ javahttps://github.com/hudson-plugins/git-plugin/tree/603c07c72de5f206836b6311fb9694b0ef5476fe/src/main/java/ hudsonhttps://github.com/hudson-plugins/git-plugin/tree/603c07c72de5f206836b6311fb9694b0ef5476fe/src/main/java/hudson/ pluginshttps://github.com/hudson-plugins/git-plugin/tree/603c07c72de5f206836b6311fb9694b0ef5476fe/src/main/java/hudson/plugins/ githttps://github.com/hudson-plugins/git-plugin/tree/603c07c72de5f206836b6311fb9694b0ef5476fe/src/main/java/hudson/plugins/git/ *browser could be enhanced to check for URLs that contain bitbucket in addition to the current github. * Regards, Andrew
Re: Git Plugin Causes http: //ci.jenkins-ci.org/people to Timeout
I also think this is a buggy feature - assuming the use case you suggest is a feature. Moving author - user creation to GitChangeSet constructor makes sense, and will mostly preserve this use case afaik 2012/3/16 Mirko Friedenhagen mfriedenha...@gmail.com Maybe this is a mechanism to allow overriding the email address in Jenkins? When starting with git, some people forget to set their correct email adress, so it is automatically set to LOCALUSER@WORKSTATIO_NAME. You may then easily override this with the correct email address in the people folder. Regards Mirko On Fri, Mar 16, 2012 at 20:23, Andrew Bayer andrew.ba...@gmail.com wrote: Yeah, that sounds like a bug to me. A. On Fri, Mar 16, 2012 at 10:04 AM, Ryan Campbell ryan.campb...@gmail.com wrote: I just tried to load (maybe you shouldn't click it) http ://ci.jenkins-ci.org/people and I got this error: 504 Gateway Time-out The server didn't respond in time. I've seen similar problems on our own Jenkins (causing 100% CPU usage), with threads hanging like so: https://gist.github.com/00db0f6d7e48e1f4bf02 This points to the code in GitChangeSet.getAuthor: https://github.com/jenkinsci/git-plugin/blob/master/src/main/java/hudson/plugins/git/GitChangeSet.java#L254 I don't understand why we want persistent users created in our user database just because they committed to a project we happen to be building. And I especially don't understand why we'd want to do this in a *get* method which one would expect to be side-effect free. It seems to me that the resolution (and creation) of the Author's User should be done in the constructor of the GitChangeSet, no? This will be more in line with how the SVN and CVS plugins work, and transfers the user-creation work to the build time instead of page-loading time. Thanks, Ryan
Re: Pending git-plugin pull requests
Thanks for kicking my ass on this, I should have reviewed those pull request long time ago... Taking some time this morning to review pending pull requests Nicolas 2012/2/23 Haefliger, Juerg juerg.haefli...@hp.com Oldest pull request is now 4 months old. Is this plugin not being maintained anymore? ...Juerg -Original Message- From: Haefliger, Juerg Sent: Wednesday, January 18, 2012 6:48 AM To: 'jenkinsci-dev@googlegroups.com' Subject: Pending git-plugin pull requests Hi, There are three pending pull requests for the git plugin, the oldest one dating back to Oct 26, 2011. Can I asked the maintainer(s) to take a look at them? Thanks ...Juerg
Re: JUC Paris T-shirt
+1 to #3. 2012/2/22 Adrien Lecharpentier adrien.lecharpent...@gmail.com Great work! my +1 to #3 -- Adrien Lecharpentier Le 22 février 2012 09:06, Alyssa Tong at...@cloudbees.com a écrit : Super. Thanks KK. #3 #5 are also my favorites..my top pick is #5. On Tue, Feb 21, 2012 at 11:38 PM, Kohsuke Kawaguchi k...@kohsuke.orgwrote: These all look awesome! My +1 to #3 and #5. 2012/2/22 Alyssa Tong at...@cloudbees.com: Hello, Based on feedback received, here's some images we came up with. Could I kindly get the community's vote on which image you like best? Again, if there's suggestions to tweak any of these images pls do share. https://skitch.com/alytong/8dwka/jenkinsinparis-crv-1.pdf-1-page thank you in advance, alyssa -- Kohsuke Kawaguchi
platform-labeler plugin maitainer ?
Hi, is https://wiki.jenkins-ci.org/display/JENKINS/PlatformLabeler+Plugin still actively maintained ? if not, I volunteer to move it to github and assume the maintainer role
Re: platform-labeler plugin maitainer ?
2012/2/9 Robert Collins robe...@robertcollins.net On Thu, Feb 9, 2012 at 10:17 PM, nicolas de loof nicolas.del...@gmail.com wrote: Hi, is https://wiki.jenkins-ci.org/display/JENKINS/PlatformLabeler+Pluginstill actively maintained ? if not, I volunteer to move it to github and assume the maintainer role Hi, I'm the original author. I've been meaning to move it to github and apply the pending patches, but we had a baby recently - life is just a -little- hectic atm. I know that, I have 3 children ! If you want to move it to github and get that all sorted, that would be most excellent; I would like to keep commit rights - but am very happy to share them with you (and any other interested and capable folk). No problem to share maintainer role, take care of your family and come back to the plugin as you get more spare time. -Rob
