[JIRA] [workflow-plugin] (JENKINS-31096) Unicode characters in console logs do not print correctly in Workflow builds
Title: Message Title
owenmehegan edited a comment on JENKINS-31096
Re: Unicode characters in console logs do not print correctly in Workflow builds
/systemInfo tells me the encoding is ANSI_X3.4-1968. I get the same failure whether running on the master or other nodes. I am setting LANGUAGE = en_US.UTF-8 and LC_ALL = en_US.UTF-8 in the environment variables config for my build nodes, but not for the master.Output of 'locale' on the master:{{LANG=LANGUAGE=LC_CTYPE="POSIX"LC_NUMERIC="POSIX"LC_TIME="POSIX"LC_COLLATE="POSIX"LC_MONETARY="POSIX"LC_MESSAGES="POSIX"LC_PAPER="POSIX"LC_NAME="POSIX"LC_ADDRESS="POSIX"LC_TELEPHONE="POSIX"LC_MEASUREMENT="POSIX"LC_IDENTIFICATION="POSIX"LC_ALL=}}Output of 'locale' on a build node:{{LANG=en_US.UTF-8LANGUAGE=en_US.UTF-8LC_CTYPE="en_US.UTF-8"LC_NUMERIC="en_US.UTF-8"LC_TIME="en_US.UTF-8"LC_COLLATE="en_US.UTF-8"LC_MONETARY="en_US.UTF-8"LC_MESSAGES="en_US.UTF-8"LC_PAPER="en_US.UTF-8"LC_NAME="en_US.UTF-8"LC_ADDRESS="en_US.UTF-8"LC_TELEPHONE="en_US.UTF-8"LC_MEASUREMENT="en_US.UTF-8"LC_IDENTIFICATION="en_US.UTF-8"LC_ALL=en_US.UTF-8}}
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-30873) Jenkins reparses all previous build.xml on restart
Title: Message Title
Benoit Sigoure updated an issue
Jenkins / JENKINS-30873
Jenkins reparses all previous build.xml on restart
Change By:
Benoit Sigoure
Summary:
Jenkins reparses all previous build.xml after job rename on restart
Priority:
Major Critical
edit: I originally thought this was related to renaming a project, but this seems to be a general issue when restarting Jenkins. When we upgraded to 1.634 we simply restart Jenkins with the new {{.war}} file and even after 12h it wasn't done parsing the XML files from our tens of thousands of archived builds. We ended up moving all the old build directories out of the way and this immediately resolved the problem for us (we just can't access these old builds anymore, but that's less problematic than Jenkins itself being stuck on certain projects).I renamed a job with the following steps:# Shut down Jenkins# {{mv ~jenkins/job/prevname ~jenkins/job/newname}}# Adjust any other references to the job name# Start Jenkins(It's not the first time I do this and I've never had any issues in the past)This time I renamed a couple jobs with "lots" of previous builds (26k and 5k, respectively). Upon launching the first build for either of these jobs after restarting Jenkins, it was apparent that the build wasn't starting, couldn't be stopped, and was seemingly hung. Checking {{/threadDump}} and doing a bit of {{strace}}'ing showed that Jenkins was loading every single prior {{build.xml}} for these jobs.Common part of the stack trace:{code} at jenkins.model.lazy.LazyBuildMixIn.loadBuild(LazyBuildMixIn.java:158) at jenkins.model.lazy.LazyBuildMixIn$1.create(LazyBuildMixIn.java:135) at hudson.model.RunMap.retrieve(RunMap.java:224) at hudson.model.RunMap.retrieve(RunMap.java:57) at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:465) - locked hudson.model.RunMap@2cedf74 at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:448) at jenkins.model.lazy.AbstractLazyLoadRunMap.getByNumber(AbstractLazyLoadRunMap.java:356) at jenkins.model.lazy.AbstractLazyLoadRunMap.search(AbstractLazyLoadRunMap.java:332) at jenkins.model.lazy.LazyBuildMixIn$RunMixIn.getPreviousBuild(LazyBuildMixIn.java:357) at hudson.model.AbstractBuild.getPreviousBuild(AbstractBuild.java:199) at hudson.model.AbstractBuild.getPreviousBuild(AbstractBuild.java:107) at hudson.plugins.git.GitSCM.getBuildData(GitSCM.java:1553) at hudson.plugins.git.GitSCM.buildEnvVars(GitSCM.java:1161) at hudson.model.AbstractBuild.getEnvironment(AbstractBuild.java:940) at hudson.model.AbstractBuild$AbstractBuildExecution.decideWorkspace(AbstractBuild.java:481) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:521) at
[JIRA] [core] (JENKINS-30873) Jenkins reparses all previous build.xml on restart
Title: Message Title Benoit Sigoure commented on JENKINS-30873 Re: Jenkins reparses all previous build.xml on restart I originally thought this was related to renaming a project, but this seems to be a general issue when restarting Jenkins. When we upgraded to 1.634 we simply restart Jenkins with the new .war file and even after 12h it wasn't done parsing the XML files from our tens of thousands of archived builds. We ended up moving all the old build directories out of the way and this immediately resolved the problem for us (we just can't access these old builds anymore, but that's less problematic than Jenkins itself being stuck on certain 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] [tfs-plugin] (JENKINS-31110) Support credentials plugin
Title: Message Title Will Saxon updated an issue Jenkins / JENKINS-31110 Support credentials plugin Change By: Will Saxon As a user, I would like the tfs plugin to support the credentials plugin, so I can store my credentials in one location and share them amongst my many jobs. 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] [jira-plugin] (JENKINS-31113) Configurable HTTP timeout parameter for JiraRestService
Title: Message Title Tom Weber created an issue Jenkins / JENKINS-31113 Configurable HTTP timeout parameter for JiraRestService Issue Type: New Feature Assignee: Unassigned Components: jira-plugin Created: 22/Oct/15 7:39 PM Environment: Jenkins ver. 1.634 jira-plugin ver. 2.0.2 Priority: Critical Reporter: Tom Weber For long running JQL queries it is necessary to increase to default HTTP timeout of 10 seconds to a higher (configurable) value such as 120 seconds etc. Add Comment
[JIRA] [cli] (JENKINS-31098) New delete-node CLI command breaks node cleanup in cloud plugins
Title: Message Title Fritz Elfert commented on JENKINS-31098 Re: New delete-node CLI command breaks node cleanup in cloud plugins Even if doDoDelete() is a Stapler call designed for UIs, it is currently the only possible place to intercept node-deletion (that I know of). I have not looked into other cloud plugins right now but at least JClouds as well as OpenStack need something like this in order to shutdown and/or delete unused VMs. 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] [kubernetes-plugin] (JENKINS-30894) Kubernetes plugin should support certificate-based https API calls
Title: Message Title Mathias Rühle commented on JENKINS-30894 Re: Kubernetes plugin should support certificate-based https API calls I created a pull request dealing with this issue: https://github.com/jenkinsci/kubernetes-plugin/pull/29 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cli] (JENKINS-31098) New delete-node CLI command breaks node cleanup in cloud plugins
Title: Message Title Oliver Gondža commented on JENKINS-31098 Re: New delete-node CLI command breaks node cleanup in cloud plugins As far as I can tell, only CLI sis affected as it does no loner delegates to the UI method. Deleting from UI or the JCLouds cleanup thread should still work. While I agree with Oleg that this is rather hackish, I see no other way to politely ask computer-slave pair to terminate when ready. I propose to document this purpose of Computer#doDoDelete() and fix the delete-node implementation to call that method again. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cli] (JENKINS-28041) Allow delete-* CLI commands to operate on multiple arguments
Title: Message Title Fritz Elfert reopened an issue This badly breaks cleanup of cloud-managed VMs (at least in jclouds-plugin and openstack-plugin) The cloud plugins extend AbstractCloudComputer and then override doDoDelete() in order to perform any cleanup (and delay the actual deleteion until this is done). The new delete-node command does not invoke this and thus when using this command, lots of unused VM's are kept around which get never cleaned up. In fact, there is no "hook" whatsoever anymore which allows a cloud plugin to intercept node deletion. If there's some other (new) functionality to intercept node-deletion please let me know. Unfortunately this made it into 1.625.1 LTS and I only noticed that change now. It is not even mentioned in the changelog. Jenkins / JENKINS-28041 Allow delete-* CLI commands to operate on multiple arguments Change By: Fritz Elfert Resolution: Fixed Status: Resolved Reopened Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [cli] (JENKINS-28041) Allow delete-* CLI commands to operate on multiple arguments
Title: Message Title Fritz Elfert updated an issue Jenkins / JENKINS-28041 Allow delete-* CLI commands to operate on multiple arguments Change By: Fritz Elfert Priority: Major Critical Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ant-plugin] (JENKINS-31099) Build failes, when setup build environment on runner
Title: Message Title Thomas Storm updated an issue Jenkins / JENKINS-31099 Build failes, when setup build environment on runner Change By: Thomas Storm Attachment: Screenshot 2015-10-05 14.17.17.png Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cli] (JENKINS-28041) Allow delete-* CLI commands to operate on multiple arguments
Title: Message Title Fritz Elfert commented on JENKINS-28041 Re: Allow delete-* CLI commands to operate on multiple arguments Ok. https://issues.jenkins-ci.org/browse/JENKINS-31098 Continue discussion there. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cli] (JENKINS-31098) New delete-node CLI command breaks node cleanup in cloud plugins
Title: Message Title Fritz Elfert created an issue Jenkins / JENKINS-31098 New delete-node CLI command breaks node cleanup in cloud plugins Issue Type: Bug Assignee: Unassigned Components: cli, core Created: 22/Oct/15 8:33 AM Environment: Jenkins 1.625.1 LTS Priority: Critical Reporter: Fritz Elfert The new implementation of the delete-node command badly breaks cleanup of cloud-managed VMs (at least in jclouds-plugin and openstack-plugin) The cloud plugins extend AbstractCloudComputer and then override doDoDelete() in order to perform any cleanup (and delay the actual deleteion until this is done). The new delete-node command does not invoke this and thus when using this command, lots of unused VM's are kept around which get never cleaned up. In fact, there is no "hook" whatsoever anymore which allows a cloud plugin to intercept node deletion. If there's some other (new) functionality to intercept node-deletion please let me know. Unfortunately this made it into 1.625.1 LTS and I only noticed that change now. It is not even mentioned in the changelog.
[JIRA] [unique-id] (JENKINS-30424) Run.save called inside Run.onLoad by migrator
Title: Message Title Antonio Muñiz commented on JENKINS-30424 Re: Run.save called inside Run.onLoad by migrator PR sent: https://github.com/jenkinsci/unique-id-plugin/pull/8 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] [ant-plugin] (JENKINS-31099) Build failes, when setup build environment on runner
Title: Message Title Thomas Storm created an issue Jenkins / JENKINS-31099 Build failes, when setup build environment on runner Issue Type: Bug Assignee: Unassigned Attachments: Screenshot 2015-10-05 14.17.17.png Components: ant-plugin, core Created: 22/Oct/15 8:36 AM Environment: centos 6.6 ant plugin 1.2 java.runtime.name OpenJDK Runtime Environment java.runtime.version 1.8.0_45-b13 ant 1.8.2 Priority: Critical Reporter: Thomas Storm Hi. There is interesting problem. If i setup environment properties on a runner (not in a job) i receive this problem FATAL: Cannot find executable from the chosen Ant installation "Ant 1.8.4" Build step 'Invoke Ant' marked build as failure Recording test results ERROR: Publisher 'Publish JUnit test result report' failed: No test report files were found. Configuration error?
[JIRA] [unique-id] (JENKINS-30424) Run.save called inside Run.onLoad by migrator
Title: Message Title Antonio Muñiz updated an issue Jenkins / JENKINS-30424 Run.save called inside Run.onLoad by migrator Change By: Antonio Muñiz Comment: PR sent: https://github.com/jenkinsci/unique-id-plugin/pull/8 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-31089) Signature verification failed in update site 'default'
Title: Message Title Arlo Louis O'Keeffe commented on JENKINS-31089 Re: Signature verification failed in update site 'default' Seeing the same issue with Oracle JDK 1.8.0_66-b17 but on openSUSE 13.1. Rolling back to 1.8.0_60 fixes the issue. The message I see is similar to https://issues.jenkins-ci.org/browse/JENKINS-30739. 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] [template-project-plugin] (JENKINS-27317) Support matrix aggregation with ProxyPublisher
Title: Message Title Sverre Moe commented on JENKINS-27317 Re: Support matrix aggregation with ProxyPublisher Updated commit with fix for this issue. Taken inspiration from FlexiblePublish. Thanks to ikedam for his assistance. https://github.com/DJViking/template-project-plugin/commit/13a0169562db32f90b0e48e135ca5d7cb60f1d76 I will go through the code some more, add some logging in the ProxyMatrixAggregator and then submit a 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] [cli] (JENKINS-28041) Allow delete-* CLI commands to operate on multiple arguments
Title: Message Title Oliver Gondža resolved as Fixed Jenkins / JENKINS-28041 Allow delete-* CLI commands to operate on multiple arguments Change By: Oliver Gondža 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] [gerrit-trigger-plugin] (JENKINS-31080) old label linked to new build
Title: Message Title Kurt Li assigned an issue to Unassigned Jenkins / JENKINS-31080 old label linked to new build Change By: Kurt Li Assignee: Kurt Li 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-31096) Unicode characters in console logs do not print correctly in Workflow builds
Title: Message Title
owenmehegan edited a comment on JENKINS-31096
Re: Unicode characters in console logs do not print correctly in Workflow builds
/systemInfo tells me the encoding is ANSI_X3.4-1968. I get the same failure whether running on the master or other nodes. I am setting LANGUAGE = en_US.UTF-8 and LC_ALL = en_US.UTF-8 in the environment variables config for my build nodes, but not for the master.Output of 'locale' on the master:{ { noformat} LANG=LANGUAGE=LC_CTYPE="POSIX"LC_NUMERIC="POSIX"LC_TIME="POSIX"LC_COLLATE="POSIX"LC_MONETARY="POSIX"LC_MESSAGES="POSIX"LC_PAPER="POSIX"LC_NAME="POSIX"LC_ADDRESS="POSIX"LC_TELEPHONE="POSIX"LC_MEASUREMENT="POSIX"LC_IDENTIFICATION="POSIX"LC_ALL= {noformat } } Output of 'locale' on a build node:{ { noformat} LANG=en_US.UTF-8LANGUAGE=en_US.UTF-8LC_CTYPE="en_US.UTF-8"LC_NUMERIC="en_US.UTF-8"LC_TIME="en_US.UTF-8"LC_COLLATE="en_US.UTF-8"LC_MONETARY="en_US.UTF-8"LC_MESSAGES="en_US.UTF-8"LC_PAPER="en_US.UTF-8"LC_NAME="en_US.UTF-8"LC_ADDRESS="en_US.UTF-8"LC_TELEPHONE="en_US.UTF-8"LC_MEASUREMENT="en_US.UTF-8"LC_IDENTIFICATION="en_US.UTF-8"LC_ALL=en_US.UTF-8 {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] [core] (JENKINS-30873) Jenkins reparses all previous build.xml on restart
Title: Message Title
Benoit Sigoure updated an issue
Jenkins / JENKINS-30873
Jenkins reparses all previous build.xml on restart
Change By:
Benoit Sigoure
edit: I originally thought this was related to renaming a project, but this seems to be a general issue when restarting Jenkins. When we upgraded to 1.634 we simply restart Jenkins with the new {{.war}} file and even after 12h it wasn't done parsing the XML files from our tens of thousands of archived builds. We ended up moving all the old build directories out of the way and this immediately resolved the problem for us (we just can't access these old builds anymore, but that's less problematic than Jenkins itself being stuck on certain projects). I renamed a job with the following steps:# Shut down Jenkins# {{mv ~jenkins/job/prevname ~jenkins/job/newname}}# Adjust any other references to the job name# Start Jenkins(It's not the first time I do this and I've never had any issues in the past)This time I renamed a couple jobs with "lots" of previous builds (26k and 5k, respectively). Upon launching the first build for either of these jobs after restarting Jenkins, it was apparent that the build wasn't starting, couldn't be stopped, and was seemingly hung. Checking {{/threadDump}} and doing a bit of {{strace}}'ing showed that Jenkins was loading every single prior {{build.xml}} for these jobs.Common part of the stack trace:{code} at jenkins.model.lazy.LazyBuildMixIn.loadBuild(LazyBuildMixIn.java:158) at jenkins.model.lazy.LazyBuildMixIn$1.create(LazyBuildMixIn.java:135) at hudson.model.RunMap.retrieve(RunMap.java:224) at hudson.model.RunMap.retrieve(RunMap.java:57) at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:465) - locked hudson.model.RunMap@2cedf74 at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:448) at jenkins.model.lazy.AbstractLazyLoadRunMap.getByNumber(AbstractLazyLoadRunMap.java:356) at jenkins.model.lazy.AbstractLazyLoadRunMap.search(AbstractLazyLoadRunMap.java:332) at jenkins.model.lazy.LazyBuildMixIn$RunMixIn.getPreviousBuild(LazyBuildMixIn.java:357) at hudson.model.AbstractBuild.getPreviousBuild(AbstractBuild.java:199) at hudson.model.AbstractBuild.getPreviousBuild(AbstractBuild.java:107) at hudson.plugins.git.GitSCM.getBuildData(GitSCM.java:1553) at hudson.plugins.git.GitSCM.buildEnvVars(GitSCM.java:1161) at hudson.model.AbstractBuild.getEnvironment(AbstractBuild.java:940) at hudson.model.AbstractBuild$AbstractBuildExecution.decideWorkspace(AbstractBuild.java:481) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:521) at hudson.model.Run.execute(Run.java:1741) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:408){code}{{strace}} output:{code}~/jobs/foo-master @sw-pm1.sjc> strace -fp 1964 -e trace='!futex' |& fgrep arista [pid 2216] open("/home/jenkins/jobs/foo-master/builds/6461/build.xml", O_RDONLY) = 506[pid 2216] open("/home/jenkins/jobs/foo-master/builds/6459/build.xml", O_RDONLY) = 500[pid 2216]
[JIRA] [job-dsl-plugin] (JENKINS-31111) DownstreamTriggerParameterContext should be an ExtensibleContext
Title: Message Title Dan Alvizu commented on JENKINS-3 Re: DownstreamTriggerParameterContext should be an ExtensibleContext Mailing list context: https://groups.google.com/forum/#!msg/job-dsl-plugin/qO7asEPCndo/nzwUhAD_BQAJ 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-31109) Template Workspace behaviour does not set workspace Root
Title: Message Title Andrew Barnish created an issue Jenkins / JENKINS-31109 Template Workspace behaviour does not set workspace Root Issue Type: Bug Assignee: Paul Allen Components: p4-plugin Created: 22/Oct/15 5:28 PM Environment: Jenkins ver. 1.625.1 P4 plugin 1.3.2 OS: RHEL 6.4 Java: 1.8.0_60 Labels: p4-plugin Priority: Minor Reporter: Andrew Barnish I'm seeing that when using the "Template" workspace behaviour the workspace "Root:" field is not being set in the generated workspaces. i.e. it is left as "null" and not updated with the proper workspace path
[JIRA] [publish-over-dropbox-plugin] (JENKINS-31112) Apply fix from: "New release of Publish over SSH breaks configure pages"
Title: Message Title René de Groot created an issue Jenkins / JENKINS-31112 Apply fix from: "New release of Publish over SSH breaks configure pages" Issue Type: Bug Assignee: René de Groot Components: publish-over-dropbox-plugin Created: 22/Oct/15 7:21 PM Priority: Blocker Reporter: René de Groot Similar to https://issues.jenkins-ci.org/browse/JENKINS-10268 Fix in https://github.com/rcgroot/jenkins-publish-over-dropbox-plugin/pull/3 Add Comment
[JIRA] [job-dsl-plugin] (JENKINS-31111) DownstreamTriggerParameterContext should be an ExtensibleContext
Title: Message Title
Dan Alvizu created an issue
Jenkins / JENKINS-3
DownstreamTriggerParameterContext should be an ExtensibleContext
Issue Type:
Improvement
Assignee:
Daniel Spilker
Components:
job-dsl-plugin
Created:
22/Oct/15 7:20 PM
Priority:
Minor
Reporter:
Dan Alvizu
I am using the Job DSL plugin on my project. I have a proprietary plugin, part of which is a provider of parameters for the parameterized-trigger plugin. This allows me to trigger a deployment with properties specified by my plugin:
public class MyCustomBuildParameters
extends hudson.plugins.parameterizedtrigger.AbstractBuildParameters
{
// ...
@Extension
public static class DescriptorImpl extends Descriptor
{
// ...
}
}
This works great in the UI - I would like to be able to specify this somehow as part of a job DSL:
job('example') {
publishers {
// ...
downstreamParameterized{
trigger('') {
myCustomParameters()
}
}
}
}
In order to do this, DownstreamTriggerParameterContext needs to be an ExtensibleContext
[JIRA] [cli] (JENKINS-31098) New delete-node CLI command breaks node cleanup in cloud plugins
Title: Message Title Fritz Elfert commented on JENKINS-31098 Re: New delete-node CLI command breaks node cleanup in cloud plugins lgtm - works perfectly 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] [tfs-plugin] (JENKINS-29006) Team Foundation Server Plugin "Local workfolder" variable setting can't use job variables like ${VAR}
Title: Message Title
Will Saxon commented on JENKINS-29006
Re: Team Foundation Server Plugin "Local workfolder" variable setting can't use job variables like ${VAR}
This should ideally be available in all the string parameter fields - server, project path, local workspace, etc.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-31096) Unicode characters in console logs do not print correctly in Workflow builds
Title: Message Title
owenmehegan commented on JENKINS-31096
Re: Unicode characters in console logs do not print correctly in Workflow builds
/systemInfo tells me the encoding is ANSI_X3.4-1968. I get the same failure whether running on the master or other nodes. I am setting LANGUAGE = en_US.UTF-8 and LC_ALL = en_US.UTF-8 in the environment variables config for my build nodes, but not for the master.
Output of 'locale' on the master: {{LANG= LANGUAGE= LC_CTYPE="POSIX" LC_NUMERIC="POSIX" LC_TIME="POSIX" LC_COLLATE="POSIX" LC_MONETARY="POSIX" LC_MESSAGES="POSIX" LC_PAPER="POSIX" LC_NAME="POSIX" LC_ADDRESS="POSIX" LC_TELEPHONE="POSIX" LC_MEASUREMENT="POSIX" LC_IDENTIFICATION="POSIX" LC_ALL=}}
Output of 'locale' on a build node: {{LANG=en_US.UTF-8 LANGUAGE=en_US.UTF-8 LC_CTYPE="en_US.UTF-8" LC_NUMERIC="en_US.UTF-8" LC_TIME="en_US.UTF-8" LC_COLLATE="en_US.UTF-8" LC_MONETARY="en_US.UTF-8" LC_MESSAGES="en_US.UTF-8" LC_PAPER="en_US.UTF-8" LC_NAME="en_US.UTF-8" LC_ADDRESS="en_US.UTF-8" LC_TELEPHONE="en_US.UTF-8" LC_MEASUREMENT="en_US.UTF-8" LC_IDENTIFICATION="en_US.UTF-8" LC_ALL=en_US.UTF-8}}
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-pipeline-plugin] (JENKINS-19121) Build pipeline plugin no longer prompts for parameters of parameterised job
Title: Message Title Bruno Martins commented on JENKINS-19121 Re: Build pipeline plugin no longer prompts for parameters of parameterised job +1 Same problem with Jenkins Jenkins ver. 1.609.2 and Build Pipeline 1.4.8 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.
RE
I have a proposal for you kindly contact me via: mrsyi...@outlook.com * The information in this email and any attachments may contain confidential, privileged or copyright material belonging to us, related entities or third parties. If you are not the intended recipient you are prohibited from disclosing this information. If you have received this email in error, please contact the sender immediately by return email or phone and delete it. We apologise for any inconvenience caused. We use security software but do not guarantee this email is free from viruses. You assume responsibility for any consequences arising from the use of this email. This email may contain personal views of the sender not authorised by us. * -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-31108) Git-Publisher should allow to push tags from a shallow clone
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-31108 Git-Publisher should allow to push tags from a shallow clone Change By: Mark Waite Assignee: Mark Waite 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-31108) Git-Publisher should allow to push tags from a shallow clone
Title: Message Title Mark Waite commented on JENKINS-31108 Re: Git-Publisher should allow to push tags from a shallow clone So long as your pull request includes tests to show the problem, and follows the guidelines in CONTRIBUTING.md, I'm willing to consider that change of behavior. If you're not willing to write tests, please don't submit the pull request. Pull requests without tests are frustrating because they assume the plugin developer will repeatedly (interactively) verify the changed behavior at each plugin release. 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-30873) Jenkins reparses all previous build.xml on restart
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-30873 Jenkins reparses all previous build.xml on restart The current Jenkins design basically relies on plugins not requiring to load an excessive number of builds to not defeat lazy loading of build records. It looks like the Git Plugin is responsible in this case. Note that some of this can be prevented through enough RAM (to prevent GC and discarding of already loaded build records) and fast disks; but if the problem only occurs once per job after startup, the former won't help much. Change By: Daniel Beck Component/s: git-plugin Component/s: 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
[JIRA] [tfs-plugin] (JENKINS-31110) Support credentials plugin
Title: Message Title Will Saxon created an issue Jenkins / JENKINS-31110 Support credentials plugin Issue Type: Improvement Assignee: redsolo Components: tfs-plugin Created: 22/Oct/15 5:31 PM Priority: Minor Reporter: Will Saxon As a user, I would like the tfs plugin to support the credentials plugin, so I can store my credentials in one location and share them amongst my jobs. Add Comment This message was sent by Atlassian JIRA
[JIRA] [build-pipeline-plugin] (JENKINS-28478) Build Pipeline plugin loses track of upstream build when retrying of a failed build
Title: Message Title John Martel commented on JENKINS-28478 Re: Build Pipeline plugin loses track of upstream build when retrying of a failed build Got the same issue here. Build number is not updated in the pipeline view for the "failed-then-successful" job and the backgrouond stays red. 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] [ant-plugin] (JENKINS-31114) Ant escape incorrectly on Windows
Title: Message Title Ruan Berg created an issue Jenkins / JENKINS-31114 Ant escape incorrectly on Windows Issue Type: Bug Assignee: Unassigned Components: ant-plugin, copyartifact-plugin Created: 22/Oct/15 7:46 PM Environment: Windows Server 2012, Windows 7 Jenkins 1.634 Ant plugin 1.2 copyartifact plugin 1.36.1 chrome browser, IE 11 browser Priority: Major Reporter: Ruan Berg Using BuildSelector to give a specific build number the CopyArtifact plugin step works fine. In a later step we run an ant script to deploy the artifacts in deploy job workspace now. The Ant generated parameter that appears to cause problem is "-DTARGET_BUILD= 66" When runs gets error Target "66 -DBUILD_USER=" does not exist in the project This prevents running deploy job. The same deploy job running on Jenkins 1.476 and CopyArtifact plugin 1.29 and Ant 1.1 works. We are attempting to upgrade to a newer version of Jenkins and all the newer version use ant 1.2.
[JIRA] [git-plugin] (JENKINS-31108) Git-Publisher should allow to push tags from a shallow clone
Title: Message Title Jarek Lipski created an issue Jenkins / JENKINS-31108 Git-Publisher should allow to push tags from a shallow clone Issue Type: Improvement Assignee: Mark Waite Components: git-plugin Created: 22/Oct/15 5:25 PM Priority: Minor Reporter: Jarek Lipski Git-Publisher should allow to push tags / branches from a shallow clone. New Git versions (1.9.0+) allow pushing tags from shallow clone (see here and here for example), but latest version of Git-Publisher still forbids this (see source code). It prints the following message, but it does not fail the build: GitPublisher disabled while using shallow clone. I could propose a pull request to resolve this ticket in the coming days. My solution would be to try to push the tag, and show a reasonably nice error message if it fails due to old Git version. This behavior is slightly different than the current one, because currently job succeeds. What do you think?
[JIRA] [core] (JENKINS-31115) Build Time Trend shows deleted job runs - 404 error
Title: Message Title Kevin Neufeld created an issue Jenkins / JENKINS-31115 Build Time Trend shows deleted job runs - 404 error Issue Type: Bug Assignee: Unassigned Components: core Created: 22/Oct/15 8:02 PM Environment: Version: 1.634, clean install, default plugins. Labels: build time trend Priority: Minor Reporter: Kevin Neufeld Summary: the Build Time Trend shows portions for deleted job runs. Clicking on a section pertaining to a deleted job results in a 404 error. Steps to recreate: create a new job run job, say 5 times
[JIRA] [cli] (JENKINS-31098) New delete-node CLI command breaks node cleanup in cloud plugins
Title: Message Title Pavel Janoušek commented on JENKINS-31098 Re: New delete-node CLI command breaks node cleanup in cloud plugins Hello, as the author of that change I can fix the behavior and delegate deletion of computer back to Computer.doDoDelete(). It should solve your issue. Working on 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] [workflow-plugin] (JENKINS-31100) Workflow Job has no git submodule options
Title: Message Title Marcus Cobden created an issue Jenkins / JENKINS-31100 Workflow Job has no git submodule options Issue Type: Improvement Assignee: Jesse Glick Components: workflow-plugin Created: 22/Oct/15 9:19 AM Priority: Minor Reporter: Marcus Cobden I'd like to request recursive submodule checkout on my git repo, but there doesn't seem to be an option. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [maven-plugin] (JENKINS-4561) "Delete All Disabled Modules" Not visible for project users
Title: Message Title Michael Prankl commented on JENKINS-4561 Re: "Delete All Disabled Modules" Not visible for project users Have you tried "http://hudson-installation/job/the-project/doDeleteAllDisabledModules"? The web method is called "doDoDeleteAllDisabledModules", maybe this should be fixed? source: https://github.com/jenkinsci/maven-plugin/blob/master/src/main/java/hudson/maven/MavenModuleSet.java#L1237 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cli] (JENKINS-31098) New delete-node CLI command breaks node cleanup in cloud plugins
Title: Message Title Fritz Elfert commented on JENKINS-31098 Re: New delete-node CLI command breaks node cleanup in cloud plugins Thanks Pavel Janoušek, I will have a look this evening. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cli] (JENKINS-30521) Extract reload-job CLI command from Core to CLI
Title: Message Title Pavel Janoušek resolved as Fixed Jenkins / JENKINS-30521 Extract reload-job CLI command from Core to CLI Change By: Pavel Janoušek 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] [build-pipeline-plugin] (JENKINS-25427) Build Pipeline Plugin no longer allows starting build with parameters
Title: Message Title Anentropic commented on JENKINS-25427 Re: Build Pipeline Plugin no longer allows starting build with parameters This is broken for me in plugin v1.4.7 using Chrome OSX when I click the Run button in the build pipeline view, nothing happens I'd like to be able to start a job with parameters Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-pipeline-plugin] (JENKINS-25427) Build Pipeline Plugin no longer allows starting build with parameters
Title: Message Title Anentropic edited a comment on JENKINS-25427 Re: Build Pipeline Plugin no longer allows starting build with parameters This is broken for me in plugin v1.4.7 using Chrome OSXwhen I click the Run button in the build pipeline view, nothing happensI'd like to be able to start a job with parameters upgraded to v1.4.8, still broken 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] [performance-plugin] (JENKINS-28284) Images for Test Case trends is broken and generate exception
Title: Message Title inbar rose updated an issue Jenkins / JENKINS-28284 Images for Test Case trends is broken and generate exception Another example. All images are broken here. But when pressing on their link, the images work. Change By: inbar rose Attachment: Capture.jenkinserr2.PNG Attachment: Capture.jenkinserr.PNG Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [matrix-project-plugin] (JENKINS-31116) Upgrade of Jenkins from 1.466.1 to 1.609.1 causing dead locks and assigning lower build number than the existing build number.
Title: Message Title Kishore K created an issue Jenkins / JENKINS-31116 Upgrade of Jenkins from 1.466.1 to 1.609.1 causing dead locks and assigning lower build number than the existing build number. Issue Type: Bug Assignee: Kohsuke Kawaguchi Components: matrix-project-plugin Created: 22/Oct/15 8:39 PM Environment: Jenkins and Nexus Labels: jenkins Priority: Critical Reporter: Kishore K We recently added two new jenkins servers with the version 1.609.1. We copied the jobs from the old jenkins servers(version 1.466.1). on RHEL 6. When we run the jobs on the new servers we are seeing dead build executors and the following error:java.lang.IllegalStateException: cannot create a build with number 33241 since that (or higher) is already in use among [33144, 33145, 33146, 33147, 33148, 33149, 33150, 33151, 33152, 33153, 33154, 33155, 33156, 33157, 33158, 33159, 33160, 33161, 33162, 33163, 33164, 33165, 33166, 33167, 33168, 33169, 33170, 33171, 33172, I as trying to find a
[JIRA] [matrix-project-plugin] (JENKINS-31116) Upgrade of Jenkins from 1.466.1 to 1.609.1 causing dead locks and assigning lower build number than the existing build number.
Title: Message Title Kishore K commented on JENKINS-31116 Re: Upgrade of Jenkins from 1.466.1 to 1.609.1 causing dead locks and assigning lower build number than the existing build number. hello..Kohsuke Kawaguchi..I've seen some of your posts related to similar issue but none of them actually worked for me. Here are some of the steps I tried as per your suggestion in other posts: 1) deleted the symlink and restarted Jenkins- but no success 2) Increased the build executor count- still no success 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] [ec2-plugin] (JENKINS-30208) Can't launch spot slave instance with aws-java-sdk 1.10.*
Title: Message Title Lee Hicks commented on JENKINS-30208 Re: Can't launch spot slave instance with aws-java-sdk 1.10.* Can confirm compiling prior to AWS SDK 1.10 is working great. 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-31096) Unicode characters in console logs do not print correctly in Workflow builds
Title: Message Title Jesse Glick commented on JENKINS-31096 Re: Unicode characters in console logs do not print correctly in Workflow builds So your master is set to use ASCII, meaning it cannot process such characters in files at all. The workaround is to set your master to use UTF-8 encoding, as virtually all modern Linux distributions do. If you cannot set it systemwide, I think you can run the Jenkins Java process with -Dfile.encoding=UTF-8. Now I have had a debate with Kohsuke Kawaguchi about this but we do not see eye to eye. His perspective is that Jenkins should always store log files in the system native encoding, which I think is mainly useful for Japanese users who are accustomed to using one of the two or three traditional encodings in that country; it is only helpful if you are directly accessing the log file from the filesystem (over the web in console it is rendered according to the encoding of the browser, or the REST client in the case of consoleText). My position is that all text files stored by Jenkins should be in UTF-8; external processes forked on a slave can be assumed to produce output in the system native encoding, which should then be recoded internally to UTF-8. Now the twist here is freestyle vs. Workflow. In the case of a freestyle build, the system encoding on the slave is noted when the build starts, recorded as part of the build record, and used to save the log. That allows the build to handle varying encodings in one CI server. But such a trick is impossible for Workflow, which starts the build and then gets a slave, or several, or none. So it cannot use a slave-specific charset. It could either use the master’s charset, as it currently does (meaning it cannot track output from slaves using a charset which is a superset of that); or it could use UTF-8 unconditionally, which might be a better idea (though I would need some flag to indicate old build logs saved in another character set). In either case, process output should probably be recoded to that expected by the build log. This is devilishly hard to prove in an automated test, I am afraid. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [core] (JENKINS-31115) Build Time Trend shows deleted job runs - 404 error
Title: Message Title Kevin Neufeld updated an issue Jenkins / JENKINS-31115 Build Time Trend shows deleted job runs - 404 error Change By: Kevin Neufeld Attachment: 2015-10-22_152357.png 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-31107) ReverseProxySetupMonitor broken with prefix
Title: Message Title Daniel Beck commented on JENKINS-31107 Re: ReverseProxySetupMonitor broken with prefix Did you configure the URL to Jenkins properly in the global configuration (it must include the prefix)? 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-31115) Build Time Trend shows deleted job runs - 404 error
Title: Message Title Kevin Neufeld commented on JENKINS-31115 Re: Build Time Trend shows deleted job runs - 404 error Before and after. View the build time trend, delete a build run while viewing the build time trend. Trend history logs are correctly removed, but the graph is not. Restart Jenkins, close browser and view build time trend again. Same thing, graph shows removed runs. 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-31107) ReverseProxySetupMonitor broken with prefix
Title: Message Title Daniel Beck commented on JENKINS-31107 Re: ReverseProxySetupMonitor broken with prefix No. 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-31089) Signature verification failed in update site 'default'
Title: Message Title Daniel Beck commented on JENKINS-31089 Re: Signature verification failed in update site 'default' I wonder whether this in the patch notes is related: MD5 must not be used for digital signatures where collision resistance is required. In order to prevent the usage of MD5 as digital signature algorithm during X.509 certificate operations, MD5 is added to jdk.certpath.disabledAlgorithms security property. For those applications that still using MD5 signed certificate, please upgrade the weak certificate as soon as possible. Unfortunately it doesn't look like we have an MD5 cert… Could you tell me the contents of the file jre/lib/security/java.security (should be /Library/Java/JavaVirtualMachines/jdk1.8.0_XX.jdk/Contents/Home/jre/lib/security/java.security on OS X), specifically the entries jdk.certpath.disabledAlgorithms and jdk.tls.disabledAlgorithms? Could you try to change this property to see whether it works then by removing one of the values? 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-31102) Signature verification failed in update site
Title: Message Title Daniel Beck commented on JENKINS-31102 Re: Signature verification failed in update site Which version of Java was installed before? 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-31102) Signature verification failed in update site
Title: Message Title Daniel Beck resolved as Duplicate Appears to be a duplicate of JENKINS-31089. Jenkins / JENKINS-31102 Signature verification failed in update site Change By: Daniel Beck Status: Open Resolved Resolution: Duplicate 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] [literate] (JENKINS-30780) Natively support project embedded plugin, build, continuous delivery configuration
Title: Message Title Levon Karayan commented on JENKINS-30780 Re: Natively support project embedded plugin, build, continuous delivery configuration Yes it is a candidate for 2.0, it's to make the philosophy of the literate plugin be tightly integrated with jenkins core (so overrides can happen from the server) workflows and all. If it's not the right place I can move it, if you don't want to. 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] [literate] (JENKINS-30780) Natively support project embedded plugin, build, continuous delivery configuration
Title: Message Title Levon Karayan updated an issue Jenkins / JENKINS-30780 Natively support project embedded plugin, build, continuous delivery configuration Change By: Levon Karayan Labels: 2.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-26130) Print progress of pending pickles
Title: Message Title Jesse Glick commented on JENKINS-26130 Re: Print progress of pending pickles A hard kill from JENKINS-25550 works around it. Still, should behave better: should show what it is trying to resume, and a regular interruption should stop that. Currently you are given no information, and have to escalate from a regular interrupt, to a step termination, to a hard kill, and then also separately kill the unschedulable queue item. By the design of pickle resolution, we cannot really recover the build, unfortunately. I argued during the initial design of Workflow that the node step’s state should include just the slave name and workspace path, and its onResume should be responsible for trying to get that workspace back (so that this step could handle stop gracefully, for example by throwing an exception up that the script could catch and handle); but Kohsuke Kawaguchi overrode me, insisting that the serialized program state should include a representation of the FilePath, and that script execution shall not resume until that pickle is successfully dehydrated (even if there were other branches able to proceed, etc.). So the best we can do is display more clearly what is wrong and offer a hard kill right away. W.r.t. to the queue item, PlaceholderTask.run can tell via StepContext.isReady that it is still being unpickled, but it cannot use that to differentiate the case of a normal startup when we are waiting for a sluggish slave to come back online; it cannot even find the Run to tell whether it was already aborted, since it cannot call get yet. Probably it will need to persist a Run.externalizableId to implement run, and use that also instead of accessControlled. If the Run turns out to be finished, it could use Queue.getItems(Task) to cancel itself, so that cleanup from the whole process reduces to pressing the stop button once on the console page or on the flyweight executor in the executor widget. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the
[JIRA] [core] (JENKINS-31115) Build Time Trend shows deleted job runs - 404 error
Title: Message Title Daniel Beck commented on JENKINS-31115 Re: Build Time Trend shows deleted job runs - 404 error Was the build time trend page most recently loaded before or after the build was deleted? How specifically is the build deleted? 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] [sauce-ondemand-plugin] (JENKINS-30065) SELENIUM_PLATFORM not always properly set when using Matrix Axis -> Sauce Labs WebDriver tests
Title: Message Title Gavin Mogan assigned an issue to Gavin Mogan Jenkins / JENKINS-30065 SELENIUM_PLATFORM not always properly set when using Matrix Axis -> Sauce Labs WebDriver tests Change By: Gavin Mogan Assignee: Kohsuke Kawaguchi Gavin Mogan 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-27624) Upgrade minimum require Java version from 7 to 8
Title: Message Title Kohsuke Kawaguchi updated an issue Jenkins / JENKINS-27624 Upgrade minimum require Java version from 7 to 8 Change By: Kohsuke Kawaguchi Labels: 2.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] [websphere-deployer-plugin] (JENKINS-30991) Websphere deployer plugin - Unable to connect
Title: Message Title Greg Peters closed an issue as Won't Fix The default soap port is not 9043, this is typically the admin console port. Try port 8880 or login to your admin console and view the SOAP port under "Application Servers"->"Ports" Jenkins / JENKINS-30991 Websphere deployer plugin - Unable to connect Change By: Greg Peters Status: Open Closed Assignee: Greg Peters 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
[JIRA] [git-plugin] (JENKINS-30873) Jenkins' Git plugin reparses all previous build.xml on restart
Title: Message Title Benoit Sigoure updated an issue Jenkins / JENKINS-30873 Jenkins' Git plugin reparses all previous build.xml on restart Change By: Benoit Sigoure Summary: Jenkins ' Git plugin reparses all previous build.xml on restart 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] [sauce-ondemand-plugin] (JENKINS-30065) SELENIUM_PLATFORM not always properly set when using Matrix Axis -> Sauce Labs WebDriver tests
Title: Message Title Gavin Mogan assigned an issue to Andrew Campbell Jenkins / JENKINS-30065 SELENIUM_PLATFORM not always properly set when using Matrix Axis -> Sauce Labs WebDriver tests Change By: Gavin Mogan Assignee: Gavin Mogan Andrew Campbell 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] [stashnotifier-plugin] (JENKINS-31117) Plugin should be able to accept a Token Macro
Title: Message Title Michael Fowler updated an issue Jenkins / JENKINS-31117 Plugin should be able to accept a Token Macro Change By: Michael Fowler Attachment: screenshot-1.png 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] [stashnotifier-plugin] (JENKINS-31117) Plugin should be able to accept a Token Macro
Title: Message Title Michael Fowler created an issue Jenkins / JENKINS-31117 Plugin should be able to accept a Token Macro Issue Type: Improvement Assignee: Pavel Batanov Components: stashnotifier-plugin Created: 22/Oct/15 11:33 PM Priority: Minor Reporter: Michael Fowler It would be nice if a token macro could be used by the plugin. See screenshot. https://wiki.jenkins-ci.org/display/JENKINS/Token+Macro+Plugin Add Comment This message was sent
[JIRA] [sauce-ondemand-plugin] (JENKINS-30064) Optionally retry Sauce Connect failures when not related to credentials
Title: Message Title Andrew Campbell assigned an issue to Andrew Campbell Jenkins / JENKINS-30064 Optionally retry Sauce Connect failures when not related to credentials Change By: Andrew Campbell Assignee: Kohsuke Kawaguchi Andrew Campbell 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-31102) Signature verification failed in update site
Title: Message Title Jason Wooster commented on JENKINS-31102 Re: Signature verification failed in update site Yes, this appears to be caused by the jdk1.8.0_65 update. Rolling back to jdk1.8.0_60 fixes 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] [sauce-ondemand-plugin] (JENKINS-30778) Sauce Labs Test Publisher Configuration
Title: Message Title Andrew Campbell assigned an issue to Andrew Campbell Jenkins / JENKINS-30778 Sauce Labs Test Publisher Configuration Change By: Andrew Campbell Assignee: Kohsuke Kawaguchi Andrew Campbell 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-31118) Workflow jobs that are waiting for input should have a visual cue in build history
Title: Message Title owenmehegan created an issue Jenkins / JENKINS-31118 Workflow jobs that are waiting for input should have a visual cue in build history Issue Type: New Feature Assignee: Jesse Glick Components: workflow-plugin Created: 22/Oct/15 11:58 PM Labels: workflow Priority: Minor Reporter: owenmehegan When a Workflow job is waiting for input, the current visual cue for that is that the ball blinks when you look at the job history. It doesn't blink on the main Jenkins job list page. Further, if you restart Jenkins, the ball for paused jobs stops blinking even though they're still paused and can be resumed. I'm not a fan of the blinking ball visual cue because all of my users keep seeing that and thinking their jobs are "stuck" or "still building" or whatever. I think we need a special badge or ball color or something to make it clear that the job is in the 'waiting for input' state. It would also be ideal if this was visible on the Jenkins main page as well.
[JIRA] [workflow-plugin] (JENKINS-31096) Unicode characters in console logs do not print correctly in Workflow builds
Title: Message Title
owenmehegan edited a comment on JENKINS-31096
Re: Unicode characters in console logs do not print correctly in Workflow builds
FWIW, even setting it systemwide using locale didn't fix this, I had to add {{-Dfile.encoding=UTF-8}} to my java arguments. Now my logs display nicely. Thanks for the explanation!
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-31096) Unicode characters in console logs do not print correctly in Workflow builds
Title: Message Title owenmehegan commented on JENKINS-31096 Re: Unicode characters in console logs do not print correctly in Workflow builds FWIW, even setting it systemwide using locale didn't fix this, I had to add -Dfile.encoding=UTF-8 to my java arguments. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cli] (JENKINS-31098) New delete-node CLI command breaks node cleanup in cloud plugins
Title: Message Title Fritz Elfert commented on JENKINS-31098 Re: New delete-node CLI command breaks node cleanup in cloud plugins Yes, clicking the Delete button still works of course. However we almost never do that manually What we do here (In jclouds, I implemented a CLI cmd for launching new nodes) from inside a job: jclouds-provision SomeTemplateName (blocks until ready and returns IP-Address and Nodename) invoke parameterized integration test job delete-node TheNodeNameFromAbove <<< At this point we now end up with an unused VM since 1.625.1 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cli] (JENKINS-31098) New delete-node CLI command breaks node cleanup in cloud plugins
Title: Message Title Pavel Janoušek assigned an issue to Pavel Janoušek Jenkins / JENKINS-31098 New delete-node CLI command breaks node cleanup in cloud plugins Change By: Pavel Janoušek Assignee: Pavel Janoušek Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cli] (JENKINS-31098) New delete-node CLI command breaks node cleanup in cloud plugins
Title: Message Title Fritz Elfert commented on JENKINS-31098 Re: New delete-node CLI command breaks node cleanup in cloud plugins Oliver Gondža Nope, jclouds itself does not block during deletion - Well not for the duration of the deletion, only for the time it takes to send the POST. I always assumed that the delay ist due to the Channel object needing time to shutdown. About having a separate reference: I thought about that before, but there is one big disadvantage. Since the node is not persisted anymore at that point, we might still end up with stray VMs if jenkins is restarted during that 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] [xunit-plugin] (JENKINS-31101) XUnit is not rendering the test result summary correctly for a Custom tool
Title: Message Title Daniel MS updated an issue Jenkins / JENKINS-31101 XUnit is not rendering the test result summary correctly for a Custom tool Change By: Daniel MS Hello,I have a custom tool that generates a report xml file that normally follows the expected format for the XUnit report. But Whenever I click on the summary icon nothing is displayed but the error message "not found".For some reason Jenkins is expecting other files besides the Xunit report.Attached you will find # the report generated for Xunit *.zip# the list of plugins installed in Jenkins# images of the configuration and the problem of the summary The test tool already generates the report in the output format , the xsl style sheet only copies the content as is thanks in advance for your help 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] [xunit-plugin] (JENKINS-31101) XUnit is not rendering the test result summary correctly for a Custom tool
Title: Message Title
Daniel MS updated an issue
Jenkins / JENKINS-31101
XUnit is not rendering the test result summary correctly for a Custom tool
Change By:
Daniel MS
Environment:
Jenkins ver. 1.626{code} true1.94falsefalsetruetruetruexUnit pluginfalsexunitMAYBEhttp://wiki.jenkins-ci.org/display/JENKINS/xUnit+Plugin1.96{code}
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-30678) java.lang.OutOfMemoryError: PermGen space
Title: Message Title Abdul Baki closed an issue as Not A Defect Please see comments for further explanation - I was able to remedy the problem by increasing PermGen memory and verified it was due to the size of my jenkins deployment using the monitoring tool. Jenkins / JENKINS-30678 java.lang.OutOfMemoryError: PermGen space Change By: Abdul Baki Status: Open Closed Assignee: Abdul Baki Resolution: Not A Defect 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] [p4-plugin] (JENKINS-31062) Execute permission not set on files which have +x in perforce depot
Title: Message Title Paul Allen commented on JENKINS-31062 Re: Execute permission not set on files which have +x in perforce depot I confirmed the issue on Ubuntu. It seems to be a Linux related issue in the underlying API (p4java). 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] [xunit-plugin] (JENKINS-31101) XUnit is not rendering the test result summary correctly for a Custom tool
Title: Message Title Daniel MS updated an issue Jenkins / JENKINS-31101 XUnit is not rendering the test result summary correctly for a Custom tool Change By: Daniel MS 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] [cli] (JENKINS-31098) New delete-node CLI command breaks node cleanup in cloud plugins
Title: Message Title Pavel Janoušek commented on JENKINS-31098 Re: New delete-node CLI command breaks node cleanup in cloud plugins PR sent. 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-30678) java.lang.OutOfMemoryError: PermGen space
Title: Message Title Abdul Baki commented on JENKINS-30678 Re: java.lang.OutOfMemoryError: PermGen space I added more memory for the Permanent Generation memory (via /etc/default/jenkins - updated the JAVA_ARGS parameter) and also installed the monitoring plugin. This let me monitor the memory consumption for both heap, non-heap memory, and garbage collection intervals. By collecting the data I was able to confirm that the cause of PermGen OOM was due to the size of my jenkins deployment rather than a memory leak or an issue with a plugin or a core component. The problem with PermGen isn't present in Java 8 due to the removal PermGen and use of a cache memory system that doesn't have a predefined maximum. Therefore there might be an option to upgrade Java or to increase the memory allocation for Jenkins and monitor the memory to ensure that there isn't an underlying problem with a memory leak or garbage collection. As this problem is no longer affecting me I am closing this defect Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cli] (JENKINS-31098) New delete-node CLI command breaks node cleanup in cloud plugins
Title: Message Title
Oliver Gondža edited a comment on JENKINS-31098
Re: New delete-node CLI command breaks node cleanup in cloud plugins
As far as I can tell, only CLI sis is affected as it does no loner delegates to the UI method. Deleting from UI or the JCLouds JClouds cleanup thread should still work.While I agree with Oleg that this is rather hackish, I see no other way to politely ask computer-slave pair to terminate when ready. I propose to document this purpose of {{Computer#doDoDelete()}} and fix the {{delete-node}} implementation to call that method again.
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] [github-plugin] (JENKINS-27041) Thousands of threads created by thousands of GitHub pushes
Title: Message Title Kirill Merkushev commented on JENKINS-27041 Re: Thousands of threads created by thousands of GitHub pushes points to not use notifyCommit: 1. It breaks all existing setups (you should explicitly enable scm trigger, which usually not enabled) 2. If you don't want to trigger job by notifyCommit you should explicitly turn it off with additional git behaviour option (most of people don't know about this option) - it maybe in case of nightly builds, when we check git only at exact time to start heavy build. so it should be implemented without notifyCommit. Maybe we should use GH events api to poll state changing Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cli] (JENKINS-31098) New delete-node CLI command breaks node cleanup in cloud plugins
Title: Message Title Oliver Gondža commented on JENKINS-31098 Re: New delete-node CLI command breaks node cleanup in cloud plugins Fritz Elfert if I am not mistaken, the delayed machine termination is in place not to block the thread while sending remote request to cloud service. In theory, we can try not to rely on slave being offline but remove it immediately and keep the reference to the cloud machine elsewhere for the collector thread. I lean towards fixing this in core as there might be different plugins affected. 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] [xunit-plugin] (JENKINS-31101) XUnit is not rendering the test result summary correctly for a Custom tool
Title: Message Title
Daniel MS created an issue
Jenkins / JENKINS-31101
XUnit is not rendering the test result summary correctly for a Custom tool
Issue Type:
Bug
Assignee:
Gregory Boissinot
Attachments:
2015-10-22 11_24_36-OP_Cellar #1932 Test Results [Jenkins].png, 2015-10-22 11_24_58-OP_Cellar Config [Jenkins].png, generatedJUnitFiles.zip, plugins.xml
Components:
xunit-plugin
Created:
22/Oct/15 9:30 AM
Environment:
Jenkins ver. 1.626 {code} true 1.94 false false true true true xUnit plugin false xunit MAYBE http://wiki.jenkins-ci.org/display/JENKINS/xUnit+Plugin/url> 1.96 {code}
Priority:
Minor
Reporter:
Daniel MS
Hello, I have a custom tool that generates a report xml file that normally follows the expected format for the XUnit report. But Whenever I click on the summary icon nothing is displayed but the error message "not found". For some reason Jenkins is expecting other files besides the Xunit report.
[JIRA] [xunit-plugin] (JENKINS-31101) XUnit is not rendering the test result summary correctly for a Custom tool
Title: Message Title
Daniel MS updated an issue
Jenkins / JENKINS-31101
XUnit is not rendering the test result summary correctly for a Custom tool
Change By:
Daniel MS
Hello,I have a custom tool that generates a report xml file that normally follows the expected format for the XUnit report. But Whenever I click on the summary icon nothing is displayed but the error message "not found".For some reason Jenkins is expecting other files besides the Xunit report.Attached you will find # the report generated for Xunit *.zip# the list of plugins installed in Jenkins# images of the configuration and the problem of the summaryThe test tool already generates the report in the output format , the xsl style sheet only copies the content as is . Jenkins ver. 1.626{code} true1.94falsefalsetruetruetruexUnit pluginfalsexunitMAYBEhttp://wiki.jenkins-ci.org/display/JENKINS/xUnit+Plugin1.96{code} thanks in advance for your help
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] [jobcopy-builder-plugin] (JENKINS-31091) Promotions not copied to new job
Title: Message Title ikedam resolved as Not A Defect Use "Additional File Sets" in the advanced section. https://github.com/jenkinsci/jobcopy-builder-plugin/blob/master/src/main/resources/jp/ikedam/jenkins/plugins/jobcopy_builder/JobcopyBuilder/help-additionalFilesetList.html Jenkins / JENKINS-31091 Promotions not copied to new job Change By: ikedam Status: Open Resolved Assignee: Oleg Nenashev ikedam Resolution: Not A Defect 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
[JIRA] [maven-plugin] (JENKINS-4561) "Delete All Disabled Modules" Not visible for project users
Title: Message Title podskalsky updated an issue Jenkins / JENKINS-4561 "Delete All Disabled Modules" Not visible for project users Change By: podskalsky Attachment: screenshot-1.png 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-4561) "Delete All Disabled Modules" Not visible for project users
Title: Message Title podskalsky commented on JENKINS-4561 Re: "Delete All Disabled Modules" Not visible for project users Now there is no error message, but at "http://hudson-installation/job/the-project/build-number" there is still a list of disabled/removed modules 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] [jira-plugin] (JENKINS-30682) JIRA ticket creation failing with java.lang.NullPointerException
Title: Message Title Sandro Cirulli commented on JENKINS-30682 Re: JIRA ticket creation failing with java.lang.NullPointerException I attach the following screenshots: JIRA configuration. This shows a success when I validate the settings (I confirm this works properly, if I try a non-existing URL or user I get an error). Build changelog. This works correctly, I am able to see the link to a JIRA ticket. Build job configuration with my JIRA project key and assignee. Build error message with jira plugin version 2.0.2. I let a test fails on purpose in order to create a JIRA issue but this fails with the NullPointerException error message. Build error message with jira plugin version 1.41. Same type of error message. My account does not have admin rights on JIRA but I am allowed to create a ticket on my JIRA instance. Unable to render embedded object: File (jira_configuration.png) not found. 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
[JIRA] [jira-plugin] (JENKINS-30682) JIRA ticket creation failing with java.lang.NullPointerException
Title: Message Title
Radek Antoniuk updated an issue
Jenkins / JENKINS-30682
JIRA ticket creation failing with java.lang.NullPointerException
Change By:
Radek Antoniuk
Having an issue getting the plugin to create a JIRA ticket. See the configuration screenshots attached for how I've got it setup.The error I'm getting is during a failed build is: {code} Recording test resultsERROR: Build step failed with exceptionjava.lang.NullPointerExceptionat hudson.plugins.jira.JiraSession.createIssue(JiraSession.java:310)at hudson.plugins.jira.JiraCreateIssueNotifier.createJiraIssue(JiraCreateIssueNotifier.java:153)at hudson.plugins.jira.JiraCreateIssueNotifier.currentBuildResultFailure(JiraCreateIssueNotifier.java:343)at hudson.plugins.jira.JiraCreateIssueNotifier.perform(JiraCreateIssueNotifier.java:115)at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:45)at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:779)at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:726)at hudson.model.Build$BuildExecution.post2(Build.java:185)at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:671)at hudson.model.Run.execute(Run.java:1766)at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)at hudson.model.ResourceController.execute(ResourceController.java:98)at hudson.model.Executor.run(Executor.java:408)Build step 'Create Jira Issue' marked build as failure {code} If I call our JIRA rest API from the server I can create an issue just fine. {code} curl -D- -u username:password -X POST --data @data.txt -H "Content-Type: application/json" https://destinationnsw.atlassian.net/rest/api/2/issue/ {code} data.txt contains: {code} {"fields": { "project": { "key": "BUGS" }, "summary": "REST ye merry gentlemen.", "description": "Creating of an issue using project keys", "issuetype": { "name": "Bug" } }} {code} I get "HTTP/1.1 201 Created" and the ticket is available.
Add Comment
[JIRA] [workflow-plugin] (JENKINS-31096) Unicode characters in console logs do not print correctly in Workflow builds
Title: Message Title Jesse Glick commented on JENKINS-31096 Re: Unicode characters in console logs do not print correctly in Workflow builds Probably dependent on system encoding. I do not recall ever testing with anything other than UTF-8. Are you using a slave? If so, does its encoding match that of the master, or differ? Use the locale command to check. Also from /systemInfo in Jenkins you can see the file.encoding according to Java. 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] [github-plugin] (JENKINS-31103) How to troubleshoot maximum number of statuses errors?
Title: Message Title
Michael Grünewald updated an issue
Jenkins / JENKINS-31103
How to troubleshoot maximum number of statuses errors?
Change By:
Michael Grünewald
We are using Jenkins in conjunction with GitHub. Sometimes the tests are failing with the following exception:{{Sep 10, 2015 7:19:35 AM hudson.model.AbstractBuild$AbstractBuildExecution reportErrorWARNING: Publisher 'Set build status on GitHub commit' aborted due to exception: java.io.IOException: {"message":"Validation Failed","errors":[{"resource":"Status","code":"custom","message":"This SHA and context has reached the maximum number of statuses."}],"documentation_url":"https://developer.github.com/v3/repos/statuses/#create-a-status"}at org.kohsuke.github.Requester.handleApiError(Requester.java:493)at org.kohsuke.github.Requester._to(Requester.java:245)at org.kohsuke.github.Requester.to(Requester.java:191)at org.kohsuke.github.GHRepository.createCommitStatus(GHRepository.java:774)at com.cloudbees.jenkins.GitHubCommitNotifier.updateCommitStatus(GitHubCommitNotifier.java:127)at com.cloudbees.jenkins.GitHubCommitNotifier.perform(GitHubCommitNotifier.java:84)at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) }}The error message seems to report the error details sent back by the GitHub RPC endpoint, stating that Jenkins tried to update more than 1000 times the statuses associated to a given SHA or “context”. Since we have a hand of different tests, it is strange to hit that 1000 limit.How to more precisely diagnose this (non-fatal) error and figure out what is causing that limit to be hit?
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [github-plugin] (JENKINS-31103) How to troubleshoot maximum number of statuses errors?
Title: Message Title
Michael Grünewald created an issue
Jenkins / JENKINS-31103
How to troubleshoot maximum number of statuses errors?
Issue Type:
Bug
Assignee:
Kanstantsin Shautsou
Components:
github-plugin
Created:
22/Oct/15 1:12 PM
Labels:
github api limit
Priority:
Minor
Reporter:
Michael Grünewald
We are using Jenkins in conjunction with GitHub. Sometimes the tests are failing with the following exception:
{{Sep 10, 2015 7:19:35 AM hudson.model.AbstractBuild$AbstractBuildExecution reportError WARNING: Publisher 'Set build status on GitHub commit' aborted due to exception: java.io.IOException: {"message":"Validation Failed","errors":[ {"resource":"Status","code":"custom","message":"This SHA and context has reached the maximum number of statuses."}
],"documentation_url":"https://developer.github.com/v3/repos/statuses/#create-a-status"} at org.kohsuke.github.Requester.handleApiError(Requester.java:493) at org.kohsuke.github.Requester._to(Requester.java:245) at org.kohsuke.github.Requester.to(Requester.java:191) at org.kohsuke.github.GHRepository.createCommitStatus(GHRepository.java:774) at com.cloudbees.jenkins.GitHubCommitNotifier.updateCommitStatus(GitHubCommitNotifier.java:127) at com.cloudbees.jenkins.GitHubCommitNotifier.perform(GitHubCommitNotifier.java:84) at
[JIRA] [github-plugin] (JENKINS-31103) How to troubleshoot maximum number of statuses errors?
Title: Message Title
Michael Grünewald updated an issue
Jenkins / JENKINS-31103
How to troubleshoot maximum number of statuses errors?
Change By:
Michael Grünewald
We are using Jenkins in conjunction with GitHub. Sometimes the tests are failing with the following exception:{{Sep 10, 2015 7:19:35 AM hudson.model.AbstractBuild$AbstractBuildExecution reportErrorWARNING: Publisher 'Set build status on GitHub commit' aborted due to exception: java.io.IOException: {"message":"Validation Failed","errors":[{"resource":"Status","code":"custom","message":"This SHA and context has reached the maximum number of statuses."}],"documentation_url":"https://developer.github.com/v3/repos/statuses/#create-a-status"}at org.kohsuke.github.Requester.handleApiError(Requester.java:493)at org.kohsuke.github.Requester._to(Requester.java:245)at org.kohsuke.github.Requester.to(Requester.java:191)at org.kohsuke.github.GHRepository.createCommitStatus(GHRepository.java:774)at com.cloudbees.jenkins.GitHubCommitNotifier.updateCommitStatus(GitHubCommitNotifier.java:127)at com.cloudbees.jenkins.GitHubCommitNotifier.perform(GitHubCommitNotifier.java:84)at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)}}The error message seems to report the error details sent back by the GitHub RPC endpoint, stating that Jenkins tried to update more than 1000 times the statuses associated to a given SHA or “context”. Since we have a hand of different tests, it is strange to hit that 1000 limit.How to more precisely diagnose this (non-fatal) error and figure out what is causing that limit to be hit? P.S. Sorry for the poor formatting, it seems that these `{{…}}` delimiters are broken.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [workflow-plugin] (JENKINS-31096) Unicode characters in console logs do not print correctly in Workflow builds
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-31096 Unicode characters in console logs do not print correctly in Workflow builds Change By: Jesse Glick Labels: workflow encoding 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.
