[JIRA] (JENKINS-37565) Update supported Java version to Java7
Title: Message Title Oleg Nenashev started work on JENKINS-37565 Change By: Oleg Nenashev Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37565) Update supported Java version to Java7
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-37565 Update supported Java version to Java7 Change By: Mark Waite Remoting layer could benefit from bumping to Java7 due to its better resource handling and File API methods. Jenkins does not support Java 6 starting from 1. 609.x 625 (>1 year ago), hence Java 6 is not required anymore Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37565) Update supported Java version to Java7
Title: Message Title Oleg Nenashev commented on JENKINS-37565 Re: Update supported Java version to Java7 Thanks Mark Waite for the version fix. Yes, Java6 is dropped in 1.625. BTW, Java update is still reasonable Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37565) Update supported Java version to Java7
Title: Message Title Mark Waite commented on JENKINS-37565 Re: Update supported Java version to Java7 Oleg Nenashev I agree wholeheartedly. The "try with resources" additions of JDK 7 have been a great help to reduce the amount of code in the git client plugin 2.0 release, and those same additions give me more confidence that the battle against resource leaks might be a "winnable battle". Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37566) FindBugs-clean remoting layer
Title: Message Title
Oleg Nenashev updated an issue
Jenkins / JENKINS-37566
FindBugs-clean remoting layer
Change By:
Oleg Nenashev
I would like to cleanup FindBugs in remoting by Remoting 3.0.Actually the plan is to perform the most of the fixes in Remoting 2 stabilization branch and then merge them towards 3.0 Current state in the master branch:{noformat}[INFO] BugInstance size is 54[INFO] Error size is 0[INFO] Total bugs: 54[INFO] Wait not in loop in hudson.remoting.AsyncFutureImpl.get(long, TimeUnit) [hudson.remoting.AsyncFutureImpl] At AsyncFutureImpl.java:[line 83] WA_NOT_IN_LOOP[INFO] hudson.remoting.Capability.read(InputStream) may fail to close stream [hudson.remoting.Capability] At Capability.java:[line 124] OS_OPEN_STREAM[INFO] hudson.remoting.Capability.writePreamble(OutputStream) may fail to close stream [hudson.remoting.Capability] At Capability.java:[line 114] OS_OPEN_STREAM[INFO] hudson.remoting.Channel.getProperty(ChannelProperty) is unsynchronized, hudson.remoting.Channel.setProperty(Object, Object) is synchronized [hudson.remoting.Channel] At Channel.java:[line 1210] UG_SYNC_SET_UNSYNC_GET[INFO] hudson.remoting.ChannelBuilder.getProperties() may expose internal representation by returning ChannelBuilder.properties [hudson.remoting.ChannelBuilder] At ChannelBuilder.java:[line 277] EI_EXPOSE_REP[INFO] Return value of putIfAbsent is ignored, but checksum is reused in hudson.remoting.Checksum.calculateFor(URL) [hudson.remoting.Checksum] At Checksum.java:[line 111] RV_RETURN_VALUE_OF_PUTIFABSENT_IGNORED[INFO] Private method hudson.remoting.ChunkedOutputStream.frameSize() is never called [hudson.remoting.ChunkedOutputStream] At ChunkedOutputStream.java:[line 34] UPM_UNCALLED_PRIVATE_METHOD[INFO] Non serializable hudson.remoting.RemoteClassLoader$IClassLoader written to ObjectOutput in hudson.remoting.ClassLoaderHolder.writeObject(ObjectOutputStream) [hudson.remoting.ClassLoaderHolder] At ClassLoaderHolder.java:[line 44] DMI_NONSERIALIZABLE_OBJECT_WRITTEN[INFO] hudson.remoting.DiagnosedStreamCorruptionException.getReadAhead() may expose internal representation by returning DiagnosedStreamCorruptionException.readAhead [hudson.remoting.DiagnosedStreamCorruptionException] At DiagnosedStreamCorruptionException.java:[line 33] EI_EXPOSE_REP[INFO] hudson.remoting.DiagnosedStreamCorruptionException.getReadBack() may expose internal representation by returning DiagnosedStreamCorruptionException.readBack [hudson.remoting.DiagnosedStreamCorruptionException] At DiagnosedStreamCorruptionException.java:[line 29] EI_EXPOSE_REP[INFO] Unwritten field: hudson.remoting.ExportTable$Entry.recorder [hudson.remoting.ExportTable$Entry] At ExportTable.java:[line 110] UWF_UNWRITTEN_FIELD[INFO] hudson.remoting.ExportTable$ExportList is serializable but also an inner class of a non-serializable class [hudson.remoting.ExportTable$ExportList] At ExportTable.java:[lines 241-255] SE_BAD_FIELD_INNER_CLASS[INFO] Return value of Throwable.getStackTrace() ignored, but method has no side effect [hudson.remoting.Export
[JIRA] (JENKINS-37565) Update supported Java version to Java7
Title: Message Title Oleg Nenashev commented on JENKINS-37565 Re: Update supported Java version to Java7 And also Files class with normal file operations, which do not require the return value check... There is a bunch of such errors in remoting - JENKINS-37566 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33617) Can't see SVN_URL and SVN_REVISION in environment variable
Title: Message Title Daniel Beck commented on JENKINS-33617 Re: Can't see SVN_URL and SVN_REVISION in environment variable If this happens only on a particular node (master), I wonder whether envinject interferes. Disable the plugin and try again. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37477) PipelineTriggersJobProperty / pipelineTriggers() - snippet generator and syntax doc fail
Title: Message Title Daniel Beck commented on JENKINS-37477 Re: PipelineTriggersJobProperty / pipelineTriggers() - snippet generator and syntax doc fail Andrew Bayer Didn't you work in this area recently? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-20636) RVM and NodeJS plugins are incompatible
Title: Message Title Sandra Thieme commented on JENKINS-20636 Re: RVM and NodeJS plugins are incompatible Right, trying a build of the current master of the NodeJS plugin fixes this issue. Frédéric Camblor, could you create a new release of the NodeJS plugin? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-20636) RVM and NodeJS plugins are incompatible
Title: Message Title Sandra Thieme assigned an issue to Frédéric Camblor Jenkins / JENKINS-20636 RVM and NodeJS plugins are incompatible Change By: Sandra Thieme Assignee: Eito Katagiri Frédéric Camblor Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37477) PipelineTriggersJobProperty / pipelineTriggers() - snippet generator and syntax doc fail
Title: Message Title
Andrew Bayer commented on JENKINS-37477
Re: PipelineTriggersJobProperty / pipelineTriggers() - snippet generator and syntax doc fail
I did - I'll dig into this. And in the meantime - Greg Smith - this should work for you:
properties([pipelineTriggers([cron('H/15 * * * *')])])
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37477) PipelineTriggersJobProperty / pipelineTriggers() - snippet generator and syntax doc fail
Title: Message Title Andrew Bayer assigned an issue to Andrew Bayer Jenkins / JENKINS-37477 PipelineTriggersJobProperty / pipelineTriggers() - snippet generator and syntax doc fail Change By: Andrew Bayer Assignee: Jesse Glick Andrew Bayer Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35189) Spigot-Essentials Updates for 1.9.4 ?
Title: Message Title Steve Mekkelsen Madden commented on JENKINS-35189 Re: Spigot-Essentials Updates for 1.9.4 ? Even with the latest Spigot 1.10.2 build of two days ago, the issue persists. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37492) Propose adding `diff` utility step
Title: Message Title Ron Dagostino commented on JENKINS-37492 Re: Propose adding `diff` utility step At a minimum, it would be helpful if two FileWrapper instances available via the findFiies step from the Pipeline Utility Steps Plugin could be compared, perhaps like this: boolean comparedTheSame = firstFileWrapper.sameContentsAs(secondFileWrapper). A "compareFiles" step would also be helpful, of course. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37492) Propose adding `diff` utility step
Title: Message Title Ron Dagostino edited a comment on JENKINS-37492 Re: Propose adding `diff` utility step At a minimum, it would be helpful if two FileWrapper instances available via the findFiies findFiles step from the Pipeline Utility Steps Plugin could be compared, perhaps like this: boolean comparedTheSame = firstFileWrapper.sameContentsAs(secondFileWrapper). A "compareFiles" step would also be helpful, of course. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37574) Delete master build then get errors while indexing
Title: Message Title Sergey Arbuzov created an issue Jenkins / JENKINS-37574 Delete master build then get errors while indexing Issue Type: Bug Assignee: Antonio Muñiz Components: bitbucket-branch-source-plugin Created: 2016/Aug/20 3:12 PM Environment: 2.18 Priority: Blocker Reporter: Sergey Arbuzov Create Organization folder project "master" build will create automatically. One employee has access to organization folder, but jenkins can`t get access to this employee repo. Then this employee create pullrequest to master we got exception while indexing and all repo information deleted. Even healthy master branch. Then we fix this problem project and master branch will appear but all previous information deleted. For example build number started from 1 Add Comment
[JIRA] (JENKINS-37300) Update to version 1.22: ClassNotFoundException: com.joelj.jenkins.eztemplates.InheritenceStep.EzTemplateBuilder
Title: Message Title Marc Carter commented on JENKINS-37300 Re: Update to version 1.22: ClassNotFoundException: com.joelj.jenkins.eztemplates.InheritenceStep.EzTemplateBuilder Hi all. Erstwhile ez-templates plugin maintainer here. This is very poor situation indeed. InheritanceStep has never been a class of this plugin - the history is there for you to review and I share your frustration. At some point prior to ez-templates migrating into official jenkins repo, someone uploaded an unofficial hpi from their private fork. Presumably, this is the code you've been using. https://groups.google.com/d/msg/jenkinsci-dev/NVLHCFegfYw/X_5u3Us_CgAJ I rejected that change as complicating ez internals too much considering I'm (ok very slowly) intending a refactoring that will make it much more powerful. Please re-evaluate and drop support if required (but do create a new jira on both Components to add it back!) Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-20944) build metrics output should list real user
Title: Message Title Rolf Rother commented on JENKINS-20944 Re: build metrics output should list real user The User who triggered the build manually is allways shown correct. SYSTEM is for automated builds only. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-20944) build metrics output should list real user
Title: Message Title Rolf Rother closed an issue as Fixed Jenkins / JENKINS-20944 build metrics output should list real user Change By: Rolf Rother Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-20944) build metrics output should list real user
Title: Message Title Rolf Rother resolved as Fixed Not a bug. Jenkins / JENKINS-20944 build metrics output should list real user Change By: Rolf Rother Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-20945) Can we filter on Cause?
Title: Message Title Rolf Rother commented on JENKINS-20945 Re: Can we filter on Cause? Added, will be included in the next release Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-24327) Jobs ignore cron settings when set build periodically.
Title: Message Title Rolf Rother edited a comment on JENKINS-24327 Re: Jobs ignore cron settings when set build periodically. Still this problem ? Not a build-metrics problems. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-24327) Jobs ignore cron settings when set build periodically.
Title: Message Title Rolf Rother closed an issue as Not A Defect Not a build-metrics problems. Jenkins / JENKINS-24327 Jobs ignore cron settings when set build periodically. Change By: Rolf Rother Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout
[JIRA] (JENKINS-20945) Can we filter on Cause?
Title: Message Title Rolf Rother started work on JENKINS-20945 Change By: Rolf Rother Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-29823) Build Metrics Plugini accessible only with 'Administrator' Previlages
Title: Message Title Rolf Rother closed an issue as Won't Fix You can use the sidebar plugin to predefine reports and enable those predefined reports to your developers. As buid-metrics is based on global-build-stats it's not possible to simply enable it for every user. Jenkins / JENKINS-29823 Build Metrics Plugini accessible only with 'Administrator' Previlages Change By: Rolf Rother Status: Open Closed Resolution: Won't Fix Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
[JIRA] (JENKINS-33851) Allow to filter by VCS committeer
Title: Message Title Rolf Rother started work on JENKINS-33851 Change By: Rolf Rother Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33851) Allow to filter by VCS committeer
Title: Message Title Rolf Rother commented on JENKINS-33851 Re: Allow to filter by VCS committeer Seems to be possible, but can not ensure to include it in the next release. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-20945) Can we filter on Cause?
Title: Message Title SCM/JIRA link daemon commented on JENKINS-20945 Re: Can we filter on Cause? Code changed in jenkins User: Rolf Rother Path: Read.me src/main/java/jenkins/plugins/build_metrics/BuildMetricsPluginSearchFactory.java src/main/java/jenkins/plugins/build_metrics/BuildMetricsSearch.java src/main/java/jenkins/plugins/build_metrics/stats/StatsFactory.java src/main/resources/jenkins/plugins/build_metrics/BuildMetricsPlugin/index.jelly src/test/java/jenkins/plugins/build_metrics/stats/StatsFactoryTest.java src/test/java/jenkins/plugins/build_metrics/stats/StatsMathTest.java http://jenkins-ci.org/commit/build-metrics-plugin/ba430dfa6a7651180bd717e3dad3fa80827aea29 Log: JENKINS-20945 - added Cause filtering Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37329) Bug in StatsMath.java DecimalFormat
Title: Message Title SCM/JIRA link daemon commented on JENKINS-37329 Re: Bug in StatsMath.java DecimalFormat Code changed in jenkins User: Rolf Rother Path: src/main/java/jenkins/plugins/build_metrics/stats/StatsMath.java src/test/java/jenkins/plugins/build_metrics/stats/StatsMathTest.java http://jenkins-ci.org/commit/build-metrics-plugin/b4486c4ae1a216e48029d36708c9fcb47be2f4f3 Log: Revert "JENKINS-37329 - Changed caluclation of RoundDecimal again." This reverts commit f22fe982feb30c5566eb665b423a6bb2806ed022. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37329) Bug in StatsMath.java DecimalFormat
Title: Message Title SCM/JIRA link daemon commented on JENKINS-37329 Re: Bug in StatsMath.java DecimalFormat Code changed in jenkins User: Rolf Rother Path: src/main/java/jenkins/plugins/build_metrics/stats/StatsMath.java src/test/java/jenkins/plugins/build_metrics/stats/StatsMathTest.java http://jenkins-ci.org/commit/build-metrics-plugin/f22fe982feb30c5566eb665b423a6bb2806ed022 Log: JENKINS-37329 - Changed caluclation of RoundDecimal again. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37329) Bug in StatsMath.java DecimalFormat
Title: Message Title SCM/JIRA link daemon commented on JENKINS-37329 Re: Bug in StatsMath.java DecimalFormat Code changed in jenkins User: Rolf Rother Path: src/main/java/jenkins/plugins/build_metrics/stats/StatsFactory.java src/main/java/jenkins/plugins/build_metrics/stats/StatsMath.java src/main/java/jenkins/plugins/build_metrics/stats/StatsModel.java src/main/resources/jenkins/plugins/build_metrics/BuildMetricsPlugin/BuildStats.jelly http://jenkins-ci.org/commit/build-metrics-plugin/8ace1d0873af1ae523ebc25d7c269bd7ba048de8 Log: Revert "JENKINS-37329 - Changed caluclation of RoundDecimal again." This reverts commit f22fe982feb30c5566eb665b423a6bb2806ed022. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36749) Saves on templates don't propagate to implementing jobs
Title: Message Title Marc Carter started work on JENKINS-36749 Change By: Marc Carter Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36749) Saves on templates don't propagate to implementing jobs
Title: Message Title Marc Carter assigned an issue to Marc Carter Jenkins / JENKINS-36749 Saves on templates don't propagate to implementing jobs Change By: Marc Carter Assignee: Joel Johnson Marc Carter Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-22547) Git timeout setting does not work for checkout
Title: Message Title Mark Waite resolved as Fixed Included in git client plugin 1.20.0 released 20 Aug 2016 Jenkins / JENKINS-22547 Git timeout setting does not work for checkout Change By: Mark Waite Status: Reopened Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/opt
[JIRA] (JENKINS-37185) Checkout timeout is not honored when used with local branch parameter
Title: Message Title Mark Waite resolved as Fixed Included in git client plugin 1.20.0 released 20 Aug 2016 Jenkins / JENKINS-37185 Checkout timeout is not honored when used with local branch parameter Change By: Mark Waite Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https
[JIRA] (JENKINS-37185) Checkout timeout is not honored when used with local branch parameter
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-37185 Checkout timeout is not honored when used with local branch parameter Change By: Mark Waite Comment: Fix will be in the git-client-plugin 1.19.8 release Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37575) Jenkins node keeps sending the sames logs indefinitely
Title: Message Title Quentin Dufour created an issue Jenkins / JENKINS-37575 Jenkins node keeps sending the sames logs indefinitely Issue Type: Bug Assignee: Jesse Glick Components: durable-task-plugin Created: 2016/Aug/20 9:15 PM Environment: Windows Server 2012 R2 Jenkins 2.7.2 Priority: Major Reporter: Quentin Dufour Problem The build never ends on the node. It sends forever the same 20-30 lines. Some logs files can be bigger than 10GB before I kill the process. Investigation I've found on Wireshark that the node keeps sending the same logs forever. So the jenkins master is not (directly) the culprit. After enabling the debugguer on the slave, I've found that the method FileMonitoringTask$FileMonitoringController$WriteLog.invoke is called in an infinite loop somewhere in this file: durable-task-plugin\src\main\java\org\jenkinsci\plugins\durabletask\FileMonitoringTask.java The same file is read again and again with a lastLocation of 1930670. lastLocation represent the bytes already read. But I don't understand why it doesn't increase. How to reproduce I've tried to reproduce this bug for 3 days but didn't achieve to.
[JIRA] (JENKINS-37575) Jenkins node keeps sending the sames logs indefinitely
Title: Message Title Quentin Dufour updated an issue Jenkins / JENKINS-37575 Jenkins node keeps sending the sames logs indefinitely Change By: Quentin Dufour Attachment: Capture d'écran de 2016-08-20 17-04-34.png Attachment: Capture d'écran de 2016-08-20 16-35-18.png h1. ProblemThe build never ends on the node. It sends forever the same 20-30 lines.Some logs files can be bigger than 10GB before I kill the process.h1. InvestigationI've found on Wireshark that the node keeps sending the same logs forever.So the jenkins master is not (directly) the culprit.After enabling the debugguer on the slave, I've found that the method FileMonitoringTask$FileMonitoringController$WriteLog.invoke is called in an infinite loop somewhere in this file: durable-task-plugin\src\main\java\org\jenkinsci\plugins\durabletask\FileMonitoringTask.javaThe same file is read again and again with a lastLocation of 1930670. lastLocation represent the bytes already read. But I don't understand why it doesn't increase. (check the attached screenshots above) h1. How to reproduceI've tried to reproduce this bug for 3 days but didn't achieve to. Add Comment
[JIRA] (JENKINS-37575) Jenkins node keeps sending the sames logs indefinitely
Title: Message Title Quentin Dufour updated an issue Jenkins / JENKINS-37575 Jenkins node keeps sending the sames logs indefinitely Change By: Quentin Dufour Attachment: jekins_10GB_log.png Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37575) Jenkins node keeps sending the sames logs indefinitely
Title: Message Title Quentin Dufour updated an issue Jenkins / JENKINS-37575 Jenkins node keeps sending the sames logs indefinitely Change By: Quentin Dufour h1. ProblemThe build never ends on the node. It sends forever the same 20-30 lines.Some logs files can be bigger than 10GB before I kill the process.h1. Investigation h2. Steps I've found on Wireshark that the node keeps sending the same logs forever.So the jenkins master is not (directly) the culprit.After enabling the debugguer on the slave, I've found that the method FileMonitoringTask$FileMonitoringController$WriteLog.invoke is called in an infinite loop somewhere in this file: durable-task-plugin\src\main\java\org\jenkinsci\plugins\durabletask\FileMonitoringTask.javaThe same file is read again and again with a lastLocation of 1930670. lastLocation represent the bytes already read. But I don't understand why it doesn't increase. (check the attached screenshots above) h2. Screenshots On h1. How to reproduceI've tried to reproduce this bug for 3 days but didn't achieve to. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-37523) New Item page shows "field cannot be empty" error when attempting to create a duplicate item
Title: Message Title SCM/JIRA link daemon commented on JENKINS-37523 Re: New Item page shows "field cannot be empty" error when attempting to create a duplicate item Code changed in jenkins User: Keith Zantow Path: war/src/main/js/add-item.js http://jenkins-ci.org/commit/jenkins/740fef2978d491ac6e3ab752bc70871fdd56546f Log: JENKINS-37523 - wrong message for duplicate item name during create (#2513) Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37332) java.io.IOException: Failed to rename during Plugin Update
Title: Message Title SCM/JIRA link daemon commented on JENKINS-37332 Re: java.io.IOException: Failed to rename during Plugin Update Code changed in jenkins User: Oleg Nenashev Path: core/src/main/java/hudson/PluginManager.java core/src/main/java/hudson/Util.java core/src/test/java/hudson/PluginManagerTest.java http://jenkins-ci.org/commit/jenkins/96c97860b0f018094c20283b15f3ddb3bdd9effe Log: [FIXED JENKINS-37332] - Prevent File descriptor leaks when reading manifests from JARs (#2516) JENKINS-37332 - Improve diagnostics of non-closed streams during reading of the manifests in PluginManager JENKINS-37332 - Leakless processing of JarUrlConnection during Manifest parsing JENKINS-37332 - Also implement leak-safe method for retrieving file modification date JENKINS-37332 - Add spotcheck methods for manifest file access + Javadoc JENKINS-37332 - Also test multi-line and empty attributes in the test Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-37561) File leaks in AntClassLoader#findClassInComponents()
Title: Message Title SCM/JIRA link daemon commented on JENKINS-37561 Re: File leaks in AntClassLoader#findClassInComponents() Code changed in jenkins User: Oleg Nenashev Path: core/src/main/java/jenkins/util/AntClassLoader.java http://jenkins-ci.org/commit/jenkins/67347c3c5f097da968bf8e6fe9fb57b03e358677 Log: [FIXED JENKINS-37561, CID-1205051] - Prevent resource leak in AntClassLoader#findClassInComponents() (#2517) It has been originally reported by Coverity in https://scan5.coverity.com/reports.htm#v36021/p10292/fileInstanceId=97573616&defectInstanceId=28155759&mergedDefectId=1205051. It happens on Exceptional paths only, but actually I see 31 runaway handlers on my jenkins-2.18 instance (maybe happens due to plugin dynamic load failure) The issue happens, because finally block is misplaced. It handles only the last stream in this cycle Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37332) java.io.IOException: Failed to rename during Plugin Update
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-37332 java.io.IOException: Failed to rename during Plugin Update Change By: SCM/JIRA link daemon Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37575) Jenkins node keeps sending the sames logs indefinitely
Title: Message Title Quentin Dufour updated an issue Jenkins / JENKINS-37575 Jenkins node keeps sending the sames logs indefinitely Change By: Quentin Dufour h1. ProblemThe build never ends on the node. It sends forever the same 20-30 lines.Some logs files can be bigger than 10GB before I kill the process.h1. Investigationh2. StepsI've found on Wireshark that the node keeps sending the same logs forever.So the jenkins master is not (directly) the culprit.After enabling the debugguer on the slave, I've found that the method FileMonitoringTask$FileMonitoringController$WriteLog.invoke is called in an infinite loop somewhere in this file: durable-task-plugin\src\main\java\org\jenkinsci\plugins\durabletask\FileMonitoringTask.javaThe same file is read again and again with a lastLocation of 1930670. lastLocation represent the bytes already read. But I don't understand why it doesn't increase.h2. ScreenshotsOnthe first one we can see the logs. Especially that the date from timestamper is different from the date of the logs. It's a good indication that we have a problem. On the second screenshot, I've connected netbeans on the node which handle the job. I've stopped the thread and also put a breakpoint on sink.write(buf). When I hit continue, I've seen that this function is always called. We can see some variables, especially the file descriptor and its associated size. The folder of this file is open on the top left of this screenshot. We can see that the size of this file is arround 3MB.On the last screenshot, it's just an example at how big the file becomes before crashing Jenkins in an Out of Memory Exception... h1. How to reproduceI've tried to reproduce this bug for 3 days but didn't achieve to. Add Comment
[JIRA] (JENKINS-37332) java.io.IOException: Failed to rename during Plugin Update
Title: Message Title Oleg Nenashev commented on JENKINS-37332 Re: java.io.IOException: Failed to rename during Plugin Update The fix should be released in 2.19 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37438) Provide method to force the setup wizard to run
Title: Message Title SCM/JIRA link daemon commented on JENKINS-37438 Re: Provide method to force the setup wizard to run Code changed in jenkins User: Keith Zantow Path: core/src/main/java/jenkins/install/InstallUtil.java http://jenkins-ci.org/commit/jenkins/4376fdedfc85a652f77af098d539e30dd18665fa Log: JENKINS-37438 - method to run setup wizard after Jenkins is modified (#2512) Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37575) Jenkins node keeps sending the sames logs indefinitely
Title: Message Title Quentin Dufour updated an issue Jenkins / JENKINS-37575 Jenkins node keeps sending the sames logs indefinitely Change By: Quentin Dufour h1. ProblemThe build never ends on the node. It sends forever the same 20-30 lines.Some logs files can be bigger than 10GB before I kill the process.h1. Investigationh2. StepsI've found on Wireshark that the node keeps sending the same logs forever.So the jenkins master is not (directly) the culprit.After enabling the debugguer on the slave, I've found that the method FileMonitoringTask$FileMonitoringController$WriteLog.invoke is called in an infinite loop somewhere in this file: durable-task-plugin\src\main\java\org\jenkinsci\plugins\durabletask\FileMonitoringTask.javaThe same file is read again and again with a lastLocation of 1930670. lastLocation represent the bytes already read. But I don't understand why it doesn't increase. It seems that Jenkins read the whole file. If it fails, it will return 0. I suspect that Jenkins is failing to close the file descriptor. So the lastLocation is not updated. But the data are sent. Jenkins retries to read the file, fail again, etc. That's only a supposition for now. h2. ScreenshotsOn the first one we can see the logs. Especially that the date from timestamper is different from the date of the logs. It's a good indication that we have a problem.On the second screenshot, I've connected netbeans on the node which handle the job. I've stopped the thread and also put a breakpoint on sink.write(buf). When I hit continue, I've seen that this function is always called. We can see some variables, especially the file descriptor and its associated size. The folder of this file is open on the top left of this screenshot. We can see that the size of this file is arround 3MB.On the last screenshot, it's just an example at how big the file becomes before crashing Jenkins in an Out of Memory Exception...h1. How to reproduceI've tried to reproduce this bug for 3 days but didn't achieve to. Add Comment
[JIRA] (JENKINS-36749) Saves on templates don't propagate to implementing jobs
Title: Message Title Marc Carter commented on JENKINS-36749 Re: Saves on templates don't propagate to implementing jobs In reverse order: ... missing its descriptor This kind of thing happens all the time if running in debug mode or hpi:run etc. Something to do with reloaded classes and it's a Jenkins 'feature' I believe. return exclusions != null ? exclusions : Exclusions.DEFAULT; The NPE is not entirely unplanned and is actually saving you from a worse outcome which is that all Impls will get rewritten back to the template and lose many of their individual settings. saving a template doesn't propagate the changes to the implementing jobs The problem is genuine though, migrateExclusions (the key method here) only gets called from the Jelly code for an impl. Hence, they only get upgraded when you manually save the impl and not when automatically processed by a saved template. That's resolvable. Workaround until v1.2.1: downgrade again or manually Configure / Save each impl Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "
[JIRA] (JENKINS-36749) Saves on templates don't propagate to implementing jobs after upgrading to 1.2
Title: Message Title Marc Carter updated an issue Jenkins / JENKINS-36749 Saves on templates don't propagate to implementing jobs after upgrading to 1.2 Change By: Marc Carter Summary: Saves on templates don't propagate to implementing jobs after upgrading to 1.2 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36859) EZ-Templates not compatible with jobs created with the MultiBranch plugin
Title: Message Title Marc Carter commented on JENKINS-36859 Re: EZ-Templates not compatible with jobs created with the MultiBranch plugin Hi, This is raised as a Bug (critical one no less) but phrased as a new feature without any supporting stack traces etc. Can you clarify if this is a regression of something that worked previously. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37575) Jenkins node keeps sending the sames logs indefinitely
Title: Message Title Quentin Dufour updated an issue Jenkins / JENKINS-37575 Jenkins node keeps sending the sames logs indefinitely Change By: Quentin Dufour h1. ProblemThe build never ends on the node. It sends forever the same 20-30 lines.Some logs files can be bigger than 10GB before I kill the process.h1. Investigationh2. StepsI've found on Wireshark that the node keeps sending the same logs forever.So the jenkins master is not (directly) the culprit.After enabling the debugguer on the slave, I've found that the method FileMonitoringTask$FileMonitoringController$WriteLog.invoke is called in an infinite loop somewhere in this file: durable-task-plugin\src\main\java\org\jenkinsci\plugins\durabletask\FileMonitoringTask.javaThe same file is read again and again with a lastLocation of 1930670. lastLocation represent the bytes already read. But I don't understand why it doesn't increase. Edit 1: It seems that Jenkins read the whole file. If it fails, it will return 0. I suspect that Jenkins is failing to close the file descriptor. So the lastLocation is not updated. But the data are sent. Jenkins retries to read the file, fail again, etc. That's only a supposition for now. Edit 2: It seems that it comes from the network, as I've captured a java.io.InterruptedIOException in this loop. h2. ScreenshotsOn the first one we can see the logs. Especially that the date from timestamper is different from the date of the logs. It's a good indication that we have a problem.On the second screenshot, I've connected netbeans on the node which handle the job. I've stopped the thread and also put a breakpoint on sink.write(buf). When I hit continue, I've seen that this function is always called. We can see some variables, especially the file descriptor and its associated size. The folder of this file is open on the top left of this screenshot. We can see that the size of this file is arround 3MB.On the last screenshot, it's just an example at how big the file becomes before crashing Jenkins in an Out of Memory Exception...h1. How to reproduceI've tried to reproduce this bug for 3 days but didn't achieve to. Add Comment
[JIRA] (JENKINS-37575) Jenkins node keeps sending the sames logs indefinitely
Title: Message Title Quentin Dufour updated an issue Jenkins / JENKINS-37575 Jenkins node keeps sending the sames logs indefinitely Change By: Quentin Dufour Attachment: Capture d'écran de 2016-08-20 19-02-41.png Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37575) Jenkins node keeps sending the sames logs indefinitely
Title: Message Title Quentin Dufour updated an issue Jenkins / JENKINS-37575 Jenkins node keeps sending the sames logs indefinitely Change By: Quentin Dufour h1. ProblemThe build never ends on the node. It sends forever the same 20-30 lines.Some logs files can be bigger than 10GB before I kill the process.h1. Investigationh2. StepsI've found on Wireshark that the node keeps sending the same logs forever.So the jenkins master is not (directly) the culprit.After enabling the debugguer on the slave, I've found that the method FileMonitoringTask$FileMonitoringController$WriteLog.invoke is called in an infinite loop somewhere in this file: durable-task-plugin\src\main\java\org\jenkinsci\plugins\durabletask\FileMonitoringTask.javaThe same file is read again and again with a lastLocation of 1930670. lastLocation represent the bytes already read. But I don't understand why it doesn't increase.Edit 1: It seems that Jenkins read the whole file. If it fails, it will return 0. I suspect that Jenkins is failing to close the file descriptor. So the lastLocation is not updated. But the data are sent. Jenkins retries to read the file, fail again, etc. That's only a supposition for now.Edit 2: It seems that it comes from the network, as I've captured a java.io.InterruptedIOException in this loop. !Capture d'écran de 2016-08-20 19-02-41.png! h2. ScreenshotsOn the first one we can see the logs. Especially that the date from timestamper is different from the date of the logs. It's a good indication that we have a problem.On the second screenshot, I've connected netbeans on the node which handle the job. I've stopped the thread and also put a breakpoint on sink.write(buf). When I hit continue, I've seen that this function is always called. We can see some variables, especially the file descriptor and its associated size. The folder of this file is open on the top left of this screenshot. We can see that the size of this file is arround 3MB.On the last screenshot, it's just an example at how big the file becomes before crashing Jenkins in an Out of Memory Exception...h1. How to reproduceI've tried to reproduce this bug for 3 days but didn't achieve to. Add Comment
[JIRA] (JENKINS-37575) Jenkins node keeps sending the sames logs indefinitely
Title: Message Title Quentin Dufour updated an issue Jenkins / JENKINS-37575 Jenkins node keeps sending the sames logs indefinitely Change By: Quentin Dufour h1. ProblemThe build never ends on the node. It sends forever the same 20-30 lines. !Capture d'écran de 2016-08-20 19-02-41.png|thumbnail! Some logs files can be bigger than 10GB before I kill the process. !Capture d'écran de 2016-08-20 19-02-41.png|thumbnail! h1. Investigationh2. StepsI've found on Wireshark that the node keeps sending the same logs forever.So the jenkins master is not (directly) the culprit.After enabling the debugguer on the slave, I've found that the method FileMonitoringTask$FileMonitoringController$WriteLog.invoke is called in an infinite loop somewhere in this file: durable-task-plugin\src\main\java\org\jenkinsci\plugins\durabletask\FileMonitoringTask.javaThe same file is read again and again with a lastLocation of 1930670. lastLocation represent the bytes already read. But I don't understand why it doesn't increase.Edit 1: It seems that Jenkins read the whole file. If it fails, it will return 0. I suspect that Jenkins is failing to close the file descriptor. So the lastLocation is not updated. But the data are sent. Jenkins retries to read the file, fail again, etc. That's only a supposition for now.Edit 2: It seems that it comes from the network, as I've captured a java.io.InterruptedIOException in this loop.!Capture d'écran de 2016-08-20 19-02-41.png |thumbnail ! h2. ScreenshotsOn the first one we can see the logs. Especially that the date from timestamper is different from the date of the logs. It's a good indication that we have a problem.On the second screenshot, I've connected netbeans on the node which handle the job. I've stopped the thread and also put a breakpoint on sink.write(buf). When I hit continue, I've seen that this function is always called. We can see some variables, especially the file descriptor and its associated size. The folder of this file is open on the top left of this screenshot. We can see that the size of this file is arround 3MB.On the last screenshot, it's just an example at how big the file becomes before crashing Jenkins in an Out of Memory Exception... h1. How to reproduceI've tried to reproduce this bug for 3 days but didn't achieve to.
[JIRA] (JENKINS-37575) Jenkins node keeps sending the sames logs indefinitely
Title: Message Title Quentin Dufour updated an issue Jenkins / JENKINS-37575 Jenkins node keeps sending the sames logs indefinitely Change By: Quentin Dufour h1. ProblemThe build never ends on the node. It sends forever the same 20-30 lines.!Capture d'écran de 2016-08-20 19 16 - 02 35 - 41 18 .png|thumbnail!Some logs files can be bigger than 10GB before I kill the process.! Capture d'écran de 2016-08-20 19-02-41 jenkins_10GB_log .png|thumbnail!h1. Investigationh2. StepsI've found on Wireshark that the node keeps sending the same logs forever.So the jenkins master is not (directly) the culprit.After enabling the debugguer on the slave, I've found that the method FileMonitoringTask$FileMonitoringController$WriteLog.invoke is called in an infinite loop somewhere in this file: durable-task-plugin\src\main\java\org\jenkinsci\plugins\durabletask\FileMonitoringTask.javaThe same file is read again and again with a lastLocation of 1930670. lastLocation represent the bytes already read. But I don't understand why it doesn't increase. !Capture d'écran de 2016-08-20 17-04-34.png|thumbnail! Edit 1: It seems that Jenkins read the whole file. If it fails, it will return 0. I suspect that Jenkins is failing to close the file descriptor. So the lastLocation is not updated. But the data are sent. Jenkins retries to read the file, fail again, etc. That's only a supposition for now.Edit 2: It seems that it comes from the network, as I've captured a java.io.InterruptedIOException in this loop.!Capture d'écran de 2016-08-20 19-02-41.png|thumbnail!h1. How to reproduceI've tried to reproduce this bug for 3 days but didn't achieve to. Add Comment
[JIRA] (JENKINS-37575) Jenkins node keeps sending the sames logs indefinitely
Title: Message Title Quentin Dufour updated an issue Jenkins / JENKINS-37575 Jenkins node keeps sending the sames logs indefinitely Change By: Quentin Dufour h1. ProblemThe build never ends on the node. It sends forever the same 20-30 lines.!Capture d'écran de 2016-08-20 16-35-18.png|thumbnail!Some logs files can be bigger than 10GB before I kill the process.! jenkins_10GB_log jekins_10GB_log .png|thumbnail!h1. Investigationh2. StepsI've found on Wireshark that the node keeps sending the same logs forever.So the jenkins master is not (directly) the culprit.After enabling the debugguer on the slave, I've found that the method FileMonitoringTask$FileMonitoringController$WriteLog.invoke is called in an infinite loop somewhere in this file: durable-task-plugin\src\main\java\org\jenkinsci\plugins\durabletask\FileMonitoringTask.javaThe same file is read again and again with a lastLocation of 1930670. lastLocation represent the bytes already read. But I don't understand why it doesn't increase.!Capture d'écran de 2016-08-20 17-04-34.png|thumbnail!Edit 1: It seems that Jenkins read the whole file. If it fails, it will return 0. I suspect that Jenkins is failing to close the file descriptor. So the lastLocation is not updated. But the data are sent. Jenkins retries to read the file, fail again, etc. That's only a supposition for now.Edit 2: It seems that it comes from the network, as I've captured a java.io.InterruptedIOException in this loop.!Capture d'écran de 2016-08-20 19-02-41.png|thumbnail!h1. How to reproduceI've tried to reproduce this bug for 3 days but didn't achieve to. Add Comment
[JIRA] (JENKINS-37575) Jenkins node keeps sending the sames logs indefinitely
Title: Message Title Quentin Dufour updated an issue Jenkins / JENKINS-37575 Jenkins node keeps sending the sames logs indefinitely Change By: Quentin Dufour h1. ProblemThe build never ends on the node. It sends forever the same 20-30 lines. We can see the difference between the timestamper date (put when received by the master) and the log date (written during the Powershell execution) !Capture d'écran de 2016-08-20 16-35-18.png|thumbnail!Some logs files can be bigger than 10GB before I kill the process. (Yes, it's really stored in the JENKINS_HOME) !jekins_10GB_log.png|thumbnail!h1. Investigationh2. StepsI've found on Wireshark that the node keeps sending the same logs forever.So the jenkins master is not (directly) the culprit.After enabling the debugguer on the slave, I've found that the method FileMonitoringTask$FileMonitoringController$WriteLog.invoke is called in an infinite loop somewhere in this file: durable-task-plugin\src\main\java\org\jenkinsci\plugins\durabletask\FileMonitoringTask.javaThe same file is read again and again with a lastLocation of 1930670. lastLocation represent the bytes already read. But I don't understand why it doesn't increase. The process is terminated, the log file is not bigger than 3MB (and can be seen in the upper left corner of the screenshot) !Capture d'écran de 2016-08-20 17-04-34.png|thumbnail!Edit 1: It seems that Jenkins read the whole file. If it fails, it will return 0. I suspect that Jenkins is failing to close the file descriptor. So the lastLocation is not updated. But the data are sent. Jenkins retries to read the file, fail again, etc. That's only a supposition for now.Edit 2: It seems that it comes from the network, as I've captured a java.io.InterruptedIOException in this loop in hudson . remoting.ProxyOutputStream. !Capture d'écran de 2016-08-20 19-02-41.png|thumbnail!h1. How to reproduceI've tried to reproduce this bug for 3 days but didn't achieve to. Add Comment
[JIRA] (JENKINS-37300) Update to version 1.22: ClassNotFoundException: com.joelj.jenkins.eztemplates.InheritenceStep.EzTemplateBuilder
Title: Message Title Marc Carter edited a comment on JENKINS-37300 Re: Update to version 1.22: ClassNotFoundException: com.joelj.jenkins.eztemplates.InheritenceStep.EzTemplateBuilder Hi all. Erstwhile ez-templates plugin maintainer here.This is very poor situation indeed. InheritanceStep has _never_ been a class of this plugin - the history is there for you to review and I share your frustration. At some point prior to ez-templates migrating into official jenkins repo, someone uploaded an unofficial hpi from their private fork. Presumably, this is the code you've been using.https://groups.google.com/d/msg/jenkinsci-dev/NVLHCFegfYw/X_5u3Us_CgAJI rejected that change as complicating ez internals too much considering I'm (ok very slowly) intending a refactoring that will make it much more powerful. Please re-evaluate and drop support if required (but do create a new jira on both Components to add it back!) _update_: confirmed http://repo.jenkins-ci.org/public/com/joelj/jenkins/ez-templates/ needs to be expunged - that's not code that made it past a PR. As per standard - when onboarded it became ez-templates_-plugin_ and I never noticed this other stuff camping on the previous name. I'll leave it a month or two before asking for it to be removed. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37399) Choices from Choice parameter aren't populated
Title: Message Title Marc Carter commented on JENKINS-37399 Re: Choices from Choice parameter aren't populated Never used a Choice Parameter but I can understand why this would be the case, EZ makes no attempt to sync the job param so will not see your new entry. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37575) Jenkins node keeps sending the sames logs indefinitely
Title: Message Title Quentin Dufour updated an issue Jenkins / JENKINS-37575 Jenkins node keeps sending the sames logs indefinitely Change By: Quentin Dufour h1. ProblemThe build never ends on the node. It sends forever the same 20-30 lines.We can see the difference between the timestamper date (put when received by the master) and the log date (written during the Powershell execution)!Capture d'écran de 2016-08-20 16-35-18.png|thumbnail!Some logs files can be bigger than 10GB before I kill the process.(Yes, it's really stored in the JENKINS_HOME)!jekins_10GB_log.png|thumbnail!h1. Investigationh2. StepsI've found on Wireshark that the node keeps sending the same logs forever.So the jenkins master is not (directly) the culprit.After enabling the debugguer on the slave, I've found that the method FileMonitoringTask$FileMonitoringController$WriteLog.invoke is called in an infinite loop somewhere in this file: durable-task-plugin\src\main\java\org\jenkinsci\plugins\durabletask\FileMonitoringTask.javaThe same file is read again and again with a lastLocation of 1930670. lastLocation represent the bytes already read. But I don't understand why it doesn't increase.The process is terminated, the log file is not bigger than 3MB (and can be seen in the upper left corner of the screenshot)!Capture d'écran de 2016-08-20 17-04-34.png|thumbnail! Edit Update 1: It seems that Jenkins read the whole file. If it fails, it will return 0. I suspect that Jenkins is failing to close the file descriptor. So the lastLocation is not updated. But the data are sent. Jenkins retries to read the file, fail again, etc. That's only a supposition for now. Edit Update 2: It seems that it comes from the network, as I've captured a java.io.InterruptedIOException in this loop in hudson.remoting.ProxyOutputStream.!Capture d'écran de 2016-08-20 19-02-41.png|thumbnail! Update 3: It seems that the Jenkins Master is guilty. I've connected my debugger to this one. The error occurs when it tries to write the log in its JENKINS_HOME. !Capture d'écran de 2016-08-20 19-35-36.png|thumbnail! h1. How to reproduceI've tried to reproduce this bug for 3 days but didn't achieve to. Add Comment
[JIRA] (JENKINS-37575) Jenkins node keeps sending the sames logs indefinitely
Title: Message Title Quentin Dufour updated an issue Jenkins / JENKINS-37575 Jenkins node keeps sending the sames logs indefinitely Change By: Quentin Dufour Attachment: Capture d'écran de 2016-08-20 19-35-36.png Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37575) Jenkins node keeps sending the sames logs indefinitely
Title: Message Title Quentin Dufour updated an issue Jenkins / JENKINS-37575 Jenkins node keeps sending the sames logs indefinitely Change By: Quentin Dufour Attachment: Capture d'écran de 2016-08-20 19-35-13.png Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37575) Jenkins node keeps sending the sames logs indefinitely
Title: Message Title Quentin Dufour updated an issue Jenkins / JENKINS-37575 Jenkins node keeps sending the sames logs indefinitely Change By: Quentin Dufour h1. ProblemThe build never ends on the node. It sends forever the same 20-30 lines.We can see the difference between the timestamper date (put when received by the master) and the log date (written during the Powershell execution)!Capture d'écran de 2016-08-20 16-35-18.png|thumbnail!Some logs files can be bigger than 10GB before I kill the process.(Yes, it's really stored in the JENKINS_HOME)!jekins_10GB_log.png|thumbnail!h1. Investigationh2. StepsI've found on Wireshark that the node keeps sending the same logs forever.So the jenkins master is not (directly) the culprit.After enabling the debugguer on the slave, I've found that the method FileMonitoringTask$FileMonitoringController$WriteLog.invoke is called in an infinite loop somewhere in this file: durable-task-plugin\src\main\java\org\jenkinsci\plugins\durabletask\FileMonitoringTask.javaThe same file is read again and again with a lastLocation of 1930670. lastLocation represent the bytes already read. But I don't understand why it doesn't increase.The process is terminated, the log file is not bigger than 3MB (and can be seen in the upper left corner of the screenshot)!Capture d'écran de 2016-08-20 17-04-34.png|thumbnail! * Update 1: * It seems that Jenkins read the whole file. If it fails, it will return 0. I suspect that Jenkins is failing to close the file descriptor. So the lastLocation is not updated. But the data are sent. Jenkins retries to read the file, fail again, etc. That's only a supposition for now. * Update 2: * It seems that it comes from the network, as I've captured a java.io.InterruptedIOException in this loop in hudson.remoting.ProxyOutputStream.!Capture d'écran de 2016-08-20 19-02-41.png|thumbnail! * Update 3: * It seems that the Jenkins Master is guilty. I've connected my debugger to this one. The error occurs when it tries to write the log in its JENKINS_HOME. When executing the green line on the following screenshot. !Capture d'écran de 2016-08-20 19-35-36.png|thumbnail! The error is catched in DurableTaskStep$Execution.check, as it seems to be a workspace error. It seems that Jenkins doesn't find the workspace folder, as it's searching the jenkins node workspace in its local file system. C:\\ci\\int12\\ocoint... !Capture d'écran de 2016-08-20 19-35-13.png|thumbnail! h1. How to reproduceI've tried to reproduce this bug for 3 days but didn't achieve to.
[JIRA] (JENKINS-37575) Jenkins node keeps sending the sames logs indefinitely
Title: Message Title Quentin Dufour updated an issue Jenkins / JENKINS-37575 Jenkins node keeps sending the sames logs indefinitely Change By: Quentin Dufour h1. ProblemThe build never ends on the node. It sends forever the same 20-30 lines.We can see the difference between the timestamper date (put when received by the master) and the log date (written during the Powershell execution)!Capture d'écran de 2016-08-20 16-35-18.png|thumbnail!Some logs files can be bigger than 10GB before I kill the process.(Yes, it's really stored in the JENKINS_HOME)!jekins_10GB_log.png|thumbnail!h1. Investigationh2. StepsI've found on Wireshark that the node keeps sending the same logs forever.So the jenkins master is not (directly) the culprit.After enabling the debugguer on the slave, I've found that the method FileMonitoringTask$FileMonitoringController$WriteLog.invoke is called in an infinite loop somewhere in this file: durable-task-plugin\src\main\java\org\jenkinsci\plugins\durabletask\FileMonitoringTask.javaThe same file is read again and again with a lastLocation of 1930670. lastLocation represent the bytes already read. But I don't understand why it doesn't increase.The process is terminated, the log file is not bigger than 3MB (and can be seen in the upper left corner of the screenshot)!Capture d'écran de 2016-08-20 17-04-34.png|thumbnail!*Update 1:* It seems that Jenkins read the whole file. If it fails, it will return 0. I suspect that Jenkins is failing to close the file descriptor. So the lastLocation is not updated. But the data are sent. Jenkins retries to read the file, fail again, etc. That's only a supposition for now.*Update 2:* It seems that it comes from the network, as I've captured a java.io.InterruptedIOException in this loop in hudson.remoting.ProxyOutputStream.!Capture d'écran de 2016-08-20 19-02-41.png|thumbnail!*Update 3: *It seems that the Jenkins Master is guilty. I've connected my debugger to this one. The error occurs when it tries to write the log in its JENKINS_HOME. When executing the green line on the following screenshot. !Capture d'écran de 2016-08-20 19-35-36.png|thumbnail! The error is catched in DurableTaskStep$Execution.check, as it seems to be a workspace error. It seems that Jenkins doesn't find the workspace folder, as it's searching the jenkins node workspace in its local file system. C:\\ci\\int12\\ocoint... So it saves the log but interrupt the task, send to the slave that it has interrupted the task. The slave thinks that the logs has not been saved, and resend it to the master, which don't find the node workspace in it's local filesystem, etc. !Capture d'écran de 2016-08-20 19-35-13.png|thumbnail! h1. How to reproduceI've tried to reproduce this bug for 3 days but didn't achieve to.
[JIRA] (JENKINS-33549) Expose Job name for the exception java.lang.IllegalStateException: cannot create a build with number XX since that (or higher) is already in use among [XX]
Title: Message Title SCM/JIRA link daemon commented on JENKINS-33549 Re: Expose Job name for the exception java.lang.IllegalStateException: cannot create a build with number XX since that (or higher) is already in use among [XX] Code changed in jenkins User: Daniel Beck Path: core/src/main/java/jenkins/model/lazy/LazyBuildMixIn.java http://jenkins-ci.org/commit/jenkins/239ec86bdb39db1009facf7eadb693d4c6c83cdd Log: Merge pull request #2125 from fbelzunc/JENKINS-33549 [FIXED JENKINS-33549] Specify on the logger the job which cannot create a new build Compare: https://github.com/jenkinsci/jenkins/compare/4376fdedfc85...239ec86bdb39 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33549) Expose Job name for the exception java.lang.IllegalStateException: cannot create a build with number XX since that (or higher) is already in use among [XX]
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-33549 Expose Job name for the exception java.lang.IllegalStateException: cannot create a build with number XX since that (or higher) is already in use among [XX] Change By: SCM/JIRA link daemon Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37575) Jenkins node keeps sending the sames logs indefinitely
Title: Message Title Quentin Dufour updated an issue Jenkins / JENKINS-37575 Jenkins node keeps sending the sames logs indefinitely Change By: Quentin Dufour h1. Problem The Sometimes, after a certain amount of builds, the build never ends on the node. It sends forever the same 20-30 lines. It seems that the problem occures more when I restart Jenkins while there are some tasks running. We can see the difference between the timestamper date (put when received by the master) and the log date (written during the Powershell execution)!Capture d'écran de 2016-08-20 16-35-18.png|thumbnail!Some logs files can be bigger than 10GB before I kill the process.(Yes, it's really stored in the JENKINS_HOME)!jekins_10GB_log.png|thumbnail!h1. Investigationh2. StepsI've found on Wireshark that the node keeps sending the same logs forever.So the jenkins master is not (directly) the culprit.After enabling the debugguer on the slave, I've found that the method FileMonitoringTask$FileMonitoringController$WriteLog.invoke is called in an infinite loop somewhere in this file: durable-task-plugin\src\main\java\org\jenkinsci\plugins\durabletask\FileMonitoringTask.javaThe same file is read again and again with a lastLocation of 1930670. lastLocation represent the bytes already read. But I don't understand why it doesn't increase.The process is terminated, the log file is not bigger than 3MB (and can be seen in the upper left corner of the screenshot)!Capture d'écran de 2016-08-20 17-04-34.png|thumbnail!*Update 1:* It seems that Jenkins read the whole file. If it fails, it will return 0. I suspect that Jenkins is failing to close the file descriptor. So the lastLocation is not updated. But the data are sent. Jenkins retries to read the file, fail again, etc. That's only a supposition for now.*Update 2:* It seems that it comes from the network, as I've captured a java.io.InterruptedIOException in this loop in hudson.remoting.ProxyOutputStream.!Capture d'écran de 2016-08-20 19-02-41.png|thumbnail!*Update 3:* It seems that the Jenkins Master is guilty. I've connected my debugger to this one. The error occurs when it tries to write the log in its JENKINS_HOME. When executing the green line on the following screenshot. !Capture d'écran de 2016-08-20 19-35-36.png|thumbnail! The error is catched in DurableTaskStep$Execution.check, as it seems to be a workspace error. It seems that Jenkins doesn't find the workspace folder, as it's searching the jenkins node workspace in its local file system. C:\\ci\\int12\\ocoint... So it saves the log but interrupt the task, send to the slave that it has interrupted the task. The slave thinks that the logs has not been saved, and resend it to the master, which don't find the node workspace in it's local filesystem, etc. !Capture d'écran de 2016-08-20 19-35-13.png|thumbnail! h1. How to reproduceI've tried to reproduce this bug for 3 days but didn't achieve to. I had to put my production in debug to inspect the error.As I don't understand why it fails, I can't create a reproduce protocol ye
[JIRA] (JENKINS-37575) Jenkins node keeps sending the sames logs indefinitely
Title: Message Title Quentin Dufour updated an issue Jenkins / JENKINS-37575 Jenkins node keeps sending the sames logs indefinitely Change By: Quentin Dufour h1. ProblemSometimes, after a certain amount of builds, the build never ends on the node. It sends forever the same 20-30 lines.It seems that the problem occures more when I restart Jenkins while there are some tasks running.We can see the difference between the timestamper date (put when received by the master) and the log date (written during the Powershell execution)!Capture d'écran de 2016-08-20 16-35-18.png|thumbnail!Some logs files can be bigger than 10GB before I kill the process.(Yes, it's really stored in the JENKINS_HOME)!jekins_10GB_log.png|thumbnail!h1. Investigationh2. StepsI've found on Wireshark that the node keeps sending the same logs forever.So the jenkins master is not (directly) the culprit.After enabling the debugguer on the slave, I've found that the method FileMonitoringTask$FileMonitoringController$WriteLog.invoke is called in an infinite loop somewhere in this file: durable-task-plugin\src\main\java\org\jenkinsci\plugins\durabletask\FileMonitoringTask.javaThe same file is read again and again with a lastLocation of 1930670. lastLocation represent the bytes already read. But I don't understand why it doesn't increase.The process is terminated, the log file is not bigger than 3MB (and can be seen in the upper left corner of the screenshot)!Capture d'écran de 2016-08-20 17-04-34.png|thumbnail!*Update 1:* It seems that Jenkins read the whole file. If it fails, it will return 0. I suspect that Jenkins is failing to close the file descriptor. So the lastLocation is not updated. But the data are sent. Jenkins retries to read the file, fail again, etc. That's only a supposition for now.*Update 2:* It seems that it comes from the network, as I've captured a java.io.InterruptedIOException in this loop in hudson.remoting.ProxyOutputStream.!Capture d'écran de 2016-08-20 19-02-41.png|thumbnail!*Update 3:* It seems that the Jenkins Master is guilty. I've connected my debugger to this one. The error occurs when it tries to write the log in its JENKINS_HOME. When executing the green line on the following screenshot. !Capture d'écran de 2016-08-20 19-35-36.png|thumbnail! The error is catched in DurableTaskStep$Execution.check, as it seems to be a workspace error. It seems that Jenkins doesn't find the workspace folder, as it's searching the jenkins node workspace in its local file system. C:\\ci\\int12\\ocoint... So it saves the log but interrupt the task, send to the slave that it has interrupted the task. The slave thinks that the logs has not been saved, and resend it to the master, which don't find the node workspace in it's local filesystem, etc. !Capture d'écran de 2016-08-20 19-35-13.png|thumbnail! *Update 4:* It seems that when the master deserializes the response of the node, it returns a null object instead of the logs when it comes to Write Logs... !Capture d'écran de 2016-08-20 23-41-53.png|thumbnail! h1. How to
[JIRA] (JENKINS-37575) Jenkins node keeps sending the sames logs indefinitely
Title: Message Title Quentin Dufour updated an issue Jenkins / JENKINS-37575 Jenkins node keeps sending the sames logs indefinitely Change By: Quentin Dufour Attachment: Capture d'écran de 2016-08-20 23-41-53.png Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37576) Provide rest API for finding job details by job name
Title: Message Title Aleksey Maksimov created an issue Jenkins / JENKINS-37576 Provide rest API for finding job details by job name Issue Type: New Feature Assignee: Unassigned Components: core Created: 2016/Aug/21 5:04 AM Priority: Minor Reporter: Aleksey Maksimov Currently, in order to find job information by job name, somebody would need to query REST API for all jobs and then find required job in list. This is expensive operation on Jenkins instances that has thousands of jobs - the returned list will be huge with a lot of information which is not relevant for required operation. Limiting data with "?tree=" option doesn't help much because it will still contain all jobs and their urls. I've tried to use "Find job" AJAX call that is used by search box, but this search doesn't operate on job name, but operate on job display name. Having a special REST call to retrieve job details by job name would be great to have, especially for large Jenkins instances. Note: I am maintainer of Jenkinsapi python library (https://github.com/pycontribs/jenkinsapi) Add Comment
[JIRA] (JENKINS-37568) Email Ext Plugin broke the Jenkins
Title: Message Title David van Laatum commented on JENKINS-37568 Re: Email Ext Plugin broke the Jenkins Are you using watching? I haven't touched anything around there recently if your not using try turning off Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
