[JIRA] [findbugs-plugin] (JENKINS-28650) "Publish Findbugs" stops Maven web site publishing, not publishing Findbugs reports
Title: Message Title John Elion updated an issue Jenkins / JENKINS-28650 "Publish Findbugs" stops Maven web site publishing, not publishing Findbugs reports Change By: John Elion After getting a small Maven demonstration project working within Jenkins, I attempted to add the static analysis reports, installing the Static Analysis Utilities and Collector and the Findbugs Plugin. I tried several settings but was never able to see a FindBugs report on the Jenkins build status page, and eventually noticed that the 'Maven-generated site' link disappeared from the left-hand side of my project links.Ultimately I traced this down to: If "Publish Findbugs analysis results" is checked in the Build Settings area below "Add post-build step", no link is generated; if it is unchecked, the Maven web site link appears.The log files are instructive: near the end of a successful build I see the following, which seems to show the web site tree copy to where Jenkins stores the web site:00:01:02.137 [INFO] Cobertura Report generation was successful.00:01:02.137 [INFO] Generating "CPD" report --- maven-pmd-plugin:3.4:cpd00:01:02.168 [INFO] Generating "PMD" report --- maven-pmd-plugin:3.4:pmd00:01:02.324 [JENKINS] Archiving site from C:\Program Files (x86)\Jenkins\workspace\VizCommon\target\site to C:\Program Files (x86)\Jenkins\jobs\VizCommon\siteNear the end of a failed build I see this instead00:01:04.536 [INFO] Generating "CPD" report --- maven-pmd-plugin:3.4:cpd00:01:04.581 [INFO] Generating "PMD" report --- maven-pmd-plugin:3.4:pmd00:01:05.345 log4j:WARN No appenders could be found for logger (org.apache.commons.digester3.Digester.sax).00:01:05.345 log4j:WARN Please initialize the log4j system properly.00:01:06.534 [WARNING] Using default org.dom4j.DocumentFactory00:01:06.553 [WARNING] Using default org.dom4j.DocumentFactory00:01:06.595 [WARNING] Using default org.dom4j.DocumentFactory00:01:06.596 [WARNING] Using default org.dom4j.DocumentFactory00:01:06.885 [WARNING] Failed to notify spy hudson.maven.Maven3Builder$JenkinsEventSpy: null00:01:06.885 [INFO] 00:01:06.885 [INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ viz-common ---Note that I only enabled Findbugs reporting, even though Maven successfully generates the PMD and Cobertura reports (I had installed the Cobertura plugin but first disabled, then uninstalled it. I suspect the problem is with Findbugs (see PMD test below).I thought this might be related to JENKINS- 24743 26923 , which suggested a problem with common-io (although I believe my version of the SA tool includes that bug's fix); so I stopped Jenkins, renamed commons-io-2.2.jar and restarted; but re-running a "Publish Findbugs" build still presented the log4j and dom4j warnings and no web site.I suspect (or hope) these errors are not only causing the Maven web site to not be published, but may be why I never saw a link to Findbugs reports.I did also try the case where "Publish PMD analysis results" is checked (only, with the Findbugs box unchecked). In that case I saw the log4j warnings, but not the dom4j warnings; the web site did publish - and I also got a PMD link.
[JIRA] [findbugs-plugin] (JENKINS-28650) "Publish Findbugs" stops Maven web site publishing, not publishing Findbugs reports
Title: Message Title John Elion created an issue Jenkins / JENKINS-28650 "Publish Findbugs" stops Maven web site publishing, not publishing Findbugs reports Issue Type: Bug Assignee: Ulli Hafner Components: findbugs-plugin Created: 30/May/15 4:23 AM Environment: Jenkins 1.615 running on Windows 7 Enterprise SP1 on X64 Findbugs Plugin 4.6.0 PMD Plugin 3.41 Static Analysis Collector Plugin 1.43 Static Analysis Utilities 1.71 Maven 3.3.3 Findbugs 3.0.1 Priority: Major Reporter: John Elion After getting a small Maven demonstration project working within Jenkins, I attempted to add the static analysis reports, installing the Static Analysis Utilities and Collector and the Findbugs Plugin. I tried several settings but was never able to see a FindBugs report on the Jenkins build status page, and eventually noticed that the 'Maven-generated site' link disappeared from the left-hand side of my project links. Ultimately I traced this down to: If "Publish Findbugs analysis results" is checked in the Build Settings area below "Add post-build step", no link is generated; if it is unchecked, the Maven web site link appears. The log files are instructive: near the end of a successful build I see the following, which seems to show the web site tree copy to where Jenkins stores the web site: 00:01:02.137 [
[JIRA] [unity3d-plugin] (JENKINS-24386) Unity Test Tools package returns 2 or 3 for failed integration testing.
Title: Message Title Mark McNeely commented on JENKINS-24386 Re: Unity Test Tools package returns 2 or 3 for failed integration testing. Thank you for completing this request. I appreciate the addition to the plugin. 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-24386) Unity Test Tools package returns 2 or 3 for failed integration testing.
Title: Message Title Mark McNeely commented on JENKINS-24386 Re: Unity Test Tools package returns 2 or 3 for failed integration testing. Looks good to me. I used the "unity test tools" tests to try it out. With an exit code of 2, I tried the following values for the unstable codes field. nothing - fail 2,3 - unstable 02,03 - unstable 4, - fail 2, - unstable It looks like it is working as you'd expect. 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] [durable-task-plugin] (JENKINS-25727) Occasional exit status -1 with long latencies
Title: Message Title A C reopened an issue Reopening. A similar hang is occasionally occurring again with Jenkins 1.6.13 - 1.6.15 and Workflow 1.6 during bat steps in Windows. The process that workflow is waiting for has successfully ended according to log output, there are no rogue generated batch files and directories left either, so it still seems like a race condition exists. Why is this concatenating to a jenkins-results.txt file anyway, that doesn't seem very robust? Can't we just re-pipe standard out and standard error directly? Jenkins / JENKINS-25727 Occasional exit status -1 with long latencies Change By: A C Resolution: Fixed Status: Resolved 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
[JIRA] [logstash-plugin] (JENKINS-28040) Allow logstash plugin to feed a syslog server
Title: Message Title Rusty Gerard commented on JENKINS-28040 Re: Allow logstash plugin to feed a syslog server Someone submitted a pull request for this feature: https://github.com/jenkinsci/logstash-plugin/pull/10 I'm all for merging it in to close this issue, but is this good long-term, Cyrille Le Clerc? (i.e. will this just be redundant when a future version of syslog-logger comes out?) 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-28648) allow lambda s3 artifact location
Title: Message Title SCM/JIRA link daemon commented on JENKINS-28648 Re: allow lambda s3 artifact location Code changed in jenkins User: cast Path: pom.xml src/main/java/com/xti/jenkins/plugin/awslambda/exception/AWSLambdaPluginException.java src/main/java/com/xti/jenkins/plugin/awslambda/exception/LambdaDeployException.java src/main/java/com/xti/jenkins/plugin/awslambda/service/LambdaDeployService.java src/main/java/com/xti/jenkins/plugin/awslambda/service/WorkSpaceZipper.java src/main/java/com/xti/jenkins/plugin/awslambda/upload/LambdaUploader.java src/main/java/com/xti/jenkins/plugin/awslambda/util/LambdaClientConfig.java src/test/java/com/xti/jenkins/plugin/awslambda/service/LambdaDeployServiceTest.java src/test/java/com/xti/jenkins/plugin/awslambda/service/WorkSpaceZipperTest.java src/test/java/com/xti/jenkins/plugin/awslambda/upload/LambdaUploaderTest.java http://jenkins-ci.org/commit/aws-lambda-plugin/978953de47e8c8cb8a731d478c0582810e8f5d04 Log: JENKINS-28648 Implemented S3 artifact locations 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] [workflow-plugin] (JENKINS-28649) ExportedBean error with Workflow and AfterRestartTask
Title: Message Title
Steven Christou updated an issue
Jenkins / JENKINS-28649
ExportedBean error with Workflow and AfterRestartTask
Change By:
Steven Christou
Invoking an AfterRestartTask though the api throws the below exception: {noformat}WARNING: Error while serving http://localhost:8081/job/workflow-demo/api/jsonjava.lang.reflect.InvocationTargetExceptionat sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)at java.lang.reflect.Method.invoke(Method.java:483)at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:298)at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:161)at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:96)at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:121)at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:745)at org.kohsuke.stapler.Stapler.invoke(Stapler.java:875)at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:211)at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:745)at org.kohsuke.stapler.Stapler.invoke(Stapler.java:875)at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249)at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)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: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:96)at com.cloudbees.jenkins.support.slowrequest.SlowRequestFilter.doFilter(SlowRequestFilter.java:37)at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99)at com.cloudbees.opscenter.client.plugin.OfflineSecurityRealmFilter._doFilter(OfflineSecurityRealmFilter.java:90)at com.cloudbees.opscenter.client.plugin.OfflineSecurityRealmFilter.doFilter(OfflineSecurityRealmFilter.java:67)at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99)at com.cloudbees.opscenter.security.ClusterSessionFilter._doFilter(ClusterSessionFilter.java:69)at com.cloudbees.opscenter.security.ClusterSessionFilter.doFilter(ClusterSessionFilter.java:44)at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99)at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51)at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99)at org.jenkinsci.plugins.suppress_stack_trace.SuppressionFilter.doFilter(SuppressionFilter.java:34)at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99)at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:198)at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:176)at net.bull.javamelody.PluginMonitori
[JIRA] [workflow-plugin] (JENKINS-28649) ExportedBean error with Workflow and AfterRestartTask
Title: Message Title Steven Christou created an issue Jenkins / JENKINS-28649 ExportedBean error with Workflow and AfterRestartTask Issue Type: Bug Assignee: Steven Christou Components: workflow-plugin Created: 29/May/15 10:57 PM Priority: Minor Reporter: Steven Christou WARNING: Error while serving http://localhost:8081/job/workflow-demo/api/json java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:483) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:298) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:161) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:96) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:121) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:745) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:875) at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:211) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:745) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:875) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:745) at org
[JIRA] [aws-lambda-plugin] (JENKINS-28648) allow lambda s3 artifact location
Title: Message Title Michael Willemse started work on JENKINS-28648 Change By: Michael Willemse Status: Open In Progress 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-28648) allow lambda s3 artifact location
Title: Message Title Michael Willemse created an issue Jenkins / JENKINS-28648 allow lambda s3 artifact location Issue Type: New Feature Assignee: Michael Willemse Components: aws-lambda-plugin Created: 29/May/15 10:37 PM Priority: Minor Reporter: Michael Willemse allow urls of the following scheme for S3 artifact locations: s3://bucket/key or with version: s3://bucket/ket?versionId=abcdef/123 Add Comment
[JIRA] [aws-lambda-plugin] (JENKINS-28630) Allow use of Jenkins Env Vars for invocation payload and json parameters
Title: Message Title Michael Willemse resolved as Fixed Jenkins / JENKINS-28630 Allow use of Jenkins Env Vars for invocation payload and json parameters Change By: Michael Willemse Status: In Progress 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] [email-ext-plugin] (JENKINS-28645) Tokens in subject fail to get expanded when 'Error: No workspace found' encountered
Title: Message Title
Alex Earl edited a comment on JENKINS-28645
Re: Tokens in subject fail to get expanded when 'Error: No workspace found' encountered
Can you try replacing {noformat} ${DEFAULT_SUBJECT} with $DEFAULT_SUBJECT ? {noformat}
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] [email-ext-plugin] (JENKINS-28645) Tokens in subject fail to get expanded when 'Error: No workspace found' encountered
Title: Message Title
Alex Earl commented on JENKINS-28645
Re: Tokens in subject fail to get expanded when 'Error: No workspace found' encountered
Can you try replacing $ {DEFAULT_SUBJECT}
with $DEFAULT_SUBJECT?
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] [docker-build-step-plugin] (JENKINS-28646) Add support for removing volumes while removing a container
Title: Message Title Niek Palm assigned an issue to Unassigned Jenkins / JENKINS-28646 Add support for removing volumes while removing a container Change By: Niek Palm Assignee: Niek Palm 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] [email-ext-plugin] (JENKINS-28645) Tokens in subject fail to get expanded when 'Error: No workspace found' encountered
Title: Message Title Alex Earl commented on JENKINS-28645 Re: Tokens in subject fail to get expanded when 'Error: No workspace found' encountered The interesting thing is that the error in the log is actually occurring in the code AFTER the subject has already been set. What type of job is this? FreeStyle? Also, I don't know if it would affect anything (it shouldn't) but why do you have the Mailer plugin enabled for the job as well? 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] [email-ext-plugin] (JENKINS-28645) Tokens in subject fail to get expanded when 'Error: No workspace found' encountered
Title: Message Title Alex Earl edited a comment on JENKINS-28645 Re: Tokens in subject fail to get expanded when 'Error: No workspace found' encountered The interesting thing is that the error in the log is actually occurring in the code AFTER the subject has already been set. What type of job is this? FreeStyle? Also, I don't know if it would affect anything (it shouldn't) but why do you have the Mailer plugin enabled for the job as well? Can you also list plugins you have installed (and enabled) and versions? 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] [email-ext-plugin] (JENKINS-28645) Tokens in subject fail to get expanded when 'Error: No workspace found' encountered
Title: Message Title Mark Manning commented on JENKINS-28645 Re: Tokens in subject fail to get expanded when 'Error: No workspace found' encountered Yes, everytime. 100% repeatable. 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] [perforce-plugin] (JENKINS-28647) Token in 'View Map from File' fails to be expanded when polling for SCM changes
Title: Message Title Rob Petti commented on JENKINS-28647 Re: Token in 'View Map from File' fails to be expanded when polling for SCM changes Envinject is a build wrapper with a plethora or compatibility issues. You can't use properties defined by it outside of a build context. This includes SCM polling. Use a built-in env variable, or a job 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] [perforce-plugin] (JENKINS-28647) Token in 'View Map from File' fails to be expanded when polling for SCM changes
Title: Message Title Rob Petti assigned an issue to Unassigned Jenkins / JENKINS-28647 Token in 'View Map from File' fails to be expanded when polling for SCM changes Change By: Rob Petti Assignee: Rob Petti 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] [starteam-plugin] (JENKINS-8739) Starteam plugin seems to use the last directory set in the starteam client for checkout
Title: Message Title David Halonen commented on JENKINS-8739 Re: Starteam plugin seems to use the last directory set in the starteam client for checkout Found the cause: when the working directory of the StarTeam view is changed to the alternate directory, the plug-in inserts the alternate directory into the path after the working directory name. Hence, the c:\jenkins\workspacec:\alternate directory... as noted above. Remedy: reset the view's working directory with the same account as used by Jenkins. The change is simple: click the working directory button. This allows the plug-in to work, regardless of that directory setting. 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] [perforce-plugin] (JENKINS-28647) Token in 'View Map from File' fails to be expanded when polling for SCM changes
Title: Message Title Mark Manning created an issue Jenkins / JENKINS-28647 Token in 'View Map from File' fails to be expanded when polling for SCM changes Issue Type: Bug Assignee: Rob Petti Attachments: p4_config.xml, scmPollLog.txt Components: perforce-plugin Created: 29/May/15 8:49 PM Environment: Jenkins LTS 1.596.3 perforce-plugin 1.3.34 Priority: Major Reporter: Mark Manning Token used for the value 'View Map from File' fails to be expanded when polling for SCM changes. Job config.xml and scmPollLog attached.
[JIRA] [docker-build-step-plugin] (JENKINS-28646) Add support for removing volumes while removing a container
Title: Message Title Niek Palm created an issue Jenkins / JENKINS-28646 Add support for removing volumes while removing a container Issue Type: Bug Assignee: Niek Palm Components: docker-build-step-plugin Created: 29/May/15 8:49 PM Priority: Minor Reporter: Niek Palm Add support for the -v option of the docker rm command. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [email-ext-plugin] (JENKINS-28645) Tokens in subject fail to get expanded when 'Error: No workspace found' encountered
Title: Message Title Alex Earl commented on JENKINS-28645 Re: Tokens in subject fail to get expanded when 'Error: No workspace found' encountered Does this happen every 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] [email-ext-plugin] (JENKINS-28645) Tokens in subject fail to get expanded when 'Error: No workspace found' encountered
Title: Message Title Mark Manning created an issue Jenkins / JENKINS-28645 Tokens in subject fail to get expanded when 'Error: No workspace found' encountered Issue Type: Bug Assignee: Alex Earl Attachments: config.xml, log-EmailExtDebugEnabled.txt Components: email-ext-plugin Created: 29/May/15 8:27 PM Environment: Jenkins LTS 1.596.3 email-ext-plugin 2.40.2 Priority: Major Reporter: Mark Manning Tokens in subject fail to get expanded when 'Error: No workspace found' encountered. However, the same tokens in the content/body of the email are expanded properly. Attachments: job config.xml, consolelog with debug for email-ext-plugin enabled
[JIRA] [starteam-plugin] (JENKINS-8739) Starteam plugin seems to use the last directory set in the starteam client for checkout
Title: Message Title David Halonen commented on JENKINS-8739 Re: Starteam plugin seems to use the last directory set in the starteam client for checkout Hi, any resolution on this? 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-9104) Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed
Title: Message Title Kevin Phillips commented on JENKINS-9104 Re: Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed Update While reporting the issue in my last comment I had the idea for a slight variation of the configuration described there which does appear to work in both use cases. The main modification that I made was to separate the build operation into two separate build operations: the first is a simple Windows command line call which overrides BUILD_ID and then launches mspdbsrv.exe. Once this first operation completes, Jenkins terminates the shell session that is linked to the pdbsrv process thus decoupling it from the agent. Combined with the overloaded BUILD_ID env var, Jenkins can no longer track the process. the second operation is just another instance of a Windows shell session that then calls into msbuild to proceed with the build. Theoretically even this solution "could" fall prey to the same problem I described in my previous comment, however the execution time of this initial build step is negligible and is highly unlikely to be exploited in practice (ie: a user would need to hit the kill button on the build at just that small fraction of a second it takes Jenkins to launch mspdbsrv.exe). I'm not sure how easy this hack will be for us to roll out into production at the scale we need, but just in case others find this tidbit of information helpful I thought I'd provide it here. 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 r
[JIRA] [core] (JENKINS-9104) Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed
Title: Message Title Kevin Phillips commented on JENKINS-9104 Re: Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed Update As a quick sanity check I decided to throw together a quick ad-hoc test configuration where by I overload the BUILD_ID in the environment for one of my compilation jobs just to see if one of the hacks proposed earlier will potentially work. Unfortunately it looks like this is not a robust solution either. I have confirmed in the trivial case that the solution does work, as in: Setup a job with a single shell operation as a build step, configured as follows: override the BUILD_ID env var with some arbitrary value call into MSBuild to perform the compilation run a build of the given job upon completion, confirm that the mspdbsrv.exe process is still running - TEST SUCCESSFUL However, unfortunately I've found another case where this solution doesn't work. Apparently if you manually kill the build while it is running Jenkins still somehow manages to locate the orphaned pdbsrv process and kill it, despite the changes described above. So, to put it more clearly: Setup a job with a single shell operation as a build step, configured as follows: override the BUILD_ID env var with some arbitrary value call into MSBuild to perform the compilation run a build of the given job while the compilation operation is running, and you have confirmed the mspdbsrv.exe process has been launched, manually force the running build to terminate (ie: by clicking on the X icon next to the running build on the Jenkins dashboard) FAILURE - Jenkins still terminates the pdbsrv process
[JIRA] [core] (JENKINS-9104) Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed
Title: Message Title Kevin Phillips commented on JENKINS-9104 Re: Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed Update So, it turns out setting up some kind of background process to spawn a copy of the pdbsrv process isn't going to work as expected. From what I can tell Windows seems to be able to tell when a process has been launched from a system service and it will prevent those sub-processes from using other processes that are spawned elsewhere. The particulars of my test case are as follows: Setup a small Python script that launches a copy of mspdbsrv.exe when called Setup a scheduled task in Windows to run the python script on boot Reboot the agent - confirm the mspdbsrv.exe process is running trigger a compilation operation via the Jenkins dashboard A new, secondary copy of mspdbsrv.exe is spawned to serve the Jenkins agent. This sub-process is then terminated as per usual once the Jenkins build is complete. I have confirmed that both the service that runs the Jenkins agent and the scheduled task use the same user profile and credentials and that both environments are using the same version of mspdbsrv.exe with the same set of command line parameters (ie: -start -spawn). Looks like I have to head back to the drawing board. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [git-plugin] (JENKINS-28644) Trigger job when polling off if sha1 specified in push notification
Title: Message Title Mark Waite commented on JENKINS-28644 Re: Trigger job when polling off if sha1 specified in push notification You might attempt the same configuration with git plugin 2.3.4 rather than 2.3.5. There may have been regressions in the polling behavior in 2.3.5 which affected your use case. 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] [hp-application-automation-tools-plugin] (JENKINS-25477) Unable to connect to ALM 12.01
Title: Message Title Winston Polhamus commented on JENKINS-25477 Re: Unable to connect to ALM 12.01 You can close 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] [git-plugin] (JENKINS-28644) Trigger job when polling off if sha1 specified in push notification
Title: Message Title Leif Gruenwoldt commented on JENKINS-28644 Re: Trigger job when polling off if sha1 specified in push notification I seem to be asking for the opposite of JENKINS-26540 I think. Which makes me wonder why this isn't working for me. I'm using v2.3.5. 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-28644) Trigger job when polling off if sha1 specified in push notification
Title: Message Title Leif Gruenwoldt created an issue Jenkins / JENKINS-28644 Trigger job when polling off if sha1 specified in push notification Issue Type: Improvement Assignee: Nicolas De Loof Components: git-plugin Created: 29/May/15 6:07 PM Priority: Minor Reporter: Leif Gruenwoldt The documentation suggests that polling is not required when the "sha1" commitID param is given, so should it not be possible to trigger a build this way with polling turned off for the job? From testing it appears polling is still required in this case too. "Commit ID is optional. If set, it will immediately trigger a build, without requirement to poll for changes." I have > 100 Jenkins jobs I'd like to migrate to this style post-receive job trigger however having to modify the job configuration in this way for eachone sounds like a very long afternoon. Add Comment
[JIRA] [unity3d-plugin] (JENKINS-24386) Unity Test Tools package returns 2 or 3 for failed integration testing.
Title: Message Title lacostej commented on JENKINS-24386 Re: Unity Test Tools package returns 2 or 3 for failed integration testing. Hei Mark, thanks for the help! I've added integration tests so it should go reasonably well, but some user feedback from those who requested the feature might help! v1.0 was released with the feature. The plugins update site hasn't picked it up yet I think, but you can fetch it from here: http://updates.jenkins-ci.org/download/plugins/unity3d-plugin/ 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-client-plugin] (JENKINS-26757) "Error cloning remote repo 'origin'" with username:passw...@bitbucket.org URLs
Title: Message Title Mark Waite commented on JENKINS-26757 Re: "Error cloning remote repo 'origin'" with username:passw...@bitbucket.org URLs Daren Smith as far as I can tell from my experiments and the description from Flavio Donzé and the duplicate bug JENKINS-24368, no amount of retries will allow an https based URL with embedded username and password to work with a private bitbucket (or Stash) repository. While your failure may have similar symptoms (failure cloning the repo), I believe it is a different bug, or it is a configuration 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] [hp-application-automation-tools-plugin] (JENKINS-25477) Unable to connect to ALM 12.01
Title: Message Title Winston Polhamus commented on JENKINS-25477 Re: Unable to connect to ALM 12.01 We are now integrating via the Perf. Center API, so this is no longer an issue for us. 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] [hp-application-automation-tools-plugin] (JENKINS-25477) Unable to connect to ALM 12.01
Title: Message Title Winston Polhamus updated an issue Jenkins / JENKINS-25477 Unable to connect to ALM 12.01 Change By: Winston Polhamus Priority: Major Trivial 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-client-plugin] (JENKINS-26757) "Error cloning remote repo 'origin'" with username:passw...@bitbucket.org URLs
Title: Message Title Daren Smith commented on JENKINS-26757 Re: "Error cloning remote repo 'origin'" with username:passw...@bitbucket.org URLs Seeing a similar issue sporadically using GIT plugin 2.3.5, GIT client plugin 1.17.1, and Jenkins 1.607 with Stash. Re-queuing the build has resolved the issue each time, but we were not seeing it when running 1.574 and earlier plugins prior to upgrading. I will review the logs and add any detail that I can find associated with the 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-28110) 1.610 “Failed to instantiate” error
Title: Message Title Irina Vinokurova commented on JENKINS-28110 Re: 1.610 “Failed to instantiate” error Thank's a lot! 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-28110) 1.610 “Failed to instantiate” error
Title: Message Title Johannes Schüth commented on JENKINS-28110 Re: 1.610 “Failed to instantiate” error @kefirkin Yes, 1.611 was also affected. Please update to a newer version. Afaik the earliest version that contains the fix is 1.612 https://github.com/jenkinsci/jenkins/commit/1f41bec8ef656da014b7145fdff82563c030ca29 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-28110) 1.610 “Failed to instantiate” error
Title: Message Title
Irina Vinokurova reopened an issue
Sorry but i have the same problem in Jenkins v. 1.611
Stacktrace:
javax.servlet.ServletException: java.lang.RuntimeException: Failed to instantiate class hudson.plugins.performance.PerformancePublisher from {"parsers":{"glob":"result.xml","kind":"hudson.plugins.performance.JMeterParser$DescriptorImpl"},"modeOfThreshold":"false","errorUnstableThreshold":"0","errorFailedThreshold":"0","errorUnstableResponseTimeThreshold":"","relativeUnstableThresholdNegative":"0.0","relativeUnstableThresholdPositive":"0.0","relativeFailedThresholdNegative":"0.0","relativeFailedThresholdPositive":"0.0","compareBuildPrevious":"true","nthBuildNumber":"0","comparisonType":"ART","modePerformancePerTestCase":true,"modeThroughput":true,"stapler-class":"hudson.plugins.performance.PerformancePublisher","$class":"hudson.plugins.performance.PerformancePublisher"}
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876)
at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249)
at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876)
at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249)
at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
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.java:48)
at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482)
at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84)
at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51)
at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117)
at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125)
at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142)
at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271)
at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at jenkins.security.BasicHeaderProcessor.doFilter(BasicHeaderProcessor.java:93)
at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249)
at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67)
at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76)
at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:171)
at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482)
at org.kohsuke.stapler.
[JIRA] [core] (JENKINS-28633) Plugin update does not work any more
Title: Message Title Grigoriy Milman updated an issue Jenkins / JENKINS-28633 Plugin update does not work any more Change By: Grigoriy Milman Labels: core 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-28633) Plugin update does not work any more
Title: Message Title Grigoriy Milman updated an issue Jenkins / JENKINS-28633 Plugin update does not work any more Change By: Grigoriy Milman Labels: core plugins update 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-28633) Plugin update does not work any more
Title: Message Title Grigoriy Milman updated an issue Jenkins / JENKINS-28633 Plugin update does not work any more Change By: Grigoriy Milman Just switched from Jenkins 1.611 to 1.614. Jenkins 1.615 has the same issueJenkins Plugin Manager, in "Updates" tab I have selected all 3 plugins to update and started the update by clickning clicking "Download now and install after restart" (see picture !Plugin1.png|thumbnail!), but update did not performed!I came back to the Plugin Manager. Selected the same plugins and started the update (see picture !Plugin2.png|thumbnail!). The same plugins appeared with status pending twice and still now any activity! 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-24386) Unity Test Tools package returns 2 or 3 for failed integration testing.
Title: Message Title Mark McNeely commented on JENKINS-24386 Re: Unity Test Tools package returns 2 or 3 for failed integration testing. Hey Lacostej, I can help you test it if you still need it. For some reason the site was inaccessible yesterday so I couldn't respond. 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] [s3-plugin] (JENKINS-26297) S3 download link incorrect when Destination bucket includes a path prefix
Title: Message Title SCM/JIRA link daemon commented on JENKINS-26297 Re: S3 download link incorrect when Destination bucket includes a path prefix Code changed in jenkins User: Nicolas De loof Path: src/main/java/hudson/plugins/s3/S3Profile.java src/main/java/hudson/plugins/s3/callable/S3UploadCallable.java http://jenkins-ci.org/commit/s3-plugin/ab3afa1be121fd90693b23f353e915ec552da98c Log: Merge pull request #58 from ndeloof/JENKINS-26297 use the user bucketname entry that includes prefixes in fingerprint Compare: https://github.com/jenkinsci/s3-plugin/compare/c6308fef7279...ab3afa1be121 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] [docker-traceability-plugin] (JENKINS-28643) timestamps in the UI are not correct
Title: Message Title James Nord created an issue Jenkins / JENKINS-28643 timestamps in the UI are not correct Issue Type: Bug Assignee: Oleg Nenashev Attachments: dt_screenshot.png Components: docker-traceability-plugin Created: 29/May/15 4:41 PM Priority: Minor Reporter: James Nord see screenshot from submission of events via Docker events hook. Add Comment
[JIRA] [core] (JENKINS-9104) Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed
Title: Message Title Gavin Swanson commented on JENKINS-9104 Re: Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed Stopping after a timeout period after all active requests and continuing to run when it gets a new request are the way mspdbsrv runs normally when something doesn't go around killing it (ala Jenkins). I believe the correct solution is a whitelist. 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-9104) Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed
Title: Message Title Lars Rosenboom commented on JENKINS-9104 Re: Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed Maybe there is a way to shut down the mspdbsrv.exe softly, so it stops only after all active request (by msbuild.exe or devenv.exe in parallel builds) are done. Then it should simply restart on the next request. Another solution would be to allow the user to give a list of process names not to kill (or maybe hardcode not to kill mspdbsrv.exe). 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-9104) Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed
Title: Message Title Lars Rosenboom edited a comment on JENKINS-9104 Re: Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed Maybe there is a way to shut down the mspdbsrv.exe softly, so it stops only after all active request (by msbuild.exe or devenv.exe in parallel builds) are done. Then it should simply restart on the next request.Another solution would be to allow the user to give a list of process names not to kill (or maybe hardcode not to kill mspdbsrv.exe). 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] [logstash-plugin] (JENKINS-28546) logstash doesn't connect to a server and puts no messages out
Title: Message Title Rinaldo DiGiorgio commented on JENKINS-28546 Re: logstash doesn't connect to a server and puts no messages out Can I get any details on what the expectations are for using the plugin. The directions imply it just works. I have a new elasticsearch instance and I try to connect and nothing happens. I have downloaded the source and will start to look at it. Does the index need to exist? Many river plugins in elasticsearch just create the index does this plugin do that? I am leaving the username and the password blank will this cause the failure. 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] [hp-application-automation-tools-plugin] (JENKINS-28609) Could not create scheduler, please verify ALM client installation
Title: Message Title Tyler Hoffman closed an issue as Fixed Issue seems to have been related to HP Client Registration add-in not being properly installed Jenkins / JENKINS-28609 Could not create scheduler, please verify ALM client installation Change By: Tyler Hoffman Status: Open Closed 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] [buildresult-trigger-plugin] (JENKINS-25753) BuildResultTrigger doesn't trigger build
Title: Message Title Alexandru Gheorghe updated an issue Jenkins / JENKINS-25753 BuildResultTrigger doesn't trigger build Change By: Alexandru Gheorghe Component/s: buildresulttrigger 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] [buildresult-trigger-plugin] (JENKINS-25753) BuildResultTrigger doesn't trigger build
Title: Message Title Alexandru Gheorghe commented on JENKINS-25753 Re: BuildResultTrigger doesn't trigger build Same with H 17 * * 5, the upstream job (makes the upstream/downstream automatically when i try to monitor a job) has its state as SUCCESS however after poll it says "No changes" and just stays like that. It should trigger upon "SUCCESS" and my option to "Combine all job info" is disabled. 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] [cloudfoundry-plugin] (JENKINS-28311) Create CloudFoundry services via Plug-in
Title: Message Title
Andreas Buchen commented on JENKINS-28311
Re: Create CloudFoundry services via Plug-in
"Create services if they don't exist" under that, so it's available for either services in manifest files or services in the Jenkins config.
Not sure if this sufficient. At least to my knowledge, the manifest only contains the service instance name. But you would need service name ("postgress") and plan ("free") to actually be able to create it. I guess those additional parameters one would have to provide to the Jenkins plug-in?!?
One cloud also also think along the lines of having another "post build action" besides "deploy to CF". For example, create (and drop and create) service instance.
Thanks for the great work. The plug-in is being used daily
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] [cloudfoundry-plugin] (JENKINS-28602) Error: Default domain calculated from "api" domain
Title: Message Title Andreas Buchen commented on JENKINS-28602 Re: Error: Default domain calculated from "api" domain > a little refactoring [...] so I'll work on that Cool. I quickly glanced at the code, but I believe you are much better placed to refactor it as you see fit 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] [p4-plugin] (JENKINS-25468) Add a "Verbosity" option to allow detailed p4 info
Title: Message Title Paul Allen closed an issue as Fixed Added even more logging in release 1.2.3. Jenkins / JENKINS-25468 Add a "Verbosity" option to allow detailed p4 info Change By: Paul Allen Status: Open Closed 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] [p4-plugin] (JENKINS-26486) Workspace fails to update when Replace missing/modified files is checked
Title: Message Title Paul Allen commented on JENKINS-26486 Re: Workspace fails to update when Replace missing/modified files is checked The latest release uses the 2014.1 p4 clean feature (reconcile -w). It might resolve this for users on 2014.1 or above, but I will leave this issue open as it still needs fixing for older versions. 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-9104) Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed
Title: Message Title Alexey Larsky updated an issue Jenkins / JENKINS-9104 Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed Change By: Alexey Larsky Environment: Windows XP, Windows 7 using MSBuild or devenv.exe to build MS Visual Studio Projects 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] [p4-plugin] (JENKINS-28448) "Publish Assets delete files when no shelve is used for review
Title: Message Title Paul Allen commented on JENKINS-28448 Re: "Publish Assets delete files when no shelve is used for review If the files are in the 'have' list metadata for the workspace being used to do the Publish, but not physically present, then the reconcile command will mark the files for delete. I guess this could happen if: the Workspace root was incorrectly set, a cleanup had removed all the workspace's files, or the Publish step happened on a different slave to the build. To prevent these kind of accidents, perhaps I should disable 'delete' actions in Publish. I think 99% of most uses-cases are add or edit operations. 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-9104) Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed
Title: Message Title Kevin Phillips commented on JENKINS-9104 Re: Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed PS: Sorry for the rant. My team and I have been aggravated for some time now, hoping this bug would be fixed so we can move off the old version of Jenkins we're currently stuck on and thus able to pick up some new bug fixes both in the core as well as in numerous plugins which only support newer versions. Hopefully I don't come across as overly adversarial. 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-9104) Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed
Title: Message Title Kevin Phillips commented on JENKINS-9104 Re: Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed @steve carter First, let me thank you for summarizing the earlier comment threads. That does help bring everything into focus. 4) Jenkins, in order to catch rogue processes at job end (i.e. those that have broken ties with their parent process) scans the whole process space for those with the particular BUILD_ID in their environment, and kills them. This is correct and good behavior by Jenkins. Agreed. This is a perfectly valid and useful enhancement for the majority of cases. However, given the debilitating effect it has on this specific use case combined with the fact that the change was included on an LTS release which is expected to be kept as stable as possible is where I take issue. I see this problem as a bug, albeit a difficult to detect bug and admittedly a bug that is really caused by some questionable behavior provided by the Microsoft build tools, but a bug none the less. In that case critical, production halt kind of bugs like this should be fixed immediately or reverted until an appropriate fix can be made. Doing otherwise reduces users' confidence in the stability of the tool. There is a reason shops like ours choose to use LTS editions for production work - to avoid problems like this that may be found on the latest, cutting edge versions. 8) Solution 1: start pdbsrv with a BUILD_ID that doesn't match the build jobs. Then pdbsrv will not be killed at the end of the job. This should be called a workaround or hack rather than a solution. That point aside, this workaround again won't work for our particular build environment. We use the BUILD_ID throughout our build processes to embed metadata in the binary files we generate. If we reset that environment variable as part of our build this metadata will essentially get corrupted. Changing our tooling to use an alternative environment variable would require significant effort as well, having to be propagated out to dozens of products across several release branches each. 9) Solution 2: use Daniel's whitelist feature to not kill pdbsrv at the end of the job. Based on my review of his pull request, Daniel's feature has not yet been completed nor has it been included in any actual LTS release. I do believe this would be a reasonable and appropriate solution to this defect though, so hopefully this work can be completed sooner rather than later. 10) The problem with Solutions 1 and 2 are this: pdbsrv still has a timeout, so you will get sporadic failures when the server goes away. I know some earlier posters did indicate that this was an issue for them I have not been able to reproduce the problem as described. When a compile begins and this process is running it makes use of the existing process, and if the process is not already running it starts it. I have never had a compile running and seen the mspdbsrv process terminate mid-compile without any other background process or system event occurring. Also, I work with many development teams including many dozens of developers
[JIRA] [p4-plugin] (JENKINS-28450) Publish Assets submit files even if build steps marked as failure
Title: Message Title Paul Allen commented on JENKINS-28450 Re: Publish Assets submit files even if build steps marked as failure On the PostBuild step for Tagging/Labeling I have a 'Only tag on build success' check box. Perhaps the same would work for Publish? 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] [p4-plugin] (JENKINS-28498) Null Pointer when publishing assets and server is down
Title: Message Title Paul Allen closed an issue as Fixed Resolved in 1.2.3 Jenkins / JENKINS-28498 Null Pointer when publishing assets and server is down Change By: Paul Allen Status: Open Closed 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] [maven-plugin] (JENKINS-19844) Maven agent socket bind too inflexible (allow Jenkins in virtualized environment)
Title: Message Title Lucien Weller edited a comment on JENKINS-19844 Re: Maven agent socket bind too inflexible (allow Jenkins in virtualized environment) Sorry reopened by mistake... But @Roberto Andrade: you're pull request seams not to be fully ok. Can you fix 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] [maven-plugin] (JENKINS-19844) Maven agent socket bind too inflexible (allow Jenkins in virtualized environment)
Title: Message Title Lucien Weller edited a comment on JENKINS-19844 Re: Maven agent socket bind too inflexible (allow Jenkins in virtualized environment) Sorry reopened by mistake... But @Roberto Andrade: you're pull request seams not to be fully ok. Can you fix 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] [maven-plugin] (JENKINS-19844) Maven agent socket bind too inflexible (allow Jenkins in virtualized environment)
Title: Message Title Lucien Weller resolved as Fixed Sorry reopened by mistake... Jenkins / JENKINS-19844 Maven agent socket bind too inflexible (allow Jenkins in virtualized environment) Change By: Lucien Weller Status: Reopened 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] [maven-plugin] (JENKINS-19844) Maven agent socket bind too inflexible (allow Jenkins in virtualized environment)
Title: Message Title Lucien Weller reopened an issue Jenkins / JENKINS-19844 Maven agent socket bind too inflexible (allow Jenkins in virtualized environment) Change By: Lucien Weller Resolution: Fixed Status: Resolved 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] [embeddable-build-status-plugin] (JENKINS-28642) Add Support to the New Workflow Plugin
Title: Message Title Flávio Augusto Valones created an issue Jenkins / JENKINS-28642 Add Support to the New Workflow Plugin Issue Type: Improvement Assignee: Kohsuke Kawaguchi Components: embeddable-build-status-plugin Created: 29/May/15 2:21 PM Environment: Jenkins 1.609 workflow-plugin 1.6 embeddable-build-status-plugin 1.7 Labels: workflow Priority: Major Reporter: Flávio Augusto Valones The new Job type added by the workflow-plugin cannot be casted to AbstractProject: java.lang.ClassCastException: org.jenkinsci.plugins.workflow.job.WorkflowJob cannot be cast to hudson.model.AbstractProject at org.jenkinsci.plugins.badge.RunBadgeAction.(RunBadgeAction.java:18) at org.jenkinsci.plugins.badge.RunBadgeActionFactory.createFor(RunBadgeActionFactory.java:21) at hudson.model.Run.getTransientActions(Run.java:376)
[JIRA] [unity3d-plugin] (JENKINS-24386) Unity Test Tools package returns 2 or 3 for failed integration testing.
Title: Message Title lacostej commented on JENKINS-24386 Re: Unity Test Tools package returns 2 or 3 for failed integration testing. Released as part of v1.0. 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] [workflow-plugin] (JENKINS-25975) More reliable test infrastructure
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-25975 More reliable test infrastructure Change By: SCM/JIRA link daemon Status: In Progress 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] [workflow-plugin] (JENKINS-25975) More reliable test infrastructure
Title: Message Title SCM/JIRA link daemon commented on JENKINS-25975 Re: More reliable test infrastructure Code changed in jenkins User: Jesse Glick Path: aggregator/src/test/java/org/jenkinsci/plugins/workflow/SingleJobTestBase.java aggregator/src/test/java/org/jenkinsci/plugins/workflow/WorkflowRunTest.java aggregator/src/test/java/org/jenkinsci/plugins/workflow/WorkflowTest.java support/src/test/java/org/jenkinsci/plugins/workflow/test/steps/WatchYourStep.java http://jenkins-ci.org/commit/workflow-plugin/d3ba64ddd6eaaacad401624d5b17809ebbec9b30 Log: [FIXED JENKINS-25975] Finally able to delete WatchYourStep; using SemaphoreStep instead. 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] [workflow-plugin] (JENKINS-25975) More reliable test infrastructure
Title: Message Title SCM/JIRA link daemon commented on JENKINS-25975 Re: More reliable test infrastructure Code changed in jenkins User: Jesse Glick Path: aggregator/src/test/java/org/jenkinsci/plugins/workflow/WorkflowTest.java durable-task-step/src/main/java/org/jenkinsci/plugins/workflow/steps/durable_task/DurableTaskStep.java http://jenkins-ci.org/commit/workflow-plugin/27e5b23046ae4e913edff0fa05256fdfafff0029 Log: JENKINS-25975 Seem to have fixed a race condition whereby quick `sh` steps would sometimes not print all of their output. 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] [mesos-plugin] (JENKINS-28641) Allow for configuration of a custom command shell when using docker
Title: Message Title nickithewatt updated an issue Jenkins / JENKINS-28641 Allow for configuration of a custom command shell when using docker Change By: nickithewatt By default, when using the docker configuration option, the approach used by mesos to run a docker based jenkins slave is by passing the jenkins slave commands as arguments to the standard shell e.g. ``` /bin/sh -c java -jar ... ```. There may be cases (for example when wanting to run a docker-in-docker akadind image) where a custom shell command is desired instead so that more than just the jenkins slave command can be executed. I.e. start docker then run the jenkins slave command.This has been highlighted in a google group chat as well. See https://groups.google.com/forum/#!topic/jenkins-mesos/JgFCmqOO7FgIt would be nice to be able to override this behaviour to make it possible. 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] [mesos-plugin] (JENKINS-28641) Allow for configuration of a custom command shell when using docker
Title: Message Title nickithewatt updated an issue Jenkins / JENKINS-28641 Allow for configuration of a custom command shell when using docker Change By: nickithewatt Labels: pull_request 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] [mesos-plugin] (JENKINS-28641) Allow for configuration of a custom command shell when using docker
Title: Message Title nickithewatt commented on JENKINS-28641 Re: Allow for configuration of a custom command shell when using docker Here is a PR which adds this functionality: https://github.com/jenkinsci/mesos-plugin/pull/112 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-9104) Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed
Title: Message Title Alexey Larsky updated an issue Jenkins / JENKINS-9104 Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed Change By: Alexey Larsky 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] [core] (JENKINS-9104) Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed
Title: Message Title Kevin Phillips commented on JENKINS-9104 Re: Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed Just a quick ping-back on this issue. Outstanding for like 4 years, no comments for months now, and all for a debilitating, crippling problem in the system! I did notice the pull request Daniel Webber created, which does seem to have some more recent activity on it but still no complete resolution to the issue even in the latest LTS release. Are there plans for finishing this work any time soon? We are still stuck on an LTS version from like a year or two ago because we can not accept this bug into our production environment. If there is any way to get this fix in sooner rather than later I know I'd appreciate it and I'm sure many others would as well. 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] [mailer-plugin] (JENKINS-27262) email is not sent
Title: Message Title Ferry Huberts commented on JENKINS-27262 Re: email is not sent See https://github.com/jenkinsci/mailer-plugin/pull/20 Please release the plugin right after pulling this in 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] [mesos-plugin] (JENKINS-28641) Allow for configuration of a custom command shell when using docker
Title: Message Title nickithewatt created an issue Jenkins / JENKINS-28641 Allow for configuration of a custom command shell when using docker Issue Type: Improvement Assignee: Vinod Kone Components: mesos-plugin Created: 29/May/15 1:16 PM Priority: Minor Reporter: nickithewatt By default, when using the docker configuration option, the approach used by mesos to run a docker based jenkins slave is by passing the jenkins slave commands as arguments to the standard shell e.g. ```/bin/sh -c java -jar ... ```. There may be cases (for example when wanting to run a docker-in-docker aka dind image) where a custom shell command is desired instead so that more than just the jenkins slave command can be executed. I.e. start docker then run the jenkins slave command. This has been highlighted in a google group chat as well. See https://groups.google.com/forum/#!topic/jenkins-mesos/JgFCmqOO7Fg It would be nice to be able to override this behaviour to make it possible. Add Comment
[JIRA] [ws-cleanup-plugin] (JENKINS-19717) Unable to remove Python virtual environment when specifying includes/excludes
Title: Message Title Oliver Gondža commented on JENKINS-19717 Re: Unable to remove Python virtual environment when specifying includes/excludes Can this be reproduced with recent plugin version? In this case the cause information is missing (null) because of a bug that is fixed already. 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] [ws-cleanup-plugin] (JENKINS-19274) Loading overlay remains on screen
Title: Message Title Oliver Gondža commented on JENKINS-19274 Re: Loading overlay remains on screen Can this be reproduced in modern Jenkins and latest plugin version? 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] [ws-cleanup-plugin] (JENKINS-25317) WS cleanup is not able to delete workspace containing non-ascii characters
Title: Message Title Oliver Gondža resolved as Cannot Reproduce No reply in 3 months, closing as it likely is a configuration error. Jenkins / JENKINS-25317 WS cleanup is not able to delete workspace containing non-ascii characters Change By: Oliver Gondža Status: Open Resolved Assignee: vjuranek Oliver Gondža 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.go
[JIRA] [ws-cleanup-plugin] (JENKINS-13553) Deleting project workspace Plugin: Jenkins hudson.Util.deleteFile Error
Title: Message Title Oliver Gondža updated an issue Jenkins / JENKINS-13553 Deleting project workspace Plugin: Jenkins hudson.Util.deleteFile Error Change By: Oliver Gondža Labels: Jenkins-Workspace-Cleanup-Plugin 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] [ws-cleanup-plugin] (JENKINS-27103) Include/Exclude options not shown in post-build selection list
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-27103 Include/Exclude options not shown in post-build selection list 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] [ws-cleanup-plugin] (JENKINS-27103) Include/Exclude options not shown in post-build selection list
Title: Message Title SCM/JIRA link daemon commented on JENKINS-27103 Re: Include/Exclude options not shown in post-build selection list Code changed in jenkins User: Oliver Gondža Path: src/main/resources/hudson/plugins/ws_cleanup/Pattern/config.jelly http://jenkins-ci.org/commit/ws-cleanup-plugin/ca3971eb6b69608f231811ee089f9f241b5a4387 Log: [FIXED JENKINS-27103] Require minimal width for pattern labels Compare: https://github.com/jenkinsci/ws-cleanup-plugin/compare/4856854cd748...ca3971eb6b69 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] [ws-cleanup-plugin] (JENKINS-27103) Include/Exclude options not shown in post-build selection list
Title: Message Title Oliver Gondža edited a comment on JENKINS-27103 Re: Include/Exclude options not shown in post-build selection list - I am able to reproduce that in Chromium, though not in firefox. [~ioannis], what was your browser? -The width was configured as 15% or the parent box. In different situations the label does not fix in whole, or as reported, no text was visible at all 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] [docker-workflow-plugin] (JENKINS-28607) Demo to get plugin from UC
Title: Message Title SCM/JIRA link daemon commented on JENKINS-28607 Re: Demo to get plugin from UC Code changed in jenkins User: Jesse Glick Path: .gitignore demo/Dockerfile_release demo/Dockerfile_snapshot demo/Makefile demo/docker-workflow-version.txt demo/get-snapshots.sh demo/plugins.txt demo/workflow-version.txt http://jenkins-ci.org/commit/docker-workflow-plugin/1beac603eea45e8f44479fe992b044ba862b277d Log: [FIXED JENKINS-28607] Getting released plugin versions from the update center. 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] [docker-workflow-plugin] (JENKINS-28607) Demo to get plugin from UC
Title: Message Title SCM/JIRA link daemon commented on JENKINS-28607 Re: Demo to get plugin from UC Code changed in jenkins User: Jesse Glick Path: .gitignore demo/Dockerfile_release demo/Dockerfile_snapshot demo/Makefile demo/docker-workflow-version.txt demo/get-snapshots.sh demo/plugins.txt demo/workflow-version.txt http://jenkins-ci.org/commit/docker-workflow-plugin/11529e37476f57505e74837a5c5f61529f2054e9 Log: Merge pull request #1 from jglick/Dockerfile_release- JENKINS-28607 JENKINS-28607 Getting released plugin versions from the update center Compare: https://github.com/jenkinsci/docker-workflow-plugin/compare/d11c0a76d528...11529e37476f 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] [docker-workflow-plugin] (JENKINS-28607) Demo to get plugin from UC
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-28607 Demo to get plugin from UC Change By: SCM/JIRA link daemon Status: In Progress 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] [script-security-plugin] (JENKINS-28586) Method access/properties inside Closure
Title: Message Title SCM/JIRA link daemon commented on JENKINS-28586 Re: Method access/properties inside Closure Code changed in jenkins User: Jesse Glick Path: http://jenkins-ci.org/commit/script-security-plugin/b924d4af32075a720fda5c94af56255e81cd1830 Log: Merge branch 'master' into JENKINS-28586 Compare: https://github.com/jenkinsci/script-security-plugin/compare/521a7af4dc91...b924d4af3207 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] [script-security-plugin] (JENKINS-25119) Sandbox cannot handle methods Groovy provides additionally
Title: Message Title SCM/JIRA link daemon commented on JENKINS-25119 Re: Sandbox cannot handle methods Groovy provides additionally Code changed in jenkins User: Jesse Glick Path: src/test/java/org/jenkinsci/plugins/scriptsecurity/sandbox/groovy/SandboxInterceptorTest.java http://jenkins-ci.org/commit/script-security-plugin/c6d43e762aa89ed0f13182059d219775708baa61 Log: Merge pull request #14 from jglick/ JENKINS-25119 -addendum JENKINS-25119 Cleaning up test from #7 Compare: https://github.com/jenkinsci/script-security-plugin/compare/6f16f00e0f19...c6d43e762aa8 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] [ws-cleanup-plugin] (JENKINS-27103) Include/Exclude options not shown in post-build selection list
Title: Message Title Oliver Gondža commented on JENKINS-27103 Re: Include/Exclude options not shown in post-build selection list I am able to reproduce that in Chromium, though not in firefox. Ioannis Moutsatsos, what was your browser? 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] [gerrit-trigger-plugin] (JENKINS-28593) Make gerrit comments configurable
Title: Message Title rsandell resolved as Won't Fix Works already Jenkins / JENKINS-28593 Make gerrit comments configurable Change By: rsandell Status: Open Resolved Resolution: Won't 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] [gerrit-trigger-plugin] (JENKINS-28593) Make gerrit comments configurable
Title: Message Title rsandell commented on JENKINS-28593 Re: Make gerrit comments configurable You can provide a comment file in the workspace with any content you want. As well as provide other comments via the config. 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] [ws-cleanup-plugin] (JENKINS-27103) Include/Exclude options not shown in post-build selection list
Title: Message Title Oliver Gondža commented on JENKINS-27103 Re: Include/Exclude options not shown in post-build selection list Broke somewhere between Jenkins 1.565 and 1.580. 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] [gerrit-trigger-plugin] (JENKINS-27741) Jenkins fails to report gerrit notifications spontaneously and on restart.
Title: Message Title rsandell commented on JENKINS-27741 Re: Jenkins fails to report gerrit notifications spontaneously and on restart. Will need fine level logs from com.sonymobile.tools.gerrit.gerritevents.workers.cmd and com.sonyericsson.hudson.plugins.gerrit.trigger.gerritnotifier 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] [gerrit-trigger-plugin] (JENKINS-28549) Random NPEs on jenkins start at GerritProjectList.addProject
Title: Message Title rsandell closed an issue as Won't Fix Code path removed in 2.14 in favour of other feature Jenkins / JENKINS-28549 Random NPEs on jenkins start at GerritProjectList.addProject Change By: rsandell Status: Open Closed Resolution: Won't 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] [ws-cleanup-plugin] (JENKINS-27103) Include/Exclude options not shown in post-build selection list
Title: Message Title Oliver Gondža assigned an issue to Oliver Gondža Jenkins / JENKINS-27103 Include/Exclude options not shown in post-build selection list Change By: Oliver Gondža Assignee: vjuranek 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 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] [mailer-plugin] (JENKINS-27262) email is not sent
Title: Message Title Alex Earl commented on JENKINS-27262 Re: email is not sent Which commit was identified? 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.
