[JIRA] [git-plugin] (JENKINS-28551) Git fetch fails randomly with status code 128
Title: Message Title Karthic Sivaswamy created an issue Jenkins / JENKINS-28551 Git fetch fails randomly with status code 128 Issue Type: Bug Assignee: Nicolas De Loof Components: git-plugin Created: 25/May/15 7:03 AM Labels: plugin git jenkins windows scm Priority: Minor Reporter: Karthic Sivaswamy We have configured a multi phase job where any changes in Git SCM will trigger two jobs. Among the two jobs any one of the job getting failed randomly while fetching the git changes. And, during the next build it's getting passed. Here is my error log. 11:41:52 Started by upstream project "1_CPU_Xtreme_Feedback" build number 3092 11:41:52 originally caused by: 11:41:52 Started by an SCM change 11:41:52 [EnvInject] - Loading node environment variables. 11:41:52 Building remotely on kcebuilder2 in workspace c:\jenkins_keivmcsi\workspace\CPU_XF_ARM9 11:41:55 Fetching changes from the remote Git repository 11:41:55 Fetching upstream changes from git:lift 11:42:14 FATAL: Failed to fetch from git:lift 11:42:14 hudson.plugins.git.GitException: Failed to fetch from git:lift 11:42:14 at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:612) 11:42:14 at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:836) 11:42:14 at hudson.plugins.git.GitSCM.c
[JIRA] [claim-plugin] (JENKINS-28552) visible reason in build result
Title: Message Title
Larry Cai created an issue
Jenkins / JENKINS-28552
visible reason in build result
Issue Type:
Improvement
Assignee:
Christian Bremer
Components:
claim-plugin
Created:
25/May/15 7:06 AM
Environment:
Jenkins 1.613, claim-plugin 2.7
Priority:
Minor
Reporter:
Larry Cai
So far the claimed failure reason is not visible in the build result, it was put into img's title only.
{{ title="$ {%claimed.reason(it.claimedByName,it.reason)}
" src=""> {imagesURL}
/16x16/lock.gif"/>}}
As the user, if I can see the failure reason in build result directly without hovering over the image, I don't need to click inside to check detail
And it is even better, if the text can be set in own css (like yellow background/white foreground), it can be highlight.
Surely this could be optional to keep backward compatibility. It is user's responsibility to control the text size not too long to fit into build result space.
[JIRA] [claim-plugin] (JENKINS-28552) visible reason in build result
Title: Message Title
Larry Cai updated an issue
Jenkins / JENKINS-28552
visible reason in build result
Change By:
Larry Cai
So far the claimed failure reason is not visible in the build result, it was put into img's title only.{ { quote} title="${%claimed.reason(it.claimedByName,it.reason)}" src=""> {quote } } As the user, if I can see the failure reason in build result directly without hovering over the image, I don't need to click inside to check detailAnd it is even better, if the text can be set in own css (like yellow background/white foreground), it can be highlight.Surely this could be optional to keep backward compatibility. It is user's responsibility to control the text size not too long to fit into build result space.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
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] [claim-plugin] (JENKINS-28552) visible reason in build result
Title: Message Title
Larry Cai updated an issue
Jenkins / JENKINS-28552
visible reason in build result
Change By:
Larry Cai
So far the claimed failure reason is not visible in the build result, it was put into img's title only.{ quote} { title="${%claimed.reason(it.claimedByName,it.reason)}" src=""> {quote } } see code https://github.com/jenkinsci/claim-plugin/blob/master/src/main/resources/hudson/plugins/claim/AbstractClaimBuildAction/badge.jelly As the user, if I can see the failure reason in build result directly without hovering over the image, I don't need to click inside to check detailAnd it is even better, if the text can be set in own css (like yellow background/white foreground), it can be highlight.Surely this could be optional to keep backward compatibility. It is user's responsibility to control the text size not too long to fit into build result space.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
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] [claim-plugin] (JENKINS-28552) visible reason in build result
Title: Message Title
Larry Cai updated an issue
Jenkins / JENKINS-28552
visible reason in build result
Change By:
Larry Cai
So far the claimed failure reason is not visible in the build result, it was put into img's title only. {{ see code https://github.com/jenkinsci/claim-plugin/blob/master/src/main/resources/hudson/plugins/claim/AbstractClaimBuildAction/badge.jelly As the user, if I can see the failure reason in build result directly without hovering over the image, I don't need to click inside to check detailAnd it is even better, if the text can be set in own css (like yellow background/white foreground), it can be highlight.Surely this could be optional to keep backward compatibility. It is user's responsibility to control the text size not too long to fit into build result space.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
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] [claim-plugin] (JENKINS-28552) visible claimed failure reason in build result
Title: Message Title Larry Cai updated an issue Jenkins / JENKINS-28552 visible claimed failure reason in build result Change By: Larry Cai Summary: visible claimed failure reason in build result Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [build-blocker-plugin] (JENKINS-28513) Build-Blocker-Plugin blocks on builds queued leading to deadlock
Title: Message Title Lars Vateman commented on JENKINS-28513 Re: Build-Blocker-Plugin blocks on builds queued leading to deadlock I had to downgrade to Jenkins 1.608 to make it work again. Something in 1.609 or 1.610 must have broken it. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-28419) NPE may happen if somebody tries to drop the e-mail JenkinsLocationConfiguration:setAdminAddress()
Title: Message Title SCM/JIRA link daemon commented on JENKINS-28419 Re: NPE may happen if somebody tries to drop the e-mail JenkinsLocationConfiguration:setAdminAddress() Code changed in jenkins User: Oleg Nenashev Path: core/src/main/java/hudson/ExtensionList.java core/src/main/java/jenkins/model/JenkinsLocationConfiguration.java core/src/test/java/jenkins/model/JenkinsLocationConfigurationTest.java http://jenkins-ci.org/commit/jenkins/7e4171ca5bb338aa8aba99d22c77991e20c76115 Log: Merge pull request #1707 from oleg-nenashev/jenkins_local_config [FIXED JENKINS-28419] - JenkinsLocationConfiguration::adminAddress can be reset Compare: https://github.com/jenkinsci/jenkins/compare/17f5227b1af6...7e4171ca5bb3 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-28419) NPE may happen if somebody tries to drop the e-mail JenkinsLocationConfiguration:setAdminAddress()
Title: Message Title SCM/JIRA link daemon commented on JENKINS-28419 Re: NPE may happen if somebody tries to drop the e-mail JenkinsLocationConfiguration:setAdminAddress() Code changed in jenkins User: Oleg Nenashev Path: core/src/test/java/jenkins/model/JenkinsLocationConfigurationTest.java http://jenkins-ci.org/commit/jenkins/dab392f80f68d72846927dc7345f80887f63 Log: JENKINS-28419 - Direct unit tests for JenkinsLocationConfiguration::adminAddress setter and getter Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-28419) NPE may happen if somebody tries to drop the e-mail JenkinsLocationConfiguration:setAdminAddress()
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-28419 NPE may happen if somebody tries to drop the e-mail JenkinsLocationConfiguration:setAdminAddress() Change By: SCM/JIRA link daemon Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-28419) NPE may happen if somebody tries to drop the e-mail JenkinsLocationConfiguration:setAdminAddress()
Title: Message Title SCM/JIRA link daemon commented on JENKINS-28419 Re: NPE may happen if somebody tries to drop the e-mail JenkinsLocationConfiguration:setAdminAddress() Code changed in jenkins User: Oleg Nenashev Path: core/src/main/java/jenkins/model/JenkinsLocationConfiguration.java http://jenkins-ci.org/commit/jenkins/17116a2129b808d64d76b5dcba9d3037003aed30 Log: [FIXED JENKINS-28419] - Support the reset of JenkinsLocationConfiguration::adminAddress Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [promoted-builds-plugin] (JENKINS-28533) Promoted build does not respect "Restrict where this promotion process can be run" check with empty label
Title: Message Title juan pablo santos commented on JENKINS-28533 Re: Promoted build does not respect "Restrict where this promotion process can be run" check with empty label Suggested solution still needs some rework on /hudson/plugins/promoted_builds/PromotionProcess/process-config.jelly, as the empty string on the input field is displayed as "". Perhaps would be easier to track the checkbox usage indepently of the input field? Anyway, we managed to bypass our job requirement of executing the promotion on the same node as the job build, so we are moving away from this issue. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-28553) Classic plugin loading with PluginServletFilter can fail to add a Filter even when one jenkins is already initialized
Title: Message Title Manuel Blechschmidt created an issue Jenkins / JENKINS-28553 Classic plugin loading with PluginServletFilter can fail to add a Filter even when one jenkins is already initialized Issue Type: Bug Assignee: Unassigned Components: core Created: 25/May/15 8:01 AM Environment: $ uname -a Linux ip-172-31-24-63 3.14.35-28.38.amzn1.x86_64 #1 SMP Wed Mar 11 22:50:37 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux $ java -version java version "1.7.0_79" OpenJDK Runtime Environment (amzn-2.5.5.1.59.amzn1-x86_64 u79-b14) OpenJDK 64-Bit Server VM (build 24.79-b02, mixed mode) $ jenkins 1.614 wildfly 8.2.0.Final Labels: classic plugin filter marvelution Priority: Major Reporter: Manuel Blechschmidt When starting jenkins with the JIRA plugin the following NullPointerException is thrown: 10:29:54,996 INFO [com.marvelution.jenkins.plugins.jira.JIRAPlugin] (Loading
[JIRA] [htmlpublisher-plugin] (JENKINS-24057) Jenkins HTML publisher : latest html report not publishing project level when job fails
Title: Message Title Daniel Horak commented on JENKINS-24057 Re: Jenkins HTML publisher : latest html report not publishing project level when job fails Is it possible to configure this option via Jenkins job builder? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [maven-plugin] (JENKINS-3256) maven job does not deploy jar artifacts
Title: Message Title xylo commented on JENKINS-3256 Re: maven job does not deploy jar artifacts Same for me with the latest version of jenkins (1.614). Jenkins deloys the pom.xml, the sources.jar, and the javadoc.jar, but not the binary distribution (the actual jar file). Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [maven-plugin] (JENKINS-3256) maven job does not deploy jar artifacts
Title: Message Title xylo edited a comment on JENKINS-3256 Re: maven job does not deploy jar artifacts Same for me with the latest version of jenkins (1.614). Jenkins deloys the pom.xml, the sources.jar, and the javadoc.jar, but not the binary distribution (the actual jar file). In contrast to the original bug report I don't discover any LONG waiting time for the build. Everything (including the uploads to the maven repository) works quite fast on my machine. Thus it's not a timeout issue for me. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [maven-plugin] (JENKINS-3256) maven job does not deploy jar artifacts
Title: Message Title xylo edited a comment on JENKINS-3256 Re: maven job does not deploy jar artifacts Same for me with the latest version of jenkins (1.614). Jenkins deloys the pom.xml, the sources.jar, and the javadoc.jar, but not the binary distribution (the actual jar file). I checked if all jar files are created and they are. In contrast to the original bug report I don't discover any LONG waiting time for the build. Everything (including the uploads to the maven repository) works quite fast on my machine. Thus it's not a timeout issue for me. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [extended-choice-parameter-plugin] (JENKINS-28554) Please update the plugin revision history
Title: Message Title Ilya B created an issue Jenkins / JENKINS-28554 Please update the plugin revision history Issue Type: Task Assignee: vimil Components: extended-choice-parameter-plugin Created: 25/May/15 9:01 AM Priority: Minor Reporter: Ilya B The change log in https://wiki.jenkins-ci.org/display/JENKINS/Extended+Choice+Parameter+plugin has stopped at version 0.33, that is ten revisions ago. Please describe what has changed and what is the status of the recent revisions. Add Comment
[JIRA] [maven-plugin] (JENKINS-28555) Build failed due to Maven
Title: Message Title AMRITA JOSHI created an issue Jenkins / JENKINS-28555 Build failed due to Maven Issue Type: Bug Assignee: Unassigned Components: maven-plugin Created: 25/May/15 10:46 AM Environment: Jenkins :1.605 Priority: Minor Reporter: AMRITA JOSHI Build is failing due to below error:- executing `hybris:build:ant_clean' Buildfile: E:\releng\dev\jenkins\jobs\Sandbox Build new\workspace\source\bin\platform\build.xml [echo] E:\releng\dev\jenkins\jobs\Sandbox Build new\workspace\source\bin\platform/tomcat/bin [echo] cleaning library folder E:\releng\dev\jenkins\jobs\Sandbox Build new\workspace\source\bin\platform/lib/dbdriver/ [artifact:mvn] Downloading: org/apache/maven/maven-core/2.0.10/maven-core-2.0.10.pom from repository central at http://repo1.maven.org/maven2 [artifact:mvn] Error transferring file: Connection timed out: connect [artifact:mvn] [WARNING] Unable to get resource 'org.apache.maven:maven-core:pom:2.0.10' from repository central (http://repo1.maven.org/maven2): Error transferring file: Connection timed out: connect [artifact:mvn] Downloading: org/apache/maven/maven-core/2.0.10/maven-core-2.0.10.jar from repository central at http://repo1.maven.org/maven2 [artifact:mvn] Error transferring file: Connection timed out: connect Plea
[JIRA] [gerrit-trigger-plugin] (JENKINS-28556) Verification failure when message file contains quote
Title: Message Title Orgad Shaneh created an issue Jenkins / JENKINS-28556 Verification failure when message file contains quote Issue Type: Bug Assignee: rsandell Components: gerrit-trigger-plugin Created: 25/May/15 11:54 AM Priority: Major Reporter: Orgad Shaneh May 25, 2015 2:04:48 PM SEVERE com.sonymobile.tools.gerrit.gerritevents.workers.cmd.AbstractSendCommandJob sendCommand Could not run command gerrit review 10470,43 --message 'Build Failed https://server/job/Job/13901/ : FAILURE <<< Build failed Some/File.cpp: In member function 'virtual int Class::Function(Argment&)': Some/File.cpp:284:3: error: return-statement with no value, in function returning 'int' [-fpermissive] return; ^ make: *** [Some/File.o] Error 1 make: *** Waiting for unfinished jobs >>>' --label Verified=-1 --label Code-Review=0 --notify=ALL java.io.IOException: Error during sending command at com.sonymobile.tools.gerrit.gerritevents.workers.cmd.AbstractSendCommandJob.sendCommand2(AbstractSendCommandJob.java:118) at com.sonymobile.tools.gerrit.gerritevents.workers.cmd.AbstractSendCommandJob.sendCommand(AbstractSendCommandJob.java:79) at com.sonyericsson.hudson.plugins.gerrit.trigger.gerritnotifier.GerritNotifier.buildCompleted(GerritNotifier.java:118) at com.sonyericsson.hudson.plugins.gerrit.trigger.gerritnotifier.job.ssh.BuildCompletedCommandJob.run(BuildCompletedCommandJob.java:71) 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
[JIRA] [core] (JENKINS-28155) Job fails with [An existing connection was forcibly closed by the remote host]
Title: Message Title Vassilena Treneva commented on JENKINS-28155 Re: Job fails with [An existing connection was forcibly closed by the remote host] On my slave where I see this error in the server management console I see this: TCP/IP failed to establish an outgoing connection because the selected local endpoint was recently used to connect to the same remote endpoint. This error typically occurs when outgoing connections are opened and closed at a high rate, causing all available local ports to be used and forcing TCP/IP to reuse a local port for an outgoing connection. To minimize the risk of data corruption, the TCP/IP standard requires a minimum time period to elapse between successive connections from a given local endpoint to a given remote endpoint. I guess Jenkins is abusing the connection somehow Any ideas how to resolve it? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-28155) Job fails with [An existing connection was forcibly closed by the remote host]
Title: Message Title Vassilena Treneva updated an issue Jenkins / JENKINS-28155 Job fails with [An existing connection was forcibly closed by the remote host] Change By: Vassilena Treneva Component/s: remoting Priority: Major Critical Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [aws-lambda-plugin] (JENKINS-28441) refactor project for future feature additions
Title: Message Title SCM/JIRA link daemon commented on JENKINS-28441 Re: refactor project for future feature additions Code changed in jenkins User: cast Path: src/main/java/com/xti/jenkins/plugin/awslambda/service/WorkSpaceZipper.java src/test/java/com/xti/jenkins/plugin/awslambda/service/WorkSpaceZipperTest.java http://jenkins-ci.org/commit/aws-lambda-plugin/804cea1428ff03620af1317f023bfa5023f3d4e0 Log: JENKINS-28441 Added Workspace zip tests and ensured that only the contents are zipped instead of the enclosing folder Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [unity3d-plugin] (JENKINS-25939) Job abort doesn't kill process
Title: Message Title lacostej commented on JENKINS-25939 Re: Job abort doesn't kill process I tried to reproduce the problem in a Jenkins 1.610 distributed setup with a Linux master and a Mac slave on a 5 min Unity3d 5.0.1f1 job (I use a PostprocessBuildPlayer that sleeps for 5 min). The UNity3d plugin was v0.8. To try to reproduce the problem, I used the stop button the Build Time-out plugin (1.14.1) with a 1 min max timing out if the console had no activity the same plugin with an absolute 1 min time out. In all cases, the job stopped and there was no dangling Unity3d processes on the slave. So I am unable to reproduce this issue. Please provide more information about your environment. In particular, jenkins version, unity3d plugin version, java version, Unity3d version, etc. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [unity3d-plugin] (JENKINS-25939) Job abort doesn't kill process
Title: Message Title lacostej resolved as Cannot Reproduce Resolving as "Cannot Reproduce" until I get more information. Jenkins / JENKINS-25939 Job abort doesn't kill process Change By: lacostej Status: Open Resolved Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [cli-commander-plugin] (JENKINS-28557) Show CLI short help while typing the command
Title: Message Title Oliver Gondža created an issue Jenkins / JENKINS-28557 Show CLI short help while typing the command Issue Type: Improvement Assignee: Oliver Gondža Components: cli-commander-plugin Created: 25/May/15 12:34 PM Priority: Minor Reporter: Oliver Gondža Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the
[JIRA] [cli-commander-plugin] (JENKINS-28558) Unable to authenticate when reverse proxy auth used
Title: Message Title Oliver Gondža created an issue Jenkins / JENKINS-28558 Unable to authenticate when reverse proxy auth used Issue Type: Bug Assignee: Oliver Gondža Components: cli-commander-plugin Created: 25/May/15 12:37 PM Priority: Major Reporter: Oliver Gondža javax.servlet.ServletException: org.acegisecurity.userdetails.UsernameNotFoundException: ogon...@redhat.com at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:795) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:875) at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:391) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:745) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:875) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:648) at org.kohsuke.stapler.Stapler.service(Stapler.java:237) at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:295) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) at hudson.plugins.audit_trail.AuditTrailFilter.doFilter(AuditTrailFilter.java:95) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:246) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.ap
[JIRA] [artifact-diff-plugin] (JENKINS-28559) Plug-in generates wrong URLs
Title: Message Title Pavel Janoušek created an issue Jenkins / JENKINS-28559 Plug-in generates wrong URLs Issue Type: Bug Assignee: Unassigned Components: artifact-diff-plugin Created: 25/May/15 12:39 PM Priority: Major Reporter: Pavel Janoušek If the Jenkins instance isn't deployed to the TOP level structure, plug-in doesn't recognize that and generates the wrong URLs which return HTTP code 404. Example: Jenkins is available at http: and so your 25th build of job A is http:///dir/job/A/25/. Each build archives file TMP.txt. A generated URLs for the artifact diff of TMP.txt is http:///job/A/25/artifact-diff/24/TMP.txt?output=html Fixed URL by hand: http:job/A/25/artifact-diff/24/TMP.txt?output=html works. The part of URL is missed in generated URLs. Add Comment
[JIRA] [build-pipeline-plugin] (JENKINS-28103) Build pipeline plugin again refuses to start a build with parameters
Title: Message Title Sebastian Bergandy commented on JENKINS-28103 Re: Build pipeline plugin again refuses to start a build with parameters I can't also run a pipeline where initial job contains parameters. I got _javascript_ error jQuery.fancybox is not a function. Normaly an iframe should be opened where parameters can be passed. Do you also have any JS errors? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [build-pipeline-plugin] (JENKINS-28560) Java Script error when opening pop up for job parameters
Title: Message Title Sebastian Bergandy created an issue Jenkins / JENKINS-28560 _javascript_ error when opening pop up for job parameters Issue Type: Bug Assignee: Unassigned Attachments: jenkins-build-pipline-plugin-bug-fancybox.png Components: build-pipeline-plugin Created: 25/May/15 1:26 PM Environment: Jenkins 1.613 Build Pipeline Plugin 1.4.7 Google chrome Windows 7 Priority: Minor Reporter: Sebastian Bergandy If an initial job contains parameters then a pipline can't be run. The pop up for enetering parameters isn't show. _javascript_ error occurs (see attached screenshot).
[JIRA] [aws-lambda-plugin] (JENKINS-28443) invoke lambda function as build-step and post-build-action
Title: Message Title SCM/JIRA link daemon commented on JENKINS-28443 Re: invoke lambda function as build-step and post-build-action Code changed in jenkins User: cast Path: src/main/java/com/xti/jenkins/plugin/awslambda/AWSLambdaDescriptor.java src/main/java/com/xti/jenkins/plugin/awslambda/LambdaVariables.java src/main/java/com/xti/jenkins/plugin/awslambda/exception/LambdaInvokeException.java src/main/java/com/xti/jenkins/plugin/awslambda/invoke/AWSInvokeDescriptor.java src/main/java/com/xti/jenkins/plugin/awslambda/invoke/JsonParameterVariables.java src/main/java/com/xti/jenkins/plugin/awslambda/invoke/LambdaInvokeBuildStepVariables.java src/main/java/com/xti/jenkins/plugin/awslambda/invoke/LambdaInvokeVariables.java src/main/java/com/xti/jenkins/plugin/awslambda/service/LambdaInvokeService.java src/main/java/com/xti/jenkins/plugin/awslambda/upload/LambdaUploadBuildStepVariables.java src/main/webapp/help-awsRegion.html src/test/java/com/xti/jenkins/plugin/awslambda/service/LambdaInvokeServiceTest.java http://jenkins-ci.org/commit/aws-lambda-plugin/76072b6e93f3a5c5bcce289cfba0460b017fa7a3 Log: JENKINS-28443 Added failure handling for Handled and Unhandled errors Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-28561) Can't Setup Security
Title: Message Title Ryan W created an issue Jenkins / JENKINS-28561 Can't Setup Security Issue Type: Bug Assignee: Unassigned Components: core Created: 25/May/15 4:59 PM Environment: Latest Jenkins from Ubuntu 14.04 apt-get. Using google chrome. Running Java 7 from Oracle. Priority: Critical Reporter: Ryan W Stack trace: javax.servlet.ServletException: net.sf.json.JSONException: JSONObject["realm"] is not a JSONObject. at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$13.dispatch(MetaClass.java:411) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:123) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:114) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.ja
[JIRA] [job-dsl-plugin] (JENKINS-28562) [Feature Request] Need TriggerContext as ExtensibleContext
Title: Message Title Kirill Merkushev created an issue Jenkins / JENKINS-28562 [Feature Request] Need TriggerContext as ExtensibleContext Issue Type: Bug Assignee: Daniel Spilker Components: job-dsl-plugin Created: 25/May/15 5:36 PM Priority: Major Reporter: Kirill Merkushev In 1.34 list of contexts https://github.com/jenkinsci/job-dsl-plugin/wiki/Extending-the-DSL don't includes TriggerContext. Add Comment This message was sent by Atlassian JI
[JIRA] [job-dsl-plugin] (JENKINS-28562) [Feature Request] Need TriggerContext as ExtensibleContext
Title: Message Title Kirill Merkushev updated an issue Jenkins / JENKINS-28562 [Feature Request] Need TriggerContext as ExtensibleContext Change By: Kirill Merkushev Issue Type: Bug New Feature Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [job-dsl-plugin] (JENKINS-28562) Need TriggerContext as ExtensibleContext
Title: Message Title Kirill Merkushev updated an issue Jenkins / JENKINS-28562 Need TriggerContext as ExtensibleContext Change By: Kirill Merkushev In 1.34 list List of contexts https://github.com/jenkinsci/job-dsl-plugin/wiki/Extending-the-DSLdon't includes TriggerContext. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [job-dsl-plugin] (JENKINS-28562) Need TriggerContext as ExtensibleContext
Title: Message Title Kirill Merkushev updated an issue Jenkins / JENKINS-28562 Need TriggerContext as ExtensibleContext Change By: Kirill Merkushev Summary: [Feature Request] Need TriggerContext as ExtensibleContext Priority: Major Minor Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [job-dsl-plugin] (JENKINS-28562) Need TriggerContext as ExtensibleContext
Title: Message Title Kirill Merkushev updated an issue Jenkins / JENKINS-28562 Need TriggerContext as ExtensibleContext Change By: Kirill Merkushev Environment: job-dsl-plugin 1.34 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [xcode-plugin] (JENKINS-28563) allow configuration of derivedDataPath parameter
Title: Message Title Thomas Einwaller created an issue Jenkins / JENKINS-28563 allow configuration of derivedDataPath parameter Issue Type: Bug Assignee: Unassigned Components: xcode-plugin Created: 25/May/15 6:41 PM Priority: Minor Reporter: Thomas Einwaller since Xcode 5 this is the prefered way to configure the derived data/build directory (not using CONFIGURATION_BUILD_DIR anymore) see https://developer.apple.com/library/mac/documentation/Darwin/Reference/ManPages/man1/xcodebuild.1.html Add Comment
[JIRA] [aws-lambda-plugin] (JENKINS-28441) refactor project for future feature additions
Title: Message Title SCM/JIRA link daemon commented on JENKINS-28441 Re: refactor project for future feature additions Code changed in jenkins User: cast Path: src/main/java/com/xti/jenkins/plugin/awslambda/exception/AWSLambdaPluginException.java src/main/java/com/xti/jenkins/plugin/awslambda/exception/LambdaInvokeException.java src/main/java/com/xti/jenkins/plugin/awslambda/invoke/LambdaInvoker.java src/main/java/com/xti/jenkins/plugin/awslambda/service/LambdaInvokeService.java src/main/java/com/xti/jenkins/plugin/awslambda/upload/LambdaUploader.java src/test/java/com/xti/jenkins/plugin/awslambda/invoke/LambdaInvokerTest.java src/test/java/com/xti/jenkins/plugin/awslambda/upload/LambdaUploaderTest.java http://jenkins-ci.org/commit/aws-lambda-plugin/b30a779526a5976250796efae755c02b91d02142 Log: JENKINS-28441 Tested LambdaInvoker and LambdaUploader Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [htmlpublisher-plugin] (JENKINS-24057) Jenkins HTML publisher : latest html report not publishing project level when job fails
Title: Message Title mcrooney commented on JENKINS-24057 Re: Jenkins HTML publisher : latest html report not publishing project level when job fails Good question Daniel, that would be a question for someone familiar with that plugin. I'm not sure if it requires just a documentation change from them or a code change. You could try using "always-link-to-last-build" and seeing if that works; if not, file an issue over at https://storyboard.openstack.org/#!/project/723 for the new parameter Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [active-directory-plugin] (JENKINS-12607) Active directory user names should not be case sensitive.
Title: Message Title jothibasu Kamaraj commented on JENKINS-12607 Re: Active directory user names should not be case sensitive. Any Fix is give for this issue ,we are also facing same issue due to Case Sensitive while trying to apply the Access for the jobs via Role Strategy or Matrix Based security. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [active-directory-plugin] (JENKINS-12607) Active directory user names should not be case sensitive.
Title: Message Title jothibasu Kamaraj edited a comment on JENKINS-12607 Re: Active directory user names should not be case sensitive. Any Fix is give given for this issue ,we are also facing same issue due to Case Sensitive while trying to apply the Access for the jobs via Role Strategy or Matrix Based security. Jenkins Version:1.596.2 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [matrix-auth-plugin] (JENKINS-23844) Matrix based security should apply to case insensitive user name.
Title: Message Title jothibasu Kamaraj commented on JENKINS-23844 Re: Matrix based security should apply to case insensitive user name. Any Progress on this issue. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-28120) Jenkins core to require Java7
Title: Message Title SCM/JIRA link daemon commented on JENKINS-28120 Re: Jenkins core to require Java7 Code changed in jenkins User: Kohsuke Kawaguchi Path: pom.xml http://jenkins-ci.org/commit/jenkins/6496a946848204dc908c503452fc294c7daebb73 Log: JENKINS-28120 Phase 2: allow the core to use Java7 syntax and runtime. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-28120) Jenkins core to require Java7
Title: Message Title dogfood commented on JENKINS-28120 Re: Jenkins core to require Java7 Integrated in jenkins_main_trunk #4155 JENKINS-28120 Phase 2: allow the core to use Java7 syntax and runtime. (Revision 6496a946848204dc908c503452fc294c7daebb73) Result = UNSTABLE kohsuke : 6496a946848204dc908c503452fc294c7daebb73 Files : pom.xml Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-28419) NPE may happen if somebody tries to drop the e-mail JenkinsLocationConfiguration:setAdminAddress()
Title: Message Title dogfood commented on JENKINS-28419 Re: NPE may happen if somebody tries to drop the e-mail JenkinsLocationConfiguration:setAdminAddress() Integrated in jenkins_main_trunk #4155 Result = UNSTABLE Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-17290) Category titles in Available Plugins list appear wrong in reverse sort order
Title: Message Title dogfood commented on JENKINS-17290 Re: Category titles in Available Plugins list appear wrong in reverse sort order Integrated in jenkins_main_trunk #4155 Result = UNSTABLE Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [maven-plugin] (JENKINS-28555) Build failed due to Maven
Title: Message Title AMRITA JOSHI updated an issue Jenkins / JENKINS-28555 Build failed due to Maven Change By: AMRITA JOSHI Priority: Minor Major Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-plugin] (JENKINS-9052) Git plugin needs a better error diagnosis when failing to check out
Title: Message Title Tomasz Śniatowski commented on JENKINS-9052 Re: Git plugin needs a better error diagnosis when failing to check out I believe this was resolved erroneously. The bug report was about the git plugin hiding error output, and the output Mark mentioned is only a log of all the commands issued – but if any of them fails, their stderr is still not logged. This sometimes makes debugging difficult, especially in the case of transient errors. It's not helpful at all, for example, if we have a single error 24h ago that fixed itself later, where all we get in the log is Error cloning remote repo 'origin' with no way to know if it was a timeout, authentication error or a broken workspace. Getting git's stderr into the log would be much better. I was about to report this as a new bug but found this instead. I can file it again if you prefer – but I think this one should be reopened. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [htmlpublisher-plugin] (JENKINS-24057) Jenkins HTML publisher : latest html report not publishing project level when job fails
Title: Message Title Daniel Horak commented on JENKINS-24057 Re: Jenkins HTML publisher : latest html report not publishing project level when job fails Thanks mcrooney for hint, directly using "always-link-to-last-build" doesn't work, so I've created new issue for jenkins-job-publisher: https://storyboard.openstack.org/#!/story/2000270 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [envinject-plugin] (JENKINS-23274) Do not output the "Evaluated Groovy script" to console
Title: Message Title James Telfer commented on JENKINS-23274 Re: Do not output the "Evaluated Groovy script" to console IMO, this distracts from the information that I generally want to get from the build log, so I'd like this behaviour to be changed too. However, I understand that this might be helpful for some to know what script is being executed. I would like to change the plugin to accommodate this change, but I'd like to know what kind of solution would be acceptable. As I see it, there are a few options: Don't log the script at all, just log that the inline Groovy script is being executed. Log the first line of the script Log the first `n` characters of the script, followed by an ellipsis Log the first comment line from the script. Honestly, I think (1) is the better option, as I don't see much utility in logging the entire script. I'd welcome a response though, and I'll look to put a pull request together for the agreed fix. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-plugin] (JENKINS-28551) Git fetch fails randomly with status code 128
Title: Message Title Karthic Sivaswamy commented on JENKINS-28551 Re: Git fetch fails randomly with status code 128 If the upstream job is started in "node 1" and it triggers two jobs, if both the job starts running in "node 2", at least one job fails with this message. When triggered manually both the jobs are running successfully next time. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-plugin] (JENKINS-24454) Windows GIT SCM fetch code hung
Title: Message Title
Maximin Das S L commented on JENKINS-24454
Re: Windows GIT SCM fetch code hung
Getting the same error frequently.
Jenkins - 1.574 Git Plugin - 2.2.7 git version 1.9.5.msysgit.1
While the fetch is stuck, from the Process Explorer it could be seen that the ssh.exe is stuck on the command ssh g...@github.faked.com "git-upload-pack 'XYZ/Faked.git'"
Below is from Process Explorer.
jenkins.exe
java.exe
git.exe
git.exe
ssh.exe // this one is stuck
While the process is stuck, executing the command ssh g...@github.faked.com "git-upload-pack 'XYZ/Faked.git'" from command line gives the response which ends with
.
005467bd6f492ad36325aea516dfc2f423b1bc5e8dfe refs/tags/branch1
0057747b9750f2389c6ca630480674a85e1decad2387 refs/tags/branch1^{}
Connection to github.faked.com closed by remote host.
From the dump which generated while the process was hung,
STACK_TEXT:
0028d53c 74ee15f7 0002 0028d58c 0001 ntdll!NtWaitForMultipleObjects+0x15
0028d5d8 76741a0c 0028d58c 0028d600 KERNELBASE!WaitForMultipleObjectsEx+0x100
0028d620 767441f0 0002 7efde000 kernel32!WaitForMultipleObjectsExImplementation+0xe0
0028d63c 68015424 0002 0028d694 kernel32!WaitForMultipleObjects+0x18
The last control flow was to ntdll!NtWaitForMultipleObjects. From the name of the thread it seems like it is waiting for some resources, which is not known at this point.
Any ideas on how to fix this or workarounds which is working?
Add Comment
This message was sent by Atlassian JIRA (v6
