[JIRA] (JENKINS-3803) Archived artifacts are served with improper mime-types
[ https://issues.jenkins-ci.org/browse/JENKINS-3803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159376#comment-159376 ] SCM/JIRA link daemon commented on JENKINS-3803: --- Code changed in jenkins User: George Shakhnazaryan Path: war/src/main/webapp/WEB-INF/web.xml http://jenkins-ci.org/commit/jenkins/c1d2c945465d30efb63de7abce51d95289170e63 Log: Adding the video/webm mime type for files with extension .webm. The change is similar to JENKINS-3803, just a different extension. Archived artifacts are served with improper mime-types -- Key: JENKINS-3803 URL: https://issues.jenkins-ci.org/browse/JENKINS-3803 Project: Jenkins Issue Type: Bug Components: core Affects Versions: current Environment: Platform: All, OS: All Reporter: R. Tyler Croy Attachments: web.xml.diff We use the Archive build artifacts to save a number of logs pertaining to the build, these files are all text files with a .log suffix. Regardless of this however, Hudson still serves these files with the 'application/octet-stream' mime- type, causing stupid browsers like Firefox to try to download the file instead of render the text. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12628) Executable file permission not set anymore
[ https://issues.jenkins-ci.org/browse/JENKINS-12628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159377#comment-159377 ] Alex Lehmann commented on JENKINS-12628: this needs to be in a try block that catches NoSuchMethodError similar to the permission method in hudson.utils Executable file permission not set anymore -- Key: JENKINS-12628 URL: https://issues.jenkins-ci.org/browse/JENKINS-12628 Project: Jenkins Issue Type: Bug Components: cvs Environment: CentOS release 5.7 (affected system, Slave), Windows Server 2003 (Master) Reporter: Marco Borm Assignee: Michael Clarke Fix For: current Updating the cvs plugin from 1.6 to 2.0 breaks all our linux builds, due the fact that our compile scripts don't have executable permission bit set anymore. The bit is correctly set on the affected files on cvs server side. cvs plugin 1.6: -rwxrwx--- 1 jenkins jenkins261 15. Mai 2007 compile.linux.so.release cvs plugin 2.0: -rw-rw-r-- 1 jenkins jenkins261 15. Mai 2007 compile.linux.so.release -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12499) Using Jenkins as installed by the installer results in permissions issues when trying to build using the Xcode Plugin.
[
https://issues.jenkins-ci.org/browse/JENKINS-12499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arnaud Héritier closed JENKINS-12499.
-
Using Jenkins as installed by the installer results in permissions issues
when trying to build using the Xcode Plugin.
--
Key: JENKINS-12499
URL: https://issues.jenkins-ci.org/browse/JENKINS-12499
Project: Jenkins
Issue Type: Bug
Components: xcode
Environment: Mac OSX 10.7, Jenkins 1.446, XCode PI 1.2
Reporter: Allen Fisher
Assignee: Sami Tikka
Fix For: current
The Jenkins Mac OS installer adds Jenkins as a system daemon, which makes it
difficult unlock a keychain and sign an iOS application.
I can build just fine from Xcode itself and I can run all the commands from
the command line that Jenkins generates. However, when I try and allow
Jenkins to build it,
I get several errors: Allowing Jenkins to unlock the keychain:
Started by user
ha:jx+LCABb85aBtbiIQSajNKU4P08vOT+vOD8nVc+jsiC1KCczL9svvyT1dMUiOWdZ/mImBiZPBrac1Lz0kgwfBubSopwSBiGfrMSyRP2cxLx0/eCSosy8dOuKIgYpNOOcITTIMAYIYGRiYKgoADI4Sxj49UuLU4v0E/Py8ypz80uLARtlXCuUanonymous
Using master perforce client: AF_MobileProject_CI perforce stuff snipped
Working directory is
/Users/allen/Projects/Jenkins/MobileProject/Cocoa_Dev/MyAppDev/MyApp/MACPROJ.
[MACPROJ] $ /usr/bin/xcodebuild -version Xcode 4.2.1 Build version 4D502
version stuff snipped
Cleaning up test-reports :
/Users/allen/Projects/Jenkins/MobileProject/Cocoa_Dev/MyAppDev/MyApp/MACPROJ/test-reports
[MACPROJ] $ /usr/bin/security list-keychains -s
/Library/Keychains/System.keychain
[MACPROJ] $ /usr/bin/security login-keychain -d user -s
/Library/Keychains/System.keychain
[MACPROJ] $ /usr/bin/security unlock-keychain -p
/Library/Keychains/System.keychain
security: SecKeychainUnlock /Library/Keychains/System.keychain: The user name
or passphrase you entered is not correct. FATAL: Unable to unlock the
keychain.
ha:WB+LCABb85aBtbiIQSmjNKU4P08vOT+vOD8nVc8DzHWtSE4tKMnMz/PLL0ldFVf2c+b/lb5MDAwVRQxSaBqcITRIIQMEMIIUFgAAckCEiWA=Build
step 'XCode' marked build as failure
Finished: FAILURE
In an attempt to get it building, I turned off unlocking the keychain to let
it prompt me:
beginning stuff snipped
Cleaning up test-reports :
/Users/allen/Projects/Jenkins/FinMo/Cocoa_Dev/MyAppDev/MyApp/MACPROJ/test-reports
Going to invoke xcodebuild:target: MyAppGo, sdk: DEFAULT, project:
/Users/allen/Projects/Jenkins/MyApp/Cocoa_Dev/MyAppDev/MyApp/MACPROJ/MyApp.xcodeproj,
configuration: , clean: NO, symRoot: DEFAULT, configurationBuildDir:
/Users/allen/Desktop/
[MACPROJ] $ /usr/bin/xcodebuild -target MyAppGo -project
/Users/allen/Projects/Jenkins/MyApp/Cocoa_Dev/MyAppDev/MyApp/MACPROJ/MyApp.xcodeproj
-configuration build CONFIGURATION_BUILD_DIR=/Users/allen/Desktop/
Build settings from command line: CONFIGURATION_BUILD_DIR =
/Users/allen/Desktop/
2012-01-19 13:39:53.670 xcodebuild[72650:a0b] [MT] IDELogStore: Failed to
open Build log store: Error Domain=NSCocoaErrorDomain Code=257 The file
“Cache.db” couldn’t be opened because you don’t have permission to
view it. UserInfo=0x4024f3180
{NSFilePath=/var/root/Library/Developer/Xcode/DerivedData/MyApp-ankgjozmpmrcwuejjwykmeibjorp/Logs/Build/Cache.db,
NSUnderlyingError=0x4024f3200 The operation couldn’t be completed.
Permission denied}. User info: { NSFilePath =
/var/root/Library/Developer/Xcode/DerivedData/MyApp-ankgjozmpmrcwuejjwykmeibjorp/Logs/Build/Cache.db;
NSUnderlyingError = Error Domain=NSPOSIXErrorDomain Code=13 \The operation
couldn\U2019t be completed. Permission denied\; }. --- xcodebuild: WARNING:
Configuration is not in the project. Building default configuration.
=== BUILD NATIVE TARGET MyAppGo OF PROJECT MyApp WITH THE DEFAULT
CONFIGURATION (Debug) ===
Check dependencies
[BEROR]Code Sign error: a valid provisioning profile matching the
application's Identifier 'com.mycompany.MyApp' could not be found
** BUILD FAILED **
The following build commands failed: Check dependencies
(1 failure) Build step 'XCode' marked build as failure
Finished: FAILURE The provisioning file and all the other items the project
need are available.
To work around it, if I run the Jenkins.war as me (or as sudo and use the
system keychain), the build works correctly.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12853) The Findbugs XML file is not searched correctly with latest Maven Findbugs plugin
cristalp created JENKINS-12853:
--
Summary: The Findbugs XML file is not searched correctly with
latest Maven Findbugs plugin
Key: JENKINS-12853
URL: https://issues.jenkins-ci.org/browse/JENKINS-12853
Project: Jenkins
Issue Type: Bug
Components: findbugs
Affects Versions: current
Environment: Jenkins 1.451, Maven 3.0.4, Maven Findbugs Plugin 2.4.0,
Jenkins Findbugs Plugin 4.33
Reporter: cristalp
Assignee: Ulli Hafner
When using the Maven2/3 job type, the Findbugs XML file isn't found. However,
it is found under the following circumstances:
* Using a free-style build
* Adding {{findbugsXmlOutputtrue/findbugsXmlOutput}} to the Maven Findbugs
configuration. But this parameter [has been
deprecated|http://mojo.codehaus.org/findbugs-maven-plugin-2.4.0/findbugs-mojo.html].
From the Maven site, it's not very clear what its behavior is: {{This has been
deprecated and is on by default. Default value is: false.}}
Even though the generated files are the same, the plugin seems to search for
the XML files in a different way.
Here's the output when the XML files are not found:
{code}
[INFO] --- findbugs-maven-plugin:2.4.0:findbugs (default) @ base-impl ---
[INFO] Fork Value is true
[java] Warnings generated: 4
[INFO] Done FindBugs Analysis
[FINDBUGS] Parsing 1 files in
/ige/jenkins/work/jobs/base/workspace/base-impl/target
[FINDBUGS] Successfully parsed file
/ige/jenkins/work/jobs/base/workspace/base-impl/target/findbugs.xml of module
Implementation of Base Services with 0 warnings.
{code}
Here's the output when the XML files are found:
{code}
[INFO] --- findbugs-maven-plugin:2.4.0:findbugs (default) @ base-impl ---
[java] Warnings generated: 4
[INFO] Done FindBugs Analysis
[FINDBUGS] Parsing 1 files in
/ige/jenkins/work/jobs/base/workspace/base-impl/target
[FINDBUGS] Successfully parsed file
/ige/jenkins/work/jobs/base/workspace/base-impl/target/findbugsXml.xml of
module Implementation of Base Services with 4 warnings.
{code}
Also see the [discussion on the mailing
list|http://groups.google.com/group/jenkinsci-users/browse_thread/thread/0d4d5d006b93e4d4#].
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12217) xcode-plugin: fails to set default keychain when using alternate (non login) keychain
[
https://issues.jenkins-ci.org/browse/JENKINS-12217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arnaud Héritier closed JENKINS-12217.
-
xcode-plugin: fails to set default keychain when using alternate (non login)
keychain
-
Key: JENKINS-12217
URL: https://issues.jenkins-ci.org/browse/JENKINS-12217
Project: Jenkins
Issue Type: Bug
Components: plugin, xcode
Affects Versions: current
Environment: Mac OS X 10.7.2
Reporter: David Whetstone
Assignee: Arnaud Héritier
Priority: Blocker
Using the following settings:
Unlock Keychain? checked
Keychain path: ${HOME}/Library/Keychains/tout-iphone.keychain
Keychain password: **
The build fails with the error:
Code Sign error: The identity 'iPhone Developer: ()' doesn't
match any valid certificate/private key pair in the default keychain
In addition, once the build is complete, my login keychain is no longer
present in the Keychain Access application.
I've tracked this down to XCodeBuilder.java:286
268:
launcher.launch().envs(envs).cmds(/usr/bin/security,login-keychain,-d,user,
-s,keychainPath).stdout(listener).pwd(projectRoot).join();
Specifically, it's calling 'security login-keychain' when I believe it should
be calling 'security default-keychain'. My build succeeds after changing
this line to the following:
268:
launcher.launch().envs(envs).cmds(/usr/bin/security,default-keychain,-d,user,
-s,keychainPath).stdout(listener).pwd(projectRoot).join();
I haven't looked into how this affects configurations that don't specify an
alternate keychain file.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-10449) Excluded regions do not exclude commits from changelog
[ https://issues.jenkins-ci.org/browse/JENKINS-10449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159379#comment-159379 ] Eugene Leonov edited comment on JENKINS-10449 at 2/22/12 11:08 AM: --- Of course it also relates to Included Regions field! Perhaps Excluded Users and Excluded Commit Message too, it's up to you. There is another reason to resolve this issue: [JIRA Plugin|https://wiki.jenkins-ci.org/display/JENKINS/JIRA+Plugin] writes comments to all issues from all commits in Changes. I don't sure, perhaps Jira Plugin gets issue-list from commits itself (without using changes field). If so, I'll create separate issue with jira component. Could anybody answer me? was (Author: eleonov): Of course it also relates to Included Regions field! Perhaps Excluded Users and Excluded Commit Message too, it's up to you. There is another reason to resolve this issue: [JIRA Plugin|https://wiki.jenkins-ci.org/display/JENKINS/JIRA+Plugin] writes comments to all issues from all commits in Changes. I don't sure, perhaps Jira Plugin gets issue-list from commits itself (without using changes field). If so, I'll create separate issue with jira component. Could somebody answer me? Excluded regions do not exclude commits from changelog -- Key: JENKINS-10449 URL: https://issues.jenkins-ci.org/browse/JENKINS-10449 Project: Jenkins Issue Type: Bug Components: subversion Affects Versions: current Reporter: Jørgen Tjernø Priority: Minor When using Excluded Regions to exclude certain parts of a repository from triggering a build (because it does not affect the build), the commits performed to those excluded regions are still listed in the changelog. If this is a feature and not a bug, it'd be great to at least have an option to exclude them from the changelog. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12108) EnvInject failure using multi-configuration jobs
[ https://issues.jenkins-ci.org/browse/JENKINS-12108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159356#comment-159356 ] JavierB edited comment on JENKINS-12108 at 2/22/12 11:48 AM: - This issue has happened to me again today when I've upgraded to version 1.26 of the EnvInject plugin From console output: [EnvInject] - Executing scripts and injecting environment variables after the SCM step. [EnvInject] - [ERROR] - [EnvInject] - [ERROR] - Problems occurs on injecting env vars as a build wrap: hudson.matrix.MatrixConfiguration cannot be cast to hudson.model.TopLevelItem I've rolled back to previous version 1.25 and things are working fine again. Current Jenkins version: Jenkins ver. 1.451 [under Ubuntu] was (Author: javierb): This issue has happened to me again today when I've upgraded to version 1.26 of the EnvInject plugin From console output: [EnvInject] - Executing scripts and injecting environment variables after the SCM step. [EnvInject] - [ERROR] - [EnvInject] - [ERROR] - Problems occurs on injecting env vars as a build wrap: hudson.matrix.MatrixConfiguration cannot be cast to hudson.model.TopLevelItem I've rolled back to previous version 1.25 and things are working fine again. Current Jenkins version: Jenkins ver. 1.451 EnvInject failure using multi-configuration jobs Key: JENKINS-12108 URL: https://issues.jenkins-ci.org/browse/JENKINS-12108 Project: Jenkins Issue Type: Bug Components: envinject Affects Versions: current Environment: Debian 5.0 Reporter: Thomas Wood Assignee: gbois Priority: Critical We recently upgraded to 1.424.1 LTS, and switched to the EnvInject plugin instead of the deprecated Hudson SetEnv plugin to set environment variables for our jobs. All our multi-configuration jobs are now failing: [EnvInject] - [ERROR] - [EnvInject] - [ERROR] - Problems occurs on injecting env vars as a build step: hudson.matrix.MatrixConfiguration cannot be cast to hudson.model.TopLevelItem This is easy to reproduce: - Install EnvInject - Create a new multiconfiguration job - Add an axis named axis with the values a b c - Add an execute shell build step consisting of echo $axis - Save and run the job (it should execute successfully against three configurations) - Now, edit the job and check Inject environment variables to the build process in the Build Environment section. You don't actually need to add any properties content to reproduce the problem--just check the checkbox. - Run the job again. All three configurations fail. This is a big problem for us as all our multi-configuration jobs also use environment variables. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12841) EnvInject Plugin 1.26 does not substitute ${WORKSPACE} correctly
[
https://issues.jenkins-ci.org/browse/JENKINS-12841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
mwebber updated JENKINS-12841:
--
Attachment: config.xml
Uploaded config.xml for the job that had the problem
EnvInject Plugin 1.26 does not substitute ${WORKSPACE} correctly
Key: JENKINS-12841
URL: https://issues.jenkins-ci.org/browse/JENKINS-12841
Project: Jenkins
Issue Type: Bug
Components: envinject
Reporter: mwebber
Assignee: gbois
Priority: Critical
Attachments: config.xml
This problem appeared when I upgraded the EnvInject Plugin from 1.25 to 1.26,
so the problem was probably introduced with the fix for JENKINS-12704.
I have a job with Inject environment variables to the build process
selected, and the following line in Properties Content:
materialize_workspace_path=${WORKSPACE}/materialize_workspace
In 1.25, this environment variable was correctly given the value
{{/scratch/jenkins_workspace/GDA_master.tests.RH5_64/materialize_workspace}}
In 1.26, this environment variable was WRONGLY given the value
{{/scratch/jenkins_slave//scratch/jenkins_workspace/GDA_master.tests.RH5_64/materialize_workspace}}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12108) EnvInject failure using multi-configuration jobs
[ https://issues.jenkins-ci.org/browse/JENKINS-12108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159356#comment-159356 ] JavierB edited comment on JENKINS-12108 at 2/22/12 11:59 AM: - This issue has happened to me again today when I've upgraded to version 1.26 of the EnvInject plugin From console output: [EnvInject] - Executing scripts and injecting environment variables after the SCM step. [EnvInject] - [ERROR] - [EnvInject] - [ERROR] - Problems occurs on injecting env vars as a build wrap: hudson.matrix.MatrixConfiguration cannot be cast to hudson.model.TopLevelItem I've rolled back to previous version [1.25|http://mirrors.jenkins-ci.org/plugins/envinject/1.25/] and things are working fine again. Current Jenkins version: Jenkins ver. 1.451 [under Ubuntu] was (Author: javierb): This issue has happened to me again today when I've upgraded to version 1.26 of the EnvInject plugin From console output: [EnvInject] - Executing scripts and injecting environment variables after the SCM step. [EnvInject] - [ERROR] - [EnvInject] - [ERROR] - Problems occurs on injecting env vars as a build wrap: hudson.matrix.MatrixConfiguration cannot be cast to hudson.model.TopLevelItem I've rolled back to previous version 1.25 and things are working fine again. Current Jenkins version: Jenkins ver. 1.451 [under Ubuntu] EnvInject failure using multi-configuration jobs Key: JENKINS-12108 URL: https://issues.jenkins-ci.org/browse/JENKINS-12108 Project: Jenkins Issue Type: Bug Components: envinject Affects Versions: current Environment: Debian 5.0 Reporter: Thomas Wood Assignee: gbois Priority: Critical We recently upgraded to 1.424.1 LTS, and switched to the EnvInject plugin instead of the deprecated Hudson SetEnv plugin to set environment variables for our jobs. All our multi-configuration jobs are now failing: [EnvInject] - [ERROR] - [EnvInject] - [ERROR] - Problems occurs on injecting env vars as a build step: hudson.matrix.MatrixConfiguration cannot be cast to hudson.model.TopLevelItem This is easy to reproduce: - Install EnvInject - Create a new multiconfiguration job - Add an axis named axis with the values a b c - Add an execute shell build step consisting of echo $axis - Save and run the job (it should execute successfully against three configurations) - Now, edit the job and check Inject environment variables to the build process in the Build Environment section. You don't actually need to add any properties content to reproduce the problem--just check the checkbox. - Run the job again. All three configurations fail. This is a big problem for us as all our multi-configuration jobs also use environment variables. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12108) EnvInject failure using multi-configuration jobs
[ https://issues.jenkins-ci.org/browse/JENKINS-12108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159356#comment-159356 ] JavierB edited comment on JENKINS-12108 at 2/22/12 11:59 AM: - This issue has happened to me again today when I've upgraded to version [1.26|http://mirrors.jenkins-ci.org/plugins/envinject/1.26/] of the EnvInject plugin From console output: [EnvInject] - Executing scripts and injecting environment variables after the SCM step. [EnvInject] - [ERROR] - [EnvInject] - [ERROR] - Problems occurs on injecting env vars as a build wrap: hudson.matrix.MatrixConfiguration cannot be cast to hudson.model.TopLevelItem I've rolled back to previous version [1.25|http://mirrors.jenkins-ci.org/plugins/envinject/1.25/] and things are working fine again. Current Jenkins version: Jenkins ver. 1.451 [under Ubuntu] was (Author: javierb): This issue has happened to me again today when I've upgraded to version 1.26 of the EnvInject plugin From console output: [EnvInject] - Executing scripts and injecting environment variables after the SCM step. [EnvInject] - [ERROR] - [EnvInject] - [ERROR] - Problems occurs on injecting env vars as a build wrap: hudson.matrix.MatrixConfiguration cannot be cast to hudson.model.TopLevelItem I've rolled back to previous version [1.25|http://mirrors.jenkins-ci.org/plugins/envinject/1.25/] and things are working fine again. Current Jenkins version: Jenkins ver. 1.451 [under Ubuntu] EnvInject failure using multi-configuration jobs Key: JENKINS-12108 URL: https://issues.jenkins-ci.org/browse/JENKINS-12108 Project: Jenkins Issue Type: Bug Components: envinject Affects Versions: current Environment: Debian 5.0 Reporter: Thomas Wood Assignee: gbois Priority: Critical We recently upgraded to 1.424.1 LTS, and switched to the EnvInject plugin instead of the deprecated Hudson SetEnv plugin to set environment variables for our jobs. All our multi-configuration jobs are now failing: [EnvInject] - [ERROR] - [EnvInject] - [ERROR] - Problems occurs on injecting env vars as a build step: hudson.matrix.MatrixConfiguration cannot be cast to hudson.model.TopLevelItem This is easy to reproduce: - Install EnvInject - Create a new multiconfiguration job - Add an axis named axis with the values a b c - Add an execute shell build step consisting of echo $axis - Save and run the job (it should execute successfully against three configurations) - Now, edit the job and check Inject environment variables to the build process in the Build Environment section. You don't actually need to add any properties content to reproduce the problem--just check the checkbox. - Run the job again. All three configurations fail. This is a big problem for us as all our multi-configuration jobs also use environment variables. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12108) EnvInject failure using multi-configuration jobs
[ https://issues.jenkins-ci.org/browse/JENKINS-12108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159380#comment-159380 ] JavierB edited comment on JENKINS-12108 at 2/22/12 11:59 AM: - Issue happens for version [1.26|http://mirrors.jenkins-ci.org/plugins/envinject/1.26/] was (Author: javierb): Issue happens for version 1.26 EnvInject failure using multi-configuration jobs Key: JENKINS-12108 URL: https://issues.jenkins-ci.org/browse/JENKINS-12108 Project: Jenkins Issue Type: Bug Components: envinject Affects Versions: current Environment: Debian 5.0 Reporter: Thomas Wood Assignee: gbois Priority: Critical We recently upgraded to 1.424.1 LTS, and switched to the EnvInject plugin instead of the deprecated Hudson SetEnv plugin to set environment variables for our jobs. All our multi-configuration jobs are now failing: [EnvInject] - [ERROR] - [EnvInject] - [ERROR] - Problems occurs on injecting env vars as a build step: hudson.matrix.MatrixConfiguration cannot be cast to hudson.model.TopLevelItem This is easy to reproduce: - Install EnvInject - Create a new multiconfiguration job - Add an axis named axis with the values a b c - Add an execute shell build step consisting of echo $axis - Save and run the job (it should execute successfully against three configurations) - Now, edit the job and check Inject environment variables to the build process in the Build Environment section. You don't actually need to add any properties content to reproduce the problem--just check the checkbox. - Run the job again. All three configurations fail. This is a big problem for us as all our multi-configuration jobs also use environment variables. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-9073) Job systematic failuer when selecting Exclude element CHECKEDOUT from the UCM Baseline build parameter
[ https://issues.jenkins-ci.org/browse/JENKINS-9073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Romain Seguy updated JENKINS-9073: -- Component/s: clearcase-ucm-baseline Job systematic failuer when selecting Exclude element CHECKEDOUT from the UCM Baseline build parameter -- Key: JENKINS-9073 URL: https://issues.jenkins-ci.org/browse/JENKINS-9073 Project: Jenkins Issue Type: Bug Components: clearcase-ucm-baseline Environment: Hudson 1.393 clearcase 7.0.1.2 Reporter: jlpinardon Assignee: Romain Seguy Priority: Critical When defining the UCM Baseline parameter, if the Exclude element CHECKEDOUT is checked, the job systematically fails when creating the view's config spec. The error message is : --- config spec start --- element /mts_tools/HudsonAdm/... B_HUDSONADM_V01_E24 -nocheckout element * /main/0 -ucm -nocheckout load /mts_tools/HudsonAdm/Controler --- config spec end --- [HUDSON_CTRL_B_HUDSONADM_V01_E24] $ /usr/atria/bin/cleartool setcs -tag HUDSON_CTRL_B_HUDSONADM_V01_E24 ../configspec50873.txt cleartool: Error: The first element rule of a snapshot view's config spec must be element * CHECKEDOUT. cleartool: Error: Config spec semantic processing failed. cleartool: Error: Unable to change configuration specification: error in configuration specification. FATAL: ClearCase UCM baseline failed. exit code=1 Note that it works correctly if the checkbox is not checked. But it means that we cannot ensure that checkedout versions are not loaded, which is a critical problem when building or testing stable configuration. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12184) role management or view configuration leads to server Error 500, and the configuration works in memory but not in Jenkins's config.xml
[ https://issues.jenkins-ci.org/browse/JENKINS-12184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Romain Seguy reassigned JENKINS-12184: -- Assignee: Daniel Petisme (was: Romain Seguy) role management or view configuration leads to server Error 500, and the configuration works in memory but not in Jenkins's config.xml --- Key: JENKINS-12184 URL: https://issues.jenkins-ci.org/browse/JENKINS-12184 Project: Jenkins Issue Type: Bug Components: core, role-strategy Affects Versions: current Environment: Red Hat Enterprise Linux Server release 5.4, Reporter: Halcyon Yang Assignee: Daniel Petisme Priority: Critical When configure Manage Roles, or manage views or do some other configurations, Jenkins returns the following error messg. The question is the configuration did works! But restart Jenkins or reload the configuration from file, the former configuration disappears. This problem works with server latest Jenkins version. javax.servlet.ServletException: java.lang.RuntimeException: Failed to serialize jenkins.model.Jenkins#authorizationStrategy for class hudson.model.Hudson org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:603) org.kohsuke.stapler.Stapler.invoke(Stapler.java:646) org.kohsuke.stapler.Stapler.invoke(Stapler.java:477) org.kohsuke.stapler.Stapler.service(Stapler.java:159) javax.servlet.http.HttpServlet.service(HttpServlet.java:717) hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95) net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:185) net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:159) net.bull.javamelody.PluginMonitoringFilter.doFilter(PluginMonitoringFilter.java:86) org.jvnet.hudson.plugins.monitoring.HudsonMonitoringFilter.doFilter(HudsonMonitoringFilter.java:84) hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98) hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:74) hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98) hudson.plugins.audit_trail.AuditTrailFilter.doFilter(AuditTrailFilter.java:66) hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98) hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87) hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:47) hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) org.acegisecurity.ui.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:166) hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:173) hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:61) hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:66) hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) root cause java.lang.RuntimeException: Failed to serialize jenkins.model.Jenkins#authorizationStrategy for class hudson.model.Hudson hudson.util.RobustReflectionConverter$2.writeField(RobustReflectionConverter.java:167)
[JIRA] (JENKINS-11201) QC test report does not show up when Junit test is enabled
[ https://issues.jenkins-ci.org/browse/JENKINS-11201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Romain Seguy reassigned JENKINS-11201: -- Assignee: Daniel Petisme (was: Romain Seguy) QC test report does not show up when Junit test is enabled -- Key: JENKINS-11201 URL: https://issues.jenkins-ci.org/browse/JENKINS-11201 Project: Jenkins Issue Type: Bug Components: qc Reporter: Ever Tang Assignee: Daniel Petisme I have a project that has both Junit tests and QTP regression tests(configured through QC Plugin). If enable only one of these 2 test reports, the test result shows the trend report properly. However if both reports are enabled, Hudson(2.1.1) shows 2 identical trend reports reflecting only the Junit test result. The unit test reports are under /unittest-report/ folder and QC reports are under the workspace root. Both test report files contain correct data. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11085) QC test report is same as the Junit Test report(parsing the wrong file?)
[ https://issues.jenkins-ci.org/browse/JENKINS-11085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Romain Seguy reassigned JENKINS-11085: -- Assignee: Daniel Petisme (was: Romain Seguy) QC test report is same as the Junit Test report(parsing the wrong file?) Key: JENKINS-11085 URL: https://issues.jenkins-ci.org/browse/JENKINS-11085 Project: Jenkins Issue Type: Bug Components: qc Affects Versions: current Environment: Hudson 1.389 running on a Windows box, with QTP/QC client installed properly Reporter: Ever Tang Assignee: Daniel Petisme Attachments: TestResultGraph.JPG I have a project that has both unit tests and QTP regression tests(hooked up with QC Plugin). If I disable the Junit report in the Post Build step(Junit test is still enabled), and only enable QC report, Hudson shows the test result trend graph properly. For instance, I have 3 QTP regression tests and it shows correctly 2 success 1 failure etc. But if I enable the Junit Test Report in the Post Build steps, I will see 2 identical test result trend graphs both showing the Junit test results(~100 of them). The QC test result is no where to be found -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-10207) regex doesn't support multiple OR patern
[ https://issues.jenkins-ci.org/browse/JENKINS-10207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Romain Seguy reassigned JENKINS-10207: -- Assignee: Daniel Petisme (was: Romain Seguy) regex doesn't support multiple OR patern Key: JENKINS-10207 URL: https://issues.jenkins-ci.org/browse/JENKINS-10207 Project: Jenkins Issue Type: Bug Components: role-strategy Affects Versions: current Reporter: sorokh Assignee: Daniel Petisme I've been trying to set up a role with the following pattern: ACT-.*-(MR|CR|PROMOTE) Though correct as regex this seem not to work. The only workaround I found is limit the scoping to 2 choices i.e. ACT-.*-((MR|CR)|PROMOTE) This doesn't seem to be wanted behaviour ;-) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-10005) Unsorted output makes 'diff' dirty and difficult to read : Role Strategy Pluigin
[ https://issues.jenkins-ci.org/browse/JENKINS-10005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Romain Seguy reassigned JENKINS-10005: -- Assignee: Daniel Petisme (was: Romain Seguy) Unsorted output makes 'diff' dirty and difficult to read : Role Strategy Pluigin Key: JENKINS-10005 URL: https://issues.jenkins-ci.org/browse/JENKINS-10005 Project: Jenkins Issue Type: Improvement Components: role-strategy Environment: Jenkins 1.410, role-strategy 1.1 Reporter: Kuh Kro Assignee: Daniel Petisme Priority: Minor this plugin outputs data to config.xml without sorting elements, for example: * permissions/pemisson * assignedSIDs/sid Of course, this is no harm, but as a result, simple diff of config.xml (ex. jobConfigHistory plugin) becomes very dirty ... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-9979) copy files back to master aborts due to InterruptedException
[
https://issues.jenkins-ci.org/browse/JENKINS-9979?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Romain Seguy reassigned JENKINS-9979:
-
Assignee: Daniel Petisme (was: Romain Seguy)
copy files back to master aborts due to InterruptedException
Key: JENKINS-9979
URL: https://issues.jenkins-ci.org/browse/JENKINS-9979
Project: Jenkins
Issue Type: Bug
Components: copy-to-slave
Reporter: Gardner Bickford
Assignee: Daniel Petisme
Priority: Blocker
Attachments: copy-to-slave.hpi
On Jenkins *1.408* + Copy To Slave Plugin *1.3* + results/**:
{noformat}
17:17:11 BUILD SUCCESSFUL
17:17:11 Total time: 36 minutes 1 second
17:17:11 Recording test results
17:17:12 Email was triggered for: Success
17:17:12 Sending email for trigger: Success
17:17:12 Sending email to: gard...@invulnerable.org
17:17:12 ERROR: Publisher
com.michelin.cio.hudson.plugins.copytoslave.CopyToMasterNotifier aborted due
to exception
17:17:12 java.lang.InterruptedException
17:17:12 at java.lang.Object.wait(Native Method)
17:17:12 at hudson.remoting.Request.call(Request.java:122)
17:17:12 at hudson.remoting.Channel.call(Channel.java:643)
17:17:12 at hudson.EnvVars.getRemote(EnvVars.java:202)
17:17:12 at hudson.model.Computer.getEnvironment(Computer.java:796)
17:17:12 at hudson.model.Run.getEnvironment(Run.java:1766)
17:17:12 at
hudson.model.AbstractBuild.getEnvironment(AbstractBuild.java:732)
17:17:12 at
com.michelin.cio.hudson.plugins.copytoslave.CopyToMasterNotifier.perform(CopyToMasterNotifier.java:67)
17:17:12 at
hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:36)
17:17:12 at
hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:649)
17:17:12 at
hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:625)
17:17:12 at
hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:603)
17:17:12 at hudson.model.Build$RunnerImpl.cleanUp(Build.java:170)
17:17:12 at hudson.model.Run.run(Run.java:1405)
17:17:12 at hudson.matrix.MatrixRun.run(MatrixRun.java:137)
17:17:12 at
hudson.model.ResourceController.execute(ResourceController.java:88)
17:17:12 at hudson.model.Executor.run(Executor.java:145)
17:17:12 Finished: FAILURE
{noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-9073) Job systematic failuer when selecting Exclude element CHECKEDOUT from the UCM Baseline build parameter
[ https://issues.jenkins-ci.org/browse/JENKINS-9073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Romain Seguy reassigned JENKINS-9073: - Assignee: Daniel Petisme (was: Romain Seguy) Job systematic failuer when selecting Exclude element CHECKEDOUT from the UCM Baseline build parameter -- Key: JENKINS-9073 URL: https://issues.jenkins-ci.org/browse/JENKINS-9073 Project: Jenkins Issue Type: Bug Components: clearcase-ucm-baseline Environment: Hudson 1.393 clearcase 7.0.1.2 Reporter: jlpinardon Assignee: Daniel Petisme Priority: Critical When defining the UCM Baseline parameter, if the Exclude element CHECKEDOUT is checked, the job systematically fails when creating the view's config spec. The error message is : --- config spec start --- element /mts_tools/HudsonAdm/... B_HUDSONADM_V01_E24 -nocheckout element * /main/0 -ucm -nocheckout load /mts_tools/HudsonAdm/Controler --- config spec end --- [HUDSON_CTRL_B_HUDSONADM_V01_E24] $ /usr/atria/bin/cleartool setcs -tag HUDSON_CTRL_B_HUDSONADM_V01_E24 ../configspec50873.txt cleartool: Error: The first element rule of a snapshot view's config spec must be element * CHECKEDOUT. cleartool: Error: Config spec semantic processing failed. cleartool: Error: Unable to change configuration specification: error in configuration specification. FATAL: ClearCase UCM baseline failed. exit code=1 Note that it works correctly if the checkbox is not checked. But it means that we cannot ensure that checkedout versions are not loaded, which is a critical problem when building or testing stable configuration. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-9539) Quality Center Plugin Error: runTestSet.vbs(133, 5) Microsoft VBScript runtime error: ActiveX component can't create object: 'TDApiOle80.TDConnection'
[ https://issues.jenkins-ci.org/browse/JENKINS-9539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Romain Seguy reassigned JENKINS-9539: - Assignee: Daniel Petisme (was: Romain Seguy) Quality Center Plugin Error: runTestSet.vbs(133, 5) Microsoft VBScript runtime error: ActiveX component can't create object: 'TDApiOle80.TDConnection' -- Key: JENKINS-9539 URL: https://issues.jenkins-ci.org/browse/JENKINS-9539 Project: Jenkins Issue Type: Bug Components: qc Affects Versions: current Environment: Windows Vista Enterprise SP2 x64 Mozilla Firefox 4.0 Internet Explorer 8 Jenkins ver. 1.409 qc plugin 1.0 (script runTestSet.vbs used is version fixed in issue #9267) Reporter: Pablo García Assignee: Daniel Petisme Priority: Minor ERROR trying to create the object TDApiOle80.TDConnection in Class QCTestRunner. Sub Class_Initialize errors = 0 Set tdConnection = CreateObject(TDApiOle80.TDConnection) timestamp = CStr(Now) End Sub Error message reported is next: [TRUNK] $ cscript /nologo xxx\runTestSet.vbs http://xxx/qcbin pablo.garcia_hp.com xxx xxx xxx Test1 qcreport-Test1-7.xml xxx\runTestSet.vbs(133, 5) Microsoft VBScript runtime error: ActiveX component can't create object: 'TDApiOle80.TDConnection' Cant create TDConnection Object -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-8978) Image is missing on Manage Roles page.
[ https://issues.jenkins-ci.org/browse/JENKINS-8978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Romain Seguy reassigned JENKINS-8978: - Assignee: Daniel Petisme (was: Romain Seguy) Image is missing on Manage Roles page. -- Key: JENKINS-8978 URL: https://issues.jenkins-ci.org/browse/JENKINS-8978 Project: Jenkins Issue Type: Bug Components: role-strategy Affects Versions: current Reporter: Christian Höltje Assignee: Daniel Petisme Priority: Trivial I have renamed my jenkins.war file to automan.war and am reverse proxying through apache. So my URLs look like this: http://HOST/automan/... If you go to the Manage Roles screen, the image is missing. URL: http://HOST/automan/role-strategy/ The missing image's URL is: http://HOST/automansecure.gif I suspect it means to be: http://HOST/automan/static/832a5f9d/images/48x48/secure.gif -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-8075) Assign role interface does not scale to large number of users and roles
[ https://issues.jenkins-ci.org/browse/JENKINS-8075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Romain Seguy reassigned JENKINS-8075: - Assignee: Daniel Petisme (was: Romain Seguy) Assign role interface does not scale to large number of users and roles --- Key: JENKINS-8075 URL: https://issues.jenkins-ci.org/browse/JENKINS-8075 Project: Jenkins Issue Type: Improvement Components: role-strategy Environment: Hudson 1.381, Role based strategy 1.0 Reporter: Costin Caraivan Assignee: Daniel Petisme Priority: Minor Attachments: JENKINS-8075.png, roleassignment-mockup.png, roleassignment-original.png Hello, Our Hudson deployment has a lot of independent projects which need to have several roles assigned inside the team, some team members having more rights than others. The end result: lots of users, lots of projects x several roles per project = a huge bunch of roles. The number of users and roles will only increase - right now we are at about 50% of the final capacity. Trying to use the Role Based Strategy plugin, we noticed some scaling issues with the Assign roles page. See roleassignment-original.png attachment for the problems. Notice the scroll bars when having lots of users and roles. Having lots of users is ok, vertical scrolling is something common on webpages. However, having both vertical scrolling and horizontal scrolling is confusing. The Hudson row/column highlight is helpful, however the interface is still cumbersome. I would propose the following interface change for the assign roles page: - add a text box to each table row; preferably with role autocompletion, if possible - add a label with the list or roles for each user See the roleassignement-mockup.png attachment. Thank you for your help. I propose a different design for the page, to allow it to scale when having lots of users and roles -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-8346) Copy to slave incompatible with multi configuration project
[ https://issues.jenkins-ci.org/browse/JENKINS-8346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Romain Seguy reassigned JENKINS-8346: - Assignee: Daniel Petisme (was: Romain Seguy) Copy to slave incompatible with multi configuration project --- Key: JENKINS-8346 URL: https://issues.jenkins-ci.org/browse/JENKINS-8346 Project: Jenkins Issue Type: Bug Components: copy-to-slave Affects Versions: current Reporter: psoetens Assignee: Daniel Petisme copy-to-slave does nothing when the job runs on the master. This is the wrong behavior if the job is a multi-configuration project, because these jobs run with a modified workspace, depending on the parameter of the current job. What the plugin should do when the job is running on the master, is to check if the file in the 'default' workspace is identical to the target file (it won't be in a multi-config build) and if not, copy it to the new workspace. For example, the job on master has this workspace: $ pwd .../hudson/jobs/bootstrap-toolchain/workspace $ ls buildconf config-env.yml config.yml my-bootstrap.sh TARGET where TARGET is the first category for the parametrization. The job will never run in this 'workspace' dir, but somewhere deep in the TARGET subdir. So copy-to-slave should copy the file from this workspace into the deep 'multi-config' workspace. For example, when my job runs, these variables are set: JOB_NAME=bootstrap-toolchain/TARGET=gnulinux,arch=amd64,branch=master WORKSPACE=.../hudson/jobs/bootstrap-toolchain/workspace/TARGET/gnulinux/arch/amd64/branch/master I hope this report is clear about the issue. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-8015) Baseline GUI suggestion
[ https://issues.jenkins-ci.org/browse/JENKINS-8015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Romain Seguy reassigned JENKINS-8015: - Assignee: Daniel Petisme (was: Romain Seguy) Baseline GUI suggestion --- Key: JENKINS-8015 URL: https://issues.jenkins-ci.org/browse/JENKINS-8015 Project: Jenkins Issue Type: New Feature Components: clearcase-ucm-baseline Affects Versions: current Reporter: dennys_hsieh Assignee: Daniel Petisme Although this plugin can let users to choose a baseline to build, but it's not easy to know this version is built by what baseline. The only way I know is to see the log. The following are just some ideas 1. Put the baseline name in the description of a build, or just write baseline into description field. 2. When we create baseline in CC, we will write some description in CC. Is it possible to get it too and show in Hudson? Because baseline is generated by system, it's only some numbers and not easy to distinguish. 3. Show more information of baseline in build page (I mean this page http://wiki.jenkins-ci.org/download/attachments/37749162/changes.png) 4. Show baseline information in dashboard, not just show the build no. like #55 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12108) EnvInject failure using multi-configuration jobs
[ https://issues.jenkins-ci.org/browse/JENKINS-12108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159380#comment-159380 ] JavierB edited comment on JENKINS-12108 at 2/22/12 1:47 PM: Issue happens for latest versions [1.26|http://mirrors.jenkins-ci.org/plugins/envinject/1.26/] and [1.27|http://mirrors.jenkins-ci.org/plugins/envinject/1.27/] was (Author: javierb): Issue happens for version [1.26|http://mirrors.jenkins-ci.org/plugins/envinject/1.26/] EnvInject failure using multi-configuration jobs Key: JENKINS-12108 URL: https://issues.jenkins-ci.org/browse/JENKINS-12108 Project: Jenkins Issue Type: Bug Components: envinject Affects Versions: current Environment: Debian 5.0 Reporter: Thomas Wood Assignee: gbois Priority: Critical We recently upgraded to 1.424.1 LTS, and switched to the EnvInject plugin instead of the deprecated Hudson SetEnv plugin to set environment variables for our jobs. All our multi-configuration jobs are now failing: [EnvInject] - [ERROR] - [EnvInject] - [ERROR] - Problems occurs on injecting env vars as a build step: hudson.matrix.MatrixConfiguration cannot be cast to hudson.model.TopLevelItem This is easy to reproduce: - Install EnvInject - Create a new multiconfiguration job - Add an axis named axis with the values a b c - Add an execute shell build step consisting of echo $axis - Save and run the job (it should execute successfully against three configurations) - Now, edit the job and check Inject environment variables to the build process in the Build Environment section. You don't actually need to add any properties content to reproduce the problem--just check the checkbox. - Run the job again. All three configurations fail. This is a big problem for us as all our multi-configuration jobs also use environment variables. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-8013) Baseline listbox suggestion
[ https://issues.jenkins-ci.org/browse/JENKINS-8013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Romain Seguy reassigned JENKINS-8013: - Assignee: Daniel Petisme (was: Romain Seguy) Baseline listbox suggestion --- Key: JENKINS-8013 URL: https://issues.jenkins-ci.org/browse/JENKINS-8013 Project: Jenkins Issue Type: Improvement Components: clearcase-ucm-baseline Affects Versions: current Reporter: dennys_hsieh Assignee: Daniel Petisme Priority: Minor 1. Could you add the ability to configure the order of baseline? I.e. the put the newest baseline in the 1st item of the drop box. I think it's more convenient. 2. Is it possible to add a configuration to filter baseline? I.e. just show baseline create in 1 year or n months. I think old baseline is not necessary in most cases. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12855) Unnecessary character escapes in Groovy views script
emanuelez created JENKINS-12855: --- Summary: Unnecessary character escapes in Groovy views script Key: JENKINS-12855 URL: https://issues.jenkins-ci.org/browse/JENKINS-12855 Project: Jenkins Issue Type: Bug Components: core Affects Versions: current Reporter: emanuelez in a groovy view somthing like: script( for(i = 0; i 10; i++) ) will be converted to: for(i = 0; i lt; 10; i++) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12125) Push backups in remote git repository (or any other SCM)
[ https://issues.jenkins-ci.org/browse/JENKINS-12125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159384#comment-159384 ] Robert Kahlert commented on JENKINS-12125: -- I am with Samuel on this one. Just making the backup name editable, so that people can take out the $DATE part would be sufficient. I can check it into SVN myself, that's not the issue. Push backups in remote git repository (or any other SCM) Key: JENKINS-12125 URL: https://issues.jenkins-ci.org/browse/JENKINS-12125 Project: Jenkins Issue Type: New Feature Components: thinBackup Reporter: Samuel Stirtzel Assignee: Thomas Fürer Priority: Minor Hi, it would be nice if the backup could be pushed in a remote SCM (e.g. in my configuration: git). Summarized it could be done like this: * Check if the target directory is in a SCM (for git: check if .git directory is present) * Automatic backup * Stage the backup files and commit * Push to origin (the remote repository) Alternative to that, let the user run a shell script after backups. Edit: When stored in a SCM the naming scheme is disturbing, as the files should get overwritten each time a backup is running. So if thinBackup creates backups/FULL-2011-12-01_12-15/ and backups/FULL-2011-12-08_12-15/ it is not possible to directly put them in a SCM without moving files around or it will create duplicate content. -- Regards Samuel -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12079) Support master / slave usage
[ https://issues.jenkins-ci.org/browse/JENKINS-12079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159385#comment-159385 ] Thomas Fields commented on JENKINS-12079: - This doesn't seem to be an issue any more. I've updated to Jenkins 1.450, Locked file plugin 1.6 and tweaked a few project settings. I happy to say this is resolved for now and sorry to mess you around. Support master / slave usage Key: JENKINS-12079 URL: https://issues.jenkins-ci.org/browse/JENKINS-12079 Project: Jenkins Issue Type: Bug Components: locked-files-report Affects Versions: current Reporter: Thomas Fields Assignee: redsolo Hi, Does this plugin work in a master/slave setup? I've locked a file on my slave but the build doesn't tell me that the file is locked, instead it just says: 08:59:33 Building remotely on Build1 08:59:33 hudson.util.IOException2: remote file operation failed: c:\JCI\workspace\Expat\COMPILER at hudson.remoting.Channel@64368400:Build1 08:59:33 at hudson.FilePath.act(FilePath.java:781) 08:59:33 at hudson.FilePath.act(FilePath.java:767) If the plugin doesn't tell me about locked files on slaves can that functionality be added? Cheers, Tom. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-6747) Support concurrent runs of matrix builds
[ https://issues.jenkins-ci.org/browse/JENKINS-6747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159386#comment-159386 ] Sven Appenrodt commented on JENKINS-6747: - Indeed - the problem is not fixed at all. Running a multi-configuration task having 1 user defined axis with 2 values (e.g. job1 and job2) executing a permanent-ping to localhost will block the same, again started task. There are enough build slots available. For us it will save much time, because our builds currently starting two processes and each uses only a single CPU's on a I7-machine and we need to build two of them. That means - we have enough system resources (CPU-time and RAM) to start the second task parallel... Please, can you have a look at the problem? Thx Support concurrent runs of matrix builds Key: JENKINS-6747 URL: https://issues.jenkins-ci.org/browse/JENKINS-6747 Project: Jenkins Issue Type: Improvement Components: concurrent-build Reporter: Eric Smalling Assignee: Kohsuke Kawaguchi I'd like to be able to run matrix builds in parallel, currently that option doesn't appear in the configuration so I'm assuming it's not implemented yet. :) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12856) cobertua path confusion - base clearcase - shouldn't search /view/VIEW_TAG on unix - its just not sane
Greg Moncreaff created JENKINS-12856: Summary: cobertua path confusion - base clearcase - shouldn't search /view/VIEW_TAG on unix - its just not sane Key: JENKINS-12856 URL: https://issues.jenkins-ci.org/browse/JENKINS-12856 Project: Jenkins Issue Type: Bug Components: cobertura Affects Versions: current Environment: rhel 5.5 Reporter: Greg Moncreaff Assignee: stephenconnolly I have two jobs that attempt to publish cobertura xml (produced with gcov/gcovr on ada .gcda files) Job 1 works fine, its got a custom workspace (/view/foo/vobs/bar/scope) with no SCM. It looks for xml in workspace root (coverage.xml) Job 2 attempts to do the same thing (custom workspace still) with Base clearcase as SCM. When I didn't wildcard (**/coverage.xml), it couldn't find it. The help text indicates some malarkey about multiple SCM and module root not being workspace root. I'm not running multiple SCM. When I added the wild card, I got the following blow up, where it looks like its trying to look in .. and all that implies to find something! Which it should NEVER EVER do as both the custom workspace and the SCM load rules should would presumably bound where it searches. I don't know what it considers module root for Base clearcase, but it can NEVER EVER be /view/VIEW_TAG, since base clearcase (UNIX) links in all root filesystems into every view, hence you get never finishing searches or recursive link problems due to historical insanity. skipping symbolic link /view/foo/dev/.udev/silliness -- too many levels of symbolic links. Feb 22, 2012 4:33:32 PM hudson.model.AbstractBuild$AbstractRunner performAllBuildSteps WARNING: Publisher hudson.plugins.cobertura.CoberturaPublisher aborted due to exception Caught error while checking for symbolic links at org.apache.tools.ant.DirectoryScanner.causesIllegalSymlinkLoop(DirectoryScanner.java:1859) at org.apache.tools.ant.DirectoryScanner.scandir(DirectoryScanner.java:1240) at org.apache.tools.ant.DirectoryScanner.scandir(DirectoryScanner.java:1259) at org.apache.tools.ant.DirectoryScanner.scandir(DirectoryScanner.java:1259) at org.apache.tools.ant.DirectoryScanner.scandir(DirectoryScanner.java:1259) at org.apache.tools.ant.DirectoryScanner.scandir(DirectoryScanner.java:1259) at org.apache.tools.ant.DirectoryScanner.scandir(DirectoryScanner.java:1259) at org.apache.tools.ant.DirectoryScanner.scandir(DirectoryScanner.java:1259) at org.apache.tools.ant.DirectoryScanner.scandir(DirectoryScanner.java:1259) at org.apache.tools.ant.DirectoryScanner.scandir(DirectoryScanner.java:1259) at org.apache.tools.ant.DirectoryScanner.scandir(DirectoryScanner.java:1259) at org.apache.tools.ant.DirectoryScanner.scandir(DirectoryScanner.java:1259) at org.apache.tools.ant.DirectoryScanner.scandir(DirectoryScanner.java:1259) at org.apache.tools.ant.DirectoryScanner.scandir(DirectoryScanner.java:1259) at org.apache.tools.ant.DirectoryScanner.scandir(DirectoryScanner.java:1259) at org.apache.tools.ant.DirectoryScanner.scandir(DirectoryScanner.java:1259) at org.apache.tools.ant.DirectoryScanner.scandir(DirectoryScanner.java:1259) at org.apache.tools.ant.DirectoryScanner.scandir(DirectoryScanner.java:1259) at org.apache.tools.ant.DirectoryScanner.scandir(DirectoryScanner.java:1259) at org.apache.tools.ant.DirectoryScanner.scandir(DirectoryScanner.java:1259) at org.apache.tools.ant.DirectoryScanner.scandir(DirectoryScanner.java:1259) at org.apache.tools.ant.DirectoryScanner.scandir(DirectoryScanner.java:1259) at org.apache.tools.ant.DirectoryScanner.scandir(DirectoryScanner.java:1259) at org.apache.tools.ant.DirectoryScanner.scandir(DirectoryScanner.java:1259) at org.apache.tools.ant.DirectoryScanner.scandir(DirectoryScanner.java:1259) at org.apache.tools.ant.DirectoryScanner.scandir(DirectoryScanner.java:1259) at org.apache.tools.ant.DirectoryScanner.scandir(DirectoryScanner.java:1259) at org.apache.tools.ant.DirectoryScanner.scandir(DirectoryScanner.java:1184) at org.apache.tools.ant.DirectoryScanner.scandir(DirectoryScanner.java:1146) at org.apache.tools.ant.DirectoryScanner.checkIncludePatterns(DirectoryScanner.java:928) at org.apache.tools.ant.DirectoryScanner.scan(DirectoryScanner.java:882) at org.apache.tools.ant.types.AbstractFileSet.getDirectoryScanner(AbstractFileSet.java:490) at hudson.FilePath.glob(FilePath.java:1343) at hudson.FilePath.access$700(FilePath.java:164) at hudson.FilePath$24.invoke(FilePath.java:1322) at hudson.FilePath$24.invoke(FilePath.java:1320) at
[JIRA] (JENKINS-12857) cobertura - add option to make build as unstable (or not at all) instead of failed when no coverage xml files are found
Greg Moncreaff created JENKINS-12857: Summary: cobertura - add option to make build as unstable (or not at all) instead of failed when no coverage xml files are found Key: JENKINS-12857 URL: https://issues.jenkins-ci.org/browse/JENKINS-12857 Project: Jenkins Issue Type: Bug Components: cobertura Environment: rhel 5.5 Reporter: Greg Moncreaff Assignee: stephenconnolly To be more graceful, consider an configuration option so the build isn't automatically marked as failed if no coverage files are found. If you want visibility, you can always have some warning (exclamation point !) version of coverage icon on build landing page to say that 0 coverage files in anomalous situations. and in normal ones you could report how many coverage files you found? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12852) Automating the management of iOS provisioning profiles
[ https://issues.jenkins-ci.org/browse/JENKINS-12852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159388#comment-159388 ] lacostej commented on JENKINS-12852: Actually, I had some problems in get your ruby scripts to run. I don't use ruby, so I missed a lot of packages dependencies. That part I want to fix by making it a proper gem. That way it will be properly installed automatically. Also, it takes a bit of time to debug inside your bash script to understand why they didn't work. Yes. The script is tuned to my particular environment and clearly could fail in other environments. I am pretty new to iOS projects. Feel free to send your changes so that I can look at what you have done. About the API I was wondering if would be better to include everything in the same job so there is no need to look into the relative path to find the job that download the certificate (as you wrote in the tutorial). I am a bit against putting the 2 tasks in the same job for several reasons * things that don't need to be separate dont need to be merged in * if you have a build farm, multiple projects or multiple developers, you still only need to download Apple's information once. And by splitting the tasks, you don't need to share the credentials either * The part that is in batch today could definitively move into the plugin. The reason I used a batch script was 1. it was faster to implement 2. I needed to use it outside the CI server (on my developer box, I need to do the same things) Still could you share your changes to the xcode batch scripts so that we know how to best integrate this into the xcode plugin ? Automating the management of iOS provisioning profiles -- Key: JENKINS-12852 URL: https://issues.jenkins-ci.org/browse/JENKINS-12852 Project: Jenkins Issue Type: New Feature Components: xcode Reporter: Valerio Mazzeo Priority: Minor I was wondering if this is possible, and yesterday I bumped into this article: http://lacostej.blogspot.com/2012/02/automating-management-of-ios.html I have spent one day to make it work, but now is perfect! So, now could be really good to have this feature implemented into the plugin. Basically there are two steps: 1) download all the profile you need from the apple developer center 2) installing the new certificate into xcode and update the project file with the new one if just the second point is integrated into the plugin should be sufficient but if you can integrate all this process would be really amazing. I have already dealt with it, so I'm happy to answer your questions and doubt about it. What do you think guys? I think would be a very great feature! -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12821) android.device
[ https://issues.jenkins-ci.org/browse/JENKINS-12821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159389#comment-159389 ] Richard Mortimer commented on JENKINS-12821: Proof of concept fix committed to my personal github a-e-p fork. https://github.com/oldelvet/android-emulator-plugin/tree/jenkins-12821-poc I intend to implement the port allocator side of this in due course but have verified that the fix allows android.device=emulator to work with the proof of concept. android.device --- Key: JENKINS-12821 URL: https://issues.jenkins-ci.org/browse/JENKINS-12821 Project: Jenkins Issue Type: Bug Components: android-emulator Affects Versions: current Reporter: Sebastian Schefczyk Assignee: Richard Mortimer Priority: Minor The following configuration of the android-maven-plugin will not find the running emulator on Jenkins. Commenting this line will find the emulator. On my local machine this is working fine, but not in Jenkins. Both machines use maven 3.0.4 on Linux/Ubuntu. groupIdcom.jayway.maven.plugins.android.generation2/groupId artifactIdandroid-maven-plugin/artifactId configuration ... deviceemulator/device ... /configuration /plugin This configuration is useful on the local machine, if you are developing while charging your phone via USB. Best regards, that's a really nice plugin! Sebl29 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12616) Tests failes but the job is still OK
[ https://issues.jenkins-ci.org/browse/JENKINS-12616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Fürer updated JENKINS-12616: --- Priority: Minor (was: Blocker) setting threshold values solves the problem Tests failes but the job is still OK Key: JENKINS-12616 URL: https://issues.jenkins-ci.org/browse/JENKINS-12616 Project: Jenkins Issue Type: Bug Components: xunit Environment: jenkins 1.445 xunit 1.34 Ubuntu server 11.11 Reporter: Thomas Fürer Assignee: gbois Priority: Minor Attachments: boost-config.PNG, failedButOK.PNG, TEST-failed.xml just use the attached result file with BOOST the error is listed correct in the test report, but the job is still OK but need to be at least UNSTABLE. As you can see in the screenshot I do not have any thresholds set. I do not have any example at the moment, but I think we have this problem also with NUnit tests. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12858) With Maven3 when build fails does not show exceptions
Marco Tizzoni created JENKINS-12858: --- Summary: With Maven3 when build fails does not show exceptions Key: JENKINS-12858 URL: https://issues.jenkins-ci.org/browse/JENKINS-12858 Project: Jenkins Issue Type: Bug Components: console-column Affects Versions: current Environment: * Linux 2.6.18-238.1.1.el5xen #1 SMP Tue Jan 4 13:52:39 EST 2011 x86_64 x86_64 x86_64 GNU/Linux * java version 1.6.0_24 Java(TM) SE Runtime Environment (build 1.6.0_24-b07) Java HotSpot(TM) 64-Bit Server VM (build 19.1-b02, mixed mode) Reporter: Marco Tizzoni Assignee: jieryn Priority: Minor Console does not display the full stack trace when building using maven3 if the build fails. *** MAVEN 3 BUILD CONSOLE ON JENKINS *** [INFO] [INFO] Building ConnectionPool-sportello-jar 1.0.0 [INFO] [INFO] [INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @ ConnectionPool-sportello-jar --- [INFO] [INFO] --- maven-resources-plugin:2.4.3:resources (default-resources) @ ConnectionPool-sportello-jar --- [WARNING] Using platform encoding (UTF-8 actually) to copy filtered resources, i.e. build is platform dependent! [INFO] Copying 1 resource [INFO] [INFO] --- maven-compiler-plugin:2.0.2:compile (default-compile) @ ConnectionPool-sportello-jar --- [INFO] Compiling 5 source files to /var/lib/jenkins/workspace/sisi.dsvai.sportello.ConnectionPool-sportello/ConnectionPool-sportello-jar/target/classes [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 9.376s [INFO] Finished at: Wed Feb 22 19:05:08 CET 2012 [INFO] Final Memory: 7M/81M [INFO] mavenExecutionResult exceptions not empty message : Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:2.0.2:compile (default-compile) on project ConnectionPool-sportello-jar: Compilation failure cause : Compilation failure Stack trace : org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:2.0.2:compile (default-compile) on project ConnectionPool-sportello-jar: Compilation failure at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:213) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) [..] at java.lang.Thread.run(Thread.java:662) Caused by: org.apache.maven.plugin.CompilationFailureException: Compilation failure at org.apache.maven.plugin.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:516) at org.apache.maven.plugin.CompilerMojo.execute(CompilerMojo.java:114) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209) ... 27 more channel stopped Finished: FAILURE *** END MAVEN 3 BUILD CONSOLE ON JENKINS *** Real console output *** MAVEN 3 REAL OUTPUT *** [INFO] Finished at: Wed Feb 22 19:21:51 CET 2012 [INFO] Final Memory: 5M/88M [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:2.0.2:compile (default-compile) on project ConnectionPool-sportello-jar: Compilation failure: Compilation failure: [ERROR] /var/lib/jenkins/workspace/sisi.dsvai.sportello.ConnectionPool-sportello/ConnectionPool-sportello-jar/src/main/java/it/bankit/sportello/connectionPool/SockIOPool.java:[62,17] unmappable character for encoding UTF8 [ERROR] [ERROR] /var/lib/jenkins/workspace/sisi.dsvai.sportello.ConnectionPool-sportello/ConnectionPool-sportello-jar/src/main/java/it/bankit/sportello/connectionPool/SockIOPool.java:[68,56] unmappable character for encoding UTF8 [ERROR] [ERROR] /var/lib/jenkins/workspace/sisi.dsvai.sportello.ConnectionPool-sportello/ConnectionPool-sportello-jar/src/main/java/it/bankit/sportello/connectionPool/SockIOPool.java:[125,13] unmappable character for encoding UTF8 [ERROR] *** END MAVEN 2 SAMPLE OUTPUT *** Every line tagged with '[ERROR]' is not logged. Everything works using Maven2 that does not tag each line with '[ERROR]', probably a different output classification. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see:
[JIRA] (JENKINS-12858) With Maven3 when build fails does not show exceptions
[ https://issues.jenkins-ci.org/browse/JENKINS-12858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Tizzoni updated JENKINS-12858: Environment: - Linux 2.6.18-238.1.1.el5xen #1 SMP Tue Jan 4 13:52:39 EST 2011 x86_64 x86_64 x86_64 GNU/Linux - java version 1.6.0_24 Java(TM) SE Runtime Environment (build 1.6.0_24-b07) Java HotSpot(TM) 64-Bit Server VM (build 19.1-b02, mixed mode) was: * Linux 2.6.18-238.1.1.el5xen #1 SMP Tue Jan 4 13:52:39 EST 2011 x86_64 x86_64 x86_64 GNU/Linux * java version 1.6.0_24 Java(TM) SE Runtime Environment (build 1.6.0_24-b07) Java HotSpot(TM) 64-Bit Server VM (build 19.1-b02, mixed mode) Description: Console does not display the full stack trace when building using maven3 if the build fails. ### MAVEN 3 BUILD CONSOLE ON JENKINS ### [INFO] [INFO] Building ConnectionPool-sportello-jar 1.0.0 [INFO] [INFO] [INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @ ConnectionPool-sportello-jar --- [INFO] [INFO] --- maven-resources-plugin:2.4.3:resources (default-resources) @ ConnectionPool-sportello-jar --- [WARNING] Using platform encoding (UTF-8 actually) to copy filtered resources, i.e. build is platform dependent! [INFO] Copying 1 resource [INFO] [INFO] --- maven-compiler-plugin:2.0.2:compile (default-compile) @ ConnectionPool-sportello-jar --- [INFO] Compiling 5 source files to /var/lib/jenkins/workspace/sisi.dsvai.sportello.ConnectionPool-sportello/ConnectionPool-sportello-jar/target/classes [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 9.376s [INFO] Finished at: Wed Feb 22 19:05:08 CET 2012 [INFO] Final Memory: 7M/81M [INFO] mavenExecutionResult exceptions not empty message : Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:2.0.2:compile (default-compile) on project ConnectionPool-sportello-jar: Compilation failure cause : Compilation failure Stack trace : org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:2.0.2:compile (default-compile) on project ConnectionPool-sportello-jar: Compilation failure at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:213) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) [..] at java.lang.Thread.run(Thread.java:662) Caused by: org.apache.maven.plugin.CompilationFailureException: Compilation failure at org.apache.maven.plugin.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:516) at org.apache.maven.plugin.CompilerMojo.execute(CompilerMojo.java:114) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209) ... 27 more channel stopped Finished: FAILURE ### END MAVEN 3 BUILD CONSOLE ON JENKINS ### Real console output ### MAVEN 3 REAL OUTPUT ### [INFO] Finished at: Wed Feb 22 19:21:51 CET 2012 [INFO] Final Memory: 5M/88M [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:2.0.2:compile (default-compile) on project ConnectionPool-sportello-jar: Compilation failure: Compilation failure: [ERROR] /var/lib/jenkins/workspace/sisi.dsvai.sportello.ConnectionPool-sportello/ConnectionPool-sportello-jar/src/main/java/it/bankit/sportello/connectionPool/SockIOPool.java:[62,17] unmappable character for encoding UTF8 [ERROR] [ERROR] /var/lib/jenkins/workspace/sisi.dsvai.sportello.ConnectionPool-sportello/ConnectionPool-sportello-jar/src/main/java/it/bankit/sportello/connectionPool/SockIOPool.java:[68,56] unmappable character for encoding UTF8 [ERROR] [ERROR] /var/lib/jenkins/workspace/sisi.dsvai.sportello.ConnectionPool-sportello/ConnectionPool-sportello-jar/src/main/java/it/bankit/sportello/connectionPool/SockIOPool.java:[125,13] unmappable character for encoding UTF8 [ERROR] ### END MAVEN 2 SAMPLE OUTPUT ### Every line tagged with '[ERROR]' is not logged. Everything works using Maven2 that does not tag each line with '[ERROR]', probably a different output classification. was: Console does not display the full stack trace when building using maven3 if the build fails. *** MAVEN 3 BUILD CONSOLE ON JENKINS *** [INFO] [INFO] Building
[JIRA] (JENKINS-12858) With Maven3 when build fails does not show exceptions
[
https://issues.jenkins-ci.org/browse/JENKINS-12858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marco Tizzoni updated JENKINS-12858:
Description:
Console does not display the full stack trace when building using maven3 if the
build fails.
{quote}
*** MAVEN 3 BUILD CONSOLE ON JENKINS ***
[INFO]
[INFO] Building ConnectionPool-sportello-jar 1.0.0
[INFO]
[INFO]
[INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @
ConnectionPool-sportello-jar ---
[INFO]
[INFO] --- maven-resources-plugin:2.4.3:resources (default-resources) @
ConnectionPool-sportello-jar ---
[WARNING] Using platform encoding (UTF-8 actually) to copy filtered resources,
i.e. build is platform dependent!
[INFO] Copying 1 resource
[INFO]
[INFO] --- maven-compiler-plugin:2.0.2:compile (default-compile) @
ConnectionPool-sportello-jar ---
[INFO] Compiling 5 source files to
/var/lib/jenkins/workspace/sisi.dsvai.sportello.ConnectionPool-sportello/ConnectionPool-sportello-jar/target/classes
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 9.376s
[INFO] Finished at: Wed Feb 22 19:05:08 CET 2012
[INFO] Final Memory: 7M/81M
[INFO]
mavenExecutionResult exceptions not empty
message : Failed to execute goal
org.apache.maven.plugins:maven-compiler-plugin:2.0.2:compile (default-compile)
on project ConnectionPool-sportello-jar: Compilation failure
cause : Compilation failure
Stack trace :
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal
org.apache.maven.plugins:maven-compiler-plugin:2.0.2:compile (default-compile)
on project ConnectionPool-sportello-jar: Compilation failure
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:213)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
[..]
at java.lang.Thread.run(Thread.java:662)
Caused by: org.apache.maven.plugin.CompilationFailureException: Compilation
failure
at
org.apache.maven.plugin.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:516)
at org.apache.maven.plugin.CompilerMojo.execute(CompilerMojo.java:114)
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
... 27 more
channel stopped
Finished: FAILURE
*** END MAVEN 3 BUILD CONSOLE ON JENKINS ***
{quote}
Real console output
{quote}
*** MAVEN 3 REAL OUTPUT ***
[INFO] Finished at: Wed Feb 22 19:21:51 CET 2012
[INFO] Final Memory: 5M/88M
[INFO]
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-compiler-plugin:2.0.2:compile (default-compile)
on project ConnectionPool-sportello-jar: Compilation failure: Compilation
failure:
[ERROR]
/var/lib/jenkins/workspace/sisi.dsvai.sportello.ConnectionPool-sportello/ConnectionPool-sportello-jar/src/main/java/it/bankit/sportello/connectionPool/SockIOPool.java:[62,17]
unmappable character for encoding UTF8
[ERROR]
[ERROR]
/var/lib/jenkins/workspace/sisi.dsvai.sportello.ConnectionPool-sportello/ConnectionPool-sportello-jar/src/main/java/it/bankit/sportello/connectionPool/SockIOPool.java:[68,56]
unmappable character for encoding UTF8
[ERROR]
[ERROR]
/var/lib/jenkins/workspace/sisi.dsvai.sportello.ConnectionPool-sportello/ConnectionPool-sportello-jar/src/main/java/it/bankit/sportello/connectionPool/SockIOPool.java:[125,13]
unmappable character for encoding UTF8
[ERROR]
*** END MAVEN 2 SAMPLE OUTPUT ***
{quote}
Every line tagged with '[ERROR]' is not logged.
Everything works using Maven2 that does not tag each line with '[ERROR]',
probably a different output classification.
was:
Console does not display the full stack trace when building using maven3 if the
build fails.
{{
*** MAVEN 3 BUILD CONSOLE ON JENKINS ***
[INFO]
[INFO] Building ConnectionPool-sportello-jar 1.0.0
[INFO]
[INFO]
[INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @
ConnectionPool-sportello-jar ---
[INFO]
[INFO] --- maven-resources-plugin:2.4.3:resources (default-resources) @
ConnectionPool-sportello-jar ---
[WARNING] Using platform encoding (UTF-8 actually) to copy filtered resources,
i.e. build is platform dependent!
[INFO] Copying 1 resource
[INFO]
[INFO] ---
[JIRA] (JENKINS-12858) With Maven3 when build fails does not show exceptions
[
https://issues.jenkins-ci.org/browse/JENKINS-12858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marco Tizzoni updated JENKINS-12858:
Description:
Console does not display the full stack trace when building using maven3 if the
build fails.
{{
*** MAVEN 3 BUILD CONSOLE ON JENKINS ***
[INFO]
[INFO] Building ConnectionPool-sportello-jar 1.0.0
[INFO]
[INFO]
[INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @
ConnectionPool-sportello-jar ---
[INFO]
[INFO] --- maven-resources-plugin:2.4.3:resources (default-resources) @
ConnectionPool-sportello-jar ---
[WARNING] Using platform encoding (UTF-8 actually) to copy filtered resources,
i.e. build is platform dependent!
[INFO] Copying 1 resource
[INFO]
[INFO] --- maven-compiler-plugin:2.0.2:compile (default-compile) @
ConnectionPool-sportello-jar ---
[INFO] Compiling 5 source files to
/var/lib/jenkins/workspace/sisi.dsvai.sportello.ConnectionPool-sportello/ConnectionPool-sportello-jar/target/classes
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 9.376s
[INFO] Finished at: Wed Feb 22 19:05:08 CET 2012
[INFO] Final Memory: 7M/81M
[INFO]
mavenExecutionResult exceptions not empty
message : Failed to execute goal
org.apache.maven.plugins:maven-compiler-plugin:2.0.2:compile (default-compile)
on project ConnectionPool-sportello-jar: Compilation failure
cause : Compilation failure
Stack trace :
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal
org.apache.maven.plugins:maven-compiler-plugin:2.0.2:compile (default-compile)
on project ConnectionPool-sportello-jar: Compilation failure
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:213)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
[..]
at java.lang.Thread.run(Thread.java:662)
Caused by: org.apache.maven.plugin.CompilationFailureException: Compilation
failure
at
org.apache.maven.plugin.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:516)
at org.apache.maven.plugin.CompilerMojo.execute(CompilerMojo.java:114)
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
... 27 more
channel stopped
Finished: FAILURE
*** END MAVEN 3 BUILD CONSOLE ON JENKINS ***
}
Real console output
{
*** MAVEN 3 REAL OUTPUT ***
[INFO] Finished at: Wed Feb 22 19:21:51 CET 2012
[INFO] Final Memory: 5M/88M
[INFO]
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-compiler-plugin:2.0.2:compile (default-compile)
on project ConnectionPool-sportello-jar: Compilation failure: Compilation
failure:
[ERROR]
/var/lib/jenkins/workspace/sisi.dsvai.sportello.ConnectionPool-sportello/ConnectionPool-sportello-jar/src/main/java/it/bankit/sportello/connectionPool/SockIOPool.java:[62,17]
unmappable character for encoding UTF8
[ERROR]
[ERROR]
/var/lib/jenkins/workspace/sisi.dsvai.sportello.ConnectionPool-sportello/ConnectionPool-sportello-jar/src/main/java/it/bankit/sportello/connectionPool/SockIOPool.java:[68,56]
unmappable character for encoding UTF8
[ERROR]
[ERROR]
/var/lib/jenkins/workspace/sisi.dsvai.sportello.ConnectionPool-sportello/ConnectionPool-sportello-jar/src/main/java/it/bankit/sportello/connectionPool/SockIOPool.java:[125,13]
unmappable character for encoding UTF8
[ERROR]
*** END MAVEN 2 SAMPLE OUTPUT *** }}
Every line tagged with '[ERROR]' is not logged.
Everything works using Maven2 that does not tag each line with '[ERROR]',
probably a different output classification.
was:
Console does not display the full stack trace when building using maven3 if the
build fails.
### MAVEN 3 BUILD CONSOLE ON JENKINS ###
[INFO]
[INFO] Building ConnectionPool-sportello-jar 1.0.0
[INFO]
[INFO]
[INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @
ConnectionPool-sportello-jar ---
[INFO]
[INFO] --- maven-resources-plugin:2.4.3:resources (default-resources) @
ConnectionPool-sportello-jar ---
[WARNING] Using platform encoding (UTF-8 actually) to copy filtered resources,
i.e. build is platform dependent!
[INFO] Copying 1 resource
[INFO]
[INFO] ---
[JIRA] (JENKINS-12858) With Maven3 when build fails does not show exceptions
[
https://issues.jenkins-ci.org/browse/JENKINS-12858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marco Tizzoni updated JENKINS-12858:
Description:
Console does not display the full stack trace when building using maven3 if the
build fails.
{code:title=MAVEN 3 BUILD CONSOLE ON JENKINS|borderStyle=solid}
[INFO]
[INFO] Building ConnectionPool-sportello-jar 1.0.0
[INFO]
[INFO]
[INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @
ConnectionPool-sportello-jar ---
[INFO]
[INFO] --- maven-resources-plugin:2.4.3:resources (default-resources) @
ConnectionPool-sportello-jar ---
[WARNING] Using platform encoding (UTF-8 actually) to copy filtered resources,
i.e. build is platform dependent!
[INFO] Copying 1 resource
[INFO]
[INFO] --- maven-compiler-plugin:2.0.2:compile (default-compile) @
ConnectionPool-sportello-jar ---
[INFO] Compiling 5 source files to
/var/lib/jenkins/workspace/sisi.dsvai.sportello.ConnectionPool-sportello/ConnectionPool-sportello-jar/target/classes
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 9.376s
[INFO] Finished at: Wed Feb 22 19:05:08 CET 2012
[INFO] Final Memory: 7M/81M
[INFO]
mavenExecutionResult exceptions not empty
message : Failed to execute goal
org.apache.maven.plugins:maven-compiler-plugin:2.0.2:compile (default-compile)
on project ConnectionPool-sportello-jar: Compilation failure
cause : Compilation failure
Stack trace :
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal
org.apache.maven.plugins:maven-compiler-plugin:2.0.2:compile (default-compile)
on project ConnectionPool-sportello-jar: Compilation failure
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:213)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
[..]
at java.lang.Thread.run(Thread.java:662)
Caused by: org.apache.maven.plugin.CompilationFailureException: Compilation
failure
at
org.apache.maven.plugin.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:516)
at org.apache.maven.plugin.CompilerMojo.execute(CompilerMojo.java:114)
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
... 27 more
channel stopped
Finished: FAILURE
*** END MAVEN 3 BUILD CONSOLE ON JENKINS ***
{code}
Real console output
{code:title=MAVEN 3 REAL OUTPUT|borderStyle=solid}
[INFO] Finished at: Wed Feb 22 19:21:51 CET 2012
[INFO] Final Memory: 5M/88M
[INFO]
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-compiler-plugin:2.0.2:compile (default-compile)
on project ConnectionPool-sportello-jar: Compilation failure: Compilation
failure:
[ERROR]
/var/lib/jenkins/workspace/sisi.dsvai.sportello.ConnectionPool-sportello/ConnectionPool-sportello-jar/src/main/java/it/bankit/sportello/connectionPool/SockIOPool.java:[62,17]
unmappable character for encoding UTF8
[ERROR]
[ERROR]
/var/lib/jenkins/workspace/sisi.dsvai.sportello.ConnectionPool-sportello/ConnectionPool-sportello-jar/src/main/java/it/bankit/sportello/connectionPool/SockIOPool.java:[68,56]
unmappable character for encoding UTF8
[ERROR]
[ERROR]
/var/lib/jenkins/workspace/sisi.dsvai.sportello.ConnectionPool-sportello/ConnectionPool-sportello-jar/src/main/java/it/bankit/sportello/connectionPool/SockIOPool.java:[125,13]
unmappable character for encoding UTF8
[ERROR]
*** END MAVEN 2 SAMPLE OUTPUT ***
{code}
Every line tagged with '[ERROR]' is not logged.
Everything works using Maven2 that does not tag each line with '[ERROR]',
probably a different output classification.
was:
Console does not display the full stack trace when building using maven3 if the
build fails.
{code:title=MAVEN 3 BUILD CONSOLE ON JENKINS|borderStyle=solid}
[INFO]
[INFO] Building ConnectionPool-sportello-jar 1.0.0
[INFO]
[INFO]
[INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @
ConnectionPool-sportello-jar ---
[INFO]
[INFO] --- maven-resources-plugin:2.4.3:resources (default-resources) @
ConnectionPool-sportello-jar ---
[WARNING] Using platform encoding (UTF-8 actually) to copy filtered resources,
i.e. build is platform
[JIRA] (JENKINS-12858) With Maven3 when build fails does not show exceptions
[
https://issues.jenkins-ci.org/browse/JENKINS-12858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marco Tizzoni updated JENKINS-12858:
Description:
Console does not display the full stack trace when building using maven3 if the
build fails.
{code:title=MAVEN 3 BUILD CONSOLE ON JENKINS|borderStyle=solid}
[INFO]
[INFO] Building ConnectionPool-sportello-jar 1.0.0
[INFO]
[INFO]
[INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @
ConnectionPool-sportello-jar ---
[INFO]
[INFO] --- maven-resources-plugin:2.4.3:resources (default-resources) @
ConnectionPool-sportello-jar ---
[WARNING] Using platform encoding (UTF-8 actually) to copy filtered resources,
i.e. build is platform dependent!
[INFO] Copying 1 resource
[INFO]
[INFO] --- maven-compiler-plugin:2.0.2:compile (default-compile) @
ConnectionPool-sportello-jar ---
[INFO] Compiling 5 source files to
/var/lib/jenkins/workspace/sisi.dsvai.sportello.ConnectionPool-sportello/ConnectionPool-sportello-jar/target/classes
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 9.376s
[INFO] Finished at: Wed Feb 22 19:05:08 CET 2012
[INFO] Final Memory: 7M/81M
[INFO]
mavenExecutionResult exceptions not empty
message : Failed to execute goal
org.apache.maven.plugins:maven-compiler-plugin:2.0.2:compile (default-compile)
on project ConnectionPool-sportello-jar: Compilation failure
cause : Compilation failure
Stack trace :
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal
org.apache.maven.plugins:maven-compiler-plugin:2.0.2:compile (default-compile)
on project ConnectionPool-sportello-jar: Compilation failure
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:213)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
[..]
at java.lang.Thread.run(Thread.java:662)
Caused by: org.apache.maven.plugin.CompilationFailureException: Compilation
failure
at
org.apache.maven.plugin.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:516)
at org.apache.maven.plugin.CompilerMojo.execute(CompilerMojo.java:114)
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
... 27 more
channel stopped
Finished: FAILURE
*** END MAVEN 3 BUILD CONSOLE ON JENKINS ***
{code}
Real console output
{quote}
*** MAVEN 3 REAL OUTPUT ***
[INFO] Finished at: Wed Feb 22 19:21:51 CET 2012
[INFO] Final Memory: 5M/88M
[INFO]
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-compiler-plugin:2.0.2:compile (default-compile)
on project ConnectionPool-sportello-jar: Compilation failure: Compilation
failure:
[ERROR]
/var/lib/jenkins/workspace/sisi.dsvai.sportello.ConnectionPool-sportello/ConnectionPool-sportello-jar/src/main/java/it/bankit/sportello/connectionPool/SockIOPool.java:[62,17]
unmappable character for encoding UTF8
[ERROR]
[ERROR]
/var/lib/jenkins/workspace/sisi.dsvai.sportello.ConnectionPool-sportello/ConnectionPool-sportello-jar/src/main/java/it/bankit/sportello/connectionPool/SockIOPool.java:[68,56]
unmappable character for encoding UTF8
[ERROR]
[ERROR]
/var/lib/jenkins/workspace/sisi.dsvai.sportello.ConnectionPool-sportello/ConnectionPool-sportello-jar/src/main/java/it/bankit/sportello/connectionPool/SockIOPool.java:[125,13]
unmappable character for encoding UTF8
[ERROR]
*** END MAVEN 2 SAMPLE OUTPUT ***
{quote}
Every line tagged with '[ERROR]' is not logged.
Everything works using Maven2 that does not tag each line with '[ERROR]',
probably a different output classification.
was:
Console does not display the full stack trace when building using maven3 if the
build fails.
{quote}
*** MAVEN 3 BUILD CONSOLE ON JENKINS ***
[INFO]
[INFO] Building ConnectionPool-sportello-jar 1.0.0
[INFO]
[INFO]
[INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @
ConnectionPool-sportello-jar ---
[INFO]
[INFO] --- maven-resources-plugin:2.4.3:resources (default-resources) @
ConnectionPool-sportello-jar ---
[WARNING] Using platform encoding (UTF-8 actually) to copy filtered resources,
i.e. build is platform dependent!
[INFO] Copying 1 resource
[JIRA] (JENKINS-12852) Automating the management of iOS provisioning profiles
[ https://issues.jenkins-ci.org/browse/JENKINS-12852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159392#comment-159392 ] Valerio Mazzeo commented on JENKINS-12852: -- I haven't changed you script, as I wrote: In the end I realise that if you setup the project to code-sign with the automatic certificate selector, then inside the project file the PROVISIONING_PROFILE field is empty. This cause the script to fail, once I realised that I was able to fix it. The fix is to setup the project to a specified provisioning profile. This make sense because if it is automatic I think there is no way to know which one you want to use. ps: I need to run your script on my developer machine too :( Automating the management of iOS provisioning profiles -- Key: JENKINS-12852 URL: https://issues.jenkins-ci.org/browse/JENKINS-12852 Project: Jenkins Issue Type: New Feature Components: xcode Reporter: Valerio Mazzeo Priority: Minor I was wondering if this is possible, and yesterday I bumped into this article: http://lacostej.blogspot.com/2012/02/automating-management-of-ios.html I have spent one day to make it work, but now is perfect! So, now could be really good to have this feature implemented into the plugin. Basically there are two steps: 1) download all the profile you need from the apple developer center 2) installing the new certificate into xcode and update the project file with the new one if just the second point is integrated into the plugin should be sufficient but if you can integrate all this process would be really amazing. I have already dealt with it, so I'm happy to answer your questions and doubt about it. What do you think guys? I think would be a very great feature! -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11953) EC2 plugin needs to load regions dynamically (or add Oregon region to list)
[ https://issues.jenkins-ci.org/browse/JENKINS-11953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159394#comment-159394 ] SCM/JIRA link daemon commented on JENKINS-11953: Code changed in jenkins User: Francis Upton IV Path: src/main/java/hudson/plugins/ec2/AmazonEC2Cloud.java src/main/java/hudson/plugins/ec2/AwsRegion.java src/main/java/hudson/plugins/ec2/EC2Cloud.java src/main/java/hudson/plugins/ec2/EC2Computer.java src/main/java/hudson/plugins/ec2/EC2Slave.java src/main/java/hudson/plugins/ec2/PluginImpl.java src/main/java/hudson/plugins/ec2/SlaveTemplate.java src/main/resources/hudson/plugins/ec2/AmazonEC2Cloud/config-entries.jelly src/main/resources/hudson/plugins/ec2/EC2Computer/configure.jelly src/main/resources/hudson/plugins/ec2/EC2Slave/help-zone.html src/main/resources/hudson/plugins/ec2/Messages.properties src/main/resources/hudson/plugins/ec2/SlaveTemplate/config.jelly src/test/java/hudson/plugins/ec2/AmazonEC2CloudTest.java src/test/java/hudson/plugins/ec2/SlaveTemplateTest.java src/test/java/hudson/plugins/ec2/TemplateLabelsTest.java http://jenkins-ci.org/commit/ec2-plugin/f0e542fa9b2c6e4f112294b92145afd4e04eadd9 Log: [FIXED JENKINS-8946] Option to set Zone as well as region for instance creation [FIXED JENKINS-11953] Dynamically local AWS regions Compare: https://github.com/jenkinsci/ec2-plugin/compare/19c419b...f0e542f EC2 plugin needs to load regions dynamically (or add Oregon region to list) --- Key: JENKINS-11953 URL: https://issues.jenkins-ci.org/browse/JENKINS-11953 Project: Jenkins Issue Type: Bug Components: ec2 Environment: Win/Linux Reporter: Ruben Orduz Assignee: Frank Bille EC2 plug-in seems to have regions hard coded. As more regions are added, these will have to be added to the list. Instead, it should retrieve all available regions through one API call, that way there would be no list to maintain. The problem code can be seen here: https://github.com/jenkinsci/ec2-plugin/blob/master/src/main/java/hudson/plugins/ec2/AwsRegion.java (lines 19-23). It should get all that info with the API calls, not through hard-coded enum kind of thing. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-8946) Option to set Zone as well as region for instance creation
[ https://issues.jenkins-ci.org/browse/JENKINS-8946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] francis Upton resolved JENKINS-8946. Resolution: Fixed Option to set Zone as well as region for instance creation -- Key: JENKINS-8946 URL: https://issues.jenkins-ci.org/browse/JENKINS-8946 Project: Jenkins Issue Type: New Feature Components: ec2 Reporter: william selwood Assignee: francis Upton Instances in the same zone have much better performance when communicating between each other. It would be useful to be able to set the zone you wish an instance to start in as well as the region. At least they end up on the right side of the world at the moment but same server farm would be even more useful. region: eu-west zone: eu-west-1b for instance -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-8946) Option to set Zone as well as region for instance creation
[ https://issues.jenkins-ci.org/browse/JENKINS-8946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159393#comment-159393 ] SCM/JIRA link daemon commented on JENKINS-8946: --- Code changed in jenkins User: Francis Upton IV Path: src/main/java/hudson/plugins/ec2/AmazonEC2Cloud.java src/main/java/hudson/plugins/ec2/AwsRegion.java src/main/java/hudson/plugins/ec2/EC2Cloud.java src/main/java/hudson/plugins/ec2/EC2Computer.java src/main/java/hudson/plugins/ec2/EC2Slave.java src/main/java/hudson/plugins/ec2/PluginImpl.java src/main/java/hudson/plugins/ec2/SlaveTemplate.java src/main/resources/hudson/plugins/ec2/AmazonEC2Cloud/config-entries.jelly src/main/resources/hudson/plugins/ec2/EC2Computer/configure.jelly src/main/resources/hudson/plugins/ec2/EC2Slave/help-zone.html src/main/resources/hudson/plugins/ec2/Messages.properties src/main/resources/hudson/plugins/ec2/SlaveTemplate/config.jelly src/test/java/hudson/plugins/ec2/AmazonEC2CloudTest.java src/test/java/hudson/plugins/ec2/SlaveTemplateTest.java src/test/java/hudson/plugins/ec2/TemplateLabelsTest.java http://jenkins-ci.org/commit/ec2-plugin/f0e542fa9b2c6e4f112294b92145afd4e04eadd9 Log: [FIXED JENKINS-8946] Option to set Zone as well as region for instance creation [FIXED JENKINS-11953] Dynamically local AWS regions Compare: https://github.com/jenkinsci/ec2-plugin/compare/19c419b...f0e542f Option to set Zone as well as region for instance creation -- Key: JENKINS-8946 URL: https://issues.jenkins-ci.org/browse/JENKINS-8946 Project: Jenkins Issue Type: New Feature Components: ec2 Reporter: william selwood Assignee: francis Upton Instances in the same zone have much better performance when communicating between each other. It would be useful to be able to set the zone you wish an instance to start in as well as the region. At least they end up on the right side of the world at the moment but same server farm would be even more useful. region: eu-west zone: eu-west-1b for instance -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11953) EC2 plugin needs to load regions dynamically (or add Oregon region to list)
[ https://issues.jenkins-ci.org/browse/JENKINS-11953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] francis Upton resolved JENKINS-11953. - Assignee: francis Upton (was: Frank Bille) Resolution: Fixed Fixed in 1.15 EC2 plugin needs to load regions dynamically (or add Oregon region to list) --- Key: JENKINS-11953 URL: https://issues.jenkins-ci.org/browse/JENKINS-11953 Project: Jenkins Issue Type: Bug Components: ec2 Environment: Win/Linux Reporter: Ruben Orduz Assignee: francis Upton EC2 plug-in seems to have regions hard coded. As more regions are added, these will have to be added to the list. Instead, it should retrieve all available regions through one API call, that way there would be no list to maintain. The problem code can be seen here: https://github.com/jenkinsci/ec2-plugin/blob/master/src/main/java/hudson/plugins/ec2/AwsRegion.java (lines 19-23). It should get all that info with the API calls, not through hard-coded enum kind of thing. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-8946) Option to set Zone as well as region for instance creation
[ https://issues.jenkins-ci.org/browse/JENKINS-8946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159397#comment-159397 ] dogfood commented on JENKINS-8946: -- Integrated in !http://ci.jenkins-ci.org/images/16x16/blue.png! [plugins_ec2 #60|http://ci.jenkins-ci.org/job/plugins_ec2/60/] [FIXED JENKINS-8946] Option to set Zone as well as region for instance creation [FIXED JENKINS-11953] Dynamically local AWS regions (Revision f0e542fa9b2c6e4f112294b92145afd4e04eadd9) Result = SUCCESS francis : Files : * src/main/java/hudson/plugins/ec2/AmazonEC2Cloud.java * src/main/java/hudson/plugins/ec2/EC2Slave.java * src/test/java/hudson/plugins/ec2/SlaveTemplateTest.java * src/main/java/hudson/plugins/ec2/SlaveTemplate.java * src/main/resources/hudson/plugins/ec2/EC2Slave/help-zone.html * src/main/resources/hudson/plugins/ec2/AmazonEC2Cloud/config-entries.jelly * src/main/java/hudson/plugins/ec2/AwsRegion.java * src/main/resources/hudson/plugins/ec2/SlaveTemplate/config.jelly * src/main/java/hudson/plugins/ec2/EC2Computer.java * src/main/resources/hudson/plugins/ec2/Messages.properties * src/test/java/hudson/plugins/ec2/TemplateLabelsTest.java * src/main/resources/hudson/plugins/ec2/EC2Computer/configure.jelly * src/test/java/hudson/plugins/ec2/AmazonEC2CloudTest.java * src/main/java/hudson/plugins/ec2/EC2Cloud.java * src/main/java/hudson/plugins/ec2/PluginImpl.java Option to set Zone as well as region for instance creation -- Key: JENKINS-8946 URL: https://issues.jenkins-ci.org/browse/JENKINS-8946 Project: Jenkins Issue Type: New Feature Components: ec2 Reporter: william selwood Assignee: francis Upton Instances in the same zone have much better performance when communicating between each other. It would be useful to be able to set the zone you wish an instance to start in as well as the region. At least they end up on the right side of the world at the moment but same server farm would be even more useful. region: eu-west zone: eu-west-1b for instance -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11953) EC2 plugin needs to load regions dynamically (or add Oregon region to list)
[ https://issues.jenkins-ci.org/browse/JENKINS-11953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159396#comment-159396 ] dogfood commented on JENKINS-11953: --- Integrated in !http://ci.jenkins-ci.org/images/16x16/blue.png! [plugins_ec2 #60|http://ci.jenkins-ci.org/job/plugins_ec2/60/] [FIXED JENKINS-8946] Option to set Zone as well as region for instance creation [FIXED JENKINS-11953] Dynamically local AWS regions (Revision f0e542fa9b2c6e4f112294b92145afd4e04eadd9) Result = SUCCESS francis : Files : * src/main/java/hudson/plugins/ec2/AmazonEC2Cloud.java * src/main/java/hudson/plugins/ec2/EC2Slave.java * src/test/java/hudson/plugins/ec2/SlaveTemplateTest.java * src/main/java/hudson/plugins/ec2/SlaveTemplate.java * src/main/resources/hudson/plugins/ec2/EC2Slave/help-zone.html * src/main/resources/hudson/plugins/ec2/AmazonEC2Cloud/config-entries.jelly * src/main/java/hudson/plugins/ec2/AwsRegion.java * src/main/resources/hudson/plugins/ec2/SlaveTemplate/config.jelly * src/main/java/hudson/plugins/ec2/EC2Computer.java * src/main/resources/hudson/plugins/ec2/Messages.properties * src/test/java/hudson/plugins/ec2/TemplateLabelsTest.java * src/main/resources/hudson/plugins/ec2/EC2Computer/configure.jelly * src/test/java/hudson/plugins/ec2/AmazonEC2CloudTest.java * src/main/java/hudson/plugins/ec2/EC2Cloud.java * src/main/java/hudson/plugins/ec2/PluginImpl.java EC2 plugin needs to load regions dynamically (or add Oregon region to list) --- Key: JENKINS-11953 URL: https://issues.jenkins-ci.org/browse/JENKINS-11953 Project: Jenkins Issue Type: Bug Components: ec2 Environment: Win/Linux Reporter: Ruben Orduz Assignee: francis Upton EC2 plug-in seems to have regions hard coded. As more regions are added, these will have to be added to the list. Instead, it should retrieve all available regions through one API call, that way there would be no list to maintain. The problem code can be seen here: https://github.com/jenkinsci/ec2-plugin/blob/master/src/main/java/hudson/plugins/ec2/AwsRegion.java (lines 19-23). It should get all that info with the API calls, not through hard-coded enum kind of thing. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-5309) Customise user who connects to EC2 instance
[ https://issues.jenkins-ci.org/browse/JENKINS-5309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] francis Upton resolved JENKINS-5309. Assignee: francis Upton (was: Kohsuke Kawaguchi) Resolution: Duplicate Dup of JENKINS-5867 Customise user who connects to EC2 instance --- Key: JENKINS-5309 URL: https://issues.jenkins-ci.org/browse/JENKINS-5309 Project: Jenkins Issue Type: New Feature Components: ec2 Affects Versions: current Environment: Ubuntu Reporter: jamtur01 Assignee: francis Upton Newer Ubuntu releases don't allow the root user to connect - this means can't start instances with the plug-in which defaults to the root user. Can you add a field to each instance definition that allows you to customise the connecting user perhaps? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-6539) EC2 plugin does not respect remote-user parameter
[ https://issues.jenkins-ci.org/browse/JENKINS-6539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] francis Upton resolved JENKINS-6539. Assignee: francis Upton Resolution: Duplicate Dup of JENKINS-5867 EC2 plugin does not respect remote-user parameter - Key: JENKINS-6539 URL: https://issues.jenkins-ci.org/browse/JENKINS-6539 Project: Jenkins Issue Type: Bug Components: ec2 Environment: hudson 1.358, ec2-plugin 1.8 Reporter: Charles Lowell Assignee: francis Upton Using the official ubuntu EC2 images for both lucid and karmic, and a simple build script that just runs whoami the output is always 'root' no matter what the remote-user setting is configured for on the AMI -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12141) Allow connecting to an instance using an IP address instead of the domain name
[ https://issues.jenkins-ci.org/browse/JENKINS-12141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] francis Upton updated JENKINS-12141: Issue Type: New Feature (was: Bug) Allow connecting to an instance using an IP address instead of the domain name -- Key: JENKINS-12141 URL: https://issues.jenkins-ci.org/browse/JENKINS-12141 Project: Jenkins Issue Type: New Feature Components: ec2 Affects Versions: current Environment: local eucalyptus Reporter: my sql Assignee: Kohsuke Kawaguchi C:\ssh euca-10-135-236-221.eucalyptus.beclos60.china.nsn-net.net ssh: Could not resolve hostname euca-10-135-236-221.eucalyptus.beclos60.china.nsn-net.net: hostname nor servname I tested the EC2 plugin in my local eucalyptus server, hostname can't find due to ip 10.135.236.221 can't get by DNS automatically. Could you private a way to ssh connect by ip than full public domain DNS? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11105) Pipeline view's retry is broken on parametized jobs since it doesn't reuse the arguments
[ https://issues.jenkins-ci.org/browse/JENKINS-11105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159400#comment-159400 ] Devin Barbieri commented on JENKINS-11105: -- There is a thread going on about this here: http://code.google.com/p/build-pipeline-plugin/issues/detail?can=2start=0num=100q=colspec=ID%20Type%20Status%20Priority%20Milestone%20Owner%20Summarygroupby=sort=id=75 I posted that you had a fix for this Pipeline view's retry is broken on parametized jobs since it doesn't reuse the arguments Key: JENKINS-11105 URL: https://issues.jenkins-ci.org/browse/JENKINS-11105 Project: Jenkins Issue Type: Bug Components: plugin Reporter: Devin Barbieri The retry button in the Pipeline view should reuse the arguments of that specific job run, instead it uses default values. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12860) klocwork should use analysis core so it can be rolled up with its own type by static analysis portlets
Greg Moncreaff created JENKINS-12860: Summary: klocwork should use analysis core so it can be rolled up with its own type by static analysis portlets Key: JENKINS-12860 URL: https://issues.jenkins-ci.org/browse/JENKINS-12860 Project: Jenkins Issue Type: Improvement Components: analysis-core, klocwork Environment: rhel 5.5 Reporter: Greg Moncreaff Assignee: Ulli Hafner klocwork should use analysis core so it can be rolled up with its own type by static analysis portlets -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12861) klocwork - update to recognize 9.5.x xml schema
Greg Moncreaff created JENKINS-12861:
Summary: klocwork - update to recognize 9.5.x xml schema
Key: JENKINS-12861
URL: https://issues.jenkins-ci.org/browse/JENKINS-12861
Project: Jenkins
Issue Type: Improvement
Components: klocwork
Affects Versions: current
Environment: rhel 5.5
Reporter: Greg Moncreaff
Assignee: gbois
schema changed. current plugin can digest
errorList version=9.2.2
...
citingStatusAnalyze/citingStatusstateExisting/stateseverityError/severityseveritylevel3/severityleveldisplayAsError/displayAsdateOriginated1327694645000/dateOriginated
but new owner field appears in 9.5
errorList version=9.5.2
citingStatusAnalyze/citingStatusstateNew/stateownerunowned/ownerseverityCritical/severityseveritylevel1/severityleveldisplayAsError/displayAs
that causes publisher to be less than graceful:
22:08:53 Processing 2 files with the pattern 'kw*.xml'.
22:08:53 Parsing has been canceled. XML Validation failed. See errors below :
22:08:53 At line 47 of
file:/view/mafi_int_kw/vobs/csci33/csc11/kw.xml:cvc-complex-type.2.4.a: Invalid
content was found starting with element 'owner'. One of
'{http://www.klocwork.com/inForce/report/1.0:severity,
http://www.klocwork.com/inForce/report/1.0:severitylevel,
http://www.klocwork.com/inForce/report/1.0:displayAs,
http://www.klocwork.com/inForce/report/1.0:dateOriginated,
http://www.klocwork.com/inForce/report/1.0:url,
http://www.klocwork.com/inForce/report/1.0:comment,
http://www.klocwork.com/inForce/report/1.0:history,
http://www.klocwork.com/inForce/report/1.0:lastCommitter,
http://www.klocwork.com/inForce/report/1.0:dateFixed,
http://www.klocwork.com/inForce/report/1.0:category,
http://www.klocwork.com/inForce/report/1.0:lastCommit}' is expected.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12841) EnvInject Plugin 1.26 does not substitute ${WORKSPACE} correctly
[
https://issues.jenkins-ci.org/browse/JENKINS-12841?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159401#comment-159401
]
SCM/JIRA link daemon commented on JENKINS-12841:
Code changed in jenkins
User: Gregory Boissinot
Path:
src/main/java/org/jenkinsci/plugins/envinject/EnvInjectListener.java
src/main/java/org/jenkinsci/plugins/envinject/service/EnvInjectVariableGetter.java
http://jenkins-ci.org/commit/envinject-plugin/b2c132e077b2bb052df175660a8906533d681d37
Log:
Fix JENKINS-12704 and JENKINS-12841
Compare: https://github.com/jenkinsci/envinject-plugin/compare/6ff47b2...b2c132e
EnvInject Plugin 1.26 does not substitute ${WORKSPACE} correctly
Key: JENKINS-12841
URL: https://issues.jenkins-ci.org/browse/JENKINS-12841
Project: Jenkins
Issue Type: Bug
Components: envinject
Reporter: mwebber
Assignee: gbois
Priority: Critical
Attachments: config.xml
This problem appeared when I upgraded the EnvInject Plugin from 1.25 to 1.26,
so the problem was probably introduced with the fix for JENKINS-12704.
I have a job with Inject environment variables to the build process
selected, and the following line in Properties Content:
materialize_workspace_path=${WORKSPACE}/materialize_workspace
In 1.25, this environment variable was correctly given the value
{{/scratch/jenkins_workspace/GDA_master.tests.RH5_64/materialize_workspace}}
In 1.26, this environment variable was WRONGLY given the value
{{/scratch/jenkins_slave//scratch/jenkins_workspace/GDA_master.tests.RH5_64/materialize_workspace}}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12108) EnvInject failure using multi-configuration jobs
[ https://issues.jenkins-ci.org/browse/JENKINS-12108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] gbois resolved JENKINS-12108. - Resolution: Fixed EnvInject failure using multi-configuration jobs Key: JENKINS-12108 URL: https://issues.jenkins-ci.org/browse/JENKINS-12108 Project: Jenkins Issue Type: Bug Components: envinject Affects Versions: current Environment: Debian 5.0 Reporter: Thomas Wood Assignee: gbois Priority: Critical We recently upgraded to 1.424.1 LTS, and switched to the EnvInject plugin instead of the deprecated Hudson SetEnv plugin to set environment variables for our jobs. All our multi-configuration jobs are now failing: [EnvInject] - [ERROR] - [EnvInject] - [ERROR] - Problems occurs on injecting env vars as a build step: hudson.matrix.MatrixConfiguration cannot be cast to hudson.model.TopLevelItem This is easy to reproduce: - Install EnvInject - Create a new multiconfiguration job - Add an axis named axis with the values a b c - Add an execute shell build step consisting of echo $axis - Save and run the job (it should execute successfully against three configurations) - Now, edit the job and check Inject environment variables to the build process in the Build Environment section. You don't actually need to add any properties content to reproduce the problem--just check the checkbox. - Run the job again. All three configurations fail. This is a big problem for us as all our multi-configuration jobs also use environment variables. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12862) CVS confused about what to checkout and where to checkout to
nhnb created JENKINS-12862: -- Summary: CVS confused about what to checkout and where to checkout to Key: JENKINS-12862 URL: https://issues.jenkins-ci.org/browse/JENKINS-12862 Project: Jenkins Issue Type: Bug Components: cvs Affects Versions: current Reporter: nhnb Priority: Critical The recent CVS plugin is confused about what to checkout and where: CVSROOT: :pserver:anonym...@arianne.cvs.sourceforge.net:/cvsroot/arianne Remote Name: stendhal This configuration used to work in the past. But now it does a checkout of every module in the CVS-repository and it places this checkout above the workspace folder. As a result, the CVS changes are invisible because the last checkout below the workspace folder remains unchanged. Using different configurations of the Localname (empty or non empty) and Legacy Mode checkbox may result in only the right module to be checked out, but not into the workspace folder but a subfolder with the module name below the workspace folder. Again, this will result in the checkout being mostly invisible because an outdated version remains at the correct location. Furthermore deselecting the legacy mode checkbox is ignored. After saving the form and reopening the configuration form, the checkbox is selected again. It is possible to deselect it directly in config.xml, but this just causes the CVS plugin to again do a checkout of all modules to the parent folder of workspace. I tried several combinations of the configuration settings but I am still unable to find a workaround for this issue. Out jenkins server is publically available at http://stendhalgame.org/jenkins/job/stendhal_HEAD -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12616) Tests failes but the job is still OK
[ https://issues.jenkins-ci.org/browse/JENKINS-12616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] gbois closed JENKINS-12616. --- Resolution: Won't Fix Giving default values for threshold is difficult: failed test or skipped test; unstable or fail. The response depends on the context. My choice: if no values are set, no threshold is processed. Tests failes but the job is still OK Key: JENKINS-12616 URL: https://issues.jenkins-ci.org/browse/JENKINS-12616 Project: Jenkins Issue Type: Bug Components: xunit Environment: jenkins 1.445 xunit 1.34 Ubuntu server 11.11 Reporter: Thomas Fürer Assignee: gbois Priority: Minor Attachments: boost-config.PNG, failedButOK.PNG, TEST-failed.xml just use the attached result file with BOOST the error is listed correct in the test report, but the job is still OK but need to be at least UNSTABLE. As you can see in the screenshot I do not have any thresholds set. I do not have any example at the moment, but I think we have this problem also with NUnit tests. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12863) dashboard - jobs list portlet - add summary statistics
Greg Moncreaff created JENKINS-12863: Summary: dashboard - jobs list portlet - add summary statistics Key: JENKINS-12863 URL: https://issues.jenkins-ci.org/browse/JENKINS-12863 Project: Jenkins Issue Type: Improvement Components: dashboard-view Affects Versions: current Environment: rhel 5.5 Reporter: Greg Moncreaff Assignee: Peter Hayes Priority: Minor for the job list, you could add a row at bottom with information like - last success/failure - average age - last duration - total time to re-run all jobs, average time of a job -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12860) klocwork should use analysis core so it can be rolled up with its own type by static analysis portlets
[ https://issues.jenkins-ci.org/browse/JENKINS-12860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ulli Hafner reassigned JENKINS-12860: - Assignee: gbois (was: Ulli Hafner) How is the current implememtation working? Is this a text or xml file that is parsed and then gets visualized? A simple solution would be to just implement a parser for the warnings plugin. Of course using analysis-core would work, too. What do you think? klocwork should use analysis core so it can be rolled up with its own type by static analysis portlets -- Key: JENKINS-12860 URL: https://issues.jenkins-ci.org/browse/JENKINS-12860 Project: Jenkins Issue Type: Improvement Components: analysis-core, klocwork Environment: rhel 5.5 Reporter: Greg Moncreaff Assignee: gbois klocwork should use analysis core so it can be rolled up with its own type by static analysis portlets -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-8946) Option to set Zone as well as region for instance creation
[ https://issues.jenkins-ci.org/browse/JENKINS-8946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159405#comment-159405 ] SCM/JIRA link daemon commented on JENKINS-8946: --- Code changed in jenkins User: Francis Upton IV Path: src/main/java/hudson/plugins/ec2/EC2Slave.java src/main/java/hudson/plugins/ec2/SlaveTemplate.java src/main/resources/hudson/plugins/ec2/EC2Computer/configure.jelly http://jenkins-ci.org/commit/ec2-plugin/9e89c6c1914253693be02f5feb3f1e9228863a71 Log: [FIXED JENKINS-8946] Option to set Zone as well as region for instance creation (removed zone from slave instance) Option to set Zone as well as region for instance creation -- Key: JENKINS-8946 URL: https://issues.jenkins-ci.org/browse/JENKINS-8946 Project: Jenkins Issue Type: New Feature Components: ec2 Reporter: william selwood Assignee: francis Upton Instances in the same zone have much better performance when communicating between each other. It would be useful to be able to set the zone you wish an instance to start in as well as the region. At least they end up on the right side of the world at the moment but same server farm would be even more useful. region: eu-west zone: eu-west-1b for instance -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12864) NullPointerException in winstone Launcher
Thomas Andresen created JENKINS-12864: - Summary: NullPointerException in winstone Launcher Key: JENKINS-12864 URL: https://issues.jenkins-ci.org/browse/JENKINS-12864 Project: Jenkins Issue Type: Bug Components: core Environment: Debian 6.0 Jenkins v. 1.451 (installed using apt-get) RAM: 512 MB java version 1.6.0_18 OpenJDK Runtime Environment (IcedTea6 1.8.10) (6b18-1.8.10-0+squeeze2) OpenJDK 64-Bit Server VM (build 14.0-b16, mixed mode) Reporter: Thomas Andresen Priority: Blocker After a few seconds after sending the start request to Jenkins. In my log file: Running from: /usr/share/jenkins/jenkins.war Feb 22, 2012 10:32:47 PM winstone.Logger logInternal SEVERE: Container startup failed java.lang.NullPointerException at winstone.Launcher.shutdown(Launcher.java:333) at winstone.Launcher.init(Launcher.java:199) at winstone.Launcher.main(Launcher.java:384) 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:616) at Main._main(Main.java:273) at Main.main(Main.java:98) I have tried to make a fresh install of Jenkins, but with same result. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12832) check XSLT is not good enough
[ https://issues.jenkins-ci.org/browse/JENKINS-12832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159406#comment-159406 ] SCM/JIRA link daemon commented on JENKINS-12832: Code changed in jenkins User: Gregory Boissinot Path: src/main/resources/org/jenkinsci/plugins/xunit/types/check-to-junit-4.xsl src/test/resources/org/jenkinsci/plugins/xunit/types/check/testcase1/result.xml src/test/resources/org/jenkinsci/plugins/xunit/types/check/testcase2/result.xml http://jenkins-ci.org/commit/xunit-plugin/75e70d75927da29a54b36c23a13116c356752abc Log: Fix JENKINS-12832 check XSLT is not good enough - Key: JENKINS-12832 URL: https://issues.jenkins-ci.org/browse/JENKINS-12832 Project: Jenkins Issue Type: Improvement Components: xunit Affects Versions: current Reporter: Michael van der Westhuizen Assignee: gbois Labels: plugin Attachments: check-to-junit-4.xsl The recently added check transform is really insufficient and misses a lot of cases. I've rewritten the XSLT and integrated it into our build using the custom tool support (which works extremely well!). I've attached the revised XSLT for possible integration into the tree. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-8946) Option to set Zone as well as region for instance creation
[ https://issues.jenkins-ci.org/browse/JENKINS-8946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159409#comment-159409 ] dogfood commented on JENKINS-8946: -- Integrated in !http://ci.jenkins-ci.org/images/16x16/blue.png! [plugins_ec2 #61|http://ci.jenkins-ci.org/job/plugins_ec2/61/] [FIXED JENKINS-8946] Option to set Zone as well as region for instance creation (removed zone from slave instance) (Revision 9e89c6c1914253693be02f5feb3f1e9228863a71) Result = SUCCESS francis : Files : * src/main/resources/hudson/plugins/ec2/EC2Computer/configure.jelly * src/main/java/hudson/plugins/ec2/EC2Slave.java * src/main/java/hudson/plugins/ec2/SlaveTemplate.java Option to set Zone as well as region for instance creation -- Key: JENKINS-8946 URL: https://issues.jenkins-ci.org/browse/JENKINS-8946 Project: Jenkins Issue Type: New Feature Components: ec2 Reporter: william selwood Assignee: francis Upton Instances in the same zone have much better performance when communicating between each other. It would be useful to be able to set the zone you wish an instance to start in as well as the region. At least they end up on the right side of the world at the moment but same server farm would be even more useful. region: eu-west zone: eu-west-1b for instance -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12865) [ERROR] - SEVERE - Polling error Current Project is null from FSTrigger
Brad Huggins created JENKINS-12865: -- Summary: [ERROR] - SEVERE - Polling error Current Project is null from FSTrigger Key: JENKINS-12865 URL: https://issues.jenkins-ci.org/browse/JENKINS-12865 Project: Jenkins Issue Type: Bug Components: fstrigger Affects Versions: current Environment: Linux master (console only no jobs process on it) and a Windows slave Reporter: Brad Huggins Assignee: gbois Priority: Blocker Attachments: Output-IUS.xml I receive the following error when FSTrigger attempts to poll: [FSTrigger] - Monitor files Polling for the job Output-ICA Polling remotely on * Polling started on Feb 22, 2012 5:58:09 PM [ERROR] - SEVERE - Polling error Current Project is null I have attached the configuration file though I scrubbed the server name from it. I have tried using \ or / even no path with the same error. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12772) Allow instances to be stopped (instead of terminated) when they are not required
[ https://issues.jenkins-ci.org/browse/JENKINS-12772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] francis Upton resolved JENKINS-12772. - Resolution: Fixed Allow instances to be stopped (instead of terminated) when they are not required Key: JENKINS-12772 URL: https://issues.jenkins-ci.org/browse/JENKINS-12772 Project: Jenkins Issue Type: Improvement Components: ec2 Reporter: francis Upton Assignee: francis Upton This is necessary to easily allow EBS volumes to be maintained with the instance. It's much more difficult (impossible?) to configure EBS volumes to be properly saved and remounted if the instances are terminated each time. When the instance is stopped, no charges are accruing, so it's often a better solution. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12772) Allow instances to be stopped (instead of terminated) when they are not required
[ https://issues.jenkins-ci.org/browse/JENKINS-12772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159410#comment-159410 ] SCM/JIRA link daemon commented on JENKINS-12772: Code changed in jenkins User: Francis Upton IV Path: src/main/java/hudson/plugins/ec2/EC2Slave.java src/main/java/hudson/plugins/ec2/SlaveTemplate.java src/main/resources/hudson/plugins/ec2/EC2Computer/configure.jelly src/main/resources/hudson/plugins/ec2/SlaveTemplate/config.jelly src/test/java/hudson/plugins/ec2/SlaveTemplateTest.java src/test/java/hudson/plugins/ec2/TemplateLabelsTest.java http://jenkins-ci.org/commit/ec2-plugin/a2739cd93cfdf518dfff795e16da9e121a5bdcd1 Log: [FIXED JENKINS-12772] Allow instances to be stopped (instead of terminated) when they are not required Allow instances to be stopped (instead of terminated) when they are not required Key: JENKINS-12772 URL: https://issues.jenkins-ci.org/browse/JENKINS-12772 Project: Jenkins Issue Type: Improvement Components: ec2 Reporter: francis Upton Assignee: francis Upton This is necessary to easily allow EBS volumes to be maintained with the instance. It's much more difficult (impossible?) to configure EBS volumes to be properly saved and remounted if the instances are terminated each time. When the instance is stopped, no charges are accruing, so it's often a better solution. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12772) Allow instances to be stopped (instead of terminated) when they are not required
[ https://issues.jenkins-ci.org/browse/JENKINS-12772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159411#comment-159411 ] dogfood commented on JENKINS-12772: --- Integrated in !http://ci.jenkins-ci.org/images/16x16/blue.png! [plugins_ec2 #62|http://ci.jenkins-ci.org/job/plugins_ec2/62/] [FIXED JENKINS-12772] Allow instances to be stopped (instead of terminated) when they are not required (Revision a2739cd93cfdf518dfff795e16da9e121a5bdcd1) Result = SUCCESS francis : Files : * src/main/java/hudson/plugins/ec2/EC2Slave.java * src/main/resources/hudson/plugins/ec2/SlaveTemplate/config.jelly * src/test/java/hudson/plugins/ec2/TemplateLabelsTest.java * src/main/resources/hudson/plugins/ec2/EC2Computer/configure.jelly * src/main/java/hudson/plugins/ec2/SlaveTemplate.java * src/test/java/hudson/plugins/ec2/SlaveTemplateTest.java Allow instances to be stopped (instead of terminated) when they are not required Key: JENKINS-12772 URL: https://issues.jenkins-ci.org/browse/JENKINS-12772 Project: Jenkins Issue Type: Improvement Components: ec2 Reporter: francis Upton Assignee: francis Upton This is necessary to easily allow EBS volumes to be maintained with the instance. It's much more difficult (impossible?) to configure EBS volumes to be properly saved and remounted if the instances are terminated each time. When the instance is stopped, no charges are accruing, so it's often a better solution. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12866) Unable to connect to jenkins slave running on ARM platform
Eric Huang created JENKINS-12866: Summary: Unable to connect to jenkins slave running on ARM platform Key: JENKINS-12866 URL: https://issues.jenkins-ci.org/browse/JENKINS-12866 Project: Jenkins Issue Type: Bug Components: slave-setup Environment: pandaboard, ARM platform Reporter: Eric Huang Assignee: Kohsuke Kawaguchi I am trying to setup a jenkins slave that is running on a pandaboard. I have Ubuntu 11.10 oneiric installed, and I am using OpenJDK Runtime Environment (IcedTea6 1.11pre). I am getting a Invalid encoded sequence encountered error when attempting to connect to the slave via ssh: [02/22/12 16:45:41] [SSH] Opening SSH connection to panda-devboard:22. 6:45:47] [SSH] Authentication successful. [02/22/12 16:45:47] [SSH] The remote users environment is: BASH=/bin/bash BASHOPTS=cmdhist:extquote:force_fignore:hostcomplete:interactive_comments:progcomp:promptvars:sourcepath BASH_ALIASES=() BASH_ARGC=() BASH_ARGV=() BASH_CMDS=() BASH_EXECUTION_STRING=set BASH_LINENO=() BASH_SOURCE=() BASH_VERSINFO=([0]=4 [1]=2 [2]=10 [3]=1 [4]=release [5]=arm-unknown-linux-gnueabi) BASH_VERSION='4.2.10(1)-release' DIRSTACK=() EUID=4086 GROUPS=() HOME=/home/release HOSTNAME=panda-devboard HOSTTYPE=arm IFS=$' \t\n' LANG=en_CA.UTF-8 LOGNAME=release MACHTYPE=arm-unknown-linux-gnueabi MAIL=/var/mail/release OPTERR=1 OPTIND=1 OSTYPE=linux-gnueabi PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games PIPESTATUS=([0]=0) PPID=10358 PS4='+ ' PWD=/home/release SHELL=/bin/bash SHELLOPTS=braceexpand:hashall:interactive-comments SHLVL=1 SSH_CLIENT='10.1.0.195 4050 22' SSH_CONNECTION='10.1.0.195 4050 10.1.124.85 22' TERM=dumb UID=4086 USER=release XDG_SESSION_COOKIE=5c9ceadb707acb8eae13745b0009-1329957946.802516-2119305671 _=']' [02/22/12 16:45:47] [SSH] Checking java version of java [02/22/12 16:45:48] [SSH] java -version returned 1.6.0_23. [02/22/12 16:45:48] [SSH] Starting sftp client. [02/22/12 16:45:48] [SSH] Copying latest slave.jar... [02/22/12 16:45:48] [SSH] Copied 257,564 bytes. [02/22/12 16:45:48] [SSH] Starting slave process: cd '/var/hudson' java -jar slave.jar -text Running in text mode ===[JENKINS REMOTING CAPACITY]==[HUDSON TRANSMISSION BEGINS]===channel started Slave.jar version: 2.12 This is a Unix slave Copied maven-agent.jar Copied maven3-agent.jar Copied maven3-interceptor.jar Copied maven-interceptor.jar Copied maven2.1-interceptor.jar Copied plexus-classworld.jar Copied classworlds.jar Slave successfully connected and online [02/22/12 16:45:54] [SSH] Opening SSH connection to panda-devboard:22. ERROR: Connection terminated java.io.IOException: Invalid encoded sequence encountered: 6A 6D 6D 5F 19 EB 4C 7A 6A 2B C9 4B 1A at hudson.remoting.BinarySafeStream$1._read(BinarySafeStream.java:194) at hudson.remoting.BinarySafeStream$1.read(BinarySafeStream.java:80) at java.io.ObjectInputStream$PeekInputStream.peek(Unknown Source) at java.io.ObjectInputStream$BlockDataInputStream.peek(Unknown Source) at java.io.ObjectInputStream$BlockDataInputStream.peekByte(Unknown Source) at java.io.ObjectInputStream.readObject0(Unknown Source) at java.io.ObjectInputStream.readObject(Unknown Source) at hudson.remoting.Channel$ReaderThread.run(Channel.java:1127) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12867) jenkins does not start in jboss container
Terry Sposato created JENKINS-12867: --- Summary: jenkins does not start in jboss container Key: JENKINS-12867 URL: https://issues.jenkins-ci.org/browse/JENKINS-12867 Project: Jenkins Issue Type: Bug Components: jboss Affects Versions: current Environment: Redhat 6.1 x64 - JBoss 5.1 EAP Reporter: Terry Sposato Assignee: JulB4 Priority: Blocker The current version of Jenkins does not deploy correctly with JBoss 5.1 EAP. Here is the server log: 2012-02-23 12:12:12,088 INFO [org.jboss.bootstrap.microcontainer.ServerImpl] (main) JBoss (Microcontainer) [5.1.0 (build: SVNTag=JBPAPP_5_1_0 date=201009150028)] Started in 36s:389ms 2012-02-23 12:12:13,332 INFO [jenkins.InitReactorRunner] (pool-14-thread-2) Started initialization 2012-02-23 12:12:18,744 INFO [jenkins.InitReactorRunner] (pool-14-thread-4) Listed all plugins 2012-02-23 12:12:21,125 INFO [jenkins.InitReactorRunner] (pool-14-thread-2) Prepared all plugins 2012-02-23 12:12:28,295 ERROR [STDERR] (Initializing plugin copyartifact) SLF4J: slf4j-api 1.6.x (or later) is incompatible with this binding. 2012-02-23 12:12:28,295 ERROR [STDERR] (Initializing plugin copyartifact) SLF4J: Your binding is version 1.5.5 or earlier. 2012-02-23 12:12:28,295 ERROR [STDERR] (Initializing plugin copyartifact) SLF4J: Upgrade your binding to version 1.6.x. or 2.0.x 2012-02-23 12:12:28,301 WARNING [hudson.ExtensionFinder$GuiceFinder] (Initializing plugin copyartifact) Failed to instantiate. Skipping this component com.google.inject.ProvisionException: Guice provision errors: 1) Error injecting constructor, java.lang.NoSuchMethodError: org.slf4j.impl.StaticLoggerBinder.getSingleton()Lorg/slf4j/impl/StaticLoggerBinder; at org.jenkinsci.main.modules.sshd.SSHD.init(SSHD.java:40) 1 error at com.google.inject.internal.ProviderToInternalFactoryAdapter.get(ProviderToInternalFactoryAdapter.java:52) at com.google.inject.Scopes$1$1.get(Scopes.java:59) at hudson.ExtensionFinder$AbstractGuiceFinder$2$1.get(ExtensionFinder.java:365) at com.google.inject.internal.InternalFactoryToProviderAdapter.get(InternalFactoryToProviderAdapter.java:41) at com.google.inject.internal.SingleFieldInjector.inject(SingleFieldInjector.java:54) at com.google.inject.internal.MembersInjectorImpl.injectMembers(MembersInjectorImpl.java:118) at com.google.inject.internal.ConstructorInjector.provision(ConstructorInjector.java:117) at com.google.inject.internal.ConstructorInjector.construct(ConstructorInjector.java:87) at com.google.inject.internal.ConstructorBindingImpl$Factory.get(ConstructorBindingImpl.java:259) at com.google.inject.internal.ProviderToInternalFactoryAdapter$1.call(ProviderToInternalFactoryAdapter.java:46) at com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1018) at com.google.inject.internal.ProviderToInternalFactoryAdapter.get(ProviderToInternalFactoryAdapter.java:40) at com.google.inject.Scopes$1$1.get(Scopes.java:59) at hudson.ExtensionFinder$AbstractGuiceFinder$2$1.get(ExtensionFinder.java:365) at com.google.inject.internal.InternalFactoryToProviderAdapter.get(InternalFactoryToProviderAdapter.java:41) at com.google.inject.internal.InjectorImpl$3$1.call(InjectorImpl.java:965) at com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1011) at com.google.inject.internal.InjectorImpl$3.get(InjectorImpl.java:961) at hudson.ExtensionFinder$AbstractGuiceFinder._find(ExtensionFinder.java:336) at hudson.ExtensionFinder$AbstractGuiceFinder.find(ExtensionFinder.java:327) at hudson.ExtensionFinder._find(ExtensionFinder.java:147) at hudson.ClassicPluginStrategy.findComponents(ClassicPluginStrategy.java:289) at hudson.ExtensionList.load(ExtensionList.java:278) at hudson.ExtensionList.ensureLoaded(ExtensionList.java:231) at hudson.ExtensionList.iterator(ExtensionList.java:138) at jenkins.model.Jenkins.getDescriptorByType(Jenkins.java:1058) at hudson.plugins.copyartifact.BuildSelectorParameter.initAliases(BuildSelectorParameter.java:100) at hudson.plugins.copyartifact.CopyArtifactPlugin.postInitialize(CopyArtifactPlugin.java:35) at hudson.PluginManager$2$1$2.run(PluginManager.java:310) at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:146) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:259) at jenkins.model.Jenkins$5.runTask(Jenkins.java:812) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:187) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:94) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
[JIRA] (JENKINS-12868) Improve navigation on the Available Plugins tab of the update center
Fred G created JENKINS-12868: Summary: Improve navigation on the Available Plugins tab of the update center Key: JENKINS-12868 URL: https://issues.jenkins-ci.org/browse/JENKINS-12868 Project: Jenkins Issue Type: Improvement Components: core Reporter: Fred G Priority: Minor In the UI Enhancement thread on the dev mailing list Brian J suggested links to jump to a certain category to improve navigation on the Available Plugins tab of the update center ([Source|https://groups.google.com/forum/#!msg/jenkinsci-users/mz0rJNTzqms/sCAqpDbNBlgJ]) Other suggested options were * search mechanism (which could be implemented nevertheless) * a second set of tabs by category The attached screenshot shows a table of contents for all categories of the Available Plugins tab in the sidepanel. Before opening a pull request I'd like to know * is the sidepanel the right place for the TOC? * should it be always visible while scrolling? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12574) Provide a better image
[ https://issues.jenkins-ci.org/browse/JENKINS-12574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jieryn reassigned JENKINS-12574: Assignee: (was: jieryn) Provide a better image -- Key: JENKINS-12574 URL: https://issues.jenkins-ci.org/browse/JENKINS-12574 Project: Jenkins Issue Type: Improvement Components: safe-restart, saferestart Reporter: Ulli Hafner Priority: Minor The image should use a better coloring. Currently I can't see the restart arrows in the upper half, maybe less fancy color effects would be better (e.g. using the tango palette or images). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12441) Update child jobs using Remote API dosen´t reload the job´s config and changes are not applied
[ https://issues.jenkins-ci.org/browse/JENKINS-12441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159413#comment-159413 ] jieryn commented on JENKINS-12441: -- This issue was in the wrong component. Update child jobs using Remote API dosen´t reload the job´s config and changes are not applied -- Key: JENKINS-12441 URL: https://issues.jenkins-ci.org/browse/JENKINS-12441 Project: Jenkins Issue Type: Bug Components: core Reporter: Raul Arabaolaza We´re using the Remote API to update a job´s config making a POST request with the new config.xml file to the jenkins_url/job/jobName/ config.xml URL, some of the things changed are the child jobs of the build. It seems to work fine, the config.xml file is changed and in the web´s UI job´s config page the new values are reflected, the same for the physical config.xml file in the Jenkins server. However in the job details page the child projects are not updated and when I execute the job the old child projects are executed. If i restart the server the new child projects are executed so it seems something related to config caches or similar. I think that updating the config.xml file should automatically reload the job configuration if it has to be usefull. Regards, Raul -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12701) Safe Restart checkbox from Plugin Install/Update page fails first time
[ https://issues.jenkins-ci.org/browse/JENKINS-12701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jieryn reassigned JENKINS-12701: Assignee: (was: jieryn) Safe Restart checkbox from Plugin Install/Update page fails first time -- Key: JENKINS-12701 URL: https://issues.jenkins-ci.org/browse/JENKINS-12701 Project: Jenkins Issue Type: Bug Components: core, safe-restart Affects Versions: current Environment: Windows 2003 SP2 Firefox 10.0 Reporter: apgray Priority: Minor Labels: jenkins, plugin, safe-restart Fix For: current When you check the Restart Jenkins when installation is complete and no jobs are running checkbox on the plugin install/upgrade page it redirects the browser. This URL returns 404 first time. Refreshing the page is successful and add Jenkins restart pending to the list of tasks to work on. This probably shouldn't fail the first time. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12858) With Maven3 when build fails does not show exceptions
[
https://issues.jenkins-ci.org/browse/JENKINS-12858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
jieryn updated JENKINS-12858:
-
Assignee: (was: jieryn)
Component/s: maven
(was: console-column)
With Maven3 when build fails does not show exceptions
-
Key: JENKINS-12858
URL: https://issues.jenkins-ci.org/browse/JENKINS-12858
Project: Jenkins
Issue Type: Bug
Components: maven
Affects Versions: current
Environment: - Linux 2.6.18-238.1.1.el5xen #1 SMP Tue Jan 4 13:52:39
EST 2011 x86_64 x86_64 x86_64 GNU/Linux
- java version 1.6.0_24
Java(TM) SE Runtime Environment (build 1.6.0_24-b07)
Java HotSpot(TM) 64-Bit Server VM (build 19.1-b02, mixed mode)
Reporter: Marco Tizzoni
Priority: Minor
Labels: console, maven
Console does not display the full stack trace when building using maven3 if
the build fails.
{code:title=MAVEN 3 BUILD CONSOLE ON JENKINS|borderStyle=solid}
[INFO]
[INFO] Building ConnectionPool-sportello-jar 1.0.0
[INFO]
[INFO]
[INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @
ConnectionPool-sportello-jar ---
[INFO]
[INFO] --- maven-resources-plugin:2.4.3:resources (default-resources) @
ConnectionPool-sportello-jar ---
[WARNING] Using platform encoding (UTF-8 actually) to copy filtered
resources, i.e. build is platform dependent!
[INFO] Copying 1 resource
[INFO]
[INFO] --- maven-compiler-plugin:2.0.2:compile (default-compile) @
ConnectionPool-sportello-jar ---
[INFO] Compiling 5 source files to
/var/lib/jenkins/workspace/sisi.dsvai.sportello.ConnectionPool-sportello/ConnectionPool-sportello-jar/target/classes
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 9.376s
[INFO] Finished at: Wed Feb 22 19:05:08 CET 2012
[INFO] Final Memory: 7M/81M
[INFO]
mavenExecutionResult exceptions not empty
message : Failed to execute goal
org.apache.maven.plugins:maven-compiler-plugin:2.0.2:compile
(default-compile) on project ConnectionPool-sportello-jar: Compilation failure
cause : Compilation failure
Stack trace :
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
goal org.apache.maven.plugins:maven-compiler-plugin:2.0.2:compile
(default-compile) on project ConnectionPool-sportello-jar: Compilation failure
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:213)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
[..]
at java.lang.Thread.run(Thread.java:662)
Caused by: org.apache.maven.plugin.CompilationFailureException: Compilation
failure
at
org.apache.maven.plugin.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:516)
at org.apache.maven.plugin.CompilerMojo.execute(CompilerMojo.java:114)
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
... 27 more
channel stopped
Finished: FAILURE
*** END MAVEN 3 BUILD CONSOLE ON JENKINS ***
{code}
Real console output
{code:title=MAVEN 3 REAL OUTPUT|borderStyle=solid}
[INFO] Finished at: Wed Feb 22 19:21:51 CET 2012
[INFO] Final Memory: 5M/88M
[INFO]
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-compiler-plugin:2.0.2:compile
(default-compile) on project ConnectionPool-sportello-jar: Compilation
failure: Compilation failure:
[ERROR]
/var/lib/jenkins/workspace/sisi.dsvai.sportello.ConnectionPool-sportello/ConnectionPool-sportello-jar/src/main/java/it/bankit/sportello/connectionPool/SockIOPool.java:[62,17]
unmappable character for encoding UTF8
[ERROR]
[ERROR]
/var/lib/jenkins/workspace/sisi.dsvai.sportello.ConnectionPool-sportello/ConnectionPool-sportello-jar/src/main/java/it/bankit/sportello/connectionPool/SockIOPool.java:[68,56]
unmappable character for encoding UTF8
[ERROR]
[ERROR]
/var/lib/jenkins/workspace/sisi.dsvai.sportello.ConnectionPool-sportello/ConnectionPool-sportello-jar/src/main/java/it/bankit/sportello/connectionPool/SockIOPool.java:[125,13]
unmappable character for encoding UTF8
[ERROR]
*** END MAVEN 2 SAMPLE OUTPUT ***
{code}
Every line tagged with
