[JIRA] [git] (JENKINS-18957) NullPointerException with jgit on Git Plugin 2.0 beta
Mark Waite commented on JENKINS-18957 NullPointerException with jgit on Git Plugin 2.0 beta There is a simpler way to show the same (or a similar) stack trace: Define a new job using Git as the SCM Assign an ssh repository URL like ssh://mwaite@somehost/git/myrepo.git The stack trace reports a null pointer exception visible in the web browser: Status Code: 500 Exception: java.lang.NullPointerException Stacktrace: javax.servlet.ServletException: java.lang.NullPointerException at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:719) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:770) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:677) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:770) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:677) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:770) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:583) at org.kohsuke.stapler.Stapler.service(Stapler.java:214) at javax.servlet.http.HttpServlet.service(HttpServlet.java:45) at winstone.ServletConfiguration.execute(ServletConfiguration.java:248) at winstone.RequestDispatcher.forward(RequestDispatcher.java:333) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:376) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:50) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at winstone.RequestDispatcher.forward(RequestDispatcher.java:331) at winstone.RequestHandlerThread.processRequest(RequestHandlerThread.java:227) at winstone.RequestHandlerThread.run(RequestHandlerThread.java:150) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at winstone.BoundedExecutorService$1.run(BoundedExecutorService.java:77) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:724) Caused by: java.lang.NullPointerException at org.jenkinsci.plugins.gitclient.trilead.TrileadSessionFactory.getSession(TrileadSessionFactory.java:34) at org.eclipse.jgit.transport.SshTransport.getSession(SshTransport.java:121) at org.eclipse.jgit.transport.TransportGitSsh$SshFetchConnection.init(TransportGitSsh.java:248) at org.eclipse.jgit.transport.TransportGitSsh.openFetch(TransportGitSsh.java:147) at org.jenkinsci.plugins.gitclient.JGitAPIImpl.getHeadRev(JGitAPIImpl.java:313) at hudson.plugins.git.UserRemoteConfig$DescriptorImpl.doCheckUrl(UserRemoteConfig.java:85) at sun.reflect.GeneratedMethodAccessor754.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:288) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:151) at
[JIRA] [git] (JENKINS-19037) Empty error dialog appears when git job definition applied with no values in fields (Git plugin 2.0 beta)
Mark Waite created JENKINS-19037 Empty error dialog appears when git job definition applied with no values in fields (Git plugin 2.0 beta) Issue Type: Bug Assignee: Nicolas De Loof Components: git Created: 01/Aug/13 1:46 PM Description: While using the Git plugin 2.0 beta, I see an empty error dialog when I: Define a new job Select Git SCM (and set no other values) Apply the definition If I use "no" SCM, I can apply without the empty error box. If I insert a value in the repository URL, then I can apply the job definition. Project: Jenkins Labels: git2 Priority: Major Reporter: Mark Waite This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-18960) Clone of 2.5 GB git repository is dramatically slower with jgit than command line git
Mark Waite updated JENKINS-18960 Clone of 2.5 GB git repository is dramatically slower with jgit than command line git Change By: Mark Waite (01/Aug/13 2:07 PM) Environment: Jenkins1.509.2 onLinuxmasteror slave and onWindowsServer2008R2 wihJDK1.7.0_25 slave This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-18960) Clone of 2.5 GB git repository is dramatically slower with jgit than command line git
Mark Waite updated JENKINS-18960 Clone of 2.5 GB git repository is dramatically slower with jgit than command line git Change By: Mark Waite (01/Aug/13 2:06 PM) Environment: Debianx86testingwithOracle Jenkins1.509.2slaveonWindowsServer2008R2wih JDK 1. 7 .0_25 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-19043) jgit hangs on Updating references with large repositories
Mark Waite created JENKINS-19043 jgit hangs on Updating references with large repositories Issue Type: Bug Assignee: Nicolas De Loof Components: git Created: 01/Aug/13 8:16 PM Description: While exploring the Git 2.0 plugin beta version, I found that several of my jobs which were attempting to update from a large repository would hang the Jenkins job at the "Updating references" stage. The jobs which hung were all using jgit rather than the command line git. When I switched the jobs from jgit back to command line git, they worked as expected. Environment: Jenkins 1.509.2 on JDK 1.7.0_25, master on Debian x64, slaves on Debian x64, x86, Windows x64, x86, and CentOS x64 Project: Jenkins Labels: git2 Priority: Major Reporter: Mark Waite This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-18988) JGit in Git plugin 2.0 beta reports CheckoutConflictException, command line Git does not
Mark Waite updated JENKINS-18988 JGit in Git plugin 2.0 beta reports CheckoutConflictException, command line Git does not Change By: Mark Waite (29/Jul/13 7:48 PM) Labels: git2 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-18988) JGit in Git plugin 2.0 beta reports CheckoutConflictException, command line Git does not
Mark Waite commented on JENKINS-18988 JGit in Git plugin 2.0 beta reports CheckoutConflictException, command line Git does not The file mentioned in the message changes frequently in the central repository, but only changes in the slave workspace when the git plugin performs a pull (or a fetch + merge). There are no local changes in that file and no modifications made to it during the build. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-18960) Clone of 2.5 GB git repository is dramatically slower with jgit than command line git
Mark Waite updated JENKINS-18960 Clone of 2.5 GB git repository is dramatically slower with jgit than command line git Change By: Mark Waite (27/Jul/13 10:39 PM) Priority: Major Critical This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-18957) NullPointerException with jgit on Git Plugin 2.0 beta
Mark Waite created JENKINS-18957 NullPointerException with jgit on Git Plugin 2.0 beta Issue Type: Bug Assignee: Nicolas De Loof Components: git Created: 26/Jul/13 7:14 PM Description: Steps I used to see the issue: installed Git Client plugin 1.1.1 and restarted Jenkins downloaded and installed Git Plugin 2.0 beta and restarted Jenkins executed several successful builds without changing configurations confirmed those builds were correctly responding to build hooks use configuration page to delete git as executable, add jgit submitted another change to git repository, watched hooks activate No build from Jenkins, and a null pointer exception is in the log file. SEVERE: Failed to record SCM polling for hudson.model.FreeStyleProject@21d1ff77p4-port-linux-Merge java.lang.NullPointerException at org.jenkinsci.plugins.gitclient.trilead.TrileadSessionFactory.getSession(TrileadSessionFactory.java:34) at org.eclipse.jgit.transport.SshTransport.getSession(SshTransport.java:121) at org.eclipse.jgit.transport.TransportGitSsh$SshFetchConnection.init(TransportGitSsh.java:248) at org.eclipse.jgit.transport.TransportGitSsh.openFetch(TransportGitSsh.java:147) at org.eclipse.jgit.transport.FetchProcess.executeImp(FetchProcess.java:136) at org.eclipse.jgit.transport.FetchProcess.execute(FetchProcess.java:122) at org.eclipse.jgit.transport.Transport.fetch(Transport.java:1105) at org.eclipse.jgit.api.FetchCommand.call(FetchCommand.java:128) at org.jenkinsci.plugins.gitclient.JGitAPIImpl.fetch(JGitAPIImpl.java:299) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at hudson.remoting.RemoteInvocationHandler$RPCRequest.perform(RemoteInvocationHandler.java:275) at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:256) at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:215) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:326) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:724) Environment: 64 bit Debian Linux testing running Jenkins 1.509.2 in winstone container running on Oracle JDK 7 Project: Jenkins Labels: git2 Priority: Major Reporter: Mark Waite This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop
[JIRA] [git] (JENKINS-18957) NullPointerException with jgit on Git Plugin 2.0 beta
Mark Waite commented on JENKINS-18957 NullPointerException with jgit on Git Plugin 2.0 beta If I click the "Build Now" button on that job, it reports the null pointer exception: Started by user anonymous Building remotely on fc-nagios-a in workspace /var/lib/jenkins/mwaite6-slave/workspace/p4-port-linux-Merge selected Git installation does not exists. Using Default Fetching changes from the remote Git repository FATAL: null java.lang.NullPointerException at org.jenkinsci.plugins.gitclient.trilead.TrileadSessionFactory.getSession(TrileadSessionFactory.java:34) at org.eclipse.jgit.transport.SshTransport.getSession(SshTransport.java:121) at org.eclipse.jgit.transport.TransportGitSsh$SshFetchConnection.init(TransportGitSsh.java:248) at org.eclipse.jgit.transport.TransportGitSsh.openFetch(TransportGitSsh.java:147) at org.eclipse.jgit.transport.FetchProcess.executeImp(FetchProcess.java:136) at org.eclipse.jgit.transport.FetchProcess.execute(FetchProcess.java:122) at org.eclipse.jgit.transport.Transport.fetch(Transport.java:1105) at org.eclipse.jgit.api.FetchCommand.call(FetchCommand.java:128) at org.jenkinsci.plugins.gitclient.JGitAPIImpl.fetch(JGitAPIImpl.java:299) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at hudson.remoting.RemoteInvocationHandler$RPCRequest.perform(RemoteInvocationHandler.java:275) at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:256) at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:215) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:326) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:724) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-18957) NullPointerException with jgit on Git Plugin 2.0 beta
Mark Waite commented on JENKINS-18957 NullPointerException with jgit on Git Plugin 2.0 beta When I select "Build Now" on another job, it includes the message in its output: selected Git installation does not exists. Using Default That surprises me, since the "JGit" implementation is the only available implementation on my Jenkins server currently, and it is built into Jenkins. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-18957) NullPointerException with jgit on Git Plugin 2.0 beta
Mark Waite commented on JENKINS-18957 NullPointerException with jgit on Git Plugin 2.0 beta If I then define a Git command line provider in the global configurations and adjust the problem job to use that command line provider, the job works again. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-18960) Clone of 2.5 GB git repository is dramatically slower with jgit than command line git
Mark Waite created JENKINS-18960 Clone of 2.5 GB git repository is dramatically slower with jgit than command line git Issue Type: Bug Assignee: Nicolas De Loof Components: git Created: 26/Jul/13 9:52 PM Description: My 2.5 GB git repository cloned to this computer (from another local area network computer using git protocol) in about 6.5 minutes using the Git plugin 2.0 beta with the Git command line provider. The same git repository cloning from the same server to the same Jenkins machine using the jgit provider (instead of the Git CLI) still has not finished after 14 minutes. There are indications on other jobs that the first time clone of that large repository may never complete. Environment: Debian x86 testing with Oracle JDK 7 Project: Jenkins Labels: git2 Priority: Major Reporter: Mark Waite This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-18232) How do I enable slave logging?
Mark Waite commented on JENKINS-18232 How do I enable slave logging? You could try the Jenkins forum on google groups - https://groups.google.com/forum/?fromgroups#!forum/jenkinsci-users This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-17763) Git plugin clean workspace blows away private maven repository
Mark Waite updated JENKINS-17763 Git plugin clean workspace blows away private maven repository Change By: Mark Waite (04/Jun/13 9:55 AM) Description: WhenyouselectCleanrepositoryworkspace,thisexecutestheequivalentofgit clean -fdxin$WORKSPACEIfyouhavelocalmavenrepositoryselected,thenthereisamavenrepoin$WORKSPACE/.repository.Sothisoption deletes cleans thewhole repo repositoryworkspace ,whichisnotwhatiswanted.Imnotsurewhatthemostreasonablefixis,though.Clearlygit clean -fdx-e.repositorywillprobablywork,butitsabit...magic This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-18125) Changelog empty or contains all changes
Mark Waite commented on JENKINS-18125 Changelog empty or contains all changes I think that is "by design" of the git plugin. A GitHub pull request is a request to merge something, and the GitHub Pull Request plugin needs a destination for that merge. I assume that destination is set in the git plugin advanced options section. I think you'll also need to add a post-build step to use the Git publisher to push the merged changes back to the destination branch. If you don't add that post-build step, then the git plugin will perform the merge to the base branch each time, and report all the differences each time (I think). At least, that is how my experiments have worked when using the git plugin to merge changes from multiple git branches (without the GitHub pull request plugin). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-17825) Configure Job page makes IE10 crash down completely
Mark Waite commented on JENKINS-17825 Configure Job page makes IE10 crash down completely I used Win 7 Pro SP1 and IE 10 to attempt to open several different jobs and was unable to see this problem. My server is Jenkins 1.509.1 running the Winstone container on a Debian Linux machine with Oracle JDK 7 build 21. I don't see any delay opening any of the configure pages, so I assume there is something distinctive about your job which is not appearing on my jobs. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-17825) Configure Job page makes IE10 crash down completely
Mark Waite resolved JENKINS-17825 as Cannot Reproduce Configure Job page makes IE10 crash down completely Change By: Mark Waite (22/May/13 10:30 PM) Status: Open Resolved Resolution: CannotReproduce This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-14201) Git submodules checked out in wrong place
Mark Waite commented on JENKINS-14201 Git submodules checked out in wrong place I attempted to create a Jenkins 1.509.1 job with git-client-plugin 1.0.6 and git-plugin 1.4.0 using git://github.com/alexbirkett/phonelocator-android.git and enabling processing of submodules in the Jenkins job definition. It fails to checkout the source code because one or more of the referenced repositories seem to no longer exist. Since Arkadiy says it works for him and there has been no counter-response from Alex, I recommend this bug be closed. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-14201) Git submodules checked out in wrong place
Mark Waite resolved JENKINS-14201 as Fixed Git submodules checked out in wrong place Reported resolved by Arkady in March 2013. Change By: Mark Waite (19/May/13 9:52 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-17569) False positive on git polling
Mark Waite commented on JENKINS-17569 False positive on git polling Can you provide any further details on the conditions which cause the false positive on git polling? Many users are using the Git plugin without seeing false positives as far as I can tell. My projects don't show false positives either. Even if few people see the problem, it is still likely a bug, but unless the bug can be duplicated, it is especially difficult to fix it. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-17898) Git plugin: tags triggers don't work as expected
Mark Waite updated JENKINS-17898 Git plugin: tags triggers dont work as expected Change By: Mark Waite (16/May/13 3:47 AM) Issue Type: Bug Improvement This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-16941) Git publisher post build action fails on slave agent - unable to serialize
Mark Waite closed JENKINS-16941 as Fixed Git publisher post build action fails on slave agent - unable to serialize Confirmed fixed with git-client-plugin 1.0.6 and git-plugin 1.4.0. Change By: Mark Waite (14/May/13 11:59 AM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-14575) SCM checkout retry count not working
Mark Waite resolved JENKINS-14575 as Fixed SCM checkout retry count not working I confirmed the retry happens as expected with git-client-plugin 1.0.6 and git-plugin 1.4.0. Change By: Mark Waite (14/May/13 12:22 PM) Status: InProgress Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-16941) Git publisher post build action fails on slave agent - unable to serialize
Mark Waite resolved JENKINS-16941 as Fixed Git publisher post build action fails on slave agent - unable to serialize Agreed with @jglick that since the change has been submitted, this should be resolved. Change By: Mark Waite (13/May/13 4:33 PM) Status: InProgress Resolved Assignee: AdamPAPAI NicolasDeLoof Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-16941) Git publisher post build action fails on slave agent - unable to serialize
Mark Waite commented on JENKINS-16941 Git publisher post build action fails on slave agent - unable to serialize Kohsuke just pushed a release of git-client-plugin 1.0.6 and git-plugin 1.4.0. The git-client-plugin release is already available on the updates site. The git-plugin release should be available soon. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-16941) Git publisher post build action fails on slave agent - unable to serialize
Mark Waite edited a comment on JENKINS-16941 Git publisher post build action fails on slave agent - unable to serialize Nicolas just pushed a release of git-client-plugin 1.0.6 and git-plugin 1.4.0. The git-client-plugin release is already available on the updates site. The git-plugin release should be available soon. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-17653) git-plugin cause endless number of builds
Mark Waite resolved JENKINS-17653 as Fixed git-plugin cause endless number of builds The git-client-plugin 1.0.6 and git-plugin 1.4.0 should be available from the usual download site soon with those submissions. Change By: Mark Waite (13/May/13 9:52 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-17928) Extended label are not currently supported.
Mark Waite commented on JENKINS-17928 Extended label are not currently supported. You may need to place the MultiCastDisabled at a different location in the command line. Place it before the jenkins.war so that it is not interpreted as an argument for jenkins.war. Refer to http://jenkins.361315.n4.nabble.com/How-to-use-dhudson-DNSMultiCast-disable-and-close-port-5353-td3172489.html for a previous discussion about it. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-15103) jenkins slave process does not let go of .git\objects\pack\*.pack file causeing Unable to delete when wiping workspace
Mark Waite resolved JENKINS-15103 as Fixed jenkins slave process does not let go of .git\objects\pack\*.pack file causeing Unable to delete when wiping workspace I used the latest released git client plugin (1.0.5) and the latest git plugin (1.3.0) with two different Windows machines (one Windows 6.1 kernel Windows Home Server 2011, one Windows 6.2 kernel Windows 8) and was unable to duplicate this problem. As far as I can tell, it is resolved. Change By: Mark Waite (11/May/13 12:45 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-17700) Windows: Git clone fails on computer with multiple executors or slaves
Mark Waite commented on JENKINS-17700 Windows: Git clone fails on computer with multiple executors or slaves I created a small ant based freestyle project using git as the source control system and copied it eight times, assigning all the jobs to execute on a single Windows machine with three executors. I configured a hook in the git repository to start a poll when a submission arrives. Then I made multiple submissions at varying time intervals to that repository and watched as the jobs queued, executed, and completed successfully. I did not see any hangs. The git repository was small (a build.xml that compiles a Java source file and a Java test file, then executes the test with the ant junit task). Do you see the problem with small git repositories as well as with your production git repo? Is the issue visible only on a specific Windows version? Are there any other processes running (virus scanners, etc.) which might only show the problem on your machine? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-17894) Can't Clone Git repository over SSH 'Process leaked file descriptors'
Mark Waite commented on JENKINS-17894 Cant Clone Git repository over SSH Process leaked file descriptors I don't think you want the tool location to be gitk.cmd. The gitk.cmd launchs a graphical git browser. If you really need a cmd file, then you probably want to invoke git.cmd rather than gitk.cmd. There have been other bug reports which reported issues with using git.cmd, and my experience has been only with git.exe. I'd recommend using git.exe as the tool until you find compelling reasons to do otherwise. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-17894) Can't Clone Git repository over SSH 'Process leaked file descriptors'
Mark Waite resolved JENKINS-17894 as Not A Defect Cant Clone Git repository over SSH Process leaked file descriptors I don't think this is a bug, since gitk is not a functional replacement for the git.exe program. Change By: Mark Waite (11/May/13 2:15 PM) Status: Open Resolved Resolution: NotADefect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-16191) Matrix job fails on git repos if node labels have special characters
Mark Waite
commented on JENKINS-16191
Matrix job fails on git repos if node labels have special characters
Embedding a colon (":") into the label name will also make it impossible to run your matrix job on a windows machine, since the colon character is not allowed in file names on windows file systems.
I agree with Samuel Moritz that the colon could be escaped in the tag name, I think it is not wise to use a colon in your label names.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-16191) Matrix job fails on git repos if node labels have special characters
Mark Waite resolved JENKINS-16191 as Postponed Matrix job fails on git repos if node labels have special characters I propose that this should not be fixed because using a colon in a multi-configuration job on Windows causes the checkout to fail. In this example, it appears Jenkins tried to create a label=os:win directory on Windows, and Windows refused. Rather than adding support for labels with colon characters into many different locations, it seems better to admit that a colon character in a node label does not work as the original submitter hoped. Change By: Mark Waite (11/May/13 2:26 PM) Status: Open Resolved Resolution: Postponed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-15955) Tree query support with config.xml
Mark Waite updated JENKINS-15955 Tree query support with config.xml Change By: Mark Waite (11/May/13 2:27 PM) Component/s: core Component/s: git This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-13955) Git should write some file with content of $GIT_COMMIT environment variable
Mark Waite updated JENKINS-13955 Git should write some file with content of $GIT_COMMIT environment variable Change By: Mark Waite (11/May/13 2:29 PM) Issue Type: Bug NewFeature This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-15136) Support for Poll on Master for git SCM plugin
Mark Waite resolved JENKINS-15136 as Fixed Support for Poll on Master for git SCM plugin Fast remote polling resolves this request. The "git ls-remote" command is used to implement the polling without requiring a clone of the repository on the master. Change By: Mark Waite (10/May/13 11:30 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-15136) Support for Poll on Master for git SCM plugin
Mark Waite closed JENKINS-15136 as Fixed Support for Poll on Master for git SCM plugin Fast remote polling resolves this request Change By: Mark Waite (10/May/13 11:31 AM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-16941) Git publisher post build action fails on slave agent - unable to serialize
Mark Waite updated JENKINS-16941 Git publisher post build action fails on slave agent - unable to serialize Change By: Mark Waite (10/May/13 11:39 AM) Description: Usingthegitplugintopublishamergedchangetoacentralrepositorypreviouslywassuccessfulfromeitherthemasternodeoraslaveagent.Withthe1.2.0(and1.3.0)versionofthegitpluginitisnolongerabletopushchangestothecentralrepositoryaftertheyhavemergedandaresuccessfullybuiltontheslave. Themergestillworksasexpectedwhenperformedonthemasternode. Thestacktracereports:CommencingbuildofRevision363396d76a09a12a2f4b5d94fb4e9981e05ad4a9(origin/proposals)hudson.util.IOException2:remotefileoperationfailed:/var/lib/jenkins/mwaite6-slave/workspace/merge-proposalsathudson.remoting.Channel@4a6ecaf9:fc-agile-2011 athudson.FilePath.act(FilePath.java:848) athudson.FilePath.act(FilePath.java:834) athudson.plugins.git.GitSCM.checkout(GitSCM.java:1133) athudson.model.AbstractProject.checkout(AbstractProject.java:1256) athudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:590) atjenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88) athudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:495) athudson.model.Run.execute(Run.java:1502) athudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) athudson.model.ResourceController.execute(ResourceController.java:88) athudson.model.Executor.run(Executor.java:237)Causedby:java.io.IOException:Unabletoserializehudson.FilePath$FileCallableWrapper@7c0a37f8 athudson.remoting.UserRequest.serialize(UserRequest.java:166) athudson.remoting.UserRequest.init(UserRequest.java:62) athudson.remoting.Channel.call(Channel.java:671) athudson.FilePath.act(FilePath.java:841) ...10moreCausedby:java.io.NotSerializableException:hudson.model.FreeStyleBuild atjava.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1180) atjava.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1528) atjava.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1493) atjava.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1416) atjava.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1174) atjava.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1528) atjava.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1493) atjava.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1416) atjava.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1174) atjava.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:346) athudson.remoting.UserRequest._serialize(UserRequest.java:155) athudson.remoting.UserRequest.serialize(UserRequest.java:164) ...13moreStepstorecreatetheproblem:-configureaGitrepositoryintowhichtheJenkinsusercanpushchanges-createamasterbranchandaproposalsbranchontheGitrepository-defineaJenkinsjobwhichclonestheGitrepositorywithsshprotocol-configuretheJenkinsjobgitplugintomergefrom*/proposalsand*/mastertomaster-proposals-restrictthejobtoexecuteonanynodeexceptmasternode(!master)-defineapostbuildactiontopushtheresultingmergetotheorigin/masterbranch-Submitachangetothecentralgitrepositoryontheproposalsbranch-RuntheJenkinsjobtoconfirmitwillcombinethemasterandproposalsbranches-ConfirmtheJenkinsjobfailstopushthecombinedchange=Serializationexceptionbetweenmasterandslave.Refertomerge-proposals.xmlforthejobdefinitionIusedinmytests. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-11645) git plugin is extremely slow creating a clone - takes 5-8 minutes in jenkins job
Mark Waite resolved JENKINS-11645 as Cannot Reproduce git plugin is extremely slow creating a clone - takes 5-8 minutes in jenkins job I don't think there is much hope of duplicating this issue 18 months after it was reported. I didn't see this problem even back when it was reported (as far as I can recall). The Git plugin has been through major revisions since the bug was first reported. It still uses the same basic mechanism for cloning as it did at the time this bug was reported, and it still has many hundreds of users on Debian machines. If the original submitter can still duplicate the bug, hopefully they can provide additional information on how to configure a system that will show the bug. Change By: Mark Waite (10/May/13 11:44 AM) Status: Open Resolved Resolution: CannotReproduce This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-11177) rev-parse can display a warning message and break current build revision
Mark Waite resolved JENKINS-11177 as Fixed rev-parse can display a warning message and break current build revision Wrote an automated test to verify that git client plugin 1.0.5 does not have this problem. A pull request for the automated test has been submitted to the git-client-plugin repository. Change By: Mark Waite (10/May/13 2:41 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-11177) rev-parse can display a warning message and break current build revision
Mark Waite closed JENKINS-11177 as Fixed rev-parse can display a warning message and break current build revision Already fixed in the git-client-plugin 1.0.5 release, and possibly fixed in earlier releases as well. Change By: Mark Waite (10/May/13 2:41 AM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-17681) LastSuccessful and LastStable symlinks are invalid under Windows
Mark Waite commented on JENKINS-17681 LastSuccessful and LastStable symlinks are invalid under Windows Is it possible that you're running with UAC disabled? I'm using JDK 7u21 and I consistently see that stack on multiple machines, though they all run with user account control enabled. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-17681) LastSuccessful and LastStable symlinks are invalid under Windows
Mark Waite commented on JENKINS-17681 LastSuccessful and LastStable symlinks are invalid under Windows http://superuser.com/questions/104845/permission-to-make-symbolic-links-in-windows-7 seems to suggest that creating symlinks as a normal user is not allowed. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-17681) LastSuccessful and LastStable symlinks are invalid under Windows
Mark Waite commented on JENKINS-17681 LastSuccessful and LastStable symlinks are invalid under Windows I just checked on a Windows 8 machine and confirmed that the command program "mklink.exe" requires administrator privileges to create a file symlink. The command "mklink x.jar classworlds.jar" fails with the message: You do not have sufficient privilege to perform this operation. If I run that same command from a window that was started with Administrator privileges, then the link is created as expected. http://technet.microsoft.com/library/cc766301.aspx gives the explanation that creating symlinks may expose security bugs in programs not designed to handle symlinks. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-16941) Git publisher post build action fails on slave agent - unable to serialize
Mark Waite updated JENKINS-16941 Git publisher post build action fails on slave agent - unable to serialize Change By: Mark Waite (26/Apr/13 3:46 PM) Description: Usingthegitplugintopublishamergedchangetoacentralrepositorypreviouslywassuccessfulfromeitherthemasternodeoraslaveagent.Withthe1.2.0 (and1.3.0) versionofthegitpluginitisnolongerabletopushchangestothecentralrepositoryaftertheyhavemergedandaresuccessfullybuiltontheslave.Thestacktracereports:CommencingbuildofRevision363396d76a09a12a2f4b5d94fb4e9981e05ad4a9(origin/proposals)hudson.util.IOException2:remotefileoperationfailed:/var/lib/jenkins/mwaite6-slave/workspace/merge-proposalsathudson.remoting.Channel@4a6ecaf9:fc-agile-2011 athudson.FilePath.act(FilePath.java:848) athudson.FilePath.act(FilePath.java:834) athudson.plugins.git.GitSCM.checkout(GitSCM.java:1133) athudson.model.AbstractProject.checkout(AbstractProject.java:1256) athudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:590) atjenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88) athudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:495) athudson.model.Run.execute(Run.java:1502) athudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) athudson.model.ResourceController.execute(ResourceController.java:88) athudson.model.Executor.run(Executor.java:237)Causedby:java.io.IOException:Unabletoserializehudson.FilePath$FileCallableWrapper@7c0a37f8 athudson.remoting.UserRequest.serialize(UserRequest.java:166) athudson.remoting.UserRequest.init(UserRequest.java:62) athudson.remoting.Channel.call(Channel.java:671) athudson.FilePath.act(FilePath.java:841) ...10moreCausedby:java.io.NotSerializableException:hudson.model.FreeStyleBuild atjava.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1180) atjava.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1528) atjava.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1493) atjava.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1416) atjava.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1174) atjava.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1528) atjava.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1493) atjava.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1416) atjava.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1174) atjava.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:346) athudson.remoting.UserRequest._serialize(UserRequest.java:155) athudson.remoting.UserRequest.serialize(UserRequest.java:164) ...13moreStepstorecreatetheproblem:-configureaGitrepositoryintowhichtheJenkinsusercanpushchanges-createamasterbranchandaproposalsbranchontheGitrepository-defineaJenkinsjobwhichclonestheGitrepositorywithsshprotocol-configuretheJenkinsjobgitplugintomergefrom*/proposalsand*/mastertomaster-proposals-restrictthejobtoexecuteonanynodeexceptmasternode(!master)-defineapostbuildactiontopushtheresultingmergetotheorigin/masterbranch-Submitachangetothecentralgitrepositoryontheproposalsbranch-RuntheJenkinsjobtoconfirmitwillcombinethemasterandproposalsbranches-ConfirmtheJenkinsjobfailstopushthecombinedchange=Serializationexceptionbetweenmasterandslave.Refertomerge-proposals.xmlforthejobdefinitionIusedinmytests. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-17679) Git plugins crashes with exception for jobs using git merging features
Mark Waite commented on JENKINS-17679 Git plugins crashes with exception for jobs using git merging features When I used the Jenkins master version, it did not work in the case I tested. However, I can't explain why it did not work, since it included the same change as the version which worked for you. I think we may need to rely on Nicolas De Loof to fix it. When I checked out the Jenkins master version, I was surprised to see that the two unit tests which had been added to test the fix were also failing. That may indicate that Nicolas is not yet ready to release the fix for this problem officially. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [plugin] (JENKINS-17677) Digest mismatch in update center for LTS 1.480.3
Mark Waite commented on JENKINS-17677 Digest mismatch in update center for LTS 1.480.3 That's surprising, since that change was the "magic" for me. When you changed the update center, did you press the "Submit" button to assure the site change was applied? I was surprised that I could not modify the update center field and then press "Update Now", because the "Update Now" button seemed to ignore the new value I entered into the text field. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [plugin] (JENKINS-17677) Digest mismatch in update center for LTS 1.480.3
Mark Waite commented on JENKINS-17677 Digest mismatch in update center for LTS 1.480.3 Joe, have you attempted the work around of using one of the 3 mirrors directly rather than using the default? The three mirror sites I tried included: http://ftp-nyc.osuosl.org/pub/jenkins/updates/update-center.json http://ftp-chi.osuosl.org/pub/jenkins/updates/update-center.json http://mirror.xmission.com/jenkins/updates/update-center.json I'm most suspicious of the xmission.com site, since it seems to the out of date compared to the two sites at osuosl.org. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [plugin] (JENKINS-17677) Digest mismatch in update center for LTS 1.480.3
Mark Waite edited a comment on JENKINS-17677 Digest mismatch in update center for LTS 1.480.3 Joe, have you attempted the work around of using one of the 3 mirrors directly rather than using the default? The three mirror sites I tried included: http://ftp-nyc.osuosl.org/pub/jenkins/updates/update-center.json http://ftp-chi.osuosl.org/pub/jenkins/updates/update-center.json http://mirror.xmission.com/jenkins/updates/update-center.json I'm most suspicious of the xmission.com site, since it seems to be out of date compared to the two sites at osuosl.org. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [plugin] (JENKINS-17677) Digest mismatch in update center for LTS 1.480.3
Mark Waite commented on JENKINS-17677 Digest mismatch in update center for LTS 1.480.3 When I perform a "wget http://updates.jenkins-ci.org/update-center.json", it connects to updates.jenkins-ci.org, then follows the link to mirrors.jenkins-ci.org, then resolves that to either mirror.xmission.com or ftp-chi.osuosl.org or ftp-nyc.osuosl.org. I ran that wget 45 times and found 15 of the resulting 45 files differed from the original file, though the 15 files which differed from the original were all the same. In other words, the three servers were providing slightly different information in 1 of 3 cases (on average), though the server providing different information was consistent with itself. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-17679) Git plugins crashes with exception for jobs using git merging features
Mark Waite resolved JENKINS-17679 as Fixed Git plugins crashes with exception for jobs using git merging features Johannes confirmed that 1.3.0 resolves the issue for him. Change By: Mark Waite (24/Apr/13 4:49 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-17679) Git plugins crashes with exception for jobs using git merging features
Mark Waite closed JENKINS-17679 as Fixed Git plugins crashes with exception for jobs using git merging features Johannes verification was done with a released version of the plugin, so no further work remains. Change By: Mark Waite (24/Apr/13 4:49 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-17679) Git plugins crashes with exception for jobs using git merging features
Mark Waite commented on JENKINS-17679 Git plugins crashes with exception for jobs using git merging features Thanks for the clarification. I believe the git plugin maintainer has merged a different solution for the same problem to the tip of the current git plugin code. I assume that will be part of git plugin 1.4.0. Refer to https://github.com/jenkinsci/git-plugin/commit/2dd62deb994f99304b4edcf94c40e504f2f61876 for the details of the change that has been merged. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [build-publisher] (JENKINS-17607) java.lang.StackOverflowError ...at jenkins.model.lazy.AbstractLazyLoadRunMap$Index.ceilingEntry(AbstractLazyLoadRunMap.java:153)
Mark Waite commented on JENKINS-17607 java.lang.StackOverflowError ...at jenkins.model.lazy.AbstractLazyLoadRunMap$Index.ceilingEntry(AbstractLazyLoadRunMap.java:153) I don't know if it is related, but the git plugin has been through some major work recently as well. Since the stack trace is referencing git, have you checked to see if your git plugin is up to date? The most recent git plugin version is 1.3.0 and it depends on git-client-plugin 1.0.5 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [plugin] (JENKINS-17677) Digest mismatch in update center for LTS 1.480.3
Mark Waite commented on JENKINS-17677 Digest mismatch in update center for LTS 1.480.3 The JSON file delivered by http://mirror.xmission.com/jenkins/updates/update-center.json reports many differences compared to the JSON file delivered by http://ftp-nyc.osuosl.org/pub/jenkins/updates/update-center.json. For example, the xmission.com location reports the build-failure-analyzer buildDate as "Mar 14, 2013" while the ftp-nyc.osuosl.org location reports the build-failure-analyzer buildDare as "Apr 24, 2013". I assume that means the xmission.com site is out of date compared to the other two sites. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [plugin] (JENKINS-17677) Digest mismatch in update center for LTS 1.480.3
Mark Waite edited a comment on JENKINS-17677 Digest mismatch in update center for LTS 1.480.3 The JSON file delivered by http://mirror.xmission.com/jenkins/updates/update-center.json reports many differences compared to the JSON file delivered by http://ftp-nyc.osuosl.org/pub/jenkins/updates/update-center.json. For example, the xmission.com location reports the build-failure-analyzer buildDate as "Mar 14, 2013" while the ftp-nyc.osuosl.org location reports the build-failure-analyzer buildDare as "Apr 24, 2013". I assume that means the xmission.com site is out of date compared to the other two sites. The output from ftp-chi.osuosl.org matches the output from ftp-nyc.osuosl.org. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [plugin] (JENKINS-17677) Digest mismatch in update center for LTS 1.480.3
Mark Waite commented on JENKINS-17677 Digest mismatch in update center for LTS 1.480.3 A possible work around seems to be to bypass the updates.jenkins-ci.org site and request the update center directly from one of the mirrors. That's not a long term solution, but it seems to have worked in at least the two cases I tried. When I request updates from any of the three update centers which are backing the updates.jenkins-ci.org location, I seem to always be able to successfully update the list of plugins and do not see any message about a digest error on the JSON. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [build-timeout] (JENKINS-17667) Unable to kill a job which is running
Mark Waite commented on JENKINS-17667 Unable to kill a job which is running Aswini, I think you may have misunderstood the nature of open source projects. Open source projects are addressed by a community of interested users who implement enhancements and work on problems based on their needs and their interests. I think the response you're expecting is much closer to commercial support, rather than an open source community. You might consider contacting CloudBees about their commercially supported offering based on Jenkins. There is also a concept of a "bug bounty" that I've seen offered elsewhere in the Jenkins project, though I'm not sure if that generally has the result you are seeking, since you seem to be seeking response times more typical of commercial products than open source projects. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [build-timeout] (JENKINS-17667) Unable to kill a job which is running
Mark Waite commented on JENKINS-17667 Unable to kill a job which is running I don't have an answer to your question. I've observed that sometimes a Jenkins job is harder to interrupt than others. My usual technique has been to click the "x" to stop the job, then if the job has not stopped shortly, I'll click somewhere else in the UI (causing the page to refresh), then click the "x" to stop the job a second time. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [plugin] (JENKINS-17677) Digest mismatch in update center for LTS 1.480.3
Mark Waite commented on JENKINS-17677 Digest mismatch in update center for LTS 1.480.3 I can see the same error on Jenkins 1.480.3 on a Windows 7 machine. The SEVERE message is on the console window where I started Jenkins, but is not visible anywhere in the Jenkins user interface. Oddly enough, my Jenkins 1.480.3 on Debian Linux does not report the digest mismatch and has not reported that digest mismatch in any of its log files from months before. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [plugin] (JENKINS-17677) Digest mismatch in update center for LTS 1.480.3
Mark Waite commented on JENKINS-17677 Digest mismatch in update center for LTS 1.480.3 Generally, opening a new bug report for the same issue will not improve responsiveness. Your original JENKINS-17711 is enough. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [plugin] (JENKINS-17677) Digest mismatch in update center for LTS 1.480.3
Mark Waite edited a comment on JENKINS-17677 Digest mismatch in update center for LTS 1.480.3 Generally, opening a new bug report for the same issue will not improve responsiveness. The new JENKINS-17711 won't help people investigate it any sooner and makes work for someone to resolve it as a duplicate. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [plugin] (JENKINS-17677) Digest mismatch in update center for LTS 1.480.3
Mark Waite commented on JENKINS-17677 Digest mismatch in update center for LTS 1.480.3 I doubt the problem is with the LTS package itself. I assume something is incorrect on the plugins site, or on one of the plugins sites (if they are mirrored somehow). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [msbuild] (JENKINS-16452) Add support of vcvarsall.bat VC compilation environment variable
Mark Waite commented on JENKINS-16452 Add support of vcvarsall.bat VC compilation environment variable Since our Windows compilation environment always requires vcvarsall.bat, and since our experience with Jenkins slaves as a service has been very bad, we configure a batch file that starts the Jenkins slave agent. Before starting the Jenkins slave agent, the batch file sets environment variables for various needs. Things like: CALL "c:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\vcvarsall.bat" SET JAVA_HOME=C:\Program Files\Java\jdk1.7.0_21 SET ANT_HOME=C:\apache-ant-1.9.0 SET PATH=tools;C:\Program Files (x86)\Git\bin;%ANT_HOME%\bin;%JAVA_HOME%\bin;%PATH% javaws javaws http://172.16.16.254:8080/computer/%COMPUTERNAME%/slave-agent.jnlp This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-15103) jenkins slave process does not let go of .git\objects\pack\*.pack file causeing Unable to delete when wiping workspace
Mark Waite commented on JENKINS-15103 jenkins slave process does not let go of .git\objects\pack\*.pack file causeing Unable to delete when wiping workspace Since Omid was able to confirm that the problem is resolved with useCLI=true, and useCLI=true is now the default with git-client-plugin version 1.0.5, I believe this issue is resolved. I was unable to duplicate the issue with many different jobs on a Windows computer. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-17681) LastSuccessful and LastStable symlinks are invalid under Windows
Mark Waite commented on JENKINS-17681 LastSuccessful and LastStable symlinks are invalid under Windows This problem is also visible in Jenkins 1.509.1 LTS release candidate. It appears as a stack trace WARNING: Failed to update hudson.model.FreeStyleProject@1b7e8effjenkins-demo l astSuccessfulBuild permalink for jenkins-demo #24 java.nio.file.NoSuchFileException: C:\Users\Mark\.jenkins\jobs\jenkins-demo\builds\lastSuccessfulBuild.tmp at sun.nio.fs.WindowsException.translateToIOException(WindowsException.java:79) at sun.nio.fs.WindowsException.rethrowAsIOException(WindowsException.java:97) at sun.nio.fs.WindowsException.rethrowAsIOException(WindowsException.java:102) at sun.nio.fs.WindowsLinkSupport.readLink(WindowsLinkSupport.java:56) at sun.nio.fs.WindowsFileSystemProvider.readSymbolicLink(WindowsFileSystemProvider.java:636) at java.nio.file.Files.readSymbolicLink(Files.java:1382) at sun.reflect.GeneratedMethodAccessor125.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:601) at hudson.Util.resolveSymlink(Util.java:1188) at jenkins.model.PeepholePermalink.updateCache(PeepholePermalink.java:146) at jenkins.model.PeepholePermalink.resolve(PeepholePermalink.java:118) at hudson.model.Job.getLastSuccessfulBuild(Job.java:802) at sun.reflect.GeneratedMethodAccessor213.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:601) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:288) at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:203) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:677) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:770) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:677) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:770) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:583) at org.kohsuke.stapler.Stapler.service(Stapler.java:214) at javax.servlet.http.HttpServlet.service(HttpServlet.java:45) at winstone.ServletConfiguration.execute(ServletConfiguration.java:248) at winstone.RequestDispatcher.forward(RequestDispatcher.java:333) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:376) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:50) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at winstone.RequestDispatcher.forward(RequestDispatcher.java:331) at winstone.RequestHandlerThread.processRequest(RequestHandlerThread.java:227) at winstone.RequestHandlerThread.run(RequestHandlerThread.java:150) at
[JIRA] [core] (JENKINS-17621) Return quiet_down value in API
Mark Waite resolved JENKINS-17621 as Fixed Return quiet_down value in API Since the original submitter found what they were seeking, I resolved this bug. Change By: Mark Waite (20/Apr/13 7:26 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-17611) WinIOException: Failed to create a symlink to builds/lastStableBuild error=183:null
Mark Waite commented on JENKINS-17611 WinIOException: Failed to create a symlink to builds/lastStableBuild error=183:null Refer to JENKINS-17681 for a possible duplicate report This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [clearcase] (JENKINS-16773) Delete Project causes java.lang.NullPointerException
Mark Waite updated JENKINS-16773 Delete Project causes java.lang.NullPointerException Change By: Mark Waite (20/Apr/13 7:32 PM) Component/s: clearcase Component/s: core This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-17679) Git plugins crashes with exception for jobs using git merging features
Mark Waite commented on JENKINS-17679 Git plugins crashes with exception for jobs using git merging features Refer to JENKINS-16941 for an earlier report which matches this report. That earlier report also includes a link to a pull request which proposes to repair the problem. You could attempt to use that pull request yourself to confirm it resolves the issue for you. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-16941) Git publisher post build action fails on slave agent - unable to serialize
Mark Waite commented on JENKINS-16941 Git publisher post build action fails on slave agent - unable to serialize Thanks for spending the effort to seek the failing submission. Unfortunately, I think that the actual problem change is hidden in the refactoring which abstracted the Git implementation into an interface, then provided two alternate implementations of that interface, one using the command line Git, the other using JGit. Initially, the default implementation was JGit. With git-client-plugin 1.0.5, the default implementation is now command line Git. I think the problem was introduced by the refactoring because the problem still exists even after the default implementation was switched from JGit to command line git. The high level history (as far as I can see), looks something like this: Git plugin 1.1.26 - last version known able to push a merged submission back from a slave agent Git plugin 1.2.0 + Git client plugin 1.0.1 through 1.0.4 - refactored to provide a Git interface, default implementation with JGit Git plugin 1.3.0 + Git client plugin 1.0.5 - bug fixes and switch default implementation to command line Git Part of me makes the wild guess that this issue would be resolved if we could understand why it cannot serialize. I don't understand the architecture of the slave to master communication, but I thought it was defined by the Java classes and was implemented with Java serialization. My wild guess was that some field or fields were "lost" or "redefined" in the refactoring which break the serialization between the master and slave. However, that is truly just wild guessing on my part. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-16941) Git publisher post build action fails on slave agent - unable to serialize
Mark Waite commented on JENKINS-16941 Git publisher post build action fails on slave agent - unable to serialize That sounds great! If you'd like additional testing of your patch, I'd be happy to help over the weekend. If you submit it as a pull request to the plugin repository, I can pull it into my repository as well and build it locally for my testing. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-17198) Caused by: org.eclipse.jgit.api.errors.CheckoutConflictException: Checkout conflict with files
Mark Waite resolved JENKINS-17198 as Fixed Caused by: org.eclipse.jgit.api.errors.CheckoutConflictException: Checkout conflict with files No response from original submitter. Fixed in git-client-plugin 1.0.5 bu reverting to the git command line implementation until the JGit implementation is able to handle the Jenkins use cases. Change By: Mark Waite (08/Apr/13 3:37 AM) Status: Reopened Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-17198) Caused by: org.eclipse.jgit.api.errors.CheckoutConflictException: Checkout conflict with files
Mark Waite edited a comment on JENKINS-17198 Caused by: org.eclipse.jgit.api.errors.CheckoutConflictException: Checkout conflict with files No response from original submitter. Fixed in git-client-plugin 1.0.5 by reverting to the git command line implementation until the JGit implementation is able to handle the Jenkins use cases. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-8647) Hudson 1.395 logs many messages about RecordReaper IllegalArgumentException
Mark Waite closed JENKINS-8647 as Fixed Hudson 1.395 logs many messages about RecordReaper IllegalArgumentException Confirmed fixes long ago. Change By: Mark Waite (02/Apr/13 3:43 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [mstest] (JENKINS-4632) MSTest plugin does not parse Visual Studio 2010 results
Mark Waite closed JENKINS-4632 as Fixed MSTest plugin does not parse Visual Studio 2010 results Confirmed fixed long ago. Change By: Mark Waite (02/Apr/13 3:43 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-16911) An invalid git reference repository path now causes clone to fail, previously did not fail
Mark Waite closed JENKINS-16911 as Fixed An invalid git reference repository path now causes clone to fail, previously did not fail Confirmed fixed Change By: Mark Waite (02/Apr/13 3:42 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-16914) Specifying multiple git repositories to git plugin causes git fetch to fail on all repos after first repo
Mark Waite closed JENKINS-16914 as Fixed Specifying multiple git repositories to git plugin causes git fetch to fail on all repos after first repo Confirmed fixed Change By: Mark Waite (02/Apr/13 3:43 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-16940) Git publisher fails with Invalid id: origin/master when trying to publish changes
Mark Waite closed JENKINS-16940 as Fixed Git publisher fails with Invalid id: origin/master when trying to publish changes Confirmed fixed. Change By: Mark Waite (02/Apr/13 3:44 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-17186) Linux: if there is a recursive directory within the git repo you're building, the initial checkout will fail badly
Mark Waite commented on JENKINS-17186 Linux: if there is a recursive directory within the git repo youre building, the initial checkout will fail badly Does git-client plugin 1.0.5 resolve this issue with its switch from JGit implementation back to the Git command line client implementation? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-17186) Linux: if there is a recursive directory within the git repo you're building, the initial checkout will fail badly
Mark Waite resolved JENKINS-17186 as Fixed Linux: if there is a recursive directory within the git repo youre building, the initial checkout will fail badly Fixed by git-client-plugin 1.0.5 which switches the default implementation back to command line git. The JGit implementation is not yet complete enough to satisfy all the Jenkins use cases. Change By: Mark Waite (02/Apr/13 6:15 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17204) GIT plugin fetch failing since update Git Plugin to 1.2.0+
Mark Waite commented on JENKINS-17204 GIT plugin fetch failing since update Git Plugin to 1.2.0+ I am surprised that a change from 1.507 to 1.508 Jenkins without any change of plugin versions would be the key change to cause the git-plugin or the git-client-plugin to stop working. I don't think there is any knowledge of the git plugin built into the core Jenkins code. The failure message seems to be a failure from the call to the command line interface git. Was there any other change on the system at the same time as the change from 1.507 to 1.508? Was your git server temporarily unavailable after that transition? Are others seeing the same issue with the 1.0.5 git-client-plugin and the 1.3.0 git-plugin? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16937) GIT 1.2.0 authenticates as the wrong user
Mark Waite commented on JENKINS-16937 GIT 1.2.0 authenticates as the wrong user The git-plugin 1.2.0 and its matching git-client-plugin version used JGit as their default Git implementation. The JGit implementation is not sufficient for the many use cases supported by the Jenkins Git plugins. The git-client-plugin 1.0.5 and git-plugin 1.3.0 versions switch back to using the command line Git as their default Git implementation. Could you upgrade to those versions and see if the issue is resolved for you? If it is not resolved, then the issue may be related to the refactoring that was started in 1.1.27. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17252) JGit checkout poor performaces
Mark Waite closed JENKINS-17252 as Fixed JGit checkout poor performaces Reported resolved by original submitter. Change By: Mark Waite (25/Mar/13 12:32 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17252) JGit checkout poor performaces
Mark Waite resolved JENKINS-17252 as Fixed JGit checkout poor performaces Confirmed fixed by original submitter Change By: Mark Waite (25/Mar/13 12:31 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16940) Git publisher fails with Invalid id: origin/master when trying to publish changes
Mark Waite commented on JENKINS-16940 Git publisher fails with Invalid id: origin/master when trying to publish changes The git client plugin 1.4.0 reported the push but did not actually push enough information to the remote server so that others could use it. I have confirmed that the git client plugin 1.5.0 does push enough information for others to use the resulting push. The full fix of this bug requires git client plugin 1.5.0 and glit plugin 1.3.0. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17242) pushes no longer being recorded in destination repository
Mark Waite resolved JENKINS-17242 as Fixed pushes no longer being recorded in destination repository git client plugin 1.0.5 resolved this issue for me and one other person. Change By: Mark Waite (22/Mar/13 4:21 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17195) InvalidTagNameException with version 1.0.4 of git client
Mark Waite commented on JENKINS-17195 InvalidTagNameException with version 1.0.4 of git client Since git-client-plugin 1.0.5 reverted to using the git CLI instead of using JGit as its default, I think this bug is fixed by git-client-plugin 1.0.5. Can you check that the issue is resolved by installing git-client-plugin 1.0.5? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17204) GIT plugin fetch failing since update Git Plugin to 1.2.0+
Mark Waite commented on JENKINS-17204 GIT plugin fetch failing since update Git Plugin to 1.2.0+ The git-client-plugin 1.0.5 has switched back to using the CLI version as its default implementation. It is available for download now. Does that resolve this issue? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17198) Caused by: org.eclipse.jgit.api.errors.CheckoutConflictException: Checkout conflict with files
Mark Waite commented on JENKINS-17198 Caused by: org.eclipse.jgit.api.errors.CheckoutConflictException: Checkout conflict with files @Dallas, I believe git-client-plugin 1.0.5 acknowledges that the JGit implementation is not yet mature enough for general purpose use as a replacement for the git command line implementation. When the JGit implementation has the necessary features, the plugin maintainer will consider changing the default to use JGit instead of using the command line. For at least some bug reports, there is a robot that resolves the issue when a submission is made that declares the issue is resolved. I interpreted that to mean that anyone can resolve an issue, including the submitter of the change which fixes the issue. The project does not seem to require or mandate that the issue can only be resolved by the person who reported the issue. In this case, I think it would be great if the original submitter would install git-client-plugin 1.0.5 and confirm the issue is resolved, but in the general case, if the issue is resolved, anyone can mark it as resolved. The plugin maintainer can still refer to this bug report (and others) before the next time when it is chosen to make JGit the default implementation instead of using the CLI implementation. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17252) JGit checkout poor performaces
Mark Waite commented on JENKINS-17252 JGit checkout poor performaces git-client-plugin 1.0.5 reverts to using command line git for its implementation. Can you confirm that installing the git-client-plugin 1.0.5 resolves this issue? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17195) InvalidTagNameException with version 1.0.4 of git client
Mark Waite commented on JENKINS-17195 InvalidTagNameException with version 1.0.4 of git client Go to the "Advanced" tab in the "Manage Plugins" section and you'll see an "Update Now" button in the bottom right corner. Above that "Update Now" button it will show the last time it polled for updates. If you press the "Update Now", it will poll immediately, and should then show the 1.0.5 plugin is available. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17195) InvalidTagNameException with version 1.0.4 of git client
Mark Waite resolved JENKINS-17195 as Fixed InvalidTagNameException with version 1.0.4 of git client git-client-plugin 1.0.5 resolved this by switching back to the CLI as the default git implementation. Change By: Mark Waite (22/Mar/13 6:10 PM) Status: Reopened Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17204) GIT plugin fetch failing since update Git Plugin to 1.2.0+
Mark Waite resolved JENKINS-17204 as Fixed GIT plugin fetch failing since update Git Plugin to 1.2.0+ Resolved in git-client-plugin 1.0.5 Change By: Mark Waite (22/Mar/13 6:16 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16941) Git publisher post build action fails on slave agent - unable to serialize
Mark Waite commented on JENKINS-16941 Git publisher post build action fails on slave agent - unable to serialize The git-client-plugin 1.0.5 and git-plugin 1.3.0 still show the same problem when attempting a build from a slave agent. The same build works fine if it is restricted to the master node. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16941) Git publisher post build action fails on slave agent - unable to serialize
Mark Waite edited a comment on JENKINS-16941 Git publisher post build action fails on slave agent - unable to serialize The git-client-plugin 1.0.5 and git-plugin 1.3.0 still show the same problem when attempting a build from a slave agent. The same build works fine if it is restricted to the master node. That seems to indicate that this issue is not directly related to whether the git implementation is JGit or command line Git. The git-client-plugin 1.0.4 implementation default was JGit (which showed the problem). The git-client-plugin 1.0.5 implementation default is command line Git (which also shows the problem). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17204) GIT plugin fetch failing since update Git Plugin to 1.2.0+
Mark Waite closed JENKINS-17204 as Fixed GIT plugin fetch failing since update Git Plugin to 1.2.0+ Several different users have reported the issue is resolved. Thanks! Change By: Mark Waite (23/Mar/13 4:03 AM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17273) Polling fails attempting to set an invalid tag before build
Mark Waite resolved JENKINS-17273 as Fixed Polling fails attempting to set an invalid tag before build Fixed in git-client-plugin 1.0.5 Change By: Mark Waite (23/Mar/13 4:14 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
