[JIRA] [git] (JENKINS-21914) Intermittent Git(hub) polling errors on Windows

2014-04-14 Thread dhumen...@gmail.com (JIRA)














































David Humeniuk
 commented on  JENKINS-21914


Intermittent Git(hub) polling errors on Windows















I have the same issue. There are no git.exe processes running (I'm assuming that the polling would have to run on the master, that's what I checked). git.exe will show up in the task manager, but quickly disappear. When this happens, it is intermittent. Is it possible that Jenkins is trying to use the same file for multiple jobs or something? I tried installing the File Leak Detector plug-in, but got this error when I tried to activate:


javax.servlet.ServletException: java.lang.Error: Failed to activate file leak detector: Connecting to 0
Exception in thread "main" java.lang.reflect.InvocationTargetException
	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:601)
	at org.kohsuke.file_leak_detector.Main.run(Main.java:50)
	at org.kohsuke.file_leak_detector.Main.main(Main.java:35)
Caused by: java.io.IOException: no such process
	at sun.tools.attach.WindowsVirtualMachine.openProcess(Native Method)
	at sun.tools.attach.WindowsVirtualMachine.(WindowsVirtualMachine.java:56)
	at sun.tools.attach.WindowsAttachProvider.attachVirtualMachine(WindowsAttachProvider.java:69)
	at com.sun.tools.attach.VirtualMachine.attach(VirtualMachine.java:213)
	... 6 more


It probably also noteworthy that I'm using this with the Stash Webhooks to Jenkins plug-in (https://marketplace.atlassian.com/plugins/com.nerdwin15.stash-stash-webhook-jenkins). That plug-in will trigger Jenkins to check for branches to build and I have several Jenkins jobs, one job for each development branch (plus several jobs for the master).



























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/d/optout.


[JIRA] [git-client] (JENKINS-21016) Problems with git-credentials-store for http credentials (introduced with fix for issue #20318 ?)

2014-04-14 Thread dhumen...@gmail.com (JIRA)














































David Humeniuk
 commented on  JENKINS-21016


Problems with git-credentials-store for http credentials (introduced with fix for issue #20318 ?)















I'll report my status on the other issue since that seems to be more appropriate. Thanks.



























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/d/optout.


[JIRA] [git-client] (JENKINS-21016) Problems with git-credentials-store for http credentials (introduced with fix for issue #20318 ?)

2014-04-14 Thread dhumen...@gmail.com (JIRA)














































David Humeniuk
 commented on  JENKINS-21016


Problems with git-credentials-store for http credentials (introduced with fix for issue #20318 ?)















I'm still seeing this issue with git client plug-in 1.8.0. Here's the specific message:

Started on Apr 14, 2014 12:00:10 PM
Using strategy: Default
[poll] Last Built Revision: Revision e28681748de2b634ab6cd68c55dc0ac349e6b872 (origin/master)
using .gitcredentials to set credentials
Could not remove the credential section from the git configuration
FATAL: Command "git config --local credential.helper store --file=\"C:\Users\IDTASK~1\AppData\Local\Temp\git4905599288427248808.credentials\"" returned status code 255:
stdout: 
stderr: error: could not lock config file .git/config: File exists

hudson.util.IOException2: Command "git config --local credential.helper store --file=\"C:\Users\IDTASK~1\AppData\Local\Temp\git4905599288427248808.credentials\"" returned status code 255:
stdout: 
stderr: error: could not lock config file .git/config: File exists

	at hudson.plugins.git.GitSCM.compareRemoteRevisionWith(GitSCM.java:459)
	at hudson.scm.SCM._compareRemoteRevisionWith(SCM.java:356)
	at hudson.scm.SCM.poll(SCM.java:373)
	at hudson.model.AbstractProject._poll(AbstractProject.java:1567)
	at hudson.model.AbstractProject.poll(AbstractProject.java:1490)
	at hudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:439)
	at hudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:468)
	at hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:118)
	at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
	at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
	at java.util.concurrent.FutureTask.run(Unknown Source)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
	at java.lang.Thread.run(Unknown Source)
Caused by: hudson.plugins.git.GitException: Command "git config --local credential.helper store --file=\"C:\Users\IDTASK~1\AppData\Local\Temp\git4905599288427248808.credentials\"" returned status code 255:
stdout: 
stderr: error: could not lock config file .git/config: File exists

	at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1276)
	at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1253)
	at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1249)
	at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1245)
	at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1142)
	at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1091)
	at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1082)
	at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.getHeadRev(CliGitAPIImpl.java:1739)
	at hudson.plugins.git.GitSCM.compareRemoteRevisionWithImpl(GitSCM.java:492)
	at hudson.plugins.git.GitSCM.compareRemoteRevisionWith(GitSCM.java:457)
	... 13 more
Done. Took 13 sec
No changes



























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/d/optout.


[JIRA] [multiple-scms] (JENKINS-22390) Plug-in things there are changes when there are not

2014-03-27 Thread dhumen...@gmail.com (JIRA)














































David Humeniuk
 updated  JENKINS-22390


Plug-in things there are changes when there are not
















Change By:


David Humeniuk
(27/Mar/14 4:51 PM)




Environment:


Jenkins 1.532.2, multiple SCM plug-in 0.3, Git client plug-in 1.6.6, Git plug-in 2.0.4



























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/d/optout.


[JIRA] [multiple-scms] (JENKINS-22390) Plug-in things there are changes when there are not

2014-03-27 Thread dhumen...@gmail.com (JIRA)














































David Humeniuk
 created  JENKINS-22390


Plug-in things there are changes when there are not















Issue Type:


Bug



Affects Versions:


current



Assignee:


Kevin Bell



Components:


multiple-scms



Created:


27/Mar/14 4:49 PM



Description:


Get a message like below that says changes are found so the build runs at each polling interval. However, both repositories have the latest changes (SVN rev. 6 is the latest, SHA-1 commit hash is for the latest revision for the branch.

I have other jobs that use only the Git branch with the basic plug-in that does not have any issues. Also, I have a job that is using origin/master branch with the multiple SCM plug-in and it doesn't have the same issue.


Started on Mar 27, 2014 12:40:23 PM
Polling SCM changes on centos
Received SCM poll call on centos for THOSE-Release-Docs on Mar 27, 2014 12:47:48 PM
https://xxx.yyy.com/svn/project-name/trunk is at revision 6
Using strategy: Default
[poll] Last Built Revision: Revision d8dafe61061a336db85a27c148bf57e2fc54b006 (origin/release/0.7.0)
using .gitcredentials to set credentials
Done. Took 7.7 sec
Changes found





Project:


Jenkins



Priority:


Major



Reporter:


David Humeniuk

























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/d/optout.


[JIRA] [git-client] (JENKINS-18951) Problems with too long paths

2014-02-08 Thread dhumen...@gmail.com (JIRA)














































David Humeniuk
 commented on  JENKINS-18951


Problems with too long paths 















Can't you use a Unicode path (http://msdn.microsoft.com/en-us/library/aa365247(VS.85).aspx#maxpath) that is limited to 32,767 characters instead of 256?



























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] [warnings] (JENKINS-21240) Javac compiler "cannot find annotation method" warnings are ignored

2014-01-06 Thread dhumen...@gmail.com (JIRA)














































David Humeniuk
 created  JENKINS-21240


Javac compiler "cannot find annotation method" warnings are ignored















Issue Type:


Bug



Assignee:


Ulli Hafner



Components:


warnings



Created:


06/Jan/14 5:46 PM



Description:


I have a few of the following warnings outputted by javac: 

aaa.class: warning: Cannot find annotation method 'xxx()' in type '': class file for fully.qualified.ClassName not found

However, they are not being picked up by the Warnings plug-in.  I assume it is because they don't have the typical format of "[javac] file: warning: [type] message" (as the [type] part is not there).




Project:


Jenkins



Priority:


Major



Reporter:


David Humeniuk

























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-14629) plugin don't fail the build when checkout failed

2012-10-19 Thread dhumen...@gmail.com (JIRA)














































David Humeniuk
 commented on  JENKINS-14629


plugin don't fail the build when checkout failed















This issue is included in the changelog for 1.43, but this issue hasn't been updated to reflect



























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






[JIRA] (JENKINS-14550) "Checksum mismatch while updating" with Subversion Plugin 1.42

2012-10-19 Thread dhumen...@gmail.com (JIRA)














































David Humeniuk
 commented on  JENKINS-14550


"Checksum mismatch while updating" with Subversion Plugin 1.42















This issue is included in the changelog for 1.43, but this issue hasn't been updated to reflect



























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






[JIRA] (JENKINS-4727) svn error results in 200 failed builds

2012-08-10 Thread dhumen...@gmail.com (JIRA)














































David Humeniuk
 commented on  JENKINS-4727


svn error results in 200 failed builds















I still have this problem with Jenkins 1.475 and SVN plug-in 1.42.  Any update to this?



























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