[JIRA] (JENKINS-14255) java.io.InvalidClassException:
Karsten Brandt updated JENKINS-14255 java.io.InvalidClassException: Change By: Karsten Brandt (01/Jul/12 9:20 AM) Attachment: sloccount.hpi This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14255) java.io.InvalidClassException:
Karsten Brandt commented on JENKINS-14255 java.io.InvalidClassException: I've revoked the last "optimization" in commit 2d0f2d6358cad6ae144abef5e6f304c4e3e5bb94 to keep the backward compatibility. The introducing of a new class field 'report' in class SloccountParser has lead to a change of the serialVersionUID and this leads probably to the java.io.InvalidClassException as reported in #JENKINS-14255. Please try again with the modified plugin, which has been attached to this issue. Thereto download the attached hpi file (advanced settings dialog within the plugin manager) and restart your jenkins server. After restart you should see in the plugin manager a installed plugin version look like this: 1.8-SNAPSHOT (private-07/01/2012 10:53-brandt). Please, report the test result! Best regards, Karsten This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14135) NPE
Karsten Brandt commented on JENKINS-14135 NPE @Carsten: I've revoked the last "optimization" in commit 2d0f2d6358cad6ae144abef5e6f304c4e3e5bb94 to keep the backward compatibility. The introducing of a new class field 'report' in class SloccountParser has lead to a change of the serialVersionUID and this leads probably to the java.io.InvalidClassException as reported in #JENKINS-14255. And probably also to your reported issue. Please try again with the modified plugin, which has been attached to the issue #JENKINS-14255. Thereto download the attached hpi file (advanced settings dialog within the plugin manager) and restart your jenkins server. After restart you should see in the plugin manager a installed plugin version look like this: 1.8-SNAPSHOT (private-07/01/2012 10:53-brandt). Many thanks for your effort, Karsten This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14135) NPE
Karsten Brandt edited a comment on JENKINS-14135 NPE @Carsten: I've revoked the last "optimization" in commit 2d0f2d6358cad6ae144abef5e6f304c4e3e5bb94 to keep the backward compatibility. The introducing of a new class field 'report' in class SloccountParser has lead to a change of the serialVersionUID and this leads probably to the java.io.InvalidClassException as reported in #JENKINS-14255. And probably also to your reported issue. Please try again with the modified plugin, which has been attached to issue #JENKINS-14255. Thereto download the attached hpi file (advanced settings dialog within the plugin manager) and restart your jenkins server. After restart you should see in the plugin manager a installed plugin version look like this: 1.8-SNAPSHOT (private-07/01/2012 10:53-brandt). Many thanks for your effort, Karsten This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-8046) Cannot parse CodeNarc xml report
bocytko commented on JENKINS-8046 Cannot parse CodeNarc xml report @kefirek: can you please create a new JIRA issue, link it with this one and provide the stacktrace, used plugin versions and the CodeNarcReport.xml file? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14270) The report does not show the covered/all, it shows something different
Ognjen Bubalo created JENKINS-14270 The report does not show the covered/all, it shows something different Issue Type: Bug Assignee: Ognjen Bubalo Components: jacoco Created: 01/Jul/12 3:01 PM Project: Jenkins Priority: Major Reporter: Ognjen Bubalo This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14203) Looks like the total summary is double counted
Ognjen Bubalo resolved JENKINS-14203 as Fixed Looks like the total summary is double counted Change By: Ognjen Bubalo (01/Jul/12 3:08 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14203) Looks like the total summary is double counted
Ognjen Bubalo closed JENKINS-14203 as Fixed Looks like the total summary is double counted Change By: Ognjen Bubalo (01/Jul/12 3:08 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14270) The report does not show the covered/all, it shows something different
SCM/JIRA link daemon commented on JENKINS-14270 The report does not show the covered/all, it shows something different Code changed in jenkins User: Ognjen Bubalo Path: src/main/java/hudson/plugins/jacoco/model/CoverageObject.java src/test/java/hudson/plugins/jacoco/model/CoverageObjectTest.java http://jenkins-ci.org/commit/jacoco-plugin/0eac7444a606b3f64a5f06f27105b570f4b7f769 Log: Fixing: JENKINS-14270 The report does not show the covered/all, it shows something different Fixing not valid testcases also This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14269) Archive the artifacts does not preserve file exec permissions
Gregory Boissinot updated JENKINS-14269 Archive the artifacts does not preserve file exec permissions It seems to be not an issue of the Arifactdeployer Jenkins plugin. For the ArtifactDeployer plugin, the entry point is "[ArtifactDeployer] - Deploy artifacts from workspace to remote directories". Change By: Gregory Boissinot (01/Jul/12 4:37 PM) Component/s: core Component/s: artifactdeployer This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-10106) FTP Plugin loses configuration when unchecking the box
evernat resolved JENKINS-10106 as Fixed FTP Plugin loses configuration when unchecking the box This is committed so this is certainly fixed. Change By: evernat (01/Jul/12 4:36 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-10029) Add field "name"
evernat resolved JENKINS-10029 as Fixed Add field "name" This is committed so this is certainly fixed. Change By: evernat (01/Jul/12 4:37 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14271) EnvInject claims global env vars are unresolved on slave
Jørgen Tjernø created JENKINS-14271 EnvInject claims global env vars are unresolved on slave Issue Type: Bug Affects Versions: current Assignee: Gregory Boissinot Components: envinject Created: 02/Jul/12 1:10 AM Description: Steps to reproduce: 1. Go to /configure and check 'Environment variables' under 'Global properties' 2. Add a variable called GLOBAL_VAR with the value $HOME/foo and save 3. Create a new job, check 'Prepare an environment for the run' and put 'DERIVED_VAR=$GLOBAL_VAR/bar' in 'Properties Content'. 4. Check 'Restrict where this project can be run' and make it run on a node OTHER THAN master 5. Add an 'Execute shell' build step and add: echo $GLOBAL_VAR echo $DERIVED_VAR 6. Run job Expected output: Building remotely on not_master in workspace /tmp/slave/workspace/env_test [env_test] $ /bin/sh -xe /var/folders/t5/2y9vs7rj20b7h_h3hj_d_ly98mbs7g/T/hudson2936884432042635298.sh /home/jenkins/foo /home/jenkins/foo/bar Actual output: [EnvInject] - Unset unresolved 'GLOBAL_VAR' variable. [EnvInject] - Unset unresolved 'DERIVED_VAR' variable. Building remotely on not_master in workspace /tmp/slave/workspace/env_test [env_test] $ /bin/sh -xe /var/folders/t5/2y9vs7rj20b7h_h3hj_d_ly98mbs7g/T/hudson2936884432042635298.sh /home/jenkins/foo Environment: EnvInject 1.55 Jenkins 1.472 Project: Jenkins Priority: Major Reporter: Jørgen Tjernø This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14197) Plugin is preventing setting "Restrict where this project can be run"
OHTAKE Tomohiro commented on JENKINS-14197 Plugin is preventing setting "Restrict where this project can be run" Promoted Builds 2.6.1 has been released. It will be available in several hours. Sorry for inconvenience. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14257) Saving job configuration looses slave defintion
R. Tyler Croy commented on JENKINS-14257 Saving job configuration looses slave defintion I'm seeing this behavior on 1.471 as well (for what it's worth) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14257) Saving job configuration looses slave defintion
R. Tyler Croy commented on JENKINS-14257 Saving job configuration looses slave defintion Digging through the config.xml for a job that is updated after the upgrade, it seems the tag disappears entirely from the XML. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14257) Saving job configuration loses assigned node
R. Tyler Croy resolved JENKINS-14257 as Duplicate Saving job configuration loses assigned node This is a duplicate I believe of JENKINS-14197. Jose, I fixed this by downgrading my "Promoted Builds" plugin version from 2.6, I was then able to save the assigned node properly on 1.472 Change By: R. Tyler Croy (02/Jul/12 4:34 AM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14226) Restrict where this project can be run, does not work anymore
OHTAKE Tomohiro resolved JENKINS-14226 as Duplicate Restrict where this project can be run, does not work anymore Change By: OHTAKE Tomohiro (02/Jul/12 5:05 AM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14257) Saving job configuration loses assigned node
Jose Sa commented on JENKINS-14257 Saving job configuration loses assigned node I also had to downgrade the Promoted Builds plugin as the core alone was not enough. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
