[JIRA] [join-plugin] (JENKINS-25710) Join plugin does not work with folders
Title: Message Title SCM/JIRA link daemon commented on JENKINS-25710 Re: Join plugin does not work with folders Code changed in jenkins User: Michael Donohue Path: src/main/java/join/JoinTrigger.java http://jenkins-ci.org/commit/join-plugin/8011c8a1786aa46d03ad063e852d993ec917fa80 Log: Merge pull request #8 from jeffastorey/master JENKINS-25710 join plugin does not work with folder Compare: https://github.com/jenkinsci/join-plugin/compare/9a14ed4e9864...8011c8a1786a 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 SCM/JIRA link daemon commented on JENKINS-25710 Re: Join plugin does not work with folders Code changed in jenkins User: Jeff Storey Path: src/main/java/join/JoinTrigger.java http://jenkins-ci.org/commit/join-plugin/93bb638b4d2c428c7eaaa64bb9776f68dc7ecb7b Log: JENKINS-25710 join plugin does not work with folder 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] [offlineonfailure-plugin] (JENKINS-29157) Take nod offline if job is unstable (yellow light)
Title: Message Title Conner Wang created an issue Jenkins / JENKINS-29157 Take nod offline if job is unstable (yellow light) Issue Type: Improvement Assignee: Unassigned Components: offlineonfailure-plugin Created: 01/Jul/15 5:46 AM Priority: Minor Reporter: Conner Wang We'd like an option to also take node offline if job is unstable (yellow light). This is useful if test cases are not 100% pass, which leads to an unstable job execution. Add Comment
[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
Basically, I execute a job via a remote PC and POSTing to Jenkins using python's requests module.i.e.{code}import requestswith open("file.zip", "rb") as z:file_to_send = {"jenkins_file.zip": z}requests.post("http://jenkins.local:8080/job/my_job/buildWithParameters", files=file_to_send){code}An {{upload_*.tmp}} file is created in {{/tmp}} directory of the master after executing the script. The master then builds the job on one of its nodes but the tmp file is not deleted even after the build is completed.I observed that {{jenkins_file.zip}} is created in the node's workspace once the job starts building (as expected) but no file is copied/created in the node's {{java.io.tmpdir}} directory.The instructions for configuring my job's parameters are documented here:https://wiki.jenkins-ci.org/display/JENKINS/Parameterized+Build Christopher Orr [~orrc] :I tried using your curl command with my job but it doesn't seem to set the parameters correctly. The parameters do not reflect on the {{http://jenkins.local:8080/job/my_job/build_number/parameters}} page. Although, I noticed that this time, it automatically deleted the {{upload_*.tmp}} that was generated.
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
Basically, I execute a job via a remote PC and POSTing to Jenkins using python's requests module.i.e.{code}import requestswith open("file.zip", "rb") as z:file_to_send = {"jenkins_file.zip": z}requests.post("http://jenkins.local:8080/job/my_job/buildWithParameters", files=file_to_send){code}An {{upload_*.tmp}} file is created in {{/tmp}} directory of the master after executing the script. The master then builds the job on one of its nodes but the tmp file is not deleted even after the build is completed.I observed that {{jenkins_file.zip}} is created in the node's workspace once the job starts building (as expected) but no file is copied/created in the node's {{java.io.tmpdir}} directory.The instructions for configuring my job's parameters are documented here:https://wiki.jenkins-ci.org/display/JENKINS/Parameterized+Build [ Christopher Orr ] : I tried using your curl command with my job but it doesn't seem to set the parameters correctly. The parameters do not reflect on the {{http://jenkins.local:8080/job/my_job/build_number/parameters}} page. Although, I noticed that this time, it automatically deleted the {{upload_*.tmp}} that was generated.
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
Basically, I execute a job via a remote PC and POSTing to Jenkins using python's requests module.i.e.{code :python }import requestswith open("file.zip", "rb") as z:file_to_send = {"jenkins_file.zip": z}requests.post("http://jenkins.local:8080/job/my_job/buildWithParameters", files=file_to_send){code}An {{upload_*.tmp}} file is created in {{/tmp}} directory of the master after executing the script. The master then builds the job on one of its nodes but the tmp file is not deleted even after the build is completed.I observed that {{jenkins_file.zip}} is created in the node's workspace once the job starts building (as expected) but no file is copied/created in the node's {{java.io.tmpdir}} directory.The instructions for configuring my job's parameters are documented here:https://wiki.jenkins-ci.org/display/JENKINS/Parameterized+Build[Christopher Orr]I tried using your curl command with my job but it doesn't seem to set the parameters correctly. The parameters do not reflect on the {{http://jenkins.local:8080/job/my_job/build_number/parameters}} page. Although, I noticed that this time, it automatically deleted the {{upload_*.tmp}} that was generated.
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
Basically, I execute a job via a remote PC and POSTing to Jenkins using python's requests module.i.e.{code:python}import requestswith open("file.zip", "rb") as z:file_to_send = {"jenkins_file.zip": z}requests.post("http://jenkins.local:8080/job/my_job/buildWithParameters", files=file_to_send){code}An {{upload_*.tmp}} file is created in {{/tmp}} directory of the master after executing the script. The master then builds the job on one of its nodes but the tmp file is not deleted even after the build is completed.I observed that {{jenkins_file.zip}} is created in the node's workspace once the job starts building (as expected) but no file is copied/created in the node's {{java.io.tmpdir}} directory.The instructions for configuring my job's parameters are documented here:https://wiki.jenkins-ci.org/display/JENKINS/Parameterized+Build[ ~ Christopher Orr]I tried using your curl command with my job but it doesn't seem to set the parameters correctly. The parameters do not reflect on the {{http://jenkins.local:8080/job/my_job/build_number/parameters}} page. Although, I noticed that this time, it automatically deleted the {{upload_*.tmp}} that was generated.
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 commented on JENKINS-12699
Re: Temp upload files from file param not removed after transferred to slave
Basically, I execute a job via a remote PC and POSTing to Jenkins using python's requests module. i.e.
Unable to find source-code formatter for language: python. Available languages are: actionscript, html, java, _javascript_, none, sql, xhtml, xml
import requests
with open("file.zip", "rb") as z:
file_to_send = {"jenkins_file.zip": z}
requests.post("http://jenkins.local:8080/job/my_job/buildWithParameters", files=file_to_send)
An upload_*.tmp file is created in /tmp directory of the master after executing the script. The master then builds the job on one of its nodes but the tmp file is not deleted even after the build is completed.
I observed that jenkins_file.zip is created in the node's workspace once the job starts building (as expected) but no file is copied/created in the node's java.io.tmpdir directory.
The instructions for configuring my job's parameters are documented here: https://wiki.jenkins-ci.org/display/JENKINS/Parameterized+Build
[~Christopher Orr] I tried using your curl command with my job but it doesn't seem to set the parameters correctly. The parameters do not reflect on the http://jenkins.local:8080/job/my_job/build_number/parameters page. Although, I noticed that this time, it automatically deleted the upload_*.tmp that was generated.
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 Iss
[JIRA] [git-client-plugin] (JENKINS-25389) Allow push of tags created during the build
Title: Message Title Vito Andolini commented on JENKINS-25389 Re: Allow push of tags created during the build The help text for the "Add Tag" section of the "Git Publisher" Post-Build Action states: Specify tags to push at the completion of the build. If the "Create Tag" or "Update tag" option is selected, the tag will be created or updated and pushed at the completion of the build, and the push will fail if a tag with the given name already exists. If the "Create Tag" option is not selected, the push will fail if the tag does not already exist. Environment variables may be used in the tag name - they will be replaced at build time. The repository name needs to be one of the repositories configured in the SCM section above. I have found that environment variables can be used in the tag message, but not the name. I don't understand why the plug-in would require the tag name to be hard-coded - who would go configure the job before each build to add a hard-coded tag 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] [git-client-plugin] (JENKINS-25389) Allow push of tags created during the build
Title: Message Title Vito Andolini edited a comment on JENKINS-25389 Re: Allow push of tags created during the build The help text for the "Add Tag" section of the "Git Publisher" Post-Build Action states: bq. Specify tags to push at the completion of the build. bq. If the "Create Tag" or "Update tag" option is selected, the tag will be created or updated and pushed at the completion of the build, and the push will fail if a tag with the given name already exists. If the "Create Tag" option is not selected, the push will fail if the tag does not already exist. bq. *Environment variables may be used in the tag name - they will be replaced at build time.* bq. The repository name needs to be one of the repositories configured in the SCM section above. I have found that environment variables can be used in the tag message, but not the name. I don't understand why the plug-in would require the tag name to be hard-coded - who would go configure the job before each build to add a hard-coded tag 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] [android-emulator-plugin] (JENKINS-28941) No slashes in widows AVD config.ini
Title: Message Title emmanuel dufour commented on JENKINS-28941 Re: No slashes in widows AVD config.ini sorry for the delay, here is the proper config.ini (the last line, hw.ramSize=1000 was added by editing the file directly instead of using the plugin) avd.ini.encoding=UTF-8 abi.type=armeabi-v7a hw.cpu.arch=arm hw.cpu.model=cortex-a8 hw.sdCard=yes image.sysdir.1=system-images\android-17\default\armeabi-v7a\ sdcard.size=150M skin.name=800x480 skin.path=800x480 snapshot.present=true tag.display=Default tag.id=default hw.ramSize=1000 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-29150) CronTabTest is failing while building jenkins
Title: Message Title Mayur Barge updated an issue Jenkins / JENKINS-29150 CronTabTest is failing while building jenkins Change By: Mayur Barge Environment: mayur@inspiron-n5010:~$ uname -aLinux inspiron-n5010 3.16.0-41-generic #57~14.04.1-Ubuntu SMP Thu Jun 18 18:01:13 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux mayur@inspiron-n5010:~$ java -showversionjava version "1.7.0_80"Java(TM) SE Runtime Environment (build 1.7.0_80-b15)Java HotSpot(TM) 64-Bit Server VM (build 24.80-b11, mixed mode) 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] [copyartifact-plugin] (JENKINS-28972) No page found '/hudson/plugins/promoted_builds_simple/PromotedBuildSelector/config.jelly
Title: Message Title ikedam commented on JENKINS-28972 Re: No page found '/hudson/plugins/promoted_builds_simple/PromotedBuildSelector/config.jelly I'll make a new release this weekend. 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-29156) Add the "Release Notes" functionality in TFS Plugin
Title: Message Title Dalmo Santos created an issue Jenkins / JENKINS-29156 Add the "Release Notes" functionality in TFS Plugin Issue Type: New Feature Assignee: redsolo Components: tfs-plugin Created: 30/Jun/15 10:55 PM Labels: plugin tfs-plugin tfs Priority: Trivial Reporter: Dalmo Santos I needed the "Release Notes" functionality, like a Microsoft Team Foundation Server, which shows the changesets and Work Items of the related build. Today, in Jenkins, the tfs-plugin shows only changesets. In the Rational Team Concert Plugin, it relates changesets and Work Items. Thanks. Add Comment
[JIRA] [websphere-deployer-plugin] (JENKINS-29155) Add to "update the application" option.
Title: Message Title Dalmo Santos created an issue Jenkins / JENKINS-29155 Add to "update the application" option. Issue Type: New Feature Assignee: Unassigned Components: websphere-deployer-plugin Created: 30/Jun/15 10:35 PM Labels: plugin websphere-deployer-plugin Priority: Major Reporter: Dalmo Santos Needed functionality "update application" because, in the deploy, are lost settings for shared libraries and security policies. The functionality needed of the following: -nopreCompileJSPs, -distributeApp, -nouseMetaDataFromBinary, -deployejb, -createMBeansForResources, -reloadEnabled, -deployws, -validateinstall warn, -noprocessEmbeddedConfig, -filepermission. * \. dll = 755 #. * \. so = 755 #. * \. a = 755 #. * \. sl = 755, -noallowDispatchRemoteInclude, -noallowServiceRemoteInclude, -appName, appInfo ["appName"] -MapWebModToVH, -MapModulesToServers, Tanks
[JIRA] [maven-plugin] (JENKINS-22486) API change in maven 3.2.1 causes builds with the parallel (-T option) to fail with an exception.
Title: Message Title Steve Storey commented on JENKINS-22486 Re: API change in maven 3.2.1 causes builds with the parallel (-T option) to fail with an exception. Eugene Gunov this was fixed in version 2.8 of the Maven plugin, so pls install that. I don't know why it wasn't marked as resolved at that point. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven-plugin] (JENKINS-22486) API change in maven 3.2.1 causes builds with the parallel (-T option) to fail with an exception.
Title: Message Title Steve Storey resolved as Fixed Jenkins / JENKINS-22486 API change in maven 3.2.1 causes builds with the parallel (-T option) to fail with an exception. Change By: Steve Storey 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] [websphere-deployer-plugin] (JENKINS-29154) Add JavaEE 7 on Generating EAR Level
Title: Message Title Dalmo Santos created an issue Jenkins / JENKINS-29154 Add JavaEE 7 on Generating EAR Level Issue Type: New Feature Assignee: Unassigned Attachments: JavaEE version generating.png Components: websphere-deployer-plugin Created: 30/Jun/15 10:09 PM Labels: plugin websphere-deployer-plugin Priority: Major Reporter: Dalmo Santos Hello. I would suggest that the EAR Generating the option of JavaEE 7. Currently there are only versions JavaEE 5 and Java EE 6.
[JIRA] [jclouds-plugin] (JENKINS-29136) NPE in jenkins.plugins.openstack.compute.JCloudsSlave.getRetentionTime(JCloudsSlave.java:109)
Title: Message Title Alexey Java updated an issue Jenkins / JENKINS-29136 NPE in jenkins.plugins.openstack.compute.JCloudsSlave.getRetentionTime(JCloudsSlave.java:109) Change By: Alexey Java Priority: Major Blocker 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] [jclouds-plugin] (JENKINS-29136) NPE in jenkins.plugins.openstack.compute.JCloudsSlave.getRetentionTime(JCloudsSlave.java:109)
Title: Message Title Alexey Java commented on JENKINS-29136 Re: NPE in jenkins.plugins.openstack.compute.JCloudsSlave.getRetentionTime(JCloudsSlave.java:109) also, this is a real blocker because the plugin cannot even create new instances properly: it launches a new VM and then fails with NPE and get into cycle when it tries to launch another one, then another one, etc - they all fail. and you end up with many unusable VMs and jenkins came to a halt. 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] [ansible-plugin] (JENKINS-29149) Missing Ansible installation message
Title: Message Title Jean-Christophe Sirot started work on JENKINS-29149 Change By: Jean-Christophe Sirot 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] [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 it appears the gradle plugin has the same issue - i'm going to investigate further for a workaround. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gerrit-trigger-plugin] (JENKINS-26010) Workflow plugin not working with with Gerrit event
Title: Message Title Jacob Keller commented on JENKINS-26010 Re: Workflow plugin not working with with Gerrit event Ok so it has a few good uses for the build delay. We should be able to check the instance to see if it's an AbstractProject and honor the delay there at least? Then we'd be deficient in terms of workflows but that would be better than we are now? At least if the user needs both delays they will be able ot configure the delay in the gerrit settings to be long enough. I'm also curious how possible a soft dependency on workflows would require? Ie: check if we have it and enable an instanceof check if we do? I'm sure there should be a way to do that Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-flow-plugin] (JENKINS-25952) Build flow does not release threads for scheduled or queued jobs after an abort
Title: Message Title Mable Schmidt updated an issue Jenkins / JENKINS-25952 Build flow does not release threads for scheduled or queued jobs after an abort Change By: Mable Schmidt Summary: Build flow does not release threads for schedule scheduled or queued jobs after an abort 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] [promoted-builds-plugin] (JENKINS-29132) Deleted promotion steps keep executing
Title: Message Title Alexander Dvorsky commented on JENKINS-29132 Re: Deleted promotion steps keep executing +1 seeing this as well 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] [tap-plugin] (JENKINS-29153) tap plugin fails job when not have to
Title: Message Title Mike Dubman created an issue Jenkins / JENKINS-29153 tap plugin fails job when not have to Issue Type: Bug Assignee: Bruno P. Kinoshita Attachments: tap.pdf Components: tap-plugin Created: 30/Jun/15 7:05 PM Environment: rhel6 Labels: tapResults Priority: Minor Reporter: Mike Dubman Hi, more details in the attached pdf. short version - tap plugins fails job while configured not to.
[JIRA] [jclouds-plugin] (JENKINS-29152) NPE in JCloudsComputer.doDoDelete() when node is not accessible
Title: Message Title Alexey Java updated an issue Jenkins / JENKINS-29152 NPE in JCloudsComputer.doDoDelete() when node is not accessible Change By: Alexey Java Priority: Blocker Critical Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jclouds-plugin] (JENKINS-29152) NPE in JCloudsComputer.doDoDelete() when node is not accessible
Title: Message Title Alexey Java updated an issue Jenkins / JENKINS-29152 NPE in JCloudsComputer.doDoDelete() when node is not accessible Change By: Alexey Java Priority: Minor Blocker 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] [jclouds-plugin] (JENKINS-29152) NPE in JCloudsComputer.doDoDelete() when node is not accessible
Title: Message Title Alexey Java created an issue Jenkins / JENKINS-29152 NPE in JCloudsComputer.doDoDelete() when node is not accessible Issue Type: Bug Assignee: abayer Components: jclouds-plugin Created: 30/Jun/15 6:56 PM Priority: Minor Reporter: Alexey Java I have a node that is shown as "offline" in Nodes list on the main page of Jenkins web UI (see screenshot). I tried deleting this slave manually, but got this NPE in jclouds plugin code: java.lang.NullPointerException at jenkins.plugins.openstack.compute.JCloudsComputer.doDoDelete(JCloudsComputer.java:50) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:298) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:161) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:96) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:121) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) ... 70 more
[JIRA] [jclouds-plugin] (JENKINS-29136) NPE in jenkins.plugins.openstack.compute.JCloudsSlave.getRetentionTime(JCloudsSlave.java:109)
Title: Message Title Alexey Java updated an issue Jenkins / JENKINS-29136 NPE in jenkins.plugins.openstack.compute.JCloudsSlave.getRetentionTime(JCloudsSlave.java:109) 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] [prioritysorter-plugin] (JENKINS-28935) Use Priority from Build Parameter, but priority is ignored in queue
Title: Message Title Magnus Sandberg commented on JENKINS-28935 Re: Use Priority from Build Parameter, but priority is ignored in queue This item is closed please open a new issue if you have problems. In the meanwhile make sure you also log from "PrioritySorter.Queue.Sorter" to see that the sorting actually happens. As soon as a Job as been given a priority the reason does not matter, sorting is happening in the same way. 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] [jclouds-plugin] (JENKINS-29136) NPE in jenkins.plugins.openstack.compute.JCloudsSlave.getRetentionTime(JCloudsSlave.java:109)
Title: Message Title
Alexey Java updated an issue
Jenkins / JENKINS-29136
NPE in jenkins.plugins.openstack.compute.JCloudsSlave.getRetentionTime(JCloudsSlave.java:109)
Change By:
Alexey Java
got this while saving System Configuration in Jenkins.I have this plugin installed: "Openstack Cloud PluginAllows Jenkins to build using Cloud Servers via JClouds." - Version 1.7. this may be applicable to jclouds-plugin as well (see my fix for both below)my "retention time" is set to default: 30 (minutes I assume)and on "Cloud Instance Templates" level the value shown for retention-override is shown as "0" in the web UI.{quote}javax.servlet.ServletException: java.lang.NullPointerException at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:123) at hudson.plugins.scm_sync_configuration.extensions.ScmSyncConfigurationFilter$1.call(ScmSyncConfigurationFilter.java:46) at hudson.plugins.scm_sync_configuration.ScmSyncConfigurationDataProvider.provideRequestDuring(ScmSyncConfigurationDataProvider.java:103) at hudson.plugins.scm_sync_configuration.extensions.ScmSyncConfigurationFilter.doFilter(ScmSyncConfigurationFilter.java:42) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:120) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:114) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.BasicHeaderProcessor.doFilter(BasicHeaderProcessor.java:93) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at hudson.security.HttpSessionContex
[JIRA] [ghprb-plugin] (JENKINS-29151) ghprb ignores "Commit Status Context" field value and uses "default
Title: Message Title
Mike Dubman created an issue
Jenkins / JENKINS-29151
ghprb ignores "Commit Status Context" field value and uses "default
Issue Type:
Bug
Assignee:
Honza Brázdil
Attachments:
jen.png
Components:
ghprb-plugin
Created:
30/Jun/15 6:40 PM
Environment:
linux rhel6
Labels:
ghprb github
Priority:
Minor
Reporter:
Mike Dubman
Hi, After upgrading to latest jenkins (1.617) and ghprb plugin to the version 1.24.3 - the "COmmit Status Context" appears as "default" and not as configured ("Mellanox").
Example is here: https://github.com/open-mpi/ompi-release/pull/345
[JIRA] [jclouds-plugin] (JENKINS-29136) NPE in jenkins.plugins.openstack.compute.JCloudsSlave.getRetentionTime(JCloudsSlave.java:109)
Title: Message Title Alexey Java commented on JENKINS-29136 Re: NPE in jenkins.plugins.openstack.compute.JCloudsSlave.getRetentionTime(JCloudsSlave.java:109) and here is a separate pull request for jclouds-plugin https://github.com/jenkinsci/jclouds-plugin/pull/89 (pretty much the same fix as for Openstack Cloud 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] [build-blocker-plugin] (JENKINS-28513) Build-Blocker-Plugin blocks on builds queued leading to deadlock
Title: Message Title Manni Heumann commented on JENKINS-28513 Re: Build-Blocker-Plugin blocks on builds queued leading to deadlock Yes, Trey, I just tried 1.618 and with a couple of test jobs that do nothing but sleep for a while, this release looks very promising. None of the jobs got stuck in the queue. I'll try some real jobs that gave me trouble before tomorrow, but I'm confident that the problem is gone. No idea what part of the change log to thank for, but I don't really care. 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-29150) CronTabTest is failing while building jenkins
Title: Message Title Mayur Barge created an issue Jenkins / JENKINS-29150 CronTabTest is failing while building jenkins Issue Type: Bug Assignee: Oleg Nenashev Components: core Created: 30/Jun/15 6:27 PM Environment: mayur@inspiron-n5010:~$ uname -a Linux inspiron-n5010 3.16.0-41-generic #57~14.04.1-Ubuntu SMP Thu Jun 18 18:01:13 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux Labels: test-results Priority: Minor Reporter: Mayur Barge Test is failing with following trace FYI, When I change timezone of my machine to Australia/Sydney then it works org.junit.ComparisonFailure: Expected :[35, 56] Actual :[5, 26] at org.junit.Assert.assertEquals(Assert.java:115) at org.junit.Assert.assertEquals(Assert.java:144) at hudson.scheduler.CronTabTest.testTimezone(CronTabTest.java:315) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at org.junit.runn
[JIRA] [jclouds-plugin] (JENKINS-29136) NPE in jenkins.plugins.openstack.compute.JCloudsSlave.getRetentionTime(JCloudsSlave.java:109)
Title: Message Title Alexey Java commented on JENKINS-29136 Re: NPE in jenkins.plugins.openstack.compute.JCloudsSlave.getRetentionTime(JCloudsSlave.java:109) I fixed the bug locally and submitted a pull request for Openstack Cloud plugin: https://github.com/jenkinsci/openstack-cloud-plugin/pull/12 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] [jclouds-plugin] (JENKINS-29136) NPE in jenkins.plugins.openstack.compute.JCloudsSlave.getRetentionTime(JCloudsSlave.java:109)
Title: Message Title
Alexey Java updated an issue
Jenkins / JENKINS-29136
NPE in jenkins.plugins.openstack.compute.JCloudsSlave.getRetentionTime(JCloudsSlave.java:109)
Change By:
Alexey Java
got this while saving System Configuration in Jenkins.I have this plugin installed: "Openstack Cloud PluginAllows Jenkins to build using Cloud Servers via JClouds." - Version 1.7.my "retention time" is set to default: 30 (minutes I assume)and on "Cloud Instance Templates" level the value shown for retention-override is shown as "0" in the web UI.{quote}javax.servlet.ServletException: java.lang.NullPointerException at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:123) at hudson.plugins.scm_sync_configuration.extensions.ScmSyncConfigurationFilter$1.call(ScmSyncConfigurationFilter.java:46) at hudson.plugins.scm_sync_configuration.ScmSyncConfigurationDataProvider.provideRequestDuring(ScmSyncConfigurationDataProvider.java:103) at hudson.plugins.scm_sync_configuration.extensions.ScmSyncConfigurationFilter.doFilter(ScmSyncConfigurationFilter.java:42) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:120) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:114) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.BasicHeaderProcessor.doFilter(BasicHeaderProcessor.java:93) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67) at h
[JIRA] [packer-plugin] (JENKINS-28186) Packer installer from packer.io just a text box
Title: Message Title Jeffrey Damick assigned an issue to Jeffrey Damick Jenkins / JENKINS-28186 Packer installer from packer.io just a text box Change By: Jeffrey Damick Assignee: Jeffrey Damick 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] [ansible-plugin] (JENKINS-29149) Missing Ansible installation message
Title: Message Title shen can commented on JENKINS-29149 Re: Missing Ansible installation message I used yum install ansible packages 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-22926) Extension point for augmenting Plugin Manager display
Title: Message Title Manuel Jesús Recena Soto assigned an issue to Unassigned Jenkins / JENKINS-22926 Extension point for augmenting Plugin Manager display 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-22926) Extension point for augmenting Plugin Manager display
Title: Message Title Manuel Jesús Recena Soto stopped work on JENKINS-22926 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] [maven-plugin] (JENKINS-22486) API change in maven 3.2.1 causes builds with the parallel (-T option) to fail with an exception.
Title: Message Title Eugene Gunov edited a comment on JENKINS-22486 Re: API change in maven 3.2.1 causes builds with the parallel (-T option) to fail with an exception. Is this going to be fixed? (reproduced in 1.596.2) Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-29137) Repeated failure to archive build artifacts
Title: Message Title Mark Syms resolved as Duplicate Probably duplicate of Jenkins-10629 Jenkins / JENKINS-29137 Repeated failure to archive build artifacts Change By: Mark Syms Status: Open Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-29137) Repeated failure to archive build artifacts
Title: Message Title Mark Syms commented on JENKINS-29137 Re: Repeated failure to archive build artifacts Having reworked the output of the build to produce smaller files this issue (so far) seems to have been resolved, so this does look to a variant of Jenkins-10629 which seems to manifest in a variety of subtly different exception messages. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ansible-plugin] (JENKINS-29149) Missing Ansible installation message
Title: Message Title shen can created an issue Jenkins / JENKINS-29149 Missing Ansible installation message Issue Type: Task Assignee: Jean-Christophe Sirot Attachments: QQ20150701-1.png, QQ20150701-2.png Components: ansible-plugin Created: 30/Jun/15 4:51 PM Priority: Blocker Reporter: shen can I has installed Ansible plugin at jenkins web ui, and my jenkins server has installed Ansible with root user , I has change to jenkins server running user to root in /etc/sysconfig/jenkins file. but when I create project the at jenkins web ui , has error message Missing Ansible installation. when I run the project also error. `java.io.IOException: Ansible not found` Add Comment
[JIRA] [bulk-builder-plugin] (JENKINS-29148) Bulk Builder Plugin - NOT_BUILT_ONLY enum missing
Title: Message Title gjd6640 created an issue Jenkins / JENKINS-29148 Bulk Builder Plugin - NOT_BUILT_ONLY enum missing Issue Type: Bug Assignee: Simon Westcott Components: bulk-builder-plugin Created: 30/Jun/15 4:44 PM Environment: Jenkins 1.596.2 Bulk Builder Plugin v1.5 Priority: Minor Reporter: gjd6640 To reproduce the error below click the "Bulk Builder" link on the left-side menu, click "Advanced" under "Build selection", click the radio button next to "Build only unbuilt jobs", and then click the "Build!" button. Also, at a glance it is not clear what the difference is between "Build unbuilt jobs" and "Build only unbuilt jobs". Maybe the fix is to simply remove "Build only unbuilt jobs"? javax.servlet.ServletException: java.lang.IllegalArgumentException: No enum constant org.jvnet.hudson.plugins.bulkbuilder.model.BuildType.NOT_BUILT_ONLY at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:391) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServ
[JIRA] [prioritysorter-plugin] (JENKINS-28935) Use Priority from Build Parameter, but priority is ignored in queue
Title: Message Title John Drinkwater commented on JENKINS-28935 Re: Use Priority from Build Parameter, but priority is ignored in queue Hello! I am running into similar issues with the "Use Priority from Build Parameter" feature. I put 5 instances of the same job into the queue with priorities ordered 4, 2, 5, 3, 1, and then turned the associated node online. I have the "Execute concurrent builds if necessary" option checked in the job's configuration, and I see no blocking in my log, yet the jobs are still being run in a FIFO manner. It seems to be completely disregarding the priority. Here is the log: Jun 30, 2015 11:32:21 AM FINER PrioritySorter.Queue.Items New Item: Id: 54458, JobName: groovy-test, jobGroupId: 0, reason: Use Priority from Build Parameter, priority: 4, weight: 4.0, status: WAITING Evaluating JobGroup [0] ... Checking for Job Property inclusion for [KrakenRunners]... JobGroup is enabled on job, with JobGroup [KrakenRunners] ... Job is included in JobGroup ... Evaluating strategies ... Evaluating strategy [Use Priority from Build Parameter] ... Strategy is applicable Jun 30, 2015 11:32:21 AM FINE PrioritySorter.Queue.Items Buildable: Id: 54458, JobName: groovy-test, jobGroupId: 0, reason: Use Priority from Build Parameter, priority: 4, weight: 4.0, status: BUILDABLE Jun 30, 2015 11:32:25 AM FINER PrioritySorter.Queue.Items New Item: Id: 54459, JobName: groovy-test, jobGroupId: 0, reason: Use Priority from Build Parameter, priority: 2, weight: 2.0, status: WAITING Evaluating JobGroup [0] ... Checking for Job Property inclusion for [KrakenRunners]... JobGroup is enabled on job, with JobGroup [KrakenRunners] ... Job is included in JobGroup ... Evaluating strategies ... Evaluating strategy [Use Priority from Build Parameter] ... Strategy is applicable Jun 30, 2015 11:32:25 AM FINE PrioritySorter.Queue.Items Buildable: Id: 54459, JobName: groovy-test, jobGroupId: 0, reason: Use Priority from Build Parameter, priority: 2, weight: 2.0, status: BUILDABLE Jun 30, 2015 11:32:28 AM FINER PrioritySorter.Queue.Items New Item: Id: 54460, JobName: groovy-test, jobGroupId: 0, reason: Use Priority from Build Parameter, priority: 5, weight: 5.0, status: WAITING Evaluating JobGroup [0] ... Checking for Job Property inclusion for [KrakenRunners]... JobGroup is enabled on job, with JobGroup [KrakenRunners] ... Job is included in JobGroup ... Evaluating strategies ... Evaluating strategy [Use Priority from Build Parameter] ... Strategy is applicable Jun 30, 2015 11:32:28 AM FINE PrioritySorter.Queue.Items Buildable: Id: 54460, JobName: groovy-test, jobGroupId: 0, reason: Use Priority from Build Parameter, priority: 5, weight: 5.0, status: BUILDABLE Jun 30, 2015 11:32:31 AM FINER PrioritySorter.Queue.Items New Item: Id: 54461, JobName: groovy-test, jobGroupId: 0, reason: Use Priority from Build Parameter, priority: 3, weight: 3.0, status: WAITING Evaluating JobGroup [0] ... Checking for Job Property inclusion for [KrakenRunners]... JobGroup is enabled on job, with JobGroup [KrakenRunners] ... Job is included in JobGroup ... Evaluating strategies ... Evaluating strategy [Use Priority from Build Parameter] ... Strategy is applicable Jun 30, 2015 11:32:31 AM FINE PrioritySorter.Queue.Items Buildable: Id: 54461, JobName: groovy-test, jobGroupId: 0, reason: Use Priority from Build Parameter, priority: 3, weight: 3.0, status: BUILDABLE Jun 30, 2015 11:32:33 AM FINER PrioritySorter.Queue.Items New Item: Id: 54462, JobName: groovy-test, jobGroupId: 0, reason: Use Priority from Build Parameter, priority: 1, weight: 1.0, status: WAITING Evaluating JobGroup [0] ... Checking for Job Property inclusion for [KrakenRunn
[JIRA] [disk-usage-plugin] (JENKINS-29147) java.lang.NullPointerException in DiskUsageUtil.java:439
Title: Message Title Vassil Keremidchiev created an issue Jenkins / JENKINS-29147 java.lang.NullPointerException in DiskUsageUtil.java:439 Issue Type: Bug Assignee: Lucie Votypkova Components: disk-usage-plugin Created: 30/Jun/15 4:35 PM Priority: Major Reporter: Vassil Keremidchiev Jenkins 1.615 (FreeBSD x64), disk usage plug-in 0.25 Jun 30, 2015 6:02:10 PM WARNING hudson.plugins.disk_usage.WorkspaceDiskUsageCalculationThread execute Error when recording disk usage for vray_katana_linux_build java.lang.NullPointerException at hudson.plugins.disk_usage.DiskUsageUtil.calculateWorkspaceDiskUsage(DiskUsageUtil.java:439) at hudson.plugins.disk_usage.WorkspaceDiskUsageCalculationThread.execute(WorkspaceDiskUsageCalculationThread.java:51) at hudson.model.AsyncAperiodicWork$1.run(AsyncAperiodicWork.java:76) at java.lang.Thread.run(Thread.java:745) Add Comment
[JIRA] [build-blocker-plugin] (JENKINS-28513) Build-Blocker-Plugin blocks on builds queued leading to deadlock
Title: Message Title Trey Bohon commented on JENKINS-28513 Re: Build-Blocker-Plugin blocks on builds queued leading to deadlock Anyone try 1.618? There are a few queue deadlock related fixes in that build, wondering if this is a duplicate issue with one of those. 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] [dashboard-view-plugin] (JENKINS-29146) Add support for Dashboard view
Title: Message Title Sandra Greenhalgh created an issue Jenkins / JENKINS-29146 Add support for Dashboard view Issue Type: Improvement Assignee: Peter Hayes Components: dashboard-view-plugin, job-dsl-plugin Created: 30/Jun/15 3:56 PM Priority: Minor Reporter: Sandra Greenhalgh Add support for adding a Dashboard View plugin (https://wiki.jenkins-ci.org/display/JENKINS/Dashboard+View) from the Job DSL scripts. Add Comment This message was sent by
[JIRA] [fitnesse-plugin] (JENKINS-29019) FitNesse 1.13 does not render properly FitNesse history
Title: Message Title Serge Zukov closed an issue as Fixed Thank you for fixing this. Jenkins / JENKINS-29019 FitNesse 1.13 does not render properly FitNesse history Change By: Serge Zukov Status: In Progress Closed 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] [fitnesse-plugin] (JENKINS-29019) FitNesse 1.13 does not render properly FitNesse history
Title: Message Title Serge Zukov edited a comment on JENKINS-29019 Re: FitNesse 1.13 does not render properly FitNesse history Confirm to be resolved in 1.6. This issue could be closed now. 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] [fitnesse-plugin] (JENKINS-29019) FitNesse 1.13 does not render properly FitNesse history
Title: Message Title Serge Zukov commented on JENKINS-29019 Re: FitNesse 1.13 does not render properly FitNesse history Confirm to be resolved in 1.6. 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] [compress-artifacts-plugin] (JENKINS-27558) job build fatal error on creating/compressing archive files with a "Failed to parse POMs" message
Title: Message Title Oliver Gondža resolved as Fixed This should be fixed since 1.7. Jenkins / JENKINS-27558 job build fatal error on creating/compressing archive files with a "Failed to parse POMs" message Change By: Oliver Gondža 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] [compress-artifacts-plugin] (JENKINS-27558) job build fatal error on creating/compressing archive files with a "Failed to parse POMs" message
Title: Message Title SCM/JIRA link daemon commented on JENKINS-27558 Re: job build fatal error on creating/compressing archive files with a "Failed to parse POMs" message Code changed in jenkins User: Oliver Gondža Path: src/test/java/plugins/CompressArtifactsPluginTest.java http://jenkins-ci.org/commit/acceptance-test-harness/e8747df2ac1c62e78847f08dcbfd8477902971e5 Log: JENKINS-27558 Reproduce in test 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] [coverity-plugin] (JENKINS-25323) Coverity Plugin 1.4.1 : Issues with starting a build after selecting Coverity as Post Build action
Title: Message Title
Christopher Shannon edited a comment on JENKINS-25323
Re: Coverity Plugin 1.4.1 : Issues with starting a build after selecting Coverity as Post Build action
I have seen this same issue - not sure if and it is appears to be an interaction between the Coverity and ClearCase plugins. The real problem seems to be this line in BuildUtils in the ClearCase plugin . {code:java}return builtOn . createLauncher(StreamTaskListener.NULL).isUnix();{code}This isRunningOnUnix method is called as the launcher is getting created (specifically when building the set of env variables). The call above tries to create a new launcher during this process which leads to the recursion loop / stack overflow.
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-28131) Pass NODE_NAME into node{}
Title: Message Title
Jesse Glick resolved as Fixed
Jenkins / JENKINS-28131
Pass NODE_NAME into node{}
Change By:
Jesse Glick
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] [core] (JENKINS-29145) Jenkins does not build
Title: Message Title Stefan Wagner created an issue Jenkins / JENKINS-29145 Jenkins does not build Issue Type: Bug Assignee: Unassigned Components: core Created: 30/Jun/15 3:10 PM Environment: OS X 10.10 Current master branch (2e4fe6a7) Maven 3.3.3 Java 1.8.0_20 Labels: maven Priority: Blocker Reporter: Stefan Wagner I tried to get started with Jekins development and to build it. I followed https://wiki.jenkins-ci.org/display/JENKINS/Building+Jenkins but when running mvn -Plight-test install the build fails: Results : Tests in error: LauncherTest.remoteKill:68 » NumberFormat For input string: "" XStream2Test.concurrentHashMapSerialization:302 NullPointer Tests run: 3408, Failures: 0, Errors: 2, Skipped: 3
[JIRA] [workflow-plugin] (JENKINS-28131) Pass NODE_NAME into node{}
Title: Message Title
SCM/JIRA link daemon commented on JENKINS-28131
Re: Pass NODE_NAME into node{}
Code changed in jenkins User: recena Path: aggregator/src/test/java/org/jenkinsci/plugins/workflow/AvailableEnvVarTest.java http://jenkins-ci.org/commit/workflow-plugin/a62d31f25434ac965d93e6dbb7ffd7aad7b2fdd8 Log:
JENKINS-28131
Added a new test to verify that specefic environment variables are available
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-28131) Pass NODE_NAME into node{}
Title: Message Title
SCM/JIRA link daemon commented on JENKINS-28131
Re: Pass NODE_NAME into node{}
Code changed in jenkins User: recena Path: CHANGES.md aggregator/src/test/java/org/jenkinsci/plugins/workflow/EnvWorkflowTest.java support/src/main/java/org/jenkinsci/plugins/workflow/support/steps/ExecutorStepExecution.java http://jenkins-ci.org/commit/workflow-plugin/a7abe6c0efab953cb8782eaef72d0cc54ec712d1 Log:
JENKINS-28131
Improving the test and adding some inline comments
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-28131) Pass NODE_NAME into node{}
Title: Message Title
SCM/JIRA link daemon commented on JENKINS-28131
Re: Pass NODE_NAME into node{}
Code changed in jenkins User: recena Path: aggregator/src/test/java/org/jenkinsci/plugins/workflow/AvailableEnvVarTest.java aggregator/src/test/java/org/jenkinsci/plugins/workflow/EnvWorkflowTest.java http://jenkins-ci.org/commit/workflow-plugin/b5c7f4f5b5c362ec0a9447fd668f022d398d4628 Log:
JENKINS-28131
Filename has been renamed to be more clear
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-28131) Pass NODE_NAME into node{}
Title: Message Title
SCM/JIRA link daemon commented on JENKINS-28131
Re: Pass NODE_NAME into node{}
Code changed in jenkins User: recena Path: support/src/main/java/org/jenkinsci/plugins/workflow/support/steps/ExecutorStepExecution.java http://jenkins-ci.org/commit/workflow-plugin/f9e64a4fd9aff2b9d3f0f78280fc0dd1697cb081 Log:
JENKINS-28131
Checks if the executor is a Master
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-28131) Pass NODE_NAME into node{}
Title: Message Title
SCM/JIRA link daemon commented on JENKINS-28131
Re: Pass NODE_NAME into node{}
Code changed in jenkins User: recena Path: cps/src/main/resources/org/jenkinsci/plugins/workflow/cps/EnvActionImpl/Binder/help.jelly support/src/main/java/org/jenkinsci/plugins/workflow/support/steps/ExecutorStepExecution.java http://jenkins-ci.org/commit/workflow-plugin/ae1b4c965a649bdc9743e65074e3770ec8fe25cd Log:
JENKINS-28131
- Pass NODE_NAME into node{}
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-28131) Pass NODE_NAME into node{}
Title: Message Title
SCM/JIRA link daemon commented on JENKINS-28131
Re: Pass NODE_NAME into node{}
Code changed in jenkins User: recena Path: aggregator/src/test/java/org/jenkinsci/plugins/workflow/EnvWorkflowTest.java support/src/main/java/org/jenkinsci/plugins/workflow/support/steps/ExecutorStepExecution.java http://jenkins-ci.org/commit/workflow-plugin/6a64190bfc67fbef4f91d18ff88670235ce910f4 Log:
JENKINS-28131
Solved a findbug 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] [workflow-plugin] (JENKINS-28131) Pass NODE_NAME into node{}
Title: Message Title
SCM/JIRA link daemon commented on JENKINS-28131
Re: Pass NODE_NAME into node{}
Code changed in jenkins User: recena Path: cps/src/main/resources/org/jenkinsci/plugins/workflow/cps/EnvActionImpl/Binder/help.jelly support/src/main/java/org/jenkinsci/plugins/workflow/support/steps/ExecutorStepExecution.java http://jenkins-ci.org/commit/workflow-plugin/535400df863aa3e297bee6d7a2c51c62b5d32ccc Log:
JENKINS-28131
- Pass NODE_NAME into node{}
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-28131) Pass NODE_NAME into node{}
Title: Message Title
SCM/JIRA link daemon commented on JENKINS-28131
Re: Pass NODE_NAME into node{}
Code changed in jenkins User: Jesse Glick Path: CHANGES.md aggregator/src/test/java/org/jenkinsci/plugins/workflow/EnvWorkflowTest.java cps/src/main/resources/org/jenkinsci/plugins/workflow/cps/EnvActionImpl/Binder/help.jelly support/src/main/java/org/jenkinsci/plugins/workflow/support/steps/ExecutorStepExecution.java http://jenkins-ci.org/commit/workflow-plugin/06cb328979c8772da21a12b265a69dde68024e0c Log: Merge pull request #145 from recena/master
JENKINS-28131
- Pass NODE_NAME into node{}
Compare: https://github.com/jenkinsci/workflow-plugin/compare/b127fd48c37e...06cb328979c8
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] [coverity-plugin] (JENKINS-25323) Coverity Plugin 1.4.1 : Issues with starting a build after selecting Coverity as Post Build action
Title: Message Title Christopher Shannon commented on JENKINS-25323 Re: Coverity Plugin 1.4.1 : Issues with starting a build after selecting Coverity as Post Build action I have seen this same issue - not sure if it is an interaction between the Coverity and ClearCase plugins... 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-29144) SimpleBuildStep to receive EnvVars
Title: Message Title Jesse Glick created an issue Jenkins / JENKINS-29144 SimpleBuildStep to receive EnvVars Issue Type: Improvement Assignee: Unassigned Components: core Created: 30/Jun/15 2:33 PM Labels: workflow Priority: Critical Reporter: Jesse Glick SimpleBuildStep.perform needs to be given an EnvVars argument. Otherwise there is no way for an implementation to observe any local environment variable settings. Add Comment
[JIRA] [gerrit-trigger-plugin] (JENKINS-26010) Workflow plugin not working with with Gerrit event
Title: Message Title rin_ne commented on JENKINS-26010 Re: Workflow plugin not working with with Gerrit event Sorry, my mention regarding quiet period was not enough. GT has independent filed regarding quiet period as named Build Schedule Delay. GT compares both project and GT value then set bigger ones as argument of schedule() when scheduling build. Thus GT's quiet period is still enabled even if it cannot be taken from project. Regarding quiet period, the below links should be read. For project: https://github.com/jenkinsci/jenkins/blob/master/core/src/main/resources/jenkins/model/GlobalQuietPeriodConfiguration/help-quietPeriod.html For GT: https://github.com/jenkinsci/gerrit-trigger-plugin/blob/master/src/main/webapp/help-BuildScheduleDelay.html 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] [promoted-builds-plugin] (JENKINS-29132) Deleted promotion steps keep executing
Title: Message Title anton kropp commented on JENKINS-29132 Re: Deleted promotion steps keep executing For what it's worth I was able to unblock myself by stopping all slaves and master and going to my jobs promotion folder on the master and deleting the configurations that wouldn't go away. That seemed to do the trick. If you don't stop Jenkins then if you delete those steps they get rewritten during the promotion step so it seems like they are somehow cached? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-pipeline-plugin] (JENKINS-27537) Regular list project view failing to load with Build Pipeline > 1.4.5 installed
Title: Message Title Max Burdge commented on JENKINS-27537 Re: Regular list project view failing to load with Build Pipeline > 1.4.5 installed Tried downgrading Build Pipeline to 1.4.5, but error is still happening (Jenkins 1.600). 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] [job-dsl-plugin] (JENKINS-21750) Promoted Builds Plugin
Title: Message Title Jörg Eichhorn updated an issue Jenkins / JENKINS-21750 Promoted Builds Plugin Adding promoted builds plugin component, maybe there's somebody paying attention. Change By: Jörg Eichhorn Component/s: promoted-builds-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] [core] (JENKINS-29140) Temporary file appears to leak data
Title: Message Title Mark Syms commented on JENKINS-29140 Re: Temporary file appears to leak data I think it probably was from exceeding the 8GB limit, I'm "tweaking" the build to split the output. Not nice that it can generate this though. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-pipeline-plugin] (JENKINS-27537) Regular list project view failing to load with Build Pipeline > 1.4.5 installed
Title: Message Title Max Burdge commented on JENKINS-27537 Re: Regular list project view failing to load with Build Pipeline > 1.4.5 installed Same issue here, Jenkins 1.600 Build Pipeline 1.4.7. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-29140) Temporary file appears to leak data
Title: Message Title Daniel Beck commented on JENKINS-29140 Re: Temporary file appears to leak data No idea where the file name is from, but note that if you're beyond 8GB, Jenkins archiving will fail. There are proposed fixes, but none are in yet. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven-plugin] (JENKINS-22486) API change in maven 3.2.1 causes builds with the parallel (-T option) to fail with an exception.
Title: Message Title Eugene Gunov commented on JENKINS-22486 Re: API change in maven 3.2.1 causes builds with the parallel (-T option) to fail with an exception. Is this going to be 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] [disk-usage-plugin] (JENKINS-29143) ConcurrentModificationException in Disk Usage Plugin
Title: Message Title Remo Meier created an issue Jenkins / JENKINS-29143 ConcurrentModificationException in Disk Usage Plugin Issue Type: Bug Assignee: Lucie Votypkova Components: disk-usage-plugin Created: 30/Jun/15 12:53 PM Priority: Critical Reporter: Remo Meier We have almost every evening problems with hanging Jenkins Jobs with huge amount of following java error occures: Error: Jun 29, 2015 10:34:30 PM WARNING hudson.plugins.disk_usage.DiskUsageBuildListener onCompleted Disk usage plugin fails during build calculation disk space of job EV0_UTIL_STG_LOAD java.lang.RuntimeException: Failed to serialize hudson.plugins.disk_usage.ProjectDiskUsage#buildDiskUsage for class hudson.plugins.disk_usage.ProjectDiskUsage at hudson.util.RobustReflectionConverter$2.writeField(RobustReflectionConverter.java:214) at hudson.util.RobustReflectionConverter$2.visit(RobustReflectionConverter.java:182) at com.thoughtworks.xstream.converters.reflection.PureJavaReflectionProvider.visitSerializableFields(PureJavaReflectionProvider.java:138) at hudson.util.RobustReflectionConverter.doMarshal(RobustReflectionConverter.java:167) at hudson.util.RobustReflectionConverter.marshal(RobustReflectionConverter.java:108) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller.convert(AbstractReferenceMarshaller.java:69) at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:58) at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:43) at com.thoughtworks.xstream.core.TreeMarshaller.start(TreeMarshaller.java:82) at com.thoughtworks.xstream.core.AbstractTreeMarshallingStrategy.marshal(AbstractTreeMarshallingStrategy.java:37) at com.thou
[JIRA] [core] (JENKINS-12699) Temp upload files from file param not removed after transferred to slave
Title: Message Title
Christopher Orr commented on JENKINS-12699
Re: Temp upload files from file param not removed after transferred to slave
I'm not seeing this behaviour with large file parameters, whether the build is executed on master or a slave.
But I'm not using buildWithParameters, but rather the build format documented here: https://wiki.jenkins-ci.org/display/JENKINS/Remote+access+API#RemoteaccessAPI-Submittingjobs
i.e.
curl -v -X POST http://jenkins.local:8080/job/upload-test/build \
--form f0=@/data/fw123.bin \
--form json='{"parameter": [{"name":"firmware.bin", "file":"f0"}]}'
When the job is running, I see "Copying file to firmware.bin" in the console output. But checking /tmp and the java.io.tmpdir directory on the slave while this is happening shows no temporary files being created.
Elgin Peteza: Can you provide more detail on exactly how you're starting a job?
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 Christopher Orr reopened an issue Reopening as per JENKINS-29121 . Jenkins / JENKINS-12699 Temp upload files from file param not removed after transferred to slave Change By: Christopher Orr Resolution: Incomplete Status: Resolved Reopened 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-29121) upload_*.tmp files in /tmp of master cannot be correlated to their specific job and build
Title: Message Title Christopher Orr resolved as Duplicate This is a duplicate of JENKINS-12699 . As per that issue, it would be simpler to ensure that Jenkins deletes these temporary files automatically, rather than providing some complex mechanism to allow people to perhaps delete them later. Jenkins / JENKINS-29121 upload_*.tmp files in /tmp of master cannot be correlated to their specific job and build Change By: Christopher Orr 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 m
[JIRA] [job-dsl-plugin] (JENKINS-28985) Support for Join Plugin
Title: Message Title Joschua Grube commented on JENKINS-28985 Re: Support for Join Plugin Thank you for the fast 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] [job-dsl-plugin] (JENKINS-28405) Add support for all code browser for the Git plugin
Title: Message Title Daniel Spilker commented on JENKINS-28405 Re: Add support for all code browser for the Git plugin Support for GitLab and Gitblit will be added in 1.35. 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] [job-dsl-plugin] (JENKINS-28405) Add support for all code browser for the Git plugin
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-28405 Add support for all code browser for the Git plugin Change By: SCM/JIRA link daemon 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] [job-dsl-plugin] (JENKINS-28405) Add support for all code browser for the Git plugin
Title: Message Title SCM/JIRA link daemon commented on JENKINS-28405 Re: Add support for all code browser for the Git plugin Code changed in jenkins User: Jean-Philippe BOLATRE Path: docs/Job-reference.md job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/helpers/scm/GitBrowserContext.groovy job-dsl-core/src/test/groovy/javaposse/jobdsl/dsl/helpers/ScmContextSpec.groovy http://jenkins-ci.org/commit/job-dsl-plugin/3c5f8948a88697f737483917737ee8af4c8925b9 Log: [FIXED JENKINS-28405] Add support for all missing git code browsers Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-29140) Temporary file appears to leak data
Title: Message Title Mark Syms commented on JENKINS-29140 Re: Temporary file appears to leak data The build finally failed with - Archiving artifacts ERROR: Failed to archive artifacts: java.io.IOException: Failed to extract e:\workspace__/transfer of 18325 files at hudson.FilePath.readFromTar(FilePath.java:2299) at hudson.FilePath.copyRecursiveTo(FilePath.java:2210) at jenkins.model.StandardArtifactManager.archive(StandardArtifactManager.java:61) at hudson.tasks.ArtifactArchiver.perform(ArtifactArchiver.java:219) at hudson.tasks.BuildStepCompatibilityLayer.perform(BuildStepCompatibilityLayer.java:75) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:779) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:726) at hudson.model.Build$BuildExecution.post2(Build.java:185) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:671) at hudson.model.Run.execute(Run.java:1769) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:374) Caused by: java.io.IOException: unexpected EOF with 2560 bytes unread at hudson.org.apache.tools.tar.TarInputStream.read(TarInputStream.java:349) at java.io.FilterInputStream.read(FilterInputStream.java:107) at org.apache.commons.io.IOUtils.copyLarge(IOUtils.java:1792) at org.apache.commons.io.IOUtils.copyLarge(IOUtils.java:1769) at org.apache.commons.io.IOUtils.copy(IOUtils.java:1744) at hudson.util.IOUtils.copy(IOUtils.java:40) at hudson.FilePath.readFromTar(FilePath.java:2289) ... 13 more Build step 'Archive the artifacts' changed build result to FAILURE Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://group
[JIRA] [core] (JENKINS-29140) Temporary file appears to leak data
Title: Message Title
Mark Syms commented on JENKINS-29140
Re: Temporary file appears to leak data
In the build archive folder {Build Record Root Directory}
///archive
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [vsphere-cloud-plugin] (JENKINS-28627) Jenkins Vsphere-cloud-plugin
Title: Message Title ramazanyich2 updated an issue Jenkins / JENKINS-28627 Jenkins Vsphere-cloud-plugin I have created a sample patch which uses existing customization spec and allows change IP address. Could you merge it into the main master branch ? Change By: ramazanyich2 Attachment: vsphere_customizations.patch Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven-plugin] (JENKINS-27372) Failed to getClass for org.apache.maven.plugin.source.SourceJarMojo
Title: Message Title Harald Albers commented on JENKINS-27372 Re: Failed to getClass for org.apache.maven.plugin.source.SourceJarMojo Decreasing severity to Minor as the build is not affected. This issue is only about warning messages. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven-plugin] (JENKINS-27372) Failed to getClass for org.apache.maven.plugin.source.SourceJarMojo
Title: Message Title Harald Albers updated an issue Jenkins / JENKINS-27372 Failed to getClass for org.apache.maven.plugin.source.SourceJarMojo Change By: Harald Albers Priority: Major Minor Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-29140) Temporary file appears to leak data
Title: Message Title Daniel Beck commented on JENKINS-29140 Re: Temporary file appears to leak data Where is the file located? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven-plugin] (JENKINS-27372) Failed to getClass for org.apache.maven.plugin.source.SourceJarMojo
Title: Message Title Harald Albers commented on JENKINS-27372 Re: Failed to getClass for org.apache.maven.plugin.source.SourceJarMojo For me the solution was to change the goal from jar to jar-no-fork: org.apache.maven.plugins maven-source-plugin attach-sources verify jar-no-fork true @Charles Chan please check if that also works for you and report back here. 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-29010) Installed jenkins plugins should also be listed in 'available' section in jenkins admin
Title: Message Title Daniel Beck commented on JENKINS-29010 Re: Installed jenkins plugins should also be listed in 'available' section in jenkins admin It's even worse when the installed plugin is disabled, then you can't even see the UI elements of it and really don't expect it to be installed. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven-plugin] (JENKINS-27372) Failed to getClass for org.apache.maven.plugin.source.SourceJarMojo
Title: Message Title Harald Albers commented on JENKINS-27372 Re: Failed to getClass for org.apache.maven.plugin.source.SourceJarMojo I can confirm this for Maven Project Plugin 2.9 on Jenkins 1.614: [INFO] >>> maven-source-plugin:2.4:jar (attach-sources) @ some.project >>> [WARNING] Failed to getClass for org.apache.maven.plugin.source.SourceJarMojo [INFO] <<< maven-source-plugin:2.4:jar (attach-sources) @ some.project <<< 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] [copyartifact-plugin] (JENKINS-28972) No page found '/hudson/plugins/promoted_builds_simple/PromotedBuildSelector/config.jelly
Title: Message Title Tom Ghyselinck commented on JENKINS-28972 Re: No page found '/hudson/plugins/promoted_builds_simple/PromotedBuildSelector/config.jelly Hi ikedam, We just bumped into this issue. When will the next release of the plugin be available? 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] [slave-utilization] (JENKINS-29003) 'No file' option when run jenkins slave agent
Title: Message Title Daniel Beck commented on JENKINS-29003 Re: 'No file' option when run jenkins slave agent Sasha Neftin This was resolved as Duplicate, which means it's the same issue as another already reported one, and the actual status is tracked there. For more information how we use Jira, see https://wiki.jenkins-ci.org/display/JENKINS/Issue+Tracking 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] [cmakebuilder-plugin] (JENKINS-29142) look for MSVC 15.x toolchain
Title: Message Title Simon Richter created an issue Jenkins / JENKINS-29142 look for MSVC 15.x toolchain Issue Type: Improvement Assignee: Unassigned Components: cmakebuilder-plugin Created: 30/Jun/15 10:57 AM Environment: Windows with MSVC Priority: Minor Reporter: Simon Richter The generators for MSVC require that cl.exe is in the PATH, and the LIB and INCLUDE variables have been set up before invoking cmake. The cmakebuilder plugin cannot do that, so it cannot be used with the standalone toolchain. It would be great if the plugin would test whether the prerequisites are given, and look for the toolchain on its own if they are not. Add Comment
[JIRA] [throttle-concurrent-builds-plugin] (JENKINS-29141) trottle-concurrent-build-plugin allowes concureent jobs under circumstances
Title: Message Title Thomas Schweikle created an issue Jenkins / JENKINS-29141 trottle-concurrent-build-plugin allowes concureent jobs under circumstances Issue Type: Bug Assignee: Oleg Nenashev Components: throttle-concurrent-builds-plugin Created: 30/Jun/15 10:25 AM Environment: Systemeigenschaften Name ↓ Wert user.timezone Europe/Berlin user.name jenkins user.language de user.home /var/lib/jenkins user.dir / user.country DE sun.os.patch.level unknown sun.management.compiler HotSpot 64-Bit Tiered Compilers sun.jnu.encoding UTF-8 sun.java.launcher SUN_STANDARD sun.java.command /usr/lib/jenkins/jenkins.war --logfile=/var/log/jenkins/jenkins.log --webroot=/var/cache/jenkins/war --daemon --httpPort=8080 --ajp13Port=8009 --debug=5 --handlerCountMax=100 --handlerCountMaxIdle=20 sun.io.unicode.encoding UnicodeLittle sun.font.fontmanager sun.awt.X11FontManager sun.cpu.isalist sun.cpu.endian little sun.boot.library.path /usr/java/jdk1.8.0_45/jre/lib/amd64 sun.boot.class.path /usr/java/jdk1.8.0_45/jre/lib/resources.jar:/usr/java/jdk1.8.0_45/jre/lib/rt.jar:/usr/java/jdk1.8.0_45/jre/lib/sunrsasign.jar:/usr/java/jdk1.8.0_45/jre/lib/jsse.jar:/usr/java/jdk1.8.0_45/jre/lib/jce.jar:/usr/java/jdk1.8.0_45/jre/lib/charsets.jar:/usr/java/jdk1.8.0_45/jre/lib/jfr.jar:/usr/java/jdk1.8.0_45/jre/classes sun.arch.data.model 64 path.separator : os.version 3.8.13-68.3.3.el7uek.x86_64 os.name Linux os.arch amd64 mail.smtps.sendpartial true mail.smtp.sendpartial true line.separator lib.svnkit.ssh2.persistent false lib.svnkit.http.methods Digest,Basic,NTLM,Negotiate jnidispatch.path /tmp/jna--1712433994/jna4244853536295263288.tmp jna.platform.library.path /usr/lib64:/lib64:/usr/lib:/lib JENKINS_HOME /var/lib/jenkins java.vm.version 25.45-b02 java.vm.vendor Oracle Corporation java.vm.specification.version 1.8 java.vm.specification.vendor Oracle Corporation java.vm.specification.name Java Virtual Machine Specification java.vm.name Java HotSpot(TM) 64-Bit Server VM java.vm.info mixed mode java.version 1.8.0_45 java.vendor.url.bug http://bugreport.sun.com/bugreport/ java.vendor.url http://java.oracle.com/ java.vendor Oracle Corporation java.specification.version 1.8 java.specification.vendor Oracle Corporation java.specification.name Java Platform API Specification java.runtime.version 1.8.0_45-b14 java.runtim
[JIRA] [core] (JENKINS-29140) Temporary file appears to leak data
Title: Message Title Mark Syms created an issue Jenkins / JENKINS-29140 Temporary file appears to leak data Issue Type: Bug Assignee: Unassigned Components: core Created: 30/Jun/15 10:14 AM Environment: Master. Debian Linux 7, openjdk-7-jre, 7u79-2.5.5-1~deb7u1, amd64, Jenkins 1.617 from package repository. Build Slave: Windows 2012R2, Oracle Java 8 update 45, x64 Priority: Trivial Reporter: Mark Syms While monitoring an archive operation in order to investigate Jenkins-29137 I spotted a strangely named file - rw-r r - 1 jenkins jenkins 2553815040 Jun 30 11:11 $eip $T0 ^ = $esp $T0 4 + = This file is growing so looks to be the currently working file and the file name looks suspiciously like Java Byte code. Random file name generation managing to read unclean data from the heap?
[JIRA] [core] (JENKINS-29137) Repeated failure to archive build artifacts
Title: Message Title Mark Syms commented on JENKINS-29137 Re: Repeated failure to archive build artifacts Looks like it may be a variant of https://issues.jenkins-ci.org/browse/JENKINS-10629. One of the files being archived (which is itself an archive) has grown to over 8GB. Going to look at splitting this archive into smaller pieces to see if it resolves the issue. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
