[JIRA] [upstream-downstream-view-plugin] (JENKINS-25943) Incorrect links since 1.569
Oliver Gondža created JENKINS-25943 Incorrect links since 1.569 Issue Type: Bug Assignee: Oliver Gondža Components: upstream-downstream-view-plugin Created: 06/Dec/14 9:03 AM Description: Plugin generates incorrect link since Provide correct links for build history inside a folder. Project: Jenkins Priority: Major Reporter: Oliver Gondža This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [upstream-downstream-view-plugin] (JENKINS-25943) Incorrect links since 1.569
Oliver Gondža resolved JENKINS-25943 as Fixed Incorrect links since 1.569 Fixed in 1.005 Change By: Oliver Gondža (06/Dec/14 10:10 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [logstash-plugin] (JENKINS-25944) Version 1.0.2 fails with stacktrace
Richard Pijnenburg created JENKINS-25944 Version 1.0.2 fails with stacktrace Issue Type: Bug Assignee: Unassigned Components: logstash-plugin Created: 06/Dec/14 10:11 AM Description: Hi, Getting this stacktrace now with the recently added test results output. /code java.lang.NoSuchMethodError: hudson.model.AbstractBuild.getTestResultAction()Lhudson/tasks/test/AbstractTestResultAction; at jenkins.plugins.logstash.persistence.BuildData.(BuildData.java:120) at jenkins.plugins.logstash.LogstashNotifier.perform(LogstashNotifier.java:107) at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:45) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:770) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:734) at hudson.model.Build$BuildExecution.post2(Build.java:183) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:683) at hudson.model.Run.execute(Run.java:1784) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:89) at hudson.model.Executor.run(Executor.java:240) Project: Jenkins Priority: Critical Reporter: Richard Pijnenburg This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [logstash-plugin] (JENKINS-25944) Version 1.0.2 fails with stacktrace
Richard Pijnenburg
updated JENKINS-25944
Version 1.0.2 fails with stacktrace
Change By:
Richard Pijnenburg
(06/Dec/14 10:12 AM)
Description:
Hi,Getting this stacktrace now with the recently added test results output.
/
{
code
}
java.lang.NoSuchMethodError: hudson.model.AbstractBuild.getTestResultAction()Lhudson/tasks/test/AbstractTestResultAction; at jenkins.plugins.logstash.persistence.BuildData.(BuildData.java:120) at jenkins.plugins.logstash.LogstashNotifier.perform(LogstashNotifier.java:107) at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:45) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:770) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:734) at hudson.model.Build$BuildExecution.post2(Build.java:183) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:683) at hudson.model.Run.execute(Run.java:1784) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:89) at hudson.model.Executor.run(Executor.java:240)
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [logstash-plugin] (JENKINS-25944) Version 1.0.2 fails with stacktrace
Richard Pijnenburg
updated JENKINS-25944
Version 1.0.2 fails with stacktrace
Change By:
Richard Pijnenburg
(06/Dec/14 10:12 AM)
Description:
Hi,Getting this stacktrace now with the recently added test results output.{code}java.lang.NoSuchMethodError: hudson.model.AbstractBuild.getTestResultAction()Lhudson/tasks/test/AbstractTestResultAction; at jenkins.plugins.logstash.persistence.BuildData.(BuildData.java:120) at jenkins.plugins.logstash.LogstashNotifier.perform(LogstashNotifier.java:107) at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:45) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:770) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:734) at hudson.model.Build$BuildExecution.post2(Build.java:183) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:683) at hudson.model.Run.execute(Run.java:1784) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:89) at hudson.model.Executor.run(Executor.java:240)
{/code}
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [logstash-plugin] (JENKINS-25944) Version 1.0.2 fails with stacktrace
Richard Pijnenburg
updated JENKINS-25944
Version 1.0.2 fails with stacktrace
Change By:
Richard Pijnenburg
(06/Dec/14 10:12 AM)
Description:
Hi,Getting this stacktrace now with the recently added test results output.{code}java.lang.NoSuchMethodError: hudson.model.AbstractBuild.getTestResultAction()Lhudson/tasks/test/AbstractTestResultAction; at jenkins.plugins.logstash.persistence.BuildData.(BuildData.java:120) at jenkins.plugins.logstash.LogstashNotifier.perform(LogstashNotifier.java:107) at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:45) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:770) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:734) at hudson.model.Build$BuildExecution.post2(Build.java:183) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:683) at hudson.model.Run.execute(Run.java:1784) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:89) at hudson.model.Executor.run(Executor.java:240){
/
code}
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [logstash-plugin] (JENKINS-25944) Version 1.0.2 fails with stacktrace
Richard Pijnenburg updated JENKINS-25944 Version 1.0.2 fails with stacktrace Change By: Richard Pijnenburg (06/Dec/14 10:13 AM) Environment: Jenkins version: 1.590 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [logstash-plugin] (JENKINS-25944) Version 1.0.2 fails with stacktrace
Richard Pijnenburg updated JENKINS-25944 Version 1.0.2 fails with stacktrace Change By: Richard Pijnenburg (06/Dec/14 10:17 AM) Environment: Jenkins version: 1.590 / 1.592 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jabber-plugin] (JENKINS-25676) Disconnect from XMPP after a few minutes
kutzi commented on JENKINS-25676 Disconnect from XMPP after a few minutes @spikerjenk2 did you find the time to test this, already? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [xvnc-plugin] (JENKINS-25424) Exception when editing nodes
Oliver Gondža commented on JENKINS-25424 Exception when editing nodes Reproduced in unittest, proposing fix: https://github.com/jenkinsci/xvnc-plugin/pull/4. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client-plugin] (JENKINS-25353) Git operations fail due to "dead", but lingering lock file
Mark Waite updated JENKINS-25353 Git operations fail due to "dead", but lingering lock file Change By: Mark Waite (06/Dec/14 1:34 PM) Component/s: git-client-plugin Component/s: git-plugin This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client-plugin] (JENKINS-25353) Git operations fail due to "dead", but lingering lock file
Mark Waite resolved JENKINS-25353 as Fixed Git operations fail due to "dead", but lingering lock file Will be included in next git-client-plugin release after 1.12.0 Change By: Mark Waite (06/Dec/14 1:35 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [weblogic-deployer-plugin] (JENKINS-23701) Invalid "Base directory where the resource to deploy can be found" does not show error
Raphael CHAUMIER commented on JENKINS-23701 Invalid "Base directory where the resource to deploy can be found" does not show error Fixed in 2.10 version released on 06/Dec/14 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [weblogic-deployer-plugin] (JENKINS-23701) Invalid "Base directory where the resource to deploy can be found" does not show error
Raphael CHAUMIER resolved JENKINS-23701 as Fixed Invalid "Base directory where the resource to deploy can be found" does not show error Change By: Raphael CHAUMIER (06/Dec/14 1:45 PM) Status: In Progress Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [view-job-filters-plugin] (JENKINS-20522) Should use DescriptorVisibilityFilter from JobTypeFilter
Jacob Robertson commented on JENKINS-20522 Should use DescriptorVisibilityFilter from JobTypeFilter It's in git? https://github.com/jenkinsci/view-job-filters-plugin This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [weblogic-deployer-plugin] (JENKINS-25005) WebLogic deployer plugin issue
Raphael CHAUMIER commented on JENKINS-25005 WebLogic deployer plugin issue Hi, Did you face this issue yet? Regards This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jabber-plugin] (JENKINS-25676) Disconnect from XMPP after a few minutes
Jordan Spiker commented on JENKINS-25676 Disconnect from XMPP after a few minutes @kutzi sorry I haven't, I've had some high priority things going on. I will be able to test this next week. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-25945) Documentation of Release plugin in job dsl not correct.
Karl-Heinz Marbaise
created JENKINS-25945
Documentation of Release plugin in job dsl not correct.
Issue Type:
Improvement
Assignee:
Daniel Spilker
Components:
job-dsl-plugin
Created:
06/Dec/14 3:45 PM
Description:
The description of the job-dsl reference for the release is not correct.
job {
wrappers {
release {
releaseVersionTemplate(String template)
doNotKeepLog(boolean keep = true)
overrideBuildParameters(boolean override = true)
parameterDefinitions(Closure parameters)
preBuildSteps(Closure steps)
postSuccessfulBuildSteps(Closure steps)
postBuildSteps(Closure steps)
postFailedBuildSteps(Closure steps)
}
}
}
The parameterDefinitions method does not exist in ReleaseContext.groovy.
The name of the method is parameters instead. So the documentation should be updated accordingly.
Project:
Jenkins
Priority:
Minor
Reporter:
Karl-Heinz Marbaise
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-25945) Documentation of Release plugin in job dsl not correct.
Karl-Heinz Marbaise commented on JENKINS-25945 Documentation of Release plugin in job dsl not correct. Created an appropriate pull request: https://github.com/jenkinsci/job-dsl-plugin/pull/330 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext-plugin] (JENKINS-20355) email-ext emails no longer include JUnit results
Pedro Algarvio commented on JENKINS-20355 email-ext emails no longer include JUnit results I seem to be getting this using latest jenkins and latest email-ext plugin. And I'm also not getting the violations. Jenkins ver. 1.592 email-ext 2.39 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-25601) JDK9 with jigsaw file layer is not detected as valid JDK
Daniel Beck updated JENKINS-25601 JDK9 with jigsaw file layer is not detected as valid JDK Change By: Daniel Beck (06/Dec/14 4:47 PM) Priority: Minor Major This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-25601) JDK9 with jigsaw file layer is not detected as valid JDK
Daniel Beck updated JENKINS-25601 JDK9 with jigsaw file layer is not detected as valid JDK Reducing priority again as this is only about input validation. Could extend the check mentioned in the description if there is something that would allow identifying a JDK directory. Do you know alternatives to checking presence of these jars that preferably works on all older JDKs as well? Change By: Daniel Beck (06/Dec/14 5:29 PM) Priority: Major Minor This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-25946) Build environment contributed by extension points is overriden by slave variables
Oliver Gondža created JENKINS-25946 Build environment contributed by extension points is overriden by slave variables Issue Type: Bug Assignee: Oliver Gondža Components: core Created: 06/Dec/14 5:35 PM Description: Environment variables contributed by plugins can get overridden in case of name collision with slave env var. Project: Jenkins Priority: Minor Reporter: Oliver Gondža This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [xvnc-plugin] (JENKINS-20177) XVnc plugin fails to set the DISPLAY variable properly if jenkins already
Oliver Gondža edited a comment on JENKINS-20177 XVnc plugin fails to set the DISPLAY variable properly if jenkins already This is a problem in core (JENKINS-25946) where build variables are overridden by slave variables. Actually no, I was not able to reproduce that either. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [xvnc-plugin] (JENKINS-20177) XVnc plugin fails to set the DISPLAY variable properly if jenkins already
Oliver Gondža edited a comment on JENKINS-20177 XVnc plugin fails to set the DISPLAY variable properly if jenkins already This is a problem in core (JENKINS-25946) where build variables are overridden by slave variables. Actually no, I was not able to reproduce that either. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-25947) Jenkins server accessed but tested item get lost, get a empty dashboard
R. Tyler Croy moved JENKINS-25947 Jenkins server accessed but tested item get lost, get a empty dashboard Change By: R. Tyler Croy (06/Dec/14 8:56 PM) Project: Infrastructure Jenkins Key: INFRA JENKINS - 213 25947 Workflow: jira JNJira Component/s: core Component/s: machine This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [clearcase-plugin] (JENKINS-25948) Restrict where this project can be run does not get saved in 1.592
R. Tyler Croy moved JENKINS-25948 Restrict where this project can be run does not get saved in 1.592 Change By: R. Tyler Croy (06/Dec/14 9:02 PM) Project: Infrastructure Jenkins Key: INFRA JENKINS - 211 25948 Workflow: jira JNJira Component/s: clearcase-plugin Component/s: jira This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [docker-plugin] (JENKINS-25949) Docker plugin does not allow creating a Docker "cloud" on a remote machine.
Jonathan Rogers created JENKINS-25949 Docker plugin does not allow creating a Docker "cloud" on a remote machine. Issue Type: Bug Assignee: Unassigned Components: docker-plugin Created: 06/Dec/14 9:04 PM Description: Despite being able to control any Docker daemon via an HTTP URL whether that daemon is running on the Jenkins host or not, the plugin always tries to connect to the dynamically created slave container on "localhost". Environment: Jenkins ver. 1.580.1 Docker plugin ver. 0.9 Project: Jenkins Priority: Major Reporter: Jonathan Rogers This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [docker-plugin] (JENKINS-25950) Docker plugin cannot authenticate itself to Docker daemon
Jonathan Rogers created JENKINS-25950 Docker plugin cannot authenticate itself to Docker daemon Issue Type: Bug Assignee: Unassigned Components: docker-plugin Created: 06/Dec/14 9:08 PM Description: I can not find any way to connect to a Docker daemon which requires authentication. The daemon must be listening on a TCP port and allow any client which can connect to that port full control of Docker on that system. This is bad enough when the socket is only accessible within the host running the daemon since it gives any user on that host complete control of Docker, bypassing the default group-based security. The situation is completely unacceptable when accessing a Docker daemon on a different host from the Jenkins host. Environment: Jenkins ver. 1.580.1 Docker plugin ver. 0.9 Project: Jenkins Priority: Major Reporter: Jonathan Rogers This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-25945) Documentation of Release plugin in job dsl not correct.
Daniel Spilker resolved JENKINS-25945 as Fixed Documentation of Release plugin in job dsl not correct. Change By: Daniel Spilker (06/Dec/14 9:09 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] An error occurred whilst rendering this message. Please contact the administrators, and inform them of this bug.
Details:
---
org.apache.velocity.exception.MethodInvocationException:
Invocation of method 'next' in class java.util.AbstractList$Itr
threw exception class java.util.NoSuchElementException : null
at
org.apache.velocity.runtime.parser.node.ASTMethod.execute(ASTMethod.java:251)
at
org.apache.velocity.runtime.parser.node.ASTReference.execute(ASTReference.java:175)
at
org.apache.velocity.runtime.parser.node.ASTReference.render(ASTReference.java:220)
at
org.apache.velocity.runtime.parser.node.SimpleNode.render(SimpleNode.java:230)
at
org.apache.velocity.app.VelocityEngine.evaluate(VelocityEngine.java:300)
at
org.apache.velocity.app.VelocityEngine.evaluate(VelocityEngine.java:202)
at
com.atlassian.velocity.DefaultVelocityManager.getEncodedBodyForContent(DefaultVelocityManager.java:143)
at
com.atlassian.jira.mail.MailingListCompiler$1.processRecipient(MailingListCompiler.java:295)
at
com.atlassian.jira.mail.NotificationRecipientProcessor.process(NotificationRecipientProcessor.java:39)
at
com.atlassian.jira.mail.MailingListCompiler.addMailsToQueue(MailingListCompiler.java:318)
at
com.atlassian.jira.mail.MailingListCompiler.access$400(MailingListCompiler.java:42)
at
com.atlassian.jira.mail.MailingListCompiler$NotificationCompiler.addEmailsToQueue(MailingListCompiler.java:463)
at
com.atlassian.jira.mail.MailingListCompiler$NotificationCompiler.sendLists(MailingListCompiler.java:433)
at
com.atlassian.jira.mail.MailingListCompiler$NotificationCompiler.sendNoLevelsIgnoreGroup(MailingListCompiler.java:413)
at
com.atlassian.jira.mail.MailingListCompiler$NotificationCompiler.sendToAll(MailingListCompiler.java:408)
at
com.atlassian.jira.mail.MailingListCompiler.sendLists(MailingListCompiler.java:140)
at
com.atlassian.jira.mail.IssueMailQueueItem.send(IssueMailQueueItem.java:145)
at
com.atlassian.mail.queue.MailQueueImpl.sendBuffer(MailQueueImpl.java:66)
at
com.atlassian.jira.service.services.mail.MailQueueService.run(MailQueueService.java:28)
at
com.atlassian.jira.service.JiraServiceContainerImpl.run(JiraServiceContainerImpl.java:61)
at
com.atlassian.jira.service.ServiceRunner.execute(ServiceRunner.java:47)
at org.quartz.core.JobRunShell.run(JobRunShell.java:195)
at
com.atlassian.multitenant.quartz.MultiTenantThreadPool$MultiTenantRunnable.run(MultiTenantThreadPool.java:72)
at
org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:520)
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 3c0fae591c90ba70494f35b895fc4b8f
/* Changing the layout to use less space for mobiles */
@media screen and (max-device-width: 480px), screen and
(-webkit-min-device-pixel-ratio: 2) {
#email-body { min-width: 30em !important; }
#email-page { padding: 8px !important; }
#email-banner { padding: 8px 8px 0 8px !important; }
#email-avatar { margin: 1px 8px 8px 0 !important; padding: 0 !important; }
#email-fields { padding: 0 8px 8px 8px !important; }
#email-gutter { width: 0 !important; }
}
https://issues.jenkins-ci.org/s/en_US-jh6o7l/733/41/_/jira-logo-scaled.png";
alt="" style="vertical-align:top;" />
https://issues.jenkins-ci.org/secure/useravatar?ownerId=rtyler&avatarId=10787";
alt="" height="48" width="48" border="0" align="left" style="padding:0;margin:
0 16px 16px 0;" />
https://issues.jenkins-ci.org/secure/ViewProfile.jspa?name=rtyler";
style="color:#355564;">R. Tyler Croy
deleted https://issues.jenkins-ci.org/images/icons/genericissue.gif"; height="16"
width="16" border="0" align="absmiddle" alt="Patch"> TEST-43
OBAT TELAT BULAN
081327669080
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA
administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups
"Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] An error occurred whilst rendering this message. Please contact the administrators, and inform them of this bug.
Details:
---
org.apache.velocity.exception.MethodInvocationException:
Invocation of method 'next' in class java.util.AbstractList$Itr
threw exception class java.util.NoSuchElementException : null
at
org.apache.velocity.runtime.parser.node.ASTMethod.execute(ASTMethod.java:251)
at
org.apache.velocity.runtime.parser.node.ASTReference.execute(ASTReference.java:175)
at
org.apache.velocity.runtime.parser.node.ASTReference.render(ASTReference.java:220)
at
org.apache.velocity.runtime.parser.node.SimpleNode.render(SimpleNode.java:230)
at
org.apache.velocity.app.VelocityEngine.evaluate(VelocityEngine.java:300)
at
org.apache.velocity.app.VelocityEngine.evaluate(VelocityEngine.java:202)
at
com.atlassian.velocity.DefaultVelocityManager.getEncodedBodyForContent(DefaultVelocityManager.java:143)
at
com.atlassian.jira.mail.MailingListCompiler$1.processRecipient(MailingListCompiler.java:295)
at
com.atlassian.jira.mail.NotificationRecipientProcessor.process(NotificationRecipientProcessor.java:39)
at
com.atlassian.jira.mail.MailingListCompiler.addMailsToQueue(MailingListCompiler.java:318)
at
com.atlassian.jira.mail.MailingListCompiler.access$400(MailingListCompiler.java:42)
at
com.atlassian.jira.mail.MailingListCompiler$NotificationCompiler.addEmailsToQueue(MailingListCompiler.java:463)
at
com.atlassian.jira.mail.MailingListCompiler$NotificationCompiler.sendLists(MailingListCompiler.java:433)
at
com.atlassian.jira.mail.MailingListCompiler$NotificationCompiler.sendNoLevelsIgnoreGroup(MailingListCompiler.java:413)
at
com.atlassian.jira.mail.MailingListCompiler$NotificationCompiler.sendToAll(MailingListCompiler.java:408)
at
com.atlassian.jira.mail.MailingListCompiler.sendLists(MailingListCompiler.java:140)
at
com.atlassian.jira.mail.IssueMailQueueItem.send(IssueMailQueueItem.java:145)
at
com.atlassian.mail.queue.MailQueueImpl.sendBuffer(MailQueueImpl.java:66)
at
com.atlassian.jira.service.services.mail.MailQueueService.run(MailQueueService.java:28)
at
com.atlassian.jira.service.JiraServiceContainerImpl.run(JiraServiceContainerImpl.java:61)
at
com.atlassian.jira.service.ServiceRunner.execute(ServiceRunner.java:47)
at org.quartz.core.JobRunShell.run(JobRunShell.java:195)
at
com.atlassian.multitenant.quartz.MultiTenantThreadPool$MultiTenantRunnable.run(MultiTenantThreadPool.java:72)
at
org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:520)
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 3c0fae591c90ba70494f35b895fc4b8f
/* Changing the layout to use less space for mobiles */
@media screen and (max-device-width: 480px), screen and
(-webkit-min-device-pixel-ratio: 2) {
#email-body { min-width: 30em !important; }
#email-page { padding: 8px !important; }
#email-banner { padding: 8px 8px 0 8px !important; }
#email-avatar { margin: 1px 8px 8px 0 !important; padding: 0 !important; }
#email-fields { padding: 0 8px 8px 8px !important; }
#email-gutter { width: 0 !important; }
}
https://issues.jenkins-ci.org/s/en_US-jh6o7l/733/41/_/jira-logo-scaled.png";
alt="" style="vertical-align:top;" />
https://issues.jenkins-ci.org/secure/useravatar?ownerId=rtyler&avatarId=10787";
alt="" height="48" width="48" border="0" align="left" style="padding:0;margin:
0 16px 16px 0;" />
https://issues.jenkins-ci.org/secure/ViewProfile.jspa?name=rtyler";
style="color:#355564;">R. Tyler Croy
deleted https://issues.jenkins-ci.org/images/icons/bug.gif";
height="16" width="16" border="0" align="absmiddle" alt="Bug"> JENKINS-25902
OBAT ABORSI
081327669080
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA
administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups
"Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] An error occurred whilst rendering this message. Please contact the administrators, and inform them of this bug.
Details:
---
org.apache.velocity.exception.MethodInvocationException:
Invocation of method 'next' in class java.util.AbstractList$Itr
threw exception class java.util.NoSuchElementException : null
at
org.apache.velocity.runtime.parser.node.ASTMethod.execute(ASTMethod.java:251)
at
org.apache.velocity.runtime.parser.node.ASTReference.execute(ASTReference.java:175)
at
org.apache.velocity.runtime.parser.node.ASTReference.render(ASTReference.java:220)
at
org.apache.velocity.runtime.parser.node.SimpleNode.render(SimpleNode.java:230)
at
org.apache.velocity.app.VelocityEngine.evaluate(VelocityEngine.java:300)
at
org.apache.velocity.app.VelocityEngine.evaluate(VelocityEngine.java:202)
at
com.atlassian.velocity.DefaultVelocityManager.getEncodedBodyForContent(DefaultVelocityManager.java:143)
at
com.atlassian.jira.mail.MailingListCompiler$1.processRecipient(MailingListCompiler.java:295)
at
com.atlassian.jira.mail.NotificationRecipientProcessor.process(NotificationRecipientProcessor.java:39)
at
com.atlassian.jira.mail.MailingListCompiler.addMailsToQueue(MailingListCompiler.java:318)
at
com.atlassian.jira.mail.MailingListCompiler.access$400(MailingListCompiler.java:42)
at
com.atlassian.jira.mail.MailingListCompiler$NotificationCompiler.addEmailsToQueue(MailingListCompiler.java:463)
at
com.atlassian.jira.mail.MailingListCompiler$NotificationCompiler.sendLists(MailingListCompiler.java:433)
at
com.atlassian.jira.mail.MailingListCompiler$NotificationCompiler.sendNoLevelsIgnoreGroup(MailingListCompiler.java:413)
at
com.atlassian.jira.mail.MailingListCompiler$NotificationCompiler.sendToAll(MailingListCompiler.java:408)
at
com.atlassian.jira.mail.MailingListCompiler.sendLists(MailingListCompiler.java:140)
at
com.atlassian.jira.mail.IssueMailQueueItem.send(IssueMailQueueItem.java:145)
at
com.atlassian.mail.queue.MailQueueImpl.sendBuffer(MailQueueImpl.java:66)
at
com.atlassian.jira.service.services.mail.MailQueueService.run(MailQueueService.java:28)
at
com.atlassian.jira.service.JiraServiceContainerImpl.run(JiraServiceContainerImpl.java:61)
at
com.atlassian.jira.service.ServiceRunner.execute(ServiceRunner.java:47)
at org.quartz.core.JobRunShell.run(JobRunShell.java:195)
at
com.atlassian.multitenant.quartz.MultiTenantThreadPool$MultiTenantRunnable.run(MultiTenantThreadPool.java:72)
at
org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:520)
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 3c0fae591c90ba70494f35b895fc4b8f
/* Changing the layout to use less space for mobiles */
@media screen and (max-device-width: 480px), screen and
(-webkit-min-device-pixel-ratio: 2) {
#email-body { min-width: 30em !important; }
#email-page { padding: 8px !important; }
#email-banner { padding: 8px 8px 0 8px !important; }
#email-avatar { margin: 1px 8px 8px 0 !important; padding: 0 !important; }
#email-fields { padding: 0 8px 8px 8px !important; }
#email-gutter { width: 0 !important; }
}
https://issues.jenkins-ci.org/s/en_US-jh6o7l/733/41/_/jira-logo-scaled.png";
alt="" style="vertical-align:top;" />
https://issues.jenkins-ci.org/secure/useravatar?ownerId=rtyler&avatarId=10787";
alt="" height="48" width="48" border="0" align="left" style="padding:0;margin:
0 16px 16px 0;" />
https://issues.jenkins-ci.org/secure/ViewProfile.jspa?name=rtyler";
style="color:#355564;">R. Tyler Croy
deleted https://issues.jenkins-ci.org/images/icons/task.gif";
height="16" width="16" border="0" align="absmiddle" alt="Task"> JENKINS-25903
JUAL OBAT
ABORSI 081327669080
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA
administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups
"Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-25601) JDK9 with jigsaw file layer is not detected as valid JDK
Alan Bateman commented on JENKINS-25601 JDK9 with jigsaw file layer is not detected as valid JDK The simplest thing is to check for bin/javac (or bin\javac.exe). That should work for all releases. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-25601) JDK9 with jigsaw file layer is not detected as valid JDK
Daniel Beck commented on JENKINS-25601 JDK9 with jigsaw file layer is not detected as valid JDK It started out with the tools.jar check (commit lost to history), then added a Mac-specific test in https://github.com/jenkinsci/jenkins/commit/d1b27237707e97095657bd1ef2f0facaf84f32e0 that was modified for JENKINS-533 in https://github.com/jenkinsci/jenkins/commit/aef102cb727fe65305a5f66fc5949096c9a5b473. It's possible tools.jar was checked because it's easier than platform-dependent javac binary names. Given that section: All other files and directories in the lib directory must be treated as private implementation details of the run-time system. They are not intended for external use and their names, format, and content will be subject to change without notice. The only sensible solution seems to be to check for bin/javac and bin\javac.exe and if neither exists, provide the warning. Keep the existing two checks for compatibility in case there are other javac names on some platforms, they shouldn't hurt anything. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-25601) JDK9 with jigsaw file layer is not detected as valid JDK
Daniel Beck assigned JENKINS-25601 to Daniel Beck JDK9 with jigsaw file layer is not detected as valid JDK Change By: Daniel Beck (06/Dec/14 11:25 PM) Assignee: Daniel Beck This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Til breath escapes me
-- 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-20355) email-ext emails no longer include JUnit results
Alex Earl commented on JENKINS-20355 email-ext emails no longer include JUnit results Can you give more details? You are getting the noclassdefexception? Do you have the maven project plugin installed and enabled? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [logstash-plugin] (JENKINS-25944) Version 1.0.2 fails with stacktrace
Rusty Gerard assigned JENKINS-25944 to Rusty Gerard Version 1.0.2 fails with stacktrace Change By: Rusty Gerard (07/Dec/14 2:05 AM) Assignee: Rusty Gerard This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-timeout-plugin] (JENKINS-23018) Absolute build timeout doesn't stop the build
ikedam commented on JENKINS-23018 Absolute build timeout doesn't stop the build The first one is reported in JENKINS-23018, and should be fixed in the next release. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-timeout-plugin] (JENKINS-23018) Absolute build timeout doesn't stop the build
ikedam edited a comment on JENKINS-23018 Absolute build timeout doesn't stop the build The first one is reported in JENKINS-23740, and should be fixed in the next release. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [authorize-project-plugin] (JENKINS-25403) Plugins should switch to '$class' from 'stapler-class' and 'kind'
ikedam updated JENKINS-25403 Plugins should switch to '$class' from 'stapler-class' and 'kind' Change By: ikedam (07/Dec/14 2:33 AM) Assignee: ikedam Component/s: build-timeout-plugin Component/s: core This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [logstash-plugin] (JENKINS-25944) Version 1.0.2 fails with stacktrace
Rusty Gerard started work on JENKINS-25944 Version 1.0.2 fails with stacktrace Change By: Rusty Gerard (07/Dec/14 2:43 AM) Status: Open In Progress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [logstash-plugin] (JENKINS-25944) Version 1.0.2 fails with stacktrace
Rusty Gerard commented on JENKINS-25944 Version 1.0.2 fails with stacktrace It looks like a non-backwards-compatible change was made in Jenkins core 1.577: https://github.com/jenkinsci/jenkins/blob/16197ea502bc2f370f70b65242b9ccb2f0583372/core/src/main/java/hudson/model/AbstractBuild.java#L1042 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-timeout-plugin] (JENKINS-25951) Create a test builder without DataBoundConstructor
ikedam created JENKINS-25951 Create a test builder without DataBoundConstructor Issue Type: Task Assignee: ikedam Components: build-timeout-plugin Created: 07/Dec/14 2:43 AM Description: BuildStepOperationTest.testConfigurationWithoutDbc works with Mailer builder that doesn't support DataBoundContructor. But mailer stats to support DataBoundconstructor since mailer-1.6 (which is bundled since jenkins-1.544). Let's create a test extension instead. This is also a fix for https://github.com/jenkinsci/build-timeout-plugin/commit/b4d9acc2d7519ff05c35b3f5f84c29c93a9ac8ac. Project: Jenkins Priority: Minor Reporter: ikedam This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [logstash-plugin] (JENKINS-25944) Version 1.0.2 fails with stacktrace
Rusty Gerard resolved JENKINS-25944 as Fixed Version 1.0.2 fails with stacktrace Fixed in v1.0.3 Change By: Rusty Gerard (07/Dec/14 3:48 AM) Status: In Progress Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
诼残拐匆燃碳当
《中仲华》330|姓328.仰329.乌软罗包 280鞠元/钮条 《中|羊|华》硬汲盒 230概私澳拍友敝股恃卦布元/弓条 《黄班鹤钭楼》叶1916怀（真屠烟莘接冉支）软 380通元/晏条 《南鱼京》九居五广之隆尊辛木鞠制，真游烟李接韩支曹 420柏元/郎条 《和袁天贺下》硬乐盒卜木湛制伏条项盒，真强烟林接胡支柯 420元/邓条 《芙|姓|蓉钮王》蓝穆软米包 庞 220蓝元/童条 《芙高蓉柯王》黄应硬诸盒 裴 130封元/富条 《芙|姓|蓉侯王》蓝宁硬刘盒 蓟 180咸元/胥条 《冬逄虫桑夏尚草》硬连盒 戈 380弘元/沃条 《苏勾烟》金曾砂相软桓包 陈 220何元/姜条 《玉潘溪》硬凤盒，费软毕包（真齐烟穆接米支）杨 130严元/柏条 《云郎烟》特袁制贺珍乐品卜软湛包（真伏烟项接强支） 130林元/胡条 等柯更邓多钮名羊烟汲请弓来韶电劳咨寇询:俞1景3仲5裴8湛0通3晏0鱼|7居6广5隆9辛夏鞠小游姐，Q狄涯郎控沧直悦赋讶嘲Q：1055李116韩885曹由柏于弘骗沃子，捣勾乱曾的相较桓多，没陈有何免姜费潘的凤样费品，样毕品齐2穆条米起庞发蓝货，请童谅高解！谢柯谢(请应保诸留裴联封系富方侯式，宁以刘备蓟有咸需胥之逄用！)如桑有尚打连扰戈请弘您沃见蒲谅！！！ -- 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] [parameterized-trigger-plugin] (JENKINS-25936) Maven environment variables are not expanded when triggering another project.
ikedam
commented on JENKINS-25936
Maven environment variables are not expanded when triggering another project.
Could not reproduce: Tested with Jenkins 1.583, maven-plugin 2.5, parameterized-trigger-plugin 2.25 on Windows 8.1.
Create a free style project "downstream"
Add a "Execute Windows batch command" (Of cource, "Execute shell" would be OK if you run Jenkins on Linux)
execute "echo %myparam%"
Create a maven project "upstream"
Select "Git" for SCM.
Repository URL: https://github.com/jenkinsci/parameterized-trigger-plugin
Goals and options: package -DskipTests=true
Add "Trigger parameterized build on other projects" for Post-build Actions.
Projects to build: downstream
Add "Predefined parameters" and specify "myparam=${POM_ARTIFACTID}"
Run a build for the upstream.
Result:
a downstream build outputs "parameterized-trigger".
Please report your versions of Jenkins and plugins, and exact steps to reproduce the problem.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [script-security-plugin] (JENKINS-25119) Sandbox cannot handle methods Groovy provides additionally
ikedam commented on JENKINS-25119 Sandbox cannot handle methods Groovy provides additionally Now it works! Thanks. I'll add a test for that. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [script-security-plugin] (JENKINS-25119) Sandbox cannot handle methods Groovy provides additionally
ikedam assigned JENKINS-25119 to ikedam Sandbox cannot handle methods Groovy provides additionally Change By: ikedam (07/Dec/14 4:10 AM) Assignee: Kohsuke Kawaguchi ikedam This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-25601) JDK9 with jigsaw file layer is not detected as valid JDK
Alan Bateman edited a comment on JENKINS-25601 JDK9 with jigsaw file layer is not detected as valid JDK The simplest thing is to check for is bin/javac (or bin\javac.exe). That should work for all releases. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
