[JIRA] [core] (JENKINS-12699) Temp upload files from file param not removed after transferred to slave
Title: Message Title
Elgin Peteza edited a comment on JENKINS-12699
Re: Temp upload files from file param not removed after transferred to slave
Update:I encountered another problem with the {{upload_\*.tmp}} files.I executed the job many times such that several builds will be queued on one node (and several {{upload_\*.tmp}} files created in {{/tmp}} directory of the master), and then I restarted Jenkins in the middle. Those builds before restart were built successfully ({{upload_\*.tmp}} files still not deleted). The remaining builds after restart, surprisingly, failed with the following error in the console:{code:java}FATAL: nulljava.lang.NullPointerException at hudson.model.FileParameterValue$2.setUp(FileParameterValue.java:143) at hudson.model.Build$BuildExecution.doRun(Build.java:156) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:537) at hudson.model.Run.execute(Run.java:1744) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:374){code}From previous successful builds, the console showed:{code:java}Copying file to jenkins_file.zip{code}All {{upload_\*.tmp}} files were still in {{/tmp}} directory after the error occurred. Edited Added :Maybe this is an entirely different bug. Based on my tests, only file parameters greater than 10kB generate {{upload_\*.tmp}} files in {{/tmp}} directory. The error described above also occurred even for file parameters smaller than 10kB, which didn't create an {{upload_\*.tmp}} in the first place.
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-12699) Temp upload files from file param not removed after transferred to slave
Title: Message Title
Elgin Peteza edited a comment on JENKINS-12699
Re: Temp upload files from file param not removed after transferred to slave
Update:I encountered another problem with the {{upload_\*.tmp}} files.I executed the job many times such that several builds will be queued on one node (and several {{upload_\*.tmp}} files created in {{/tmp}} directory of the master), and then I restarted Jenkins in the middle. Those builds before restart were built successfully ({{upload_\*.tmp}} files still not deleted). The remaining builds after restart, surprisingly, failed with the following error in the console:{code:java}FATAL: nulljava.lang.NullPointerException at hudson.model.FileParameterValue$2.setUp(FileParameterValue.java:143) at hudson.model.Build$BuildExecution.doRun(Build.java:156) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:537) at hudson.model.Run.execute(Run.java:1744) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:374){code}From previous successful builds, the console showed:{code:java}Copying file to jenkins_file.zip{code}All {{upload_\*.tmp}} files were still in {{/tmp}} directory after the error occurred. Edited:Maybe this is an entirely different bug. Based on my tests, only file parameters greater than 10kB generate {{upload_\*.tmp}} files in {{/tmp}} directory. The error described above also occurred even for file parameters smaller than 10kB, which didn't create an {{upload_\*.tmp}} in the first place.
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] [sectioned-view-plugin] (JENKINS-29204) Build description is not updated when job displayed by Sectioned List View
Title: Message Title Frantisek Reznicek updated an issue Jenkins / JENKINS-29204 Build description is not updated when job displayed by Sectioned List View Change By: Frantisek Reznicek Attachment: JENKINS-29204_build description_from_sectioned_list_view_page.png Attachment: JENKINS-29204_build_description_from_job_build_page.png Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [sectioned-view-plugin] (JENKINS-29204) Build description is not updated when job displayed by Sectioned List View
Title: Message Title Frantisek Reznicek commented on JENKINS-29204 Re: Build description is not updated when job displayed by Sectioned List View This issue is likely the same as part of JENKINS-21295 (redisplaying part) 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] [sectioned-view-plugin] (JENKINS-29204) Build description is not updated when job displayed by Sectioned List View
Title: Message Title Frantisek Reznicek created an issue Jenkins / JENKINS-29204 Build description is not updated when job displayed by Sectioned List View Issue Type: Bug Assignee: Timothy Bingaman Components: sectioned-view-plugin Created: 03/Jul/15 5:30 AM Environment: Jenkins ver. 1.609.1 on a RHEL 6.6 x86_64 LTS as client using FF 38.0.1 or 17.0.11 ESR Priority: Minor Reporter: Frantisek Reznicek Build description is not updated when job displayed by Sectioned List View There is discrepancy what a] http:///view/Messaging/job/mrgm_mrg2517_dtests_acceptance_r6x_vm/ b] http:///view/Messaging configured as Sectioned list view, every list section displays also Build description are displaying as a] displays correctly current build description, but b] keeps showing the obsoleted current build state (valid at the beginning when build was launched). When build finished b] updates corerctly. The problem is that b] does not update on every build description change (just o
[JIRA] [build-flow-plugin] (JENKINS-21199) Fail fast - When one parallel job fails, fail the flow job (and optionally cancel the rest)
Title: Message Title A C edited a comment on JENKINS-21199 Re: Fail fast - When one parallel job fails, fail the flow job (and optionally cancel the rest) +1Failing and cancelling a parallel block as soon as one inner block fails would be a very useful feature indeed. Either as an option on the parallel block, or as a new DSL command, as long as the idea is implemented.It's easy to envision the use cases for both:* Failing fast is useful when you know that a single failure will cause subsequent failures, eg a particular package build fails, so of course deploying the a full new package release will fail* Not failing fast is useful when you want to run a battery of independent tests 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] [warnings-plugin] (JENKINS-29203) StyleCop warnings are counted twice
Title: Message Title Michael Fowler created an issue Jenkins / JENKINS-29203 StyleCop warnings are counted twice Issue Type: Bug Assignee: Ulli Hafner Components: warnings-plugin Created: 03/Jul/15 2:32 AM Priority: Major Reporter: Michael Fowler StyleCop warnings are counted twice. Once in the MSBuild warnings, and once more in the StyleCop warnings. Can the MSBuild parser be changed to ignore StyleCop warnings? Add Comment This message was sen
[JIRA] [build-flow-plugin] (JENKINS-21199) Fail fast - When one parallel job fails, fail the flow job (and optionally cancel the rest)
Title: Message Title A C commented on JENKINS-21199 Re: Fail fast - When one parallel job fails, fail the flow job (and optionally cancel the rest) +1 Failing and cancelling a parallel block as soon as one inner block fails would be a very useful feature indeed. Either as an option on the parallel block, or as a new DSL command, as long as the idea is implemented. It's easy to envision the use cases for both: Failing fast is useful when you know that a single failure will cause subsequent failures, eg a particular package build fails, so of course deploying the new package will fail Not failing fast is useful when you want to run a battery of independent tests Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cli] (JENKINS-28527) Invoking groovy script via CLI fails with spurious 'missing jar' error.
Title: Message Title Alex Earl updated an issue Jenkins / JENKINS-28527 Invoking groovy script via CLI fails with spurious 'missing jar' error. If you are willing, can you try the attached email-ext plugin version? I removed the direct dependency on groovy and use the one included with Jenkins. I haven't been able to test this very much. Change By: Alex Earl Attachment: email-ext.hpi 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-29179) IndexOutOfBounds Exception when viewing live console
Title: Message Title Austin Ward commented on JENKINS-29179 Re: IndexOutOfBounds Exception when viewing live console This seems to happen mostly on multi configuration jobs where I have a job run on all my nodes. I am still trying to find the exact pattern. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [logstash-plugin] (JENKINS-29202) logstash 1.1.0 tries to create a queue which already exists on ReddisMQ server - and fails
Title: Message Title Alexey Java updated an issue Jenkins / JENKINS-29202 logstash 1.1.0 tries to create a queue which already exists on ReddisMQ server - and fails Change By: Alexey Java Summary: logstash 1.1.0 prints "channel is already closed due to channel error", error code 406 - it tries to create a queue which already exists on ReddisMQ server - and fails Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [logstash-plugin] (JENKINS-29202) logstash 1.1.0 prints "channel is already closed due to channel error", error code 406 - it tries to create a queue which already exists on ReddisMQ server
Title: Message Title
Alexey Java updated an issue
Jenkins / JENKINS-29202
logstash 1.1.0 prints "channel is already closed due to channel error", error code 406 - it tries to create a queue which already exists on ReddisMQ server
Change By:
Alexey Java
I get this with Jenkins 1.618 running on MacOS.Logstash plugin 1.1.0.target system: RabbitMQ. note: in the plugin settings I put a name of the existing ReddisMQ queue. apparently, the plugin tried to recreate it rather than just use it. {quote}FATAL: channel is already closed due to channel error; protocol method: #method(reply-code=406, reply-text=PRECONDITION_FAILED - inequivalent arg 'x-message-ttl'for queue 'alex-demo-queue' in vhost '/': received none but current is the value '10' of type 'long', class-id=50, method-id=10){quote}
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [logstash-plugin] (JENKINS-29202) logstash 1.1.0 prints "channel is already closed due to channel error", error code 406 - it tries to create a queue which already exists on ReddisMQ server
Title: Message Title Alexey Java updated an issue Jenkins / JENKINS-29202 logstash 1.1.0 prints "channel is already closed due to channel error", error code 406 - it tries to create a queue which already exists on ReddisMQ server Change By: Alexey Java Summary: logstash 1.1.0 prints "channel is already closed due to channel error", error code 406 - it tries to create a queue which already exists on ReddisMQ server Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [logstash-plugin] (JENKINS-29202) logstash 1.1.0 prints "channel is already closed due to channel error", error code 406
Title: Message Title Alexey Java commented on JENKINS-29202 Re: logstash 1.1.0 prints "channel is already closed due to channel error", error code 406 this page http://rabbitmq.1065348.n5.nabble.com/rabbitmq-simple-message-sending-error-td21738.html says that the problem may be because the plugin tries to re-declare (create) already existing queue. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [logstash-plugin] (JENKINS-29202) logstash 1.1.0 prints "channel is already closed due to channel error", error code 406
Title: Message Title Alexey Java updated an issue Jenkins / JENKINS-29202 logstash 1.1.0 prints "channel is already closed due to channel error", error code 406 Change By: Alexey Java Attachment: screenshot-1.png Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [logstash-plugin] (JENKINS-29202) logstash 1.1.0 prints "channel is already closed due to channel error", error code 406
Title: Message Title Alexey Java created an issue Jenkins / JENKINS-29202 logstash 1.1.0 prints "channel is already closed due to channel error", error code 406 Issue Type: Bug Assignee: Unassigned Components: logstash-plugin Created: 03/Jul/15 1:01 AM Priority: Minor Reporter: Alexey Java I get this with Jenkins 1.618 running on MacOS. Logstash plugin 1.1.0. target system: RabbitMQ. FATAL: channel is already closed due to channel error; protocol method: #method(reply-code=406, reply-text=PRECONDITION_FAILED - inequivalent arg 'x-message-ttl'for queue 'alex-demo-queue' in vhost '/': received none but current is the value '10' of type 'long', class-id=50, method-id=10) Add Comment
[JIRA] [websphere-deployer-plugin] (JENKINS-29201) Webspherer deploy error - could not bind resource refs
Title: Message Title Michael Aldor updated an issue Jenkins / JENKINS-29201 Webspherer deploy error - could not bind resource refs Change By: Michael Aldor Environment: Windows 2008R2 with Jenkins Jenkins 1.596.2 Deploying to an external Websphere 8.0 server Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [websphere-deployer-plugin] (JENKINS-29201) Webspherer deploy error - could not bind resource refs
Title: Message Title Michael Aldor created an issue Jenkins / JENKINS-29201 Webspherer deploy error - could not bind resource refs Issue Type: Bug Assignee: Unassigned Attachments: Jenkins-webspheredirectory.PNG Components: websphere-deployer-plugin Created: 02/Jul/15 11:23 PM Environment: Windows 2008R2 with Jenkins Deploying to an external Websphere 8.0 server Priority: Major Reporter: Michael Aldor Can't complete a deploy getting the following error in the logs. Suggestions welcome The Jar files are in the .Jenkins folder C:\Windows\System32\config\systemprofile\.jenkins\plugins\websphere-deployer\WEB-INF\lib com.ibm.ws.admin.client_8.0.0.jar com.ibm.ws.orb_8.0.0.jar Connecting to IBM WebSphere Application Server... The following artifacts will be deployed in this order... --- extsecadmin.ear --- Error deploying to IBM WebSphere Application
[JIRA] [bitbucket-plugin] (JENKINS-28877) Bitbucket Plugin unable to parse Bitbucket webhook response json
Title: Message Title uded commented on JENKINS-28877 Re: Bitbucket Plugin unable to parse Bitbucket webhook response json There is a great pull request to solve the issue - maybe someone can revert #15 and merge #17? https://github.com/jenkinsci/bitbucket-plugin/pull/17 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-27361) In IE11, horiz scrollbar overlaps Jenkins content
Title: Message Title Daniel Beck commented on JENKINS-27361 Re: In IE11, horiz scrollbar overlaps Jenkins content I'm not sure I understand this issue. To read what's below the scrollbar, just stop moving the mouse for a few seconds and the scrollbars hide. I think the horizontal scrolling is much more annoying (which with the -ms-overflow-style: scrollbar will always be visible). I'll try to get one of my colleagues to take a look at this. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [parameterized-remote-trigger-plugin] (JENKINS-28958) Parameters from file not passed to downstream job
Title: Message Title Keith Lee commented on JENKINS-28958 Re: Parameters from file not passed to downstream job yet another update. The 'Parameters' field needs to have any value. Seems like a bug. 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-29160) Ability to customise how many items are shown in the Build History widget
Title: Message Title Daniel Beck resolved as Won't Fix This happens because your Jenkins master does not have enough RAM available, resulting in constant loading of build records from disk (and discarding them again immediately from memory to make space for other data). Use the Xmx JVM option to increase heap size. Since this likely easily resolved performance issue motivates the request rather than e.g. usability, resolving as Won't Fix. Jenkins / JENKINS-29160 Ability to customise how many items are shown in the Build History widget Change By: Daniel Beck Status: Open Resolved Resolution: Won't Fix Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options
[JIRA] [groovy-postbuild-plugin] (JENKINS-29016) Option "If the scripts fails" doesn't cause build failure
Title: Message Title ikedam assigned an issue to ikedam Could not reproduce. You may describe more details. Steps I tested (Jenkins 1.609.1, groovy-postbuild 2.2): Create a freestyle project Add Groovy Postbuild to Post-build Actions Groovy Script foobar Use Groovy Sandbox: checked If the script fails: Make build as failed Run a build Result The build failed with FAILURE Log output: ERROR: Failed to evaluate groovy script. groovy.lang.MissingPropertyException: No such property: foobar for class: groovy.lang.Binding at groovy.lang.Binding.getVariable(Binding.java:62) at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onGetProperty(SandboxInterceptor.java:139) at org.kohsuke.groovy.sandbox.impl.Checker$4.call(Checker.java:153) at org.kohsuke.groovy.sandbox.impl.Checker.checkedGetProperty(Checker.java:150) at org.kohsuke.groovy.sandbox.impl.Checker$checkedGetProperty.callStatic(Unknown Source) at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCallStatic(CallSiteArray.java:50) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callStatic(AbstractCallSite.java:157) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callStatic(AbstractCallSite.java:177) at Script1.run(Script1.groovy:1) at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.GroovySandbox.run(GroovySandbox.java:139) at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SecureGroovyScript.evaluate(SecureGroovyScript.java:161) at org.jvnet.hudson.plugins.groovypostbuild.GroovyPostbuildRecorder.perform(GroovyPostbuildRecorder.java:361) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:761) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:721) at hudson.model.Build$BuildExecution.post2(Build.java:183) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:670) at hudson.model.Run.execute(Run.java:1766) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Exec
[JIRA] [parameterized-remote-trigger-plugin] (JENKINS-28958) Parameters from file not passed to downstream job
Title: Message Title
Keith Lee edited a comment on JENKINS-28958
Re: Parameters from file not passed to downstream job
An update. I don't know whether it's by design or not but I found that I need to have the property defined in the 'Parameters' text field.Namely in your case define WITH_COMMIT in 'Parameters' text field. No need to assign a value.My understanding on this behaviour is that the plugin replaces value of the property defined in 'Parameters' text field if exists with the value from the file and send sends it to remote Jenkins otherwise it send sends the weird {} data to remote Jenkins which it doesn't understand.hope this helpsNote: One more thing missing from the documentation is configuring remote job. I needed to check "This build is parameterized" and add a String Parameter with Name same as my property name.
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] [parameterized-remote-trigger-plugin] (JENKINS-28958) Parameters from file not passed to downstream job
Title: Message Title
Keith Lee edited a comment on JENKINS-28958
Re: Parameters from file not passed to downstream job
An update. I don't know whether it's by design or not but I found that I need to have the property defined in the 'Parameters' text field.Namely in your case define WITH_COMMIT in 'Parameters' text field. No need to assign a value.My understanding on this behaviour is that the plugin replaces value of the property defined in 'Parameters' text field if exists and send it to remote Jenkins otherwise it send the weird {} data to remote Jenkins which it doesn't understand.hope this helps Note: One more thing missing from the documentation is configuring remote job. I needed to check "This build is parameterized" and add a String Parameter with Name same as my property name.
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] [parameterized-remote-trigger-plugin] (JENKINS-28958) Parameters from file not passed to downstream job
Title: Message Title
Keith Lee commented on JENKINS-28958
Re: Parameters from file not passed to downstream job
An update. I don't know whether it's by design or not but I found that I need to have the property defined in the 'Parameters' text field. Namely in your case define WITH_COMMIT in 'Parameters' text field. No need to assign a value.
My understanding on this behaviour is that the plugin replaces value of the property defined in 'Parameters' text field if exists and send it to remote Jenkins otherwise it send the weird {} data to remote Jenkins which it doesn't understand.
hope this helps
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-29198) Console logs get truncated without reason
Title: Message Title Daniel Beck commented on JENKINS-29198 Re: Console logs get truncated without reason Please make sure any issues you experience happen on a reasonably recent version of Jenkins. Since it's been more than a year since 1.553 was released, this issue may well be obsolete. 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-27361) In IE11, horiz scrollbar overlaps Jenkins content
Title: Message Title Daniel Beck assigned an issue to Daniel Beck Jenkins / JENKINS-27361 In IE11, horiz scrollbar overlaps Jenkins content Change By: Daniel Beck Assignee: Daniel Beck 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] [cloudbees-folder-plugin] (JENKINS-29050) Move a job clean his history
Title: Message Title Daniel Beck commented on JENKINS-29050 Re: Move a job clean his history Was the build number reset to 1, or is it higher? Did you customize the location of build records in the global configuration to be outside the job folder? Is there anything related in the Jenkins log? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [tfs-plugin] (JENKINS-29200) Executing tf using the TFS Plugin throws an IO exception
Title: Message Title Lakshmi Jaganathan created an issue Jenkins / JENKINS-29200 Executing tf using the TFS Plugin throws an IO exception Issue Type: Bug Assignee: redsolo Attachments: tfs.jpg Components: tfs-plugin Created: 02/Jul/15 9:33 PM Environment: Installed Jenkins in Windows7, TFS Plugin 3.2.0 Labels: plugin jenkins exception tfs tfs-plugin Priority: Major Reporter: Lakshmi Jaganathan I have added path of tf.cmd in environment vaiables and able to see tf configured in configure systems. Also I am able to execute the tf command in command prompt from path C:\XXX\Jenkins\TEE-CLC-12.0.2 (1)\TEE-CLC-12.0.2(this is the path configured in PATH environment variables). But When i trigger the build then i m getting below error while
[JIRA] [pam-auth-plugin] (JENKINS-25741) Unix User/Group Authentication Fails
Title: Message Title Daniel Beck commented on JENKINS-25741 Re: Unix User/Group Authentication Fails Jenkins 1.586/1.587 changed the version of JNA in Jenkins ( JENKINS-24521 , JENKINS-24527 ). Paul Allen Did you recently update Jenkins? 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] [weblogic-deployer-plugin] (JENKINS-20351) Recursive artifact search
Title: Message Title Andrew Wilkinson commented on JENKINS-20351 Re: Recursive artifact search This change is causing me problems. My ant build creates the ear to be deployed in a different directory each time I update the release number, for example: build/02_05_00/app.ear build/02_06_00/app.ear Then the build copies the ear to the root of the workspace to make it quick for the deployer to find it. But now the deployer doesn't look at the root of the workspace first. It is finding the oldest ear in build/02_05_00/app.ear. I can't figure out how to prevent the recursion or make it look in the workspace root first. So now I have to either clear the workspace each time or modify a bunch of build scripts to clear out any old builds. Am I missing something? 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] [packer-plugin] (JENKINS-28186) Packer installer from packer.io just a text box
Title: Message Title Daniel Beck resolved as Duplicate Basically a duplicate of JENKINS-27694. Jenkins / JENKINS-28186 Packer installer from packer.io just a text box Change By: Daniel Beck Status: Open Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion-plugin] (JENKINS-28484) Subversion tagging not working - E200015: ISVNAuthentication provider did not provide credentials
Title: Message Title Arthur Ramsey commented on JENKINS-28484 Re: Subversion tagging not working - E200015: ISVNAuthentication provider did not provide credentials I should note, I have multiple Jenkins instances with the same configuration and they all experience the same 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] [subversion-plugin] (JENKINS-28484) Subversion tagging not working - E200015: ISVNAuthentication provider did not provide credentials
Title: Message Title Arthur Ramsey commented on JENKINS-28484 Re: Subversion tagging not working - E200015: ISVNAuthentication provider did not provide credentials @man0war, it appears you're failing at checkout due to externals. I think JENKINS-22542 covers your problem. My issue seems specific to tagging and I don't use externals. 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] [subversion-plugin] (JENKINS-28484) Subversion tagging not working - E200015: ISVNAuthentication provider did not provide credentials
Title: Message Title Serguei Ivantsov commented on JENKINS-28484 Re: Subversion tagging not working - E200015: ISVNAuthentication provider did not provide credentials I also have the latest (2.5) version of the plugin. The log looks like this: Fetching At revision 1060 Fetching At revision 1060 Fetching At revision 1060 At revision 1060 At revision 1060 hudson.util.IOException2: revision check failed on http://server/some/external/path at hudson.scm.SubversionChangeLogBuilder.buildModule(SubversionChangeLogBuilder.java:196) at hudson.scm.SubversionChangeLogBuilder.run(SubversionChangeLogBuilder.java:137) at hudson.scm.SubversionSCM.calcChangeLog(SubversionSCM.java:725) at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:860) at hudson.scm.SCM.checkout(SCM.java:485) at hudson.model.AbstractProject.checkout(AbstractProject.java:1282) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:610) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:532) at hudson.model.Run.execute(Run.java:1744) 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: org.tmatesoft.svn.core.SVNCancelException: svn: E200015: E200015: ISVNAuthentication provider did not provide credentials; HTTP authorization cancelled. svn: E200015: ISVNAuthentication provider did not provide credentials; HTTP authorization cancelled. at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:60) at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:51) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:759) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:371) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:359) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.performHttpRequest(DAVConnection.java:710) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.exchangeCapabilities(DAVConnection.java:627) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.open(DAVConnection.java:102) at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.openConnection(DAVRepository.java:1032) at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.getLatestRevision(DAVRepository.java:175) at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgRepositoryAccess.getRevisionNumber(SvnNgRepositoryAccess.java:118) at org.tmatesoft.svn.core.internal.wc2.SvnRepositoryAccess.getLocations(SvnRepositoryAccess.java:184) at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgRepositoryAccess.createRepositoryFor(SvnNgRepositoryAccess.java:45) at org.tmatesoft.svn.core.internal.wc2.remote.SvnRemoteLog.run(SvnRemoteLog.java:160) at org.tmatesoft.svn.core.internal.wc2.remote.SvnRemoteLog.run(SvnRemoteLog.java:35) at org.tmatesoft.svn.core.internal.wc2.SvnOperationRunner.run(SvnOperationRunner.java:21) at org.tmatesoft.svn.core.wc2.SvnOperationFactory.run(SvnOperationFactory.java:1259) at org.tmatesoft.svn.core.wc2.SvnOperation.run(SvnOperation.java:294) at org.tmatesoft.svn.core.wc.SVNLogClient.doLog(SVNLogClient.java:968) at org.tmatesoft.svn.core.wc.SVNLogClient.doLog(SVNLogClient.java:873) at hudson.scm.SubversionChangeLogBuilder.buildModule(SubversionChangeLogBuilder.java:184) ... 12 more Caused by: org.tmatesoft.svn.core.SVNCancelException: svn: E200015: ISVNAuthentication provider did not provide credentials; HTTP authorization cancelled. at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:689) ... 30 more
[JIRA] [subversion-plugin] (JENKINS-28484) Subversion tagging not working - E200015: ISVNAuthentication provider did not provide credentials
Title: Message Title Arthur Ramsey commented on JENKINS-28484 Re: Subversion tagging not working - E200015: ISVNAuthentication provider did not provide credentials I also built the Subversion plug-in from master (2.6-SNAPSHOT) and it does the same. 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] [credentials-plugin] (JENKINS-29199) URIRequirementBuilder clears scheme when adding a path requirement
Title: Message Title Oleg Nenashev resolved as Fixed @Jeff Thanks for the fix! Jenkins / JENKINS-29199 URIRequirementBuilder clears scheme when adding a path requirement Change By: Oleg Nenashev Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [credentials-plugin] (JENKINS-29199) URIRequirementBuilder clears scheme when adding a path requirement
Title: Message Title Jeff Grafton created an issue Jenkins / JENKINS-29199 URIRequirementBuilder clears scheme when adding a path requirement Issue Type: Bug Assignee: Jeff Grafton Components: credentials-plugin Created: 02/Jul/15 7:53 PM Priority: Minor Reporter: Jeff Grafton While debugging the GitHub Pull Request plugin, I discovered that the URIRequirementBuilder class in the Credentials Plugin did not set a scheme on parsed URLs with a path (see https://github.com/jenkinsci/ghprb-plugin/issues/117#issuecomment-115488692). It looks like this was a simple copy-paste error from when the code was originally added. A patch has already been merged in https://github.com/jenkinsci/credentials-plugin/pull/26. Add Comment
[JIRA] [junit-plugin] (JENKINS-28490) jUnit (?) discarding tags when certain attributes are equal
Title: Message Title Kris Reeves commented on JENKINS-28490 Re: jUnit (?) discarding tags when certain attributes are equal Any chance of this seeing a fix? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion-plugin] (JENKINS-28484) Subversion tagging not working - E200015: ISVNAuthentication provider did not provide credentials
Title: Message Title Arthur Ramsey commented on JENKINS-28484 Re: Subversion tagging not working - E200015: ISVNAuthentication provider did not provide credentials Yes, it broke after updating Subversion and Credentials plug-ins yet rolling back doesn't fix it. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-19756) Build Periodically Should Include Bi-Weekly as an Option
Title: Message Title Damion Waltermeyer commented on JENKINS-19756 Re: Build Periodically Should Include Bi-Weekly as an Option I'd really like this as well. I have builds I'd like to run every other week automatically. Thanks 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] [subversion-plugin] (JENKINS-28484) Subversion tagging not working - E200015: ISVNAuthentication provider did not provide credentials
Title: Message Title Manuel Jesús Recena Soto commented on JENKINS-28484 Re: Subversion tagging not working - E200015: ISVNAuthentication provider did not provide credentials Arthur Ramsey Did you do an update of Subversion plugin? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion-plugin] (JENKINS-28484) Subversion tagging not working - E200015: ISVNAuthentication provider did not provide credentials
Title: Message Title Manuel Jesús Recena Soto stopped work on JENKINS-28484 Change By: Manuel Jesús Recena Soto Status: In Progress Open 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] [google-login-plugin] (JENKINS-27117) google login plugin not working
Title: Message Title Ray Sennewald commented on JENKINS-27117 Re: google login plugin not working I'm running into the same problem here. I tried updating to v1.609.1 (latest stable LTS release), but I still get the same error. I don't have the capability of having my Jenkins server's URL on the same domain as our Google Apps. Any ETA on a fix for this? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion-plugin] (JENKINS-28484) Subversion tagging not working - E200015: ISVNAuthentication provider did not provide credentials
Title: Message Title Manuel Jesús Recena Soto started work on JENKINS-28484 Change By: Manuel Jesús Recena Soto Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion-plugin] (JENKINS-28484) Subversion tagging not working - E200015: ISVNAuthentication provider did not provide credentials
Title: Message Title Manuel Jesús Recena Soto assigned an issue to Manuel Jesús Recena Soto Jenkins / JENKINS-28484 Subversion tagging not working - E200015: ISVNAuthentication provider did not provide credentials Change By: Manuel Jesús Recena Soto Assignee: Manuel Jesús Recena Soto 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-29198) Console logs get truncated without reason
Title: Message Title Namikaze Minato edited a comment on JENKINS-29198 Re: Console logs get truncated without reason Wow, I am just facing this issue at the very moment, in the middle of a map/reduce job. (I can see in the jobtracker this map/reduce job finished a long time ago and my (still running) jenkins job started the next one map/reduce )I opened the console and all progressiveHtml calls were empty. http://prntscr.com/7o0vg9Things I tried:Refreshing - same stateOpening another tab/window - same stateLooking at /consoleText - same stateManually opening /consoleFull - same stateLogging out and logging in in an incognito window - same state(So "runing for a long time without anything getting output" has nothing to do with this bug)Number of lines before stopping this time: 3201 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-29198) Console logs get truncated without reason
Title: Message Title Namikaze Minato commented on JENKINS-29198 Re: Console logs get truncated without reason Wow, I am just facing this issue at the very moment, in the middle of a map/reduce job. (I can see in the jobtracker this job finished a long time ago and jenkins started the next one) I opened the console and all progressiveHtml calls were empty. http://prntscr.com/7o0vg9 Things I tried: Refreshing - same state Opening another tab/window - same state Looking at /consoleText - same state Manually opening /consoleFull - same state Logging out and logging in in an incognito window - same state (So "runing for a long time without anything getting output" has nothing to do with this bug) Number of lines before stopping this time: 3201 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4-plugin] (JENKINS-25364) Unable to update workspace error
Title: Message Title A C commented on JENKINS-25364 Re: Unable to update workspace error This issue just hit my Jenkins farm. This happened subsequent to a build cancelled while a long p4 sync was still in progress; have not found a workaround yet. No SCM polling is used. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-27508) Cannot used ENV Variable for repository url in GIT-Plugin in GIT Publisher
Title: Message Title Deniz Bahadir commented on JENKINS-27508 Re: Cannot used ENV Variable for repository url in GIT-Plugin in GIT Publisher There are also other form-fields where successfull variable-substitution would make sense. For example I stumbled about the missing substitution-feature for the Path field of the Sparse Checkout path option. However, variable-substitution works e.g. for the Local subdirectory for repo field of the Check out to a sub-directory option. I would suggest this plugin supports (environment) variable-substitution in all form-fields. 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-29198) Console logs get truncated without reason
Title: Message Title Namikaze Minato created an issue Jenkins / JENKINS-29198 Console logs get truncated without reason Issue Type: Bug Assignee: Unassigned Components: core Created: 02/Jul/15 5:14 PM Environment: Jenkins ver. 1.553, Chrome browser Labels: jenkins user-experience Priority: Minor Reporter: Namikaze Minato I have a bug which looks similar to JENKINS-14899 : Sometimes, when a job runs for a long time without anything getting output, the jenkins page stops updating until the job finishes. Then it add the completion lines (SUCCESS or FAILURE) to the job. The difference is that the number of line does not matter (last bug occurence was on a job that output 264 lines (+ an unknown number of non-output lines) This results in a truncated /console, /consoleFull and /consoleText. All
[JIRA] [github-plugin] (JENKINS-29197) Set Commit Status on GitHub not working
Title: Message Title
steven magelowitz created an issue
Jenkins / JENKINS-29197
Set Commit Status on GitHub not working
Issue Type:
Bug
Assignee:
Unassigned
Components:
github-plugin
Created:
02/Jul/15 5:07 PM
Priority:
Major
Reporter:
steven magelowitz
I'm getting the following error, when trying to set the build status on GitHub. Maybe the API changed?
09:59:11 Setting commit status on GitHub for https://github.com/kiva/zip/commit/8a3ae0d2bb4a90204a1f00feec6a3711e1a09c9d 09:59:11 FATAL: {"message":"Not Found","documentation_url":"https://developer.github.com/v3"}
09:59:11 java.io.FileNotFoundException: {"message":"Not Found","documentation_url":"https://developer.github.com/v3"}
09:59:11 at org.kohsuke.github.Requester.handleApiError(Requester.java:494) 09:59:11 at org.kohsuke.github.Requester._to(Requester.java:245) 09:59:11 at org.kohsuke.github.Requester.to(Requester.java:191) 09:59:11 at org.kohsuke.github.GHRepository.createCommitStatus(GHRepository.java:780) 09:59:11 at com.cloudbees.jenkins.GitHubSetCommitStatusBuilder.perform(GitHubSetCommitStatusBuilder.java:32) 09:59:11 at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) 09:59:11 at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:779) 09:59:11 at hudson.model.Build$BuildExecution.build(Build.java:205) 09:59:11 at hudson.model.Build$BuildExecution.doRun(Build.java:162) 09:59:11 at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:537) 09:59:11 at hudson.model.Run.execute(Run.java:1741) 09:59:11 at huds
[JIRA] [pam-auth-plugin] (JENKINS-25741) Unix User/Group Authentication Fails
Title: Message Title Paul Allen commented on JENKINS-25741 Re: Unix User/Group Authentication Fails I too have the same issue on Jenkins 1.598. I upgraded a plugin by uploading the HPI file and had the issue after a restart. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [test-results-analyzer-plugin] (JENKINS-29111) Show packages/classes/methods in sorted order
Title: Message Title Varun Menon resolved as Fixed Fixed in 0.2.1 Jenkins / JENKINS-29111 Show packages/classes/methods in sorted order Change By: Varun Menon Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [test-results-analyzer-plugin] (JENKINS-27628) Test results analyzer displays class as FAILED when a testcase is skipped
Title: Message Title Varun Menon resolved as Fixed Fixed in 0.2.1 Jenkins / JENKINS-27628 Test results analyzer displays class as FAILED when a testcase is skipped Change By: Varun Menon Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [test-results-analyzer-plugin] (JENKINS-27628) Test results analyzer displays class as FAILED when a testcase is skipped
Title: Message Title Varun Menon closed an issue as Fixed Jenkins / JENKINS-27628 Test results analyzer displays class as FAILED when a testcase is skipped Change By: Varun Menon Status: Resolved Closed 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] [test-results-analyzer-plugin] (JENKINS-29111) Show packages/classes/methods in sorted order
Title: Message Title Varun Menon closed an issue as Fixed Jenkins / JENKINS-29111 Show packages/classes/methods in sorted order Change By: Varun Menon Status: Resolved Closed 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] [test-results-analyzer-plugin] (JENKINS-29186) Pie chart title showing a wrong build number when the chart generated for a build from line chart
Title: Message Title Varun Menon resolved as Fixed Fixed in 0.2.1 Jenkins / JENKINS-29186 Pie chart title showing a wrong build number when the chart generated for a build from line chart Change By: Varun Menon Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [test-results-analyzer-plugin] (JENKINS-29186) Pie chart title showing a wrong build number when the chart generated for a build from line chart
Title: Message Title Varun Menon closed an issue as Fixed Jenkins / JENKINS-29186 Pie chart title showing a wrong build number when the chart generated for a build from line chart Change By: Varun Menon Status: Resolved Closed 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] [svn-tag-plugin] (JENKINS-28433) Subversion-Tagging Plugin-Tagging Fails
Title: Message Title Tom Moore commented on JENKINS-28433 Re: Subversion-Tagging Plugin-Tagging Fails This happens because the svn-tag plugin available in the Plugin Manager (1.17) was built with a dependency on version 2.2 of the Subversion plugin in its pom.xml. Until a new release of svn-tag is made, svn-tag 1.17 can be made to work with the Subversion plugin 2.5 by pulling the source for svn-tag 1.17 and changing the pom.xml to have a dependency on the subversion 2.5 plugin, then run maven clean install to generate a new .hpi Replace the existing svn-tag.hpi with the one you compiled and restart Jenkins. Tagging will work again. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [join-plugin] (JENKINS-29196) Remove deprecated copyarchiver-plugin dependency
Title: Message Title Radek Antoniuk resolved as Fixed Merged by mdonohue. Scheduled for release in 1.16. Jenkins / JENKINS-29196 Remove deprecated copyarchiver-plugin dependency Change By: Radek Antoniuk Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [copyarchiver-plugin] (JENKINS-5921) CopyArchiver Plugin: Do not saves "Shared directory" parameter
Title: Message Title Radek Antoniuk commented on JENKINS-5921 Re: CopyArchiver Plugin: Do not saves "Shared directory" parameter Removed deprecated dependency to that plugin in JENKINS-29196 . 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-29179) IndexOutOfBounds Exception when viewing live console
Title: Message Title Austin Ward updated an issue Jenkins / JENKINS-29179 IndexOutOfBounds Exception when viewing live console Change By: Austin Ward Labels: console consoleoutput crash stacktrace stapler stapler-class 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] [join-plugin] (JENKINS-29196) Remove deprecated copyarchiver-plugin dependency
Title: Message Title Radek Antoniuk created an issue Jenkins / JENKINS-29196 Remove deprecated copyarchiver-plugin dependency Issue Type: Task Assignee: Radek Antoniuk Components: join-plugin Created: 02/Jul/15 4:02 PM Labels: join-plugin-1.16 Priority: Minor Reporter: Radek Antoniuk Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [proc-cleaner-plugin] (JENKINS-29195) Plug-in doesn't work on HP-UX
Title: Message Title Pavel Janoušek created an issue Jenkins / JENKINS-29195 Plug-in doesn't work on HP-UX Issue Type: Bug Assignee: Pavel Janoušek Components: proc-cleaner-plugin Created: 02/Jul/15 4:02 PM Environment: HP-UX 11.3 Priority: Critical Reporter: Pavel Janoušek Plug-in doesn't work on HP-UX (at least on version 11.3) because it uses 'ps' CLI with '-o' cmdline option which isn't supported on that system without explicit the UNIX behavior switch on. There are several ways how to achieve the anticipated behavior, one way is for ex.: It can be called like: UNIX95= ps -u hudson -o pid,ppid,args But ps -u hudson -o pid,ppid,args provides a such result:
[JIRA] [copyarchiver-plugin] (JENKINS-5921) CopyArchiver Plugin: Do not saves "Shared directory" parameter
Title: Message Title Radek Antoniuk resolved as Won't Fix Jenkins / JENKINS-5921 CopyArchiver Plugin: Do not saves "Shared directory" parameter Change By: Radek Antoniuk Status: In Progress Resolved Resolution: Won't Fix Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [docker-custom-build-environment-plugin] (JENKINS-29194) doesn't work with remote docker servers (also when Jenkins itself is containerized)
Title: Message Title m jitakirin created an issue Jenkins / JENKINS-29194 doesn't work with remote docker servers (also when Jenkins itself is containerized) Issue Type: Bug Assignee: Nicolas De Loof Components: docker-custom-build-environment-plugin Created: 02/Jul/15 3:59 PM Environment: Ubuntu 14.04 Jenkins ver. 1.609.1 docker-custom-build-environment plugin ver. 1.2 Labels: plugin Priority: Major Reporter: m jitakirin Steps to reproduce: create new freestyle job enable Build inside a Docker container select Pull docker image from repository
[JIRA] [performance-plugin] (JENKINS-27100) Regressions in 1.12 and 1.13
Title: Message Title Daniel Beck commented on JENKINS-27100 Re: Regressions in 1.12 and 1.13 Manuel Carrasco: Are you planning to release a fixed build? If not, I can remove the broken 1.13 (and 1.12?) from the update center, so users won't get that offered for installation until you've released a new version. WDYT? 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] [join-plugin] (JENKINS-16201) Join plugin - join job does not run
Title: Message Title Radek Antoniuk updated an issue Jenkins / JENKINS-16201 Join plugin - join job does not run Change By: Radek Antoniuk Labels: join-plugin-1.16 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] [join-plugin] (JENKINS-16201) Join plugin - join job does not run
Title: Message Title Radek Antoniuk resolved as Fixed Merged. Scheduled for release in 1.16. Jenkins / JENKINS-16201 Join plugin - join job does not run Change By: Radek Antoniuk Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-29193) Same sha used for multiple git checkouts
Title: Message Title jon heckman created an issue Jenkins / JENKINS-29193 Same sha used for multiple git checkouts Issue Type: Bug Assignee: Nicolas De Loof Components: git-plugin, multiple-scms-plugin Created: 02/Jul/15 3:42 PM Environment: Jenkins: 1.575. MultipleSCM: 0.3 . Git: 2.2.4 Priority: Minor Reporter: jon heckman I have a job configured with 2 git checkouts. Sometimes it will use the sha from the first checkout on the second git checkout, failing the job since the sha does not exist there. I have not been able to replicate this consistently. But I have about 15 jobs using this plugin, which run a few times an hour. I notice the issue at least once every couple hours. The issue will randomly fix it self after a few tries. Add Comment
[JIRA] [join-plugin] (JENKINS-24566) Join job should be run even if some or all downstream jobs fail
Title: Message Title Radek Antoniuk commented on JENKINS-24566 Re: Join job should be run even if some or all downstream jobs fail I think you can achieve that by using trigger-parametrised build with condition ALWAYS on A. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [join-plugin] (JENKINS-25710) Join plugin does not work with folders
Title: Message Title Radek Antoniuk updated an issue Jenkins / JENKINS-25710 Join plugin does not work with folders Change By: Radek Antoniuk Labels: join-plugin-1.16 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] [join-plugin] (JENKINS-25710) Join plugin does not work with folders
Title: Message Title Radek Antoniuk resolved as Fixed Merged. Scheduled for release in 1.16. Jenkins / JENKINS-25710 Join plugin does not work with folders Change By: Radek Antoniuk Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion-plugin] (JENKINS-26612) svn: absolutely unacceptably SLOW
Title: Message Title Alexander Azhevsky commented on JENKINS-26612 Re: svn: absolutely unacceptably SLOW Any news on this issue? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [test-results-analyzer-plugin] (JENKINS-29192) Support for multi-module project
Title: Message Title Varun Menon created an issue Jenkins / JENKINS-29192 Support for multi-module project Issue Type: Improvement Assignee: Varun Menon Components: test-results-analyzer-plugin Created: 02/Jul/15 2:34 PM Priority: Major Reporter: Varun Menon Currently the plugin does not support for multi-module project. Needs the said support. Add Comment This message was sent by Atlassian JIRA (v6.4
[JIRA] [proc-cleaner-plugin] (JENKINS-29191) Update project pom.xml to be recognized by Idea correctly
Title: Message Title Pavel Janoušek resolved as Fixed PR sent. Jenkins / JENKINS-29191 Update project pom.xml to be recognized by Idea correctly Change By: Pavel Janoušek Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [proc-cleaner-plugin] (JENKINS-29191) Update project pom.xml to be recognized by Idea correctly
Title: Message Title Pavel Janoušek created an issue Jenkins / JENKINS-29191 Update project pom.xml to be recognized by Idea correctly Issue Type: Improvement Assignee: Pavel Janoušek Components: proc-cleaner-plugin Created: 02/Jul/15 2:32 PM Priority: Minor Reporter: Pavel Janoušek Idea doesn't correctly recognize the original pom.xml and doesn't follow it as a project (doesn't offer anything under Package view etc.). Also unified formatting helps to legibility of this file. Add Comment
[JIRA] [core] (JENKINS-27694) Download update data immediately when installing a new tool installer plugin
Title: Message Title Daniel Beck started work on JENKINS-27694 Change By: Daniel Beck Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [docker-build-publish-plugin] (JENKINS-29190) generated tag incorrect when docker registry URL is a short name
Title: Message Title m jitakirin created an issue Jenkins / JENKINS-29190 generated tag incorrect when docker registry URL is a short name Issue Type: Bug Assignee: Carlos Sanchez Components: docker-build-publish-plugin Created: 02/Jul/15 2:18 PM Environment: Ubuntu 14.04 Jenkins ver. 1.609.1 docker-build-publish plugin ver. 1.0 no reverse proxy Labels: plugin Priority: Minor Reporter: m jitakirin Steps to reproduce: create a freestyle job that will be building a docker image fill in source details (any repo with a Dockerfile) add a Docker Builld and Publish step
[JIRA] [core] (JENKINS-29072) How to Migrate from Hudson 3.1.2 to jenkins latest version
Title: Message Title ikedam updated an issue Jenkins / JENKINS-29072 How to Migrate from Hudson 3.1.2 to jenkins latest version Change By: ikedam Component/s: core Component/s: update-sites-manager-plugin Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [proc-cleaner-plugin] (JENKINS-29189) Typo in log message for switched off cleaner
Title: Message Title Pavel Janoušek updated an issue Jenkins / JENKINS-29189 Typo in log message for switched off cleaner Change By: Pavel Janoušek Summary: Typos Typo in log message for switched off cleaner 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] [proc-cleaner-plugin] (JENKINS-29189) Typos in log message for switched off cleaner
Title: Message Title
Pavel Janoušek updated an issue
Jenkins / JENKINS-29189
Typos in log message for switched off cleaner
Change By:
Pavel Janoušek
Correct message on line 43:{code}getLog().getLogger().println(" Proc Process cleanup is globally switched turned off, contact you your Jenkins administartor to turn it on . ");{code} like "Proc cleanup globally switched off, contact you Jenkins administrator to turn it on""
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] [proc-cleaner-plugin] (JENKINS-29189) Typos in log message for switched off cleaner
Title: Message Title Pavel Janoušek edited a comment on JENKINS-29189 Re: Typos in log message for switched off cleaner [PR|https://github.com/ vjuranek jenkinsci /proc-cleaner-plugin/pull/ 5 1 ] sent. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [proc-cleaner-plugin] (JENKINS-29189) Typos in log message for switched off cleaner
Title: Message Title
Pavel Janoušek updated an issue
Jenkins / JENKINS-29189
Typos in log message for switched off cleaner
Change By:
Pavel Janoušek
Correct message on line 43:{code}getLog().getLogger().println("Proc cleanup globally switched off, contract contact you Jenkins administartor to turn it on");{code} like "Proc cleanup globally switched off, contact you Jenkins administrator to turn it on""
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-29072) How to Migrate from Hudson 3.1.2 to jenkins latest version
Title: Message Title ikedam commented on JENKINS-29072 Re: How to Migrate from Hudson 3.1.2 to jenkins latest version Not related to updatesites-manager plugin. Changed the component/s to core. You'd better ask this in the user mailing list. 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] [proc-cleaner-plugin] (JENKINS-29189) Typos in log message for switched off cleaner
Title: Message Title Pavel Janoušek resolved as Fixed PR sent. Jenkins / JENKINS-29189 Typos in log message for switched off cleaner Change By: Pavel Janoušek Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [proc-cleaner-plugin] (JENKINS-29189) Typos in log message for switched off cleaner
Title: Message Title
Pavel Janoušek created an issue
Jenkins / JENKINS-29189
Typos in log message for switched off cleaner
Issue Type:
Bug
Assignee:
Pavel Janoušek
Components:
proc-cleaner-plugin
Created:
02/Jul/15 1:56 PM
Priority:
Minor
Reporter:
Pavel Janoušek
Correct message on line 43:
getLog().getLogger().println("Proc cleanup globally switched off, contract you Jenkins administartor to turn it on");
like "Proc cleanup globally switched off, contact you Jenkins administrator to turn it on""
Add Comment
[JIRA] [packer-plugin] (JENKINS-28186) Packer installer from packer.io just a text box
Title: Message Title Jeffrey Damick commented on JENKINS-28186 Re: Packer installer from packer.io just a text box Known issue: https://issues.jenkins-ci.org/browse/JENKINS-27694 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-27694) Download update data immediately when installing a new tool installer plugin
Title: Message Title Daniel Beck assigned an issue to Daniel Beck Jenkins / JENKINS-27694 Download update data immediately when installing a new tool installer plugin Change By: Daniel Beck Assignee: Daniel Beck Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-29188) api URL for REST API is not available for flowGraphTable
Title: Message Title Thomas Dalton created an issue Jenkins / JENKINS-29188 api URL for REST API is not available for flowGraphTable Issue Type: Bug Assignee: Jesse Glick Components: workflow-plugin Created: 02/Jul/15 1:36 PM Environment: Jenkins 1.617 Workflow 1.8 Labels: workflow rest Priority: Minor Reporter: Thomas Dalton The REST API isn't available for access to "step" state through the workflow "running steps" page. e.g. at http://:8080//job///flowGraphTable/api I would expect to see a REST API page, indeed there is a link at the bottom of the flowGraphTable page to the REST API page that does not exist. At the JUC in London Jesse told me that this was probably just a bug, but if you want to make this a feature/improvement request that's fine too In general I think it would be massively useful to have access to stateful information for the workflow through the REST API i.
[JIRA] [zos-connector-plugin] (JENKINS-29173) IBM zOS Connector not retrieving job RC properly
Title: Message Title Alexander Shcherbakov closed an issue as Fixed Jenkins / JENKINS-29173 IBM zOS Connector not retrieving job RC properly Change By: Alexander Shcherbakov Status: Resolved Closed 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] [zos-connector-plugin] (JENKINS-29173) IBM zOS Connector not retrieving job RC properly
Title: Message Title Alexander Shcherbakov resolved as Fixed Jenkins / JENKINS-29173 IBM zOS Connector not retrieving job RC properly Change By: Alexander Shcherbakov Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [zos-connector-plugin] (JENKINS-29173) IBM zOS Connector not retrieving job RC properly
Title: Message Title Alexander Shcherbakov commented on JENKINS-29173 Re: IBM zOS Connector not retrieving job RC properly Now RC is scanned correctly. 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-29078) hudson.triggers.Trigger$Cron doRun throwing a NullPointerException
Title: Message Title Phil Dickson commented on JENKINS-29078 Re: hudson.triggers.Trigger$Cron doRun throwing a NullPointerException Looks like JENKINS-27549 is the probable cause 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-29078) hudson.triggers.Trigger$Cron doRun throwing a NullPointerException
Title: Message Title Phil Dickson commented on JENKINS-29078 Re: hudson.triggers.Trigger$Cron doRun throwing a NullPointerException Downgrading to 1.615 fixes things for us. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [view-job-filters-plugin] (JENKINS-22574) Hide/Disable the built-in filters
Title: Message Title Tomasz Śniatowski commented on JENKINS-22574 Re: Hide/Disable the built-in filters +1 on this. It would be great to be able to hide the default checkboxes, maybe just leave a note saying how many jobs are selected. BTW this request fits one of the "version 1.x ideas" listed on the plugin page at https://wiki.jenkins-ci.org/display/JENKINS/View+Job+Filters: These features are not entered as JIRA tickets because technically no one is requesting them. If you want one of these features, please Enter a JIRA Ticket and the feature will probably be added within a week. Retrofit existing filters to be default extensions (like the way columns work). Justifications are Allow for other views besides list view to more easily make use of them (for example, the status filter wasn't picked up by other views) Minor benefit is that if you have hundreds of jobs, your view edit screen is cluttered by the list of jobs when all you wanted was a regex or a status. So, you could delete any filters you don't want to see and they won't show up again. Another strategy to handle this might simply be a checkbox titled "hide view list". However, this would obscure the fact that often a job is added to a view accidentally by clicking the "new job" link while on that view. 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] [view-job-filters-plugin] (JENKINS-22574) Hide/Disable the built-in filters
Title: Message Title
Tomasz Śniatowski edited a comment on JENKINS-22574
Re: Hide/Disable the built-in filters
+1 on this. It would be great to be able to hide the default checkboxes, maybe just leave a note saying how many jobs are selected.BTW this request fits one of the "version 1.x ideas" listed on the plugin page at https://wiki.jenkins-ci.org/display/JENKINS/View+Job+Filters:{quote}These features are not entered as JIRA tickets because technically no one is requesting them. If you want one of these features, please Enter a JIRA Ticket and the feature will probably be added within a week.Retrofit existing filters to be default extensions (like the way columns work). Justifications areAllow for other views besides list view to more easily make use of them (for example, the status filter wasn't picked up by other views)Minor benefit is that if you have hundreds of jobs, your view edit screen is cluttered by the list of jobs when all you wanted was a regex or a status. So, you could delete any filters you don't want to see and they won't show up again. Another strategy to handle this might simply be a checkbox titled "hide view list". However, this would obscure the fact that often a job is added to a view accidentally by clicking the "new job" link while on that view.{quote}
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-28155) Job fails with [An existing connection was forcibly closed by the remote host]
Title: Message Title
Jan Müller edited a comment on JENKINS-28155
Re: Job fails with [An existing connection was forcibly closed by the remote host]
We may have a similar problem. We start a windows vm and connect it via jnlp to the master, then it starts some work and after some time, usually 3-5h the slave gets disconnected unintentionally:{code}java.io.IOException: Connection aborted: org.jenkinsci.remoting.nio.NioChannelHub$MonoNioTransport@7aa84678[name=QF-WinXP] at org.jenkinsci.remoting.nio.NioChannelHub$NioTransport.abort(NioChannelHub.java:211) at org.jenkinsci.remoting.nio.NioChannelHub.run(NioChannelHub.java:631) at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745)Caused by: java.io.IOException: Connection reset by peer at sun.nio.ch.FileDispatcherImpl.read0(Native Method) at sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:39) at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:223) at sun.nio.ch.IOUtil.read(IOUtil.java:197) at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:379) at org.jenkinsci.remoting.nio.FifoBuffer$Pointer.receive(FifoBuffer.java:136) at org.jenkinsci.remoting.nio.FifoBuffer.receive(FifoBuffer.java:306) at org.jenkinsci.remoting.nio.NioChannelHub.run(NioChannelHub.java:564){code} We have only one windows machine and this machine shows this behavior. All the linux slaves are connected constantly without any problems.
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.
