[JIRA] [core] (JENKINS-10629) Tar implimentation can't handle > 8GB and doesn't error out.
Title: Message Title Mark Syms commented on JENKINS-10629 Re: Tar implimentation can't handle > 8GB and doesn't error out. At the very least, the TarArchive.visit method (or actually more likely, to preserve encapsulation, the TarEntry.setSIze() method except this is in the Apache code) should validate the file.length and error out hard if the file is too big for the format. 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-29137) Repeated failure to archive build artifacts
Title: Message Title Mark Syms resolved as Duplicate Probably duplicate of Jenkins-10629 Jenkins / JENKINS-29137 Repeated failure to archive build artifacts Change By: Mark Syms 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] [core] (JENKINS-29137) Repeated failure to archive build artifacts
Title: Message Title Mark Syms commented on JENKINS-29137 Re: Repeated failure to archive build artifacts Having reworked the output of the build to produce smaller files this issue (so far) seems to have been resolved, so this does look to a variant of Jenkins-10629 which seems to manifest in a variety of subtly different exception messages. 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-29140) Temporary file appears to leak data
Title: Message Title Mark Syms commented on JENKINS-29140 Re: Temporary file appears to leak data I think it probably was from exceeding the 8GB limit, I'm "tweaking" the build to split the output. Not nice that it can generate this though. 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-29140) Temporary file appears to leak data
Title: Message Title Mark Syms commented on JENKINS-29140 Re: Temporary file appears to leak data The build finally failed with - Archiving artifacts ERROR: Failed to archive artifacts: java.io.IOException: Failed to extract e:\workspace__/transfer of 18325 files at hudson.FilePath.readFromTar(FilePath.java:2299) at hudson.FilePath.copyRecursiveTo(FilePath.java:2210) at jenkins.model.StandardArtifactManager.archive(StandardArtifactManager.java:61) at hudson.tasks.ArtifactArchiver.perform(ArtifactArchiver.java:219) at hudson.tasks.BuildStepCompatibilityLayer.perform(BuildStepCompatibilityLayer.java:75) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) 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:1769) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:374) Caused by: java.io.IOException: unexpected EOF with 2560 bytes unread at hudson.org.apache.tools.tar.TarInputStream.read(TarInputStream.java:349) at java.io.FilterInputStream.read(FilterInputStream.java:107) at org.apache.commons.io.IOUtils.copyLarge(IOUtils.java:1792) at org.apache.commons.io.IOUtils.copyLarge(IOUtils.java:1769) at org.apache.commons.io.IOUtils.copy(IOUtils.java:1744) at hudson.util.IOUtils.copy(IOUtils.java:40) at hudson.FilePath.readFromTar(FilePath.java:2289) ... 13 more Build step 'Archive the artifacts' changed build result to FAILURE Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://group
[JIRA] [core] (JENKINS-29140) Temporary file appears to leak data
Title: Message Title
Mark Syms commented on JENKINS-29140
Re: Temporary file appears to leak data
In the build archive folder {Build Record Root Directory}
///archive
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-29140) Temporary file appears to leak data
Title: Message Title Mark Syms created an issue Jenkins / JENKINS-29140 Temporary file appears to leak data Issue Type: Bug Assignee: Unassigned Components: core Created: 30/Jun/15 10:14 AM Environment: Master. Debian Linux 7, openjdk-7-jre, 7u79-2.5.5-1~deb7u1, amd64, Jenkins 1.617 from package repository. Build Slave: Windows 2012R2, Oracle Java 8 update 45, x64 Priority: Trivial Reporter: Mark Syms While monitoring an archive operation in order to investigate Jenkins-29137 I spotted a strangely named file - rw-r r - 1 jenkins jenkins 2553815040 Jun 30 11:11 $eip $T0 ^ = $esp $T0 4 + = This file is growing so looks to be the currently working file and the file name looks suspiciously like Java Byte code. Random file name generation managing to read unclean data from the heap?
[JIRA] [core] (JENKINS-29137) Repeated failure to archive build artifacts
Title: Message Title Mark Syms commented on JENKINS-29137 Re: Repeated failure to archive build artifacts Looks like it may be a variant of https://issues.jenkins-ci.org/browse/JENKINS-10629. One of the files being archived (which is itself an archive) has grown to over 8GB. Going to look at splitting this archive into smaller pieces to see if it resolves the issue. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-29137) Repeated failure to archive build artifacts
Title: Message Title Mark Syms commented on JENKINS-29137 Re: Repeated failure to archive build artifacts Slightly different form also being seen - Archiving artifacts ERROR: Failed to archive artifacts: java.io.IOException: java.io.IOException: Failed to extract c:\jenkins\workspace\/transfer of 12137 files at hudson.FilePath.readFromTar(FilePath.java:2299) at hudson.FilePath.copyRecursiveTo(FilePath.java:2210) at jenkins.model.StandardArtifactManager.archive(StandardArtifactManager.java:61) at hudson.tasks.ArtifactArchiver.perform(ArtifactArchiver.java:219) at hudson.tasks.BuildStepCompatibilityLayer.perform(BuildStepCompatibilityLayer.java:75) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) 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:1769) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:374) Caused by: java.io.FileNotFoundException: /jenkins/builds/ /498/archive (Is a directory) at java.io.FileOutputStream.open(Native Method) at java.io.FileOutputStream.(FileOutputStream.java:221) at java.io.FileOutputStream.(FileOutputStream.java:171) at hudson.util.IOUtils.copy(IOUtils.java:38) at hudson.FilePath.readFromTar(FilePath.java:2289) ... 13 more at hudson.FilePath.copyRecursiveTo(FilePath.java:2217) at jenkins.model.StandardArtifactManager.archive(StandardArtifactManager.java:61) at hudson.tasks.ArtifactArchiver.perform(ArtifactArchiver.java:219) at hudson.tasks.BuildStepCompatibilityLayer.perform(BuildStepCompatibilityLayer.java:75) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) 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:1769) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:374) Caused by: java.util.concurrent.ExecutionException: java.io.IOException: Pipe is already closed at hudson.remoting.Channel$3.adapt(Channel.java:785) at hudson.remoting.Channel$3.adapt(Channel.java:780) at hudson.remoting.FutureAdapter.get(FutureAdapter.java:59) at hudson.FilePath.copyRecursiveTo(FilePath.java:2213) ... 12 more Caused by: java.io.IOException: Pipe is already closed at hudson.remoting.PipeWindow.checkDeath(PipeWindow.java:108) at hudson.remoting.PipeWindow$Real.get(PipeWindow.java:203) at hudson.remoting.ProxyOutputStream.write(ProxyOutputStream.java:122) at java.io.BufferedOutputStream.flushBuffer(Unknown Source) at java.io.BufferedOutputStream.write(Unknown Source) at com.jcraft.jzlib.DeflaterOutputStream.deflate(DeflaterOutputStream.java:144) at com.jcraft.jzlib.DeflaterOutputStream.write(DeflaterOutputStream.java:102) at java.io.BufferedOutputStream.write(Unknown Source) at org.apache.tools.tar.TarBuffer.writeBlock(TarBuffer.java:410) at org.apache.tools.tar.TarBuffer.writeRecord(TarBuffer.java:351) at hudson.org.apache.tools.tar.TarOutputStream.writeEOFRecord(TarOutputStream.java:356) at hudson.org.apache.tools.tar.TarOutputStream.finish(TarOutputStream.java:137) at hudson.org.apache.tools.tar.TarOutputStream.close(T
[JIRA] [core] (JENKINS-29137) Repeated failure to archive build artifacts
Title: Message Title Mark Syms updated an issue Jenkins / JENKINS-29137 Repeated failure to archive build artifacts Change By: Mark Syms Environment: Master. Debian Linux 7 , openjdk-7-jre, 7u79-2.5.5-1~deb7u1, amd64 Build Slave: Windows 2012R2 , Oracle Java 8 update 45, x64 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-29137) Repeated failure to archive build artifacts
Title: Message Title Mark Syms commented on JENKINS-29137 Re: Repeated failure to archive build artifacts Sorry, forgot to say, this is on 1.617. 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-29137) Repeated failure to archive build artifacts
Title: Message Title Mark Syms created an issue Jenkins / JENKINS-29137 Repeated failure to archive build artifacts Issue Type: Bug Assignee: Unassigned Components: core Created: 30/Jun/15 6:35 AM Environment: Master. Debian Linux 7 Build Slave: Windows 2012R2 Priority: Critical Reporter: Mark Syms We recently replaced our Windows based Jenkins master with a Linux (Debian 7) based master and since this time we are seeing repeated failures to archive the artefacts from the build jobs that runs on a Windows build slave. I can't see any existing issues which directly match this although there are some which look superficially similar. I have the following from the build log but if there is more information I can gather about this issue please let me know (with instructions) as this is becoming a severe blocker to our build processes. Archiving artifacts ERROR: Failed to archive artifacts: java.io.IOException: Failed to extract c:\jenkins\workspace\Integration/transfer of 18960 files at hudson.FilePath.readFromTar(FilePath.java:2299) at hudson.FilePath.copyRecursiveTo(FilePath.java:2210) at jenkins.model.StandardArtifactManager.archive(StandardArtifactManager.java:61) at hudson.tasks.ArtifactArchiver.perform(ArtifactArchiver.java:219) at hudson.tasks.Bu
[JIRA] [job-dsl-plugin] (JENKINS-28744) Support for confguring publish over CIFS Plugin
Title: Message Title Mark Syms created an issue Jenkins / JENKINS-28744 Support for confguring publish over CIFS Plugin Issue Type: New Feature Assignee: Mark Syms Components: job-dsl-plugin Created: 04/Jun/15 9:36 AM Priority: Minor Reporter: Mark Syms Add support for configuring the Publish over CIFS plugin to the DSL. https://wiki.jenkins-ci.org/display/JENKINS/Publish+Over+CIFS+Plugin Add Comment
[JIRA] [job-dsl-plugin] (JENKINS-28024) Support Build Publisher Plugin
Mark Syms created JENKINS-28024 Support Build Publisher Plugin Issue Type: New Feature Assignee: Mark Syms Components: job-dsl-plugin Created: 21/Apr/15 8:16 AM Description: Add support for Build Publisher plugin Project: Jenkins Priority: Minor Reporter: Mark Syms This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-27929) Allow archiveArtifacts to specify all parameters
Mark Syms started work on JENKINS-27929 Allow archiveArtifacts to specify all parameters Change By: Mark Syms (14/Apr/15 1:31 PM) Status: Open In Progress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-27929) Allow archiveArtifacts to specify all parameters
Mark Syms assigned JENKINS-27929 to Mark Syms Allow archiveArtifacts to specify all parameters Change By: Mark Syms (14/Apr/15 1:31 PM) Assignee: Daniel Spilker Mark Syms This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-27929) Allow archiveArtifacts to specify all parameters
Mark Syms updated JENKINS-27929 Allow archiveArtifacts to specify all parameters Change By: Mark Syms (14/Apr/15 1:31 PM) Description: Extend parameter support on archiveArtifacts to cover allowEmptyArchive fingerprintonlyIfSuccessful This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-27929) Allow archiveArtifacts to specify all parameters
Mark Syms created JENKINS-27929 Allow archiveArtifacts to specify all parameters Issue Type: Improvement Assignee: Daniel Spilker Components: job-dsl-plugin Created: 14/Apr/15 1:12 PM Description: Extend parameter support on archiveArtifacts to cover allowEmptyArchive fingerprint onlyIfSuccessful Project: Jenkins Priority: Minor Reporter: Mark Syms This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-27838) Allow CopyArtifacts command to specify excludes filter
Mark Syms created JENKINS-27838 Allow CopyArtifacts command to specify excludes filter Issue Type: Improvement Assignee: Daniel Spilker Components: job-dsl-plugin Created: 08/Apr/15 9:28 AM Description: The CopyArtifact command does not allow an exclude filter to be specified which requires all artefacts matching an include filter to be copied to the downstream job. This is quite inflexible when there may be several downstream test jobs requiring different subsets of build outputs. I have an implementation, pull request to follow. Project: Jenkins Priority: Minor Reporter: Mark Syms This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-27832) Allow configuration of "build after other projects" trigger
Mark Syms created JENKINS-27832 Allow configuration of "build after other projects" trigger Issue Type: Improvement Assignee: Daniel Spilker Components: job-dsl-plugin Created: 08/Apr/15 8:22 AM Description: Since Jenkins 1.560 it has been possible to configure a project to "Build after other projects are built". The DSL does not currently support this form of trigger which allows the downstream job to start independently of the upstream job rather than running as a sub task. I have an implementation, pull request will be following. Environment: Jenkins: 1.605 Project: Jenkins Priority: Minor Reporter: Mark Syms This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-27820) Support adding Windows PowerShell build steps
Mark Syms created JENKINS-27820 Support adding Windows PowerShell build steps Issue Type: Improvement Assignee: Daniel Spilker Components: job-dsl-plugin Created: 07/Apr/15 3:41 PM Description: For Windows build slaves it would be good to support PowerShell build steps, these are essentially identical to BatchFile but execute in PowerShell instead of cmd. hudson.plugins.powershell.PowerShell plugin="powershell@1.2"> PowerShell script commands here I have an implementation, a pull request will be following. Environment: Operating System: Windows Project: Jenkins Priority: Minor Reporter: Mark Syms This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-12396) Jobs remain on executor for 20 minutes after they finish
Mark Syms updated JENKINS-12396 Jobs remain on executor for 20 minutes after they finish This screen shot shows the delete operations occurring in the Master, whilst this is happening the latest build of the associated build on the build slave is spinning after the completion line. Change By: Mark Syms (26/Mar/15 8:34 AM) Attachment: Jenkins Delete operations.png This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-12396) Jobs remain on executor for 20 minutes after they finish
Mark Syms commented on JENKINS-12396 Jobs remain on executor for 20 minutes after they finish Actually, how do I extract a stack trace from the Java processes on the Master and Build slaves when they're running as Windows Services? Thanks This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-12396) Jobs remain on executor for 20 minutes after they finish
Mark Syms commented on JENKINS-12396 Jobs remain on executor for 20 minutes after they finish In my particular case I can see the file deletes (on the master) happening as being the thing that takes the time, as I say this may be down to NTFS and Windows. I'll get some stack traces when I see it happening. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-12396) Jobs remain on executor for 20 minutes after they finish
Mark Syms reopened JENKINS-12396 Jobs remain on executor for 20 minutes after they finish As this was resolved as "incomplete" and I have added additional context to the commentary I believe it should be looked at again. Change By: Mark Syms (25/Mar/15 6:15 PM) Resolution: Incomplete Status: Resolved Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-12396) Jobs remain on executor for 20 minutes after they finish
Mark Syms commented on JENKINS-12396 Jobs remain on executor for 20 minutes after they finish I don't know if it's because our Jenkins Master is Windows based and NTFS is not good at handling deletes, or that we have a lot of jobs or that our jobs are quite large (many hundreds of files) or some combination of these but this stage can regularly take in excess of an hour to complete after the job has reported that it has finished. It feels like it would be nicer if the build discard process occurred as a background housekeeping operation rather than as an inline part of the latest build, possibly also only having a single cleanup process rather than every job being able to trigger these tasks concurrently might be a good idea. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [active-directory] (JENKINS-22727) AD plugin times out for large user/group membership
Mark Syms commented on JENKINS-22727 AD plugin times out for large user/group membership Catching the LimitExceededException in chainGroupLookup and returning false seems to work but is a bit brute force. Something that did some deferred lookups on demand would probably be a better solution but I'm not sure how that would map into the architecture. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [powershell] (JENKINS-23203) PowerShell plugin doesn't report status properly if a script is called
Mark Syms
created JENKINS-23203
PowerShell plugin doesn't report status properly if a script is called
Issue Type:
Bug
Affects Versions:
current
Assignee:
Unassigned
Components:
powershell
Created:
27/May/14 12:54 PM
Description:
If the PowerShell plugin is used in a build job and the plugin calls a PS1 PowerShell script the job status is always success regardless of whether the script executed correctly as the reported status is just whether it was possible to execute the script or not.
It should be possible to call out to a PowerShell script and have the status reported correctly, even if this needs to be a configuration option to the plugin (or a variant to the plugin that will only execute scripts).
There is a workaround which involves using the Windows batch plugin and doing something like
powershell.exe "& {build_script.ps1; exit $lastexitcode }"
but this is a bit unwieldy.
Project:
Jenkins
Priority:
Minor
Reporter:
Mark Syms
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
