Comments for Kohsuke Kawaguchi http://kohsuke.org Personal website of Kohsuke Kawaguchi Tue, 15 May 2012 17:27:13 +0000 hourly 1 http://wordpress.org/?v=3.3.1 Comment on Polling must die: triggering Jenkins builds from a git hook by David Kinzer http://kohsuke.org/2011/12/01/polling-must-die-triggering-jenkins-builds-from-a-git-hook/comment-page-1/#comment-816 David Kinzer Tue, 15 May 2012 17:27:13 +0000 http://kohsuke.org/?p=89#comment-816 To me it makes sense to poll. All that hook does is trigger on a POST to a URL. I don't want the build to occur just because some bot or prankster is posting to that URL for kicks. Polling to see that a change has actually occurred makes it less likely to get frivolous builds. <a href="#comment-576" rel="nofollow">@Maarten Dirkse</a> To me it makes sense to poll. All that hook does is trigger on a POST to a URL. I don’t want the build to occur just because some bot or prankster is posting to that URL for kicks.

Polling to see that a change has actually occurred makes it less likely to get frivolous builds. @Maarten Dirkse

]]> Comment on Polling must die: triggering Jenkins builds from a git hook by Scot Wilkie http://kohsuke.org/2011/12/01/polling-must-die-triggering-jenkins-builds-from-a-git-hook/comment-page-1/#comment-814 Scot Wilkie Tue, 08 May 2012 19:10:07 +0000 http://kohsuke.org/?p=89#comment-814 Sorry, I didn't mean to hijack the thread with my comments on the git plugin versions (but 1.1.18 does not work at all for me). After updating Jenkins to the latest version today, 1.463, and also installing the Jenkins Notification plug in (because it sounds like it is needed) things sort of work. I have 3 Jenkins jobs, each one to build on master, br2, and br3 respectively. Doing a push now shows 3 lines in STDOUT indicating that scheduled polling was started for each of the 3 branches. However only a push to br2 seems to trigger a build on Jenkins, and then the jobs for both br2 and br3 run; pushes on master or br3, while getting the same STDOUT lines about scheduled polling, do not trigger the corresponding jobs to start. Seems like I am missing some criteria of what it takes to trigger the Jenkins job to start. Here is the line in my post-receive hook for the repo: curl http://smfosbuild:8080/git/notifyCommit?url=git@vfilvgit2:scmtest.git Any ideas? Sorry, I didn’t mean to hijack the thread with my comments on the git plugin versions (but 1.1.18 does not work at all for me). After updating Jenkins to the latest version today, 1.463, and also installing the Jenkins Notification plug in (because it sounds like it is needed) things sort of work. I have 3 Jenkins jobs, each one to build on master, br2, and br3 respectively. Doing a push now shows 3 lines in STDOUT indicating that scheduled polling was started for each of the 3 branches. However only a push to br2 seems to trigger a build on Jenkins, and then the jobs for both br2 and br3 run; pushes on master or br3, while getting the same STDOUT lines about scheduled polling, do not trigger the corresponding jobs to start. Seems like I am missing some criteria of what it takes to trigger the Jenkins job to start. Here is the line in my post-receive hook for the repo:
curl http://smfosbuild:8080/git/notifyCommit?url=git@vfilvgit2:scmtest.git

Any ideas?

]]> Comment on Polling must die: triggering Jenkins builds from a git hook by Scot Wilkie http://kohsuke.org/2011/12/01/polling-must-die-triggering-jenkins-builds-from-a-git-hook/comment-page-1/#comment-813 Scot Wilkie Mon, 07 May 2012 15:28:49 +0000 http://kohsuke.org/?p=89#comment-813 I upgraded to the latest Jenkins version and then the git plugin was correctly identified as 1.1.18. However now when I run my jobs I get an error about not finding any version to build. I down graded to version 1.1.14 and the jobs run fine. Please let me know if you need any information about my setup. I upgraded to the latest Jenkins version and then the git plugin was correctly identified as 1.1.18. However now when I run my jobs I get an error about not finding any version to build. I down graded to version 1.1.14 and the jobs run fine. Please let me know if you need any information about my setup.

]]> Comment on COM4J updates by Andras http://kohsuke.org/2012/04/27/com4j-updates/comment-page-1/#comment-812 Andras Mon, 07 May 2012 13:11:51 +0000 http://kohsuke.org/?p=127#comment-812 Hello Kohsuke ! Sorry to say, but I have problem using com4j. Whenever I try to run tlb import (regardless if I try to run with wshom.ocx or WIA TLB) I got the following error: F:\com4j\kohsuke-com4j-b5143ce\tlbimp\lib>java -jar tlbimp.jar -o wia -p wia %WINDIR%\system32\wiaservc.dll Exception in thread "main" java.lang.IllegalMonitorStateException at java.lang.Object.wait(Native Method) at java.lang.Object.wait(Object.java:503) at com4j.ComThread.execute(ComThread.java:220) at com4j.Task.execute(Task.java:25) at com4j.COM4J.loadTypeLibrary(COM4J.java:322) at com4j.tlbimp.driver.Lib.getLibid(Lib.java:90) at com4j.tlbimp.driver.Driver.addLib(Driver.java:38) at com4j.tlbimp.driver.Main.doMain(Main.java:123) at com4j.tlbimp.driver.Main.main(Main.java:56) Hello Kohsuke !
Sorry to say, but I have problem using com4j. Whenever I try to run tlb import (regardless if I try to run with wshom.ocx or WIA TLB) I got the following error:
F:\com4j\kohsuke-com4j-b5143ce\tlbimp\lib>java -jar tlbimp.jar -o wia -p wia %WINDIR%\system32\wiaservc.dll
Exception in thread “main” java.lang.IllegalMonitorStateException
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:503)
at com4j.ComThread.execute(ComThread.java:220)
at com4j.Task.execute(Task.java:25)
at com4j.COM4J.loadTypeLibrary(COM4J.java:322)
at com4j.tlbimp.driver.Lib.getLibid(Lib.java:90)
at com4j.tlbimp.driver.Driver.addLib(Driver.java:38)
at com4j.tlbimp.driver.Main.doMain(Main.java:123)
at com4j.tlbimp.driver.Main.main(Main.java:56)

]]> Comment on Polling must die: triggering Jenkins builds from a git hook by Scot Wilkie http://kohsuke.org/2011/12/01/polling-must-die-triggering-jenkins-builds-from-a-git-hook/comment-page-1/#comment-811 Scot Wilkie Fri, 04 May 2012 15:47:18 +0000 http://kohsuke.org/?p=89#comment-811 <a href="#comment-810" rel="nofollow">@Scot Wilkie</a> My git plugin was version 1.1.12 and there were no updates listed under the update tab. I manually down loaded 1.1.18 and copied it to the pulgins directory and restarted Jenkins. The Git directory seems to have the correct date/time stamp of 4/27/2012, but in the installed plugins tab it still reports the git plugin as version 1.1.12. @Scot Wilkie
My git plugin was version 1.1.12 and there were no updates listed under the update tab. I manually down loaded 1.1.18 and copied it to the pulgins directory and restarted Jenkins. The Git directory seems to have the correct date/time stamp of 4/27/2012, but in the installed plugins tab it still reports the git plugin as version 1.1.12.

]]> Comment on Polling must die: triggering Jenkins builds from a git hook by Scot Wilkie http://kohsuke.org/2011/12/01/polling-must-die-triggering-jenkins-builds-from-a-git-hook/comment-page-1/#comment-810 Scot Wilkie Fri, 04 May 2012 15:25:34 +0000 http://kohsuke.org/?p=89#comment-810 I am wondering if my git plugin is installed incorrectly. I do not have a git directory under jenkins, so the path http://yourserver/jenkings/git/notifyCommit is not found. I do have a git directory under plugins and I can run jobs which clone repos, but I can't find a path to notifyCommit. I am new to jenkins so any help is greatly appreciated. I am wondering if my git plugin is installed incorrectly. I do not have a git directory under jenkins, so the path http://yourserver/jenkings/git/notifyCommit is not found. I do have a git directory under plugins and I can run jobs which clone repos, but I can’t find a path to notifyCommit.

I am new to jenkins so any help is greatly appreciated.

]]> Comment on COM4J updates by kohsuke http://kohsuke.org/2012/04/27/com4j-updates/comment-page-1/#comment-809 kohsuke Fri, 04 May 2012 15:13:39 +0000 http://kohsuke.org/?p=127#comment-809 Yes, I should post the release announcement. I still consider that mailing list THE mailing list, as I don't have anywhere else to host them. Yes, I should post the release announcement. I still consider that mailing list THE mailing list, as I don’t have anywhere else to host them.

]]> Comment on COM4J updates by Jens http://kohsuke.org/2012/04/27/com4j-updates/comment-page-1/#comment-808 Jens Wed, 02 May 2012 17:33:35 +0000 http://kohsuke.org/?p=127#comment-808 Great News! Thank you! :) Maybe we should post on the "old" com4j java.net mailing list and kinda redirect users from the old project site to your new one? Great News! Thank you! :)

Maybe we should post on the “old” com4j java.net mailing list and kinda redirect users from the old project site to your new one?

]]> Comment on Polling must die: triggering Jenkins builds from a git hook by Chris Hansen http://kohsuke.org/2011/12/01/polling-must-die-triggering-jenkins-builds-from-a-git-hook/comment-page-1/#comment-807 Chris Hansen Tue, 01 May 2012 03:55:19 +0000 http://kohsuke.org/?p=89#comment-807 This is seriously cool. Thanks for a great plugin. I can confirm that leaving the schedule empty works just as well as putting in something bogus. However, I do agree that a tag (e.g. @Triggered), or perhaps a checkbox removing the schedule area if checked, would be very useful. This is seriously cool. Thanks for a great plugin.
I can confirm that leaving the schedule empty works just as well as putting in something bogus. However, I do agree that a tag (e.g. @Triggered), or perhaps a checkbox removing the schedule area if checked, would be very useful.

]]> Comment on Polling must die: triggering Jenkins builds from a git hook by David Kinzer http://kohsuke.org/2011/12/01/polling-must-die-triggering-jenkins-builds-from-a-git-hook/comment-page-1/#comment-806 David Kinzer Thu, 26 Apr 2012 18:05:54 +0000 http://kohsuke.org/?p=89#comment-806 Thanks! This was very useful (especially because we are behind a firewall and it's a challenge to set up builds by having GitHub report to our Jenkins server directly). Thanks! This was very useful (especially because we are behind a firewall and it’s a challenge to set up builds by having GitHub report to our Jenkins server directly).

]]>