[JIRA] (JENKINS-15228) Impossible to kill job run by dist-fork
Alex Vesely created JENKINS-15228 Impossible to kill job run by dist-fork Issue Type: Bug Assignee: Unassigned Components: distfork Created: 19/Sep/12 6:30 AM Description: The only way to kill a job run by dist-fork is to press the red 'X' button in Jenkins. The functionality to abort the job from the script that started it is missing. Is you kill (or terminate) the java process that called dist-fork (java -jar jenkins-cli.jar ... dist-fork proc.sh), the job will continue to execute on Jenkins. Environment: SLES 10 Project: Jenkins Priority: Major Reporter: Alex Vesely This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15202) Permanent building / consider removing latest changes
Waldek M commented on JENKINS-15202 Permanent building / consider removing latest changes Hi, Vincent I do understand that this is open source, and I do appreciate your work. Perhaps because the plugin has been so useful and robust, I got to expect it always to be perfect I'll try to be only constructive in the future. And, thanks! Waldek This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-7886) Use the JDK configured for the job
Christer Wikman reopened JENKINS-7886 Use the JDK configured for the job I have configured a project to use 32 bits JDK and default for all other project is 64 bits JDK. I also use two build nodes to build my projects. It works fine do a regular build, but once I do a "Perform Maven Release" jenkins select the default 64 bits JDK instead of the configured 32 bits, which is configured in jenkins-slave.xml Jenkins: 1.447.1 Jenkins Maven Release Plug-in Plug-in: 0.9.1 Change By: Christer Wikman (19/Sep/12 8:03 AM) Resolution: CannotReproduce Status: Resolved Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15220) Quiet mode for clean checkout (not using update)
Michael Clarke commented on JENKINS-15220 Quiet mode for clean checkout (not using update) The -q option is set if you don't have the 'Show All CVS Output' option set on the Job Config Screen. The "cvs checkout: Updating MediaViewer/src/MVDbCons" lines are what I'm referring to with my comment on CVS sending status to error output. This is not filtered by flags on the CVS command so no config is going to change this. We can't just ignore the error output since it may show failure messages but I am looking at how we can send it to a log (rather than the build console) to limit the number of lines during each build. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-7886) Use the JDK configured for the job
teilo commented on JENKINS-7886 Use the JDK configured for the job The JDK is picked up from the job configuration not the slave. If you are just using "default" JDK and have not configured jenkins with multiple JDKs (but just setting env vars in the slave config) then this is not supported - and anything that runs will likely use the platform JDK whenever Maven forks (this is not just the maven release plugin but potentially also surefire tests depending on how this is configured to run). see http://my.safaribooksonline.com/book/software-engineering-and-development/ide/9781449311155/configuring-your-jenkins-server/sect-configuration-jdks for details. If this is the case can you close the defect and update your config, otherwise can you supply more details please as I have been unable to reproduce this with multiple configured JDKs and Windows/Linux. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15221) scm_sync_configuration do not synchronize changes made on disk
Wolfgang Hauser commented on JENKINS-15221 scm_sync_configuration do not synchronize changes made on disk Forgot to tell: we use subversion as scm here This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14189) Discover permission gives Status Code 500 and Stacktrace
Arnaud Héritier commented on JENKINS-14189 Discover permission gives Status Code 500 and Stacktrace I think that this one explains why my dashboard is now empty for anonymous users. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14189) Discover permission gives Status Code 500 and Stacktrace
Arnaud Héritier updated JENKINS-14189 Discover permission gives Status Code 500 and Stacktrace Change By: Arnaud Héritier (19/Sep/12 8:39 AM) Attachment: ScreenShot2012-09-19at10.38.48AM.png This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14837) ldap email seems to perform a bind operation for each and every id that needs to be resolved
Jose Sa commented on JENKINS-14837 ldap email seems to perform a bind operation for each and every id that needs to be resolved Maybe this is not specific just to ldap email plugin as using the ldap authentication also allows to resolve email from username. We had one instance that there were so commiters since last failed build that a build that normally took 5 minutes was taking more than 20 because of constructing notification list from ldap. Mail information don't change that often, if they would be stored in the user information cached for at least a week it would greatly improve this. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-1516) JIRA Plugin Comment Template
SCM/JIRA link daemon commented on JENKINS-1516 JIRA Plugin Comment Template Code changed in jenkins User: Nicolas De Loof Path: src/main/resources/hudson/plugins/gradle/Gradle/config.jelly http://jenkins-ci.org/commit/gradle-plugin/424c67ee2d6fdb3d65c93c13a5042c77084b616d Log: FIXED JENKINS-1516 gradleName "lost" due to refactoring of web UI This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-1516) JIRA Plugin Comment Template
SCM/JIRA link daemon resolved JENKINS-1516 as Fixed JIRA Plugin Comment Template Change By: SCM/JIRA link daemon (19/Sep/12 8:44 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15221) scm_sync_configuration do not synchronize changes made on disk
Frédéric Camblor commented on JENKINS-15221 scm_sync_configuration do not synchronize changes made on disk I am too, but I don't think it is related to the SCM This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15229) There should be an option to provide the jobs for a certain build and all previous builds
Stephan Pauxberger created JENKINS-15229 There should be an option to provide the jobs for a certain build and all previous builds Issue Type: Improvement Assignee: magnayn Components: repository Created: 19/Sep/12 8:49 AM Description: This is needed for incremental build, since not all artifacts are built with every job run. Consider the following example: Project consists of Modules A, B, C, incremental builds are activated Run 1 builds all modules run 2 builds only module A If you use the artifacts provided by build, B and C are not found. If the repository plugin would consider older builds as well, this would not happen. Project: Jenkins Priority: Major Reporter: Stephan Pauxberger This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14483) Remaining Xvfb processes in matrix jobs
Thorsten Kahler commented on JENKINS-14483 Remaining Xvfb processes in matrix jobs Hi Zoran, this is the error message (in matrix job) after installing your latest snapshot version: Started by user Thorsten Kahler [EnvInject] - Preparing an environment for the job. [EnvInject] - Jenkins system variables are kept. [EnvInject] - Jenkins build variables are kept. [EnvInject] - [ERROR] - SEVERE ERROR occurs: null Finished: FAILURE This might be a compatibility issue with our outdated Jenkins version 1.434? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-7886) Use the JDK configured for the job
Christer Wikman commented on JENKINS-7886 Use the JDK configured for the job Nope, I have configured several JDKs and the job's configured JDK is not picked up for all goals when you click on "Maven Perfom Release". (But the configured JDK is correctly picked up from when you are click on "Build now"). I studied the log file from "Maven Perform Release" a bit more and it seems that the release goals are using the right JDK (1.6.0_35), but not the verify goal (JDK 1.6.0_30) "Maven Perform Release" log extract: Executing Maven: -B -f D:/jenkins/workspace/eps-uposadapter-main/product/eps/adapters/uposadapter/main/pom.xml -DdevelopmentVersion=1.0.1-SNAPSHOT -DreleaseVersion=1.0.0 -X -Dresume=false release:prepare release:perform + Error stacktraces are turned on. Apache Maven 2.2.1 (r801777; 2009-08-06 21:16:01+0200) Java version: 1.6.0_35 Java home: C:\java32\jdk1.6.0_35\jre Default locale: sv_SE, platform encoding: Cp1252 OS name: "windows 7" version: "6.1" arch: "x86" Family: "windows" DEBUG Executing: cmd.exe /X /C "D:\jenkins\tools\maven221\bin\mvn.bat -B -X -D maven.repo.local=D:\Work\LocalRepository -P alwaysOn,codesign clean verify" INFO + Error stacktraces are turned on. INFO Apache Maven 2.2.1 (r801777; 2009-08-06 21:16:01+0200) *INFO Java version: 1.6.0_30* *INFO Java home: C:\Program Files\Java\jdk1.6.0_30\jre* INFO Default locale: sv_SE, platform encoding: Cp1252 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-7886) Use the JDK configured for the job
Christer Wikman edited a comment on JENKINS-7886 Use the JDK configured for the job Nope, I have configured several JDKs and the job's configured JDK is not picked up for all goals when you click on "Maven Perfom Release". (But the configured JDK is correctly picked up from when you are click on "Build now"). I studied the log file from "Maven Perform Release" a bit more and it seems that the release goals are using the right JDK (1.6.0_35), but not the verify goal (JDK 1.6.0_30) "Maven Perform Release" log extract: Executing Maven: -B -f D:/jenkins/workspace/eps-uposadapter-main/product/eps/adapters/uposadapter/main/pom.xml -DdevelopmentVersion=1.0.1-SNAPSHOT -DreleaseVersion=1.0.0 -X -Dresume=false release:prepare release:perform Error stacktraces are turned on. Apache Maven 2.2.1 (r801777; 2009-08-06 21:16:01 0200) Java version: 1.6.0_35 Java home: C:\java32\jdk1.6.0_35\jre (correct JDK as configured in job) Default locale: sv_SE, platform encoding: Cp1252 OS name: "windows 7" version: "6.1" arch: "x86" Family: "windows" ... DEBUG Executing: cmd.exe /X /C "D:\jenkins\tools\maven221\bin\mvn.bat -B -X -D maven.repo.local=D:\Work\LocalRepository -P alwaysOn,codesign clean verify" INFO Error stacktraces are turned on. INFO Apache Maven 2.2.1 (r801777; 2009-08-06 21:16:01 0200) *INFO Java version: 1.6.0_30* *INFO Java home: C:\Program Files\Java\jdk1.6.0_30\jre* (Invalid JDK, should be c:\java32) INFO Default locale: sv_SE, platform encoding: Cp1252 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15230) Properties need some help
wernight
created JENKINS-15230
Properties need some help
Issue Type:
Bug
Assignee:
vjuranek
Components:
groovy
Created:
19/Sep/12 9:18 AM
Description:
Properties section help should tell how to access properties, via
System.getProperty('FOO')
Also it should tell if there are reasons not to use them to parse parameters.
Last but not least, environment variable expansion doesn't work in that field:
FOO=$WORKSPACE
Didn't get expanded.
Project:
Jenkins
Priority:
Minor
Reporter:
wernight
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15230) Properties need some help
wernight
updated JENKINS-15230
Properties need some help
Change By:
wernight
(19/Sep/12 9:21 AM)
Description:
Propertiessectionhelpshouldtellhowtoaccessproperties,via{code}System.getProperty(FOO){code}Alsoitshouldtelliftherearereasonsnottousethemtoparseparameters.Lastbutnotleast,
some
environmentvariableexpansion
doesn
don
tworkinthatfield:{code}FOO=$WORKSPACE{code}Didntgetexpanded
whilstitworkedviatheScriptparameterssection
.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15166) Gradle plugin fails to save selected Gradle Version in Project configuration
SCM/JIRA link daemon commented on JENKINS-15166 Gradle plugin fails to save selected Gradle Version in Project configuration Code changed in jenkins User: Nicolas De Loof Path: src/main/resources/hudson/plugins/gradle/Gradle/config.jelly http://jenkins-ci.org/commit/gradle-plugin/17bd2e4f5a11a5ef81fc67913d6ba5ac933f4ba4 Log: FIXED JENKINS-15166 gradleName "lost" due to refactoring of web UI This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15166) Gradle plugin fails to save selected Gradle Version in Project configuration
SCM/JIRA link daemon resolved JENKINS-15166 as Fixed Gradle plugin fails to save selected Gradle Version in Project configuration Change By: SCM/JIRA link daemon (19/Sep/12 9:27 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14483) Remaining Xvfb processes in matrix jobs
zregvart commented on JENKINS-14483 Remaining Xvfb processes in matrix jobs I'm guessing that env-inject plugin catches NullPointerException (probably here: https://github.com/jenkinsci/envinject-plugin/blob/master/src/main/java/org/jenkinsci/plugins/envinject/EnvInjectListener.java#L60), this could be due to setup method of xvfb plugin now returning null (https://github.com/jenkinsci/xvfb-plugin/blob/master/src/main/java/org/jenkinsci/plugins/xvfb/XvfbBuildWrapper.java#L255) on non unix platforms. Can it be that one of your slave is non-unix (windows)? It would probably be better for backward compatibility that the xvfb plugin does not return null on non-unix platforms, as it did in previous versions. I'll make that change and upload a new version on dropbox in a few minutes. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14045) Add ability to change dashboard diagrams time-scale grain for Trend charts
Dirk Kuypers commented on JENKINS-14045 Add ability to change dashboard diagrams time-scale grain for Trend charts I would also like to be able to define start and end of a day. Use case: We are running a huge regression test campaign during night starting at 20:00 h and lasting until the early morning around 4:00 h. Currently this means that the test trend charts show half of the tests of a campaign on one day, the other tests are shown for the next day. The exact time a test is executed is quite random and depends on node availability etc. So there is always a mixture of two campaigns per day and the graphs are misleading for our us... Or should I file a different ticket because this is totally unrelated? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14483) Remaining Xvfb processes in matrix jobs
SCM/JIRA link daemon commented on JENKINS-14483 Remaining Xvfb processes in matrix jobs Code changed in jenkins User: Zoran Regvart Path: src/main/java/org/jenkinsci/plugins/xvfb/XvfbBuildWrapper.java http://jenkins-ci.org/commit/xvfb-plugin/a53ce0e6cf6acc96ad5a2020d1f0492e9e7b6492 Log: JENKINS-14483 Remaining Xvfb processes in matrix jobs return empty environment instead of null from setUp method This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14483) Remaining Xvfb processes in matrix jobs
zregvart commented on JENKINS-14483 Remaining Xvfb processes in matrix jobs Thorsten, I've uploaded a new snapshot on Dropbox, if it's OK now I'll release 1.0.4 later this afternoon. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15067) NullPointerException using project-stats-plugin
Pailloncy Michaël assigned JENKINS-15067 to Pailloncy Michaël NullPointerException using project-stats-plugin Change By: Pailloncy Michaël (19/Sep/12 10:00 AM) Assignee: MarcoAmbu PailloncyMichaël This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15037) Option to consider only stable builds when calculating new warnings
Ulli Hafner commented on JENKINS-15037 Option to consider only stable builds when calculating new warnings I tried to remove the deprecated constructors in the checkstyle plug-in now, but that is not that easy. Seems that I still need to think on how to distribute the new boolean flag to the maven and matrix classes... So please be patient until this will be released, I want to minimize the work in the other plug-ins (and maintain backward compatibility for other plugins that depend on analysis core). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15228) Impossible to kill job run by dist-fork
Alex Vesely updated JENKINS-15228 Impossible to kill job run by dist-fork Change By: Alex Vesely (19/Sep/12 10:26 AM) Description: Theonlywaytokillajobrunbydist-forkistopresstheredXbuttoninJenkins.Thefunctionalitytoabortthejobfromthescriptthatstarteditismissing. Is If youkill(orterminate)thejavaprocessthatcalleddist-fork(java-jarjenkins-cli.jar...dist-forkproc.sh),thejobwillcontinuetoexecuteonJenkins. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14483) Remaining Xvfb processes in matrix jobs
Thorsten Kahler commented on JENKINS-14483 Remaining Xvfb processes in matrix jobs Hi Zoran, still the same error. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15067) NullPointerException using project-stats-plugin
Pailloncy Michaël commented on JENKINS-15067 NullPointerException using project-stats-plugin A pull-request to resolve the issue is opened : https://github.com/jenkinsci/project-stats-plugin/pull/2 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15035) cobertura plugin don't validate report files and later fail to parse them
SCM/JIRA link daemon commented on JENKINS-15035 cobertura plugin dont validate report files and later fail to parse them Code changed in jenkins User: Seiji Sogabe Path: src/main/java/hudson/plugins/cobertura/CoberturaPublisher.java http://jenkins-ci.org/commit/cobertura-plugin/875d27d82d2ffbfd802b03784a3c67c17eb2cf75 Log: Merge pull request #9 from ndeloof/JENKINS-15035 JENKINS-15035 quick check report files identified by pattern to be xml... Compare: https://github.com/jenkinsci/cobertura-plugin/compare/dd80f6c2c310...875d27d82d2f This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15035) cobertura plugin don't validate report files and later fail to parse them
SCM/JIRA link daemon commented on JENKINS-15035 cobertura plugin dont validate report files and later fail to parse them Code changed in jenkins User: Nicolas De Loof Path: src/main/java/hudson/plugins/cobertura/CoberturaPublisher.java http://jenkins-ci.org/commit/cobertura-plugin/2ad1ea3fd5dc09eb04b6fe73d531bc27008590f8 Log: JENKINS-15035 quick check report files identified by pattern to be xml ones This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15032) Layanan Bisnis Pulsa dan Token PLN
yadik hendriyanto updated JENKINS-15032 Layanan Bisnis Pulsa dan Token PLN Change By: yadik hendriyanto (19/Sep/12 11:04 AM) URL: http:// sekedarwawasan setaaan .blogspot.com/2012/09/layanan-bisnis-pulsa-dan-token-pln.html This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13614) archiving artefacts from remote MacOS X, IBM AIX slave fails
Chris Graham commented on JENKINS-13614 archiving artefacts from remote MacOS X, IBM AIX slave fails 1.482 appears to resolve the readlink issue for me. The builds that succeed, but were being failed by Jenkins, no longer do so. Can others confirm? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12230) EmmaCoverageColumn: Fix NullPointerException in logfile if projects do not have coverage data (yet)
Stig Runar Vangen commented on JENKINS-12230 EmmaCoverageColumn: Fix NullPointerException in logfile if projects do not have coverage data (yet) Could this issue please be escalated? This issue currently gives approximately 1 gig of log data per week in our setup. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15222) FTP Publisher broken for concurrent builds
Axel Heider commented on JENKINS-15222 FTP Publisher broken for concurrent builds My guess would be that this is going on internally: Job1 starts and acquires Jenkins ressources internally. The FTP publisher seems to be such ressource. Further jobs have to wait for Job1 to release the ressources So the solution should be that the ressource FTP publisher should be acquired when actually needed only. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-7667) Build waits for next available executor even if several are available
François-Xavier Choinière commented on JENKINS-7667 Build waits for next available executor even if several are available Same problem here: I've a Jenkins server on Ubuntu 32 bit and a slave on Windows 7 64 bit. The slave connects correctly on the server. When starting the job, the status always says waiting the next executor on host HOSTNAME So... I'm unable to use any of my slave! Please fix this ASAP!!! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13202) Artifact archiving from an ssh slave fails if symlinks are present
erwan_q commented on JENKINS-13202 Artifact archiving from an ssh slave fails if symlinks are present Can you confirm this fix is working with java 1.6 too? If not do we have to migrate the master or the slave where the process is running on java 1.7? I have an old slave AIX 5.3 and may be do not support java 1.7... If the fix impact the master, no problem. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15231) Job always wait for the next executor
François-Xavier Choinière created JENKINS-15231 Job always wait for the next executor Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: core Created: 19/Sep/12 11:55 AM Description: I've a Jenkins server on Ubuntu 32 bit and a slave on Windows 7 64 bit. The slave connects correctly on the server. When starting the job, the status always says waiting the next executor on host HOSTNAME So... I'm unable to use any of my slave! Please, anyone, fix this ASAP!!! Environment: Server on Ubuntu Server 12.4 32 bit Slave on Windows 7 64 bit Project: Jenkins Priority: Major Reporter: François-Xavier Choinière This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15067) NullPointerException using project-stats-plugin
SCM/JIRA link daemon commented on JENKINS-15067 NullPointerException using project-stats-plugin Code changed in jenkins User: Marco Ambu Path: src/main/java/hudson/plugins/projectstats/NumBuildsStats.java http://jenkins-ci.org/commit/project-stats-plugin/63c3393e9c4d3763432358ceee865a52651efb7b Log: Merge pull request #2 from mpapo/JENKINS-15067 FIX JENKINS-15067 : a build result can be null if the build is currently... Compare: https://github.com/jenkinsci/project-stats-plugin/compare/d31ab5bb2d09...63c3393e9c4d This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15067) NullPointerException using project-stats-plugin
SCM/JIRA link daemon commented on JENKINS-15067 NullPointerException using project-stats-plugin Code changed in jenkins User: Michael Pailloncy Path: src/main/java/hudson/plugins/projectstats/NumBuildsStats.java http://jenkins-ci.org/commit/project-stats-plugin/1debd0583b73407488a34c7fea1555119c2e Log: FIX JENKINS-15067 : a build result can be null if the build is currently building. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-7667) Build waits for next available executor even if several are available
François-Xavier Choinière updated JENKINS-7667 Build waits for next available executor even if several are available Change By: François-Xavier Choinière (19/Sep/12 12:04 PM) Affects Version/s: current This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15232) Red Hat/Fedora/CentOS package ignores user $JENKINS_USER during update
Marco Spinola Durante created JENKINS-15232 Red Hat/Fedora/CentOS package ignores user $JENKINS_USER during update Issue Type: Bug Affects Versions: current Assignee: wolfs Components: all-changes Created: 19/Sep/12 12:24 PM Description: I must run Jenkins under another user so I configure it in /etc/sysconfig/jenkins in the variable JENKINS_USER. When I update jenkins to the newest release the user is ignored, and following directories are deleted/recreated with the default user "jenkins" /var/log/jenkins /var/lib/jenkins /var/cache/jenkins Having another user configured as on the file system leeds to systematic crash of jenkins without any log information whatsoever. The workaround is to change ownership of those directories after update. Environment: RedHat EL 6.3, 64Bit machine Project: Jenkins Priority: Major Reporter: Marco Spinola Durante This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15233) Dry run should ask for build parameters
Julien Carsique created JENKINS-15233 Dry run should ask for build parameters Issue Type: Bug Assignee: Unassigned Components: dry-run Created: 19/Sep/12 1:06 PM Description: When there are build parameters, the Dry Run plugin must ask for them, like a true run does. It seems to use the default values. The build parameters may have an impact which needs to be validated when running in dry run mode. They can be used in various ways for customizing a job execution. For instance, if using the Parameterized plugin for configuring the NodeLabel, then the corresponding downstream job's build parameter is changing the slave. Project: Jenkins Priority: Minor Reporter: Julien Carsique This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14483) Remaining Xvfb processes in matrix jobs
SCM/JIRA link daemon commented on JENKINS-14483 Remaining Xvfb processes in matrix jobs Code changed in jenkins User: Zoran Regvart Path: src/main/java/org/jenkinsci/plugins/xvfb/XvfbBuildWrapper.java http://jenkins-ci.org/commit/xvfb-plugin/81e7a1ff832b99bf2652b022c56eb1e81c96163c Log: JENKINS-14483 Remaining Xvfb processes in matrix jobs fix NPE with Environment Injector Plugin installed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14483) Remaining Xvfb processes in matrix jobs
zregvart commented on JENKINS-14483 Remaining Xvfb processes in matrix jobs Hi Thorsten I was able to reproduce your problem with Environment Injector Plugin installed, luckily it was a very simple fix, and as usual I need your help testing the new version I've just uploaded to Dropbox. Thank you This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14785) Add support for slicing matrix job configuration
Jacob Robertson resolved JENKINS-14785 as Cannot Reproduce Add support for slicing matrix job configuration If you want to re-open this, please do, and provide some more detail on the feature you're requesting. Change By: Jacob Robertson (19/Sep/12 1:35 PM) Status: Open Resolved Resolution: CannotReproduce This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14784) Add support for the execute python script slicer
Jacob Robertson resolved JENKINS-14784 as Fixed Add support for the execute python script slicer look for this in version 1.33 which was released today Change By: Jacob Robertson (19/Sep/12 1:54 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15152) Add support for configure 'Block build when upstream project is building' and 'Block build when downstream project is building'
Jacob Robertson resolved JENKINS-15152 as Fixed Add support for configure Block build when upstream project is building and Block build when downstream project is building look for this in version 1.33 which was released today Change By: Jacob Robertson (19/Sep/12 1:54 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15234) Robot plugin should mark build as unstable if there are failed non-critical tests
Sergiu Tudos updated JENKINS-15234 Robot plugin should mark build as unstable if there are failed non-critical tests Change By: Sergiu Tudos (19/Sep/12 1:58 PM) Summary: Robotpluginshouldmarkbuildasunstableiftherearefailednon-critical test tests This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14954) testlink plugin can't find test results in testng-results.xml
Bruno P. Kinoshita commented on JENKINS-14954 testlink plugin cant find test results in testng-results.xml Hi Jacob! I believe I didn't make myself clear, sorry. You have a single build step, that publishes TestNG reports. That build step finds your TestNG report. As below: Executing single Build Steps. TestNG Reports Processing: START Looking for TestNG results report in workspace using pattern: /root/.jenkins/workspace/FormHttpFlowTest/qa/scripts/webnode/selenium/FormHttpFlowTest/test-output/testng-results.xml Saving reports... Processing '/root/.jenkins/jobs/FormHttpFlowTest/builds/2012-08-28_10-18-18/testng/testng-results.xml' TestNG Reports Processing: FINISH However, there is another step that invokes the result seeking strategies that you've configured. This step needs paths patterns relative to the workspace (I'm adding this to the help button next to the include pattern field in the UI). I've attached some screenshots that may help to illustrate what has been done. The TestNG XML file is the one that you uploaded here (that always helps when debugging issues, thanks a lot). Basically, I edited my project and changed the include pattern from /home/kinow/.../jobs/job/workspace/testng-results.xml to **/testng-results.xml Let me know if that helps, Bruno This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14954) testlink plugin can't find test results in testng-results.xml
Bruno P. Kinoshita updated JENKINS-14954 testlink plugin cant find test results in testng-results.xml Change By: Bruno P. Kinoshita (19/Sep/12 2:08 PM) Attachment: JENKINS-14954-001.png Attachment: JENKINS-14954-002.png Attachment: JENKINS-14954-003.png Attachment: JENKINS-14954-004.png Attachment: JENKINS-14954-005.png This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14954) testlink plugin can't find test results in testng-results.xml
Bruno P. Kinoshita updated JENKINS-14954 testlink plugin cant find test results in testng-results.xml Change By: Bruno P. Kinoshita (19/Sep/12 2:09 PM) Attachment: JENKINS-14954-006.png This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14954) testlink plugin can't find test results in testng-results.xml
Bruno P. Kinoshita resolved JENKINS-14954 as Not A Defect testlink plugin cant find test results in testng-results.xml Change By: Bruno P. Kinoshita (19/Sep/12 2:09 PM) Status: Open Resolved Resolution: NotADefect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14954) testlink plugin can't find test results in testng-results.xml
Bruno P. Kinoshita stopped work on JENKINS-14954 testlink plugin cant find test results in testng-results.xml Change By: Bruno P. Kinoshita (19/Sep/12 2:09 PM) Status: InProgress Open This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14954) testlink plugin can't find test results in testng-results.xml
SCM/JIRA link daemon commented on JENKINS-14954 testlink plugin cant find test results in testng-results.xml Code changed in jenkins User: Bruno P. Kinoshita Path: src/main/java/hudson/plugins/testlink/result/JUnitCaseNameResultSeeker.java src/main/java/hudson/plugins/testlink/result/JUnitMethodNameResultSeeker.java src/main/java/hudson/plugins/testlink/result/TestNGMethodNameDataProviderNameResultSeeker.java src/main/java/hudson/plugins/testlink/result/TestNGMethodNameResultSeeker.java src/main/resources/hudson/plugins/testlink/util/Messages.properties src/main/resources/hudson/plugins/testlink/util/Messages_en.properties src/main/resources/hudson/plugins/testlink/util/Messages_pt.properties src/main/webapp/help-junitIncludePattern.html src/main/webapp/help-junitIncludePattern_es.html src/main/webapp/help-junitIncludePattern_fr.html src/main/webapp/help-junitIncludePattern_pt.html src/main/webapp/help-tapIncludePattern.html src/main/webapp/help-tapIncludePattern_es.html src/main/webapp/help-tapIncludePattern_fr.html src/main/webapp/help-tapIncludePattern_pt.html src/main/webapp/help-testNGIncludePattern.html src/main/webapp/help-testNGIncludePattern_es.html src/main/webapp/help-testNGIncludePattern_fr.html src/main/webapp/help-testNGIncludePattern_pt.html http://jenkins-ci.org/commit/testlink-plugin/2c5ea35e32d6b4614b35fad0b21a0a24fdfa55a6 Log: JENKINS-14954 Added note about requirement to have the include patterns relative to the job workspace. Also fixed the log messages for result seeking strategies. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15210) Allow additional groovy class path to reference workspace
Daniel Beck commented on JENKINS-15210 Allow additional groovy class path to reference workspace On further thought, using $WORKSPACE breaks in a master/slave scenario, as postbuild is executed on the master. But variable resolution would still allow the global definition of an environment variable such as GROOVY_POSTBUILD_SCRIPTS_DIR and reusing that in the individual jobs an improvement upon the current situation. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-7214) FilePath.validateAntFileMask too slow for /configure
Jesse Glick started work on JENKINS-7214 FilePath.validateAntFileMask too slow for /configure Change By: Jesse Glick (19/Sep/12 3:37 PM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14845) Default SUCCESS status reported when no results are found is wrong
Bruno P. Kinoshita closed JENKINS-14845 as Fixed Default SUCCESS status reported when no results are found is wrong Fixed in 3.1.7 (available from update-center in the next hours) Change By: Bruno P. Kinoshita (19/Sep/12 3:54 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14954) testlink plugin can't find test results in testng-results.xml
Bruno P. Kinoshita closed JENKINS-14954 as Not A Defect testlink plugin cant find test results in testng-results.xml Fixed in 3.1.7 (available from update-center in the next hours) Change By: Bruno P. Kinoshita (19/Sep/12 3:54 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14263) TestLink Plugin: Jenkins reports build failure when test case is failed
Bruno P. Kinoshita closed JENKINS-14263 as Not A Defect TestLink Plugin: Jenkins reports build failure when test case is failed Fixed in 3.1.7 (available from update-center in the next hours) Change By: Bruno P. Kinoshita (19/Sep/12 3:54 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-6676) More granularity on EC2 instance caps
Quentin Hartman commented on JENKINS-6676 More granularity on EC2 instance caps Now that we have the ability stop/start existing instances, another nice addition to the instance cap behavior is to have an option to count stopped instances as well as running instances. This would allow for forcing a fixed number of instances to be created, ensuring that a job is always run on an instance with a warm workspace, or queued. In my case, starting a job on a new instance is usually the wrong thing to do because a cold workspace increases by build time by 5 times or more, waiting for a running build to finish is a much better choice. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15235) Trailing space in Git branch name causes build failures
ryan shoemaker created JENKINS-15235 Trailing space in Git branch name causes build failures Issue Type: Bug Assignee: Nicolas De Loof Components: git, git-parameter Created: 19/Sep/12 4:20 PM Description: While setting up a new job, I CP my Git branch name into the "Branch Specifier" under SCM. I didn't realize it, but there was a trailing space in the branch name. This caused the build to fail with: Started by user ryan.shoemaker Building in workspace /opt/jenkins/jobs/MyJob/workspace Checkout:workspace / /opt/jenkins/jobs/MyJob/workspace - hudson.remoting.LocalChannel@6c616408 Using strategy: Default Wiping out workspace first. Cloning the remote Git repository Cloning repository origin Fetching upstream changes from ssh://ryan.shoema...@mygitserver.com/git/MyModule ERROR: Couldn't find any revision to build. Verify the repository and branch configuration for this job. When I removed the trailing space from the branch name, everything built fine. Environment: Jenkins 1.471 git 1.1.19 git-parameter 0.2 Project: Jenkins Labels: git build configuration Priority: Minor Reporter: ryan shoemaker This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14568) Improve commit messages from SCM Sync Configuration
Frédéric Camblor commented on JENKINS-14568 Improve commit messages from SCM Sync Configuration Yup this is a limitation of the "transactional commit" feature : It's hard for me to identify a "transaction" when it comes from the SYSTEM (that is, automated modification made by jenkins, in the background). I think it should be better handled during a "human" modification (because in that case, 1 http request = 1 scm transaction). I don't know if you can modify multiple module configurations during 1 http request (I don't have multimodules on my current instance), but if you can, I think there will only be 1 commit. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15197) Add support for Maven toolchains configuration file
domi commented on JENKINS-15197 Add support for Maven toolchains configuration file Thanks Jeff, this is a really good idea! Nicolas currently is also working on the same code to make it more plugable in the core itself (the settings.xml) he needs a different implementation of this for cloudbees, therefore we want to have this as a clean EP in the core. His current state is here: https://github.com/ndeloof/jenkins/tree/maven-settings Maybe it would make sense to have your idea integrated into that change as well. wdyt? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15219) Invalid markup generated when template cannot be loaded for Maven settings file
SCM/JIRA link daemon commented on JENKINS-15219 Invalid markup generated when template cannot be loaded for Maven settings file Code changed in jenkins User: Jeff MAURY Path: src/main/java/org/jenkinsci/plugins/configfiles/maven/AbstractMavenSettingsProvider.java http://jenkins-ci.org/commit/config-file-provider-plugin/2c20c6c2f025cca29d316de53dc50c812094200d Log: JENKINS-15219 Invalid markup generated when template cannot be loaded for Maven settings file This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15219) Invalid markup generated when template cannot be loaded for Maven settings file
domi resolved JENKINS-15219 as Fixed Invalid markup generated when template cannot be loaded for Maven settings file Change By: domi (19/Sep/12 5:54 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14978) Maven Deployment Linker does not support 'dynamic' Project name (upstream uploader)
SCM/JIRA link daemon commented on JENKINS-14978 Maven Deployment Linker does not support dynamic Project name (upstream uploader) Code changed in jenkins User: imod Path: pom.xml src/main/java/hudson/plugins/mavendeploymentlinker/MavenDeploymentDownloader.java src/main/resources/hudson/plugins/mavendeploymentlinker/Messages.properties http://jenkins-ci.org/commit/maven-deployment-linker-plugin/42a3333adae238128a4dea1f75152b5ee005 Log: FIXED JENKINS-14978 expand project name with TokenMacro This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14978) Maven Deployment Linker does not support 'dynamic' Project name (upstream uploader)
SCM/JIRA link daemon resolved JENKINS-14978 as Fixed Maven Deployment Linker does not support dynamic Project name (upstream uploader) Change By: SCM/JIRA link daemon (19/Sep/12 7:08 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15197) Add support for Maven toolchains configuration file
SCM/JIRA link daemon commented on JENKINS-15197 Add support for Maven toolchains configuration file Code changed in jenkins User: Jeff MAURY Path: src/main/java/org/jenkinsci/plugins/configfiles/maven/MavenToolchainsConfig.java src/main/resources/org/jenkinsci/plugins/configfiles/Messages.properties src/main/resources/org/jenkinsci/plugins/configfiles/Messages_fr.properties src/main/resources/org/jenkinsci/plugins/configfiles/maven/MavenToolchainsConfig/MavenToolchainsConfigProvider/newInstanceDetail.jelly src/main/resources/org/jenkinsci/plugins/configfiles/maven/MavenToolchainsConfig/MavenToolchainsConfigProvider/newInstanceDetail.properties src/main/resources/org/jenkinsci/plugins/configfiles/maven/MavenToolchainsConfig/MavenToolchainsConfigProvider/newInstanceDetail_fr.properties src/main/resources/org/jenkinsci/plugins/configfiles/maven/toolchains-tpl.xml http://jenkins-ci.org/commit/config-file-provider-plugin/23fcf58e4646e5eb54459745e6b352bbb4d24fb7 Log: JENKINS-15197 Add support for Maven toolchains config files This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15197) Add support for Maven toolchains configuration file
SCM/JIRA link daemon commented on JENKINS-15197 Add support for Maven toolchains configuration file Code changed in jenkins User: Olivier Lamy Path: src/main/java/org/jenkinsci/plugins/configfiles/buildwrapper/CleanTempFilesAction.java src/main/java/org/jenkinsci/plugins/configfiles/buildwrapper/CleanTempFilesRunListener.java src/main/java/org/jenkinsci/plugins/configfiles/buildwrapper/ManagedFileUtil.java src/main/java/org/jenkinsci/plugins/configfiles/custom/CustomConfig.java src/main/java/org/jenkinsci/plugins/configfiles/groovy/GroovyScript.java src/main/java/org/jenkinsci/plugins/configfiles/maven/GlobalMavenSettingsConfig.java src/main/java/org/jenkinsci/plugins/configfiles/maven/MavenSettingsConfig.java src/main/java/org/jenkinsci/plugins/configfiles/maven/MavenToolchainsConfig.java src/main/java/org/jenkinsci/plugins/configfiles/xml/XmlConfig.java src/main/resources/org/jenkinsci/plugins/configfiles/Messages.properties src/main/resources/org/jenkinsci/plugins/configfiles/Messages_fr.properties src/main/resources/org/jenkinsci/plugins/configfiles/maven/MavenToolchainsConfig/MavenToolchainsConfigProvider/newInstanceDetail.jelly src/main/resources/org/jenkinsci/plugins/configfiles/maven/MavenToolchainsConfig/MavenToolchainsConfigProvider/newInstanceDetail.properties src/main/resources/org/jenkinsci/plugins/configfiles/maven/MavenToolchainsConfig/MavenToolchainsConfigProvider/newInstanceDetail_fr.properties src/main/resources/org/jenkinsci/plugins/configfiles/maven/toolchains-tpl.xml http://jenkins-ci.org/commit/config-file-provider-plugin/436eecab1103850d04f9d9b463169099c7f8e57a Log: Merge pull request #3 from jeffmaury/JENKINS-15197 JENKINS-15197 Add support for Maven toolchains config files Thanks ! Compare: https://github.com/jenkinsci/config-file-provider-plugin/compare/467091e6a416...436eecab1103 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-7214) FilePath.validateAntFileMask too slow for /configure
Jesse Glick updated JENKINS-7214 FilePath.validateAntFileMask too slow for /configure Demo job. Change By: Jesse Glick (19/Sep/12 8:32 PM) Attachment: config.xml This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15238) Cannot download Windows installer from Jenkins Web Site
Frank Merrow created JENKINS-15238 Cannot download Windows installer from Jenkins Web Site Issue Type: Bug Assignee: Unassigned Components: other Created: 19/Sep/12 8:44 PM Description: I have tried it from multiple systems . . . the download runs to 18.1 Megs and stops . . . I've tried IE and Chrome on multiple systems . . . all go to 18.1 Megs and stops. Project: Jenkins Priority: Major Reporter: Frank Merrow This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-7214) FilePath.validateAntFileMask too slow for /configure
SCM/JIRA link daemon commented on JENKINS-7214 FilePath.validateAntFileMask too slow for /configure Code changed in jenkins User: Jesse Glick Path: changelog.html core/src/main/java/hudson/FilePath.java core/src/main/java/hudson/util/FormFieldValidator.java core/src/main/resources/hudson/Messages.properties core/src/main/resources/hudson/util/Messages.properties core/src/test/java/hudson/FilePathTest.java http://jenkins-ci.org/commit/jenkins/a885cc2179ea76bced186c3ed223ce50fec58a75 Log: FIXED JENKINS-7214 FilePath.validateAntFileMask too slow for /configure. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11285) Ability to run postbuild script on a given node
John Dyer reopened JENKINS-11285 Ability to run postbuild script on a given node I hope this isn't against the rules, but I would liek to reopen this since I think it would be really awesome to have. I understand Gregory's suggestion, but I think a cleaner solution would providing means to allow post build steps to be executed on the master. Change By: John Dyer (19/Sep/12 9:01 PM) Resolution: Incomplete Status: Closed Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15121) Invalid URL's on Project/Build pages for deployed artifacts
Gregory Boissinot commented on JENKINS-15121 Invalid URLs on Project/Build pages for deployed artifacts A slave node might be off when you want to access a deployed artifact. Therefore, I suppose all artifacts deployed have to be accessible from the Jenkins master This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15121) Invalid URL's on Project/Build pages for deployed artifacts
Gregory Boissinot edited a comment on JENKINS-15121 Invalid URLs on Project/Build pages for deployed artifacts A slave node might be off when you want to access a deployed artifact. Therefore, I suppose all artifacts deployed have to be accessible from the Jenkins master. What do you think? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15239) Tags feature is broken
John Dyer
created JENKINS-15239
Tags feature is broken
Issue Type:
Bug
Affects Versions:
current
Assignee:
Kohsuke Kawaguchi
Components:
ec2
Created:
19/Sep/12 9:33 PM
Description:
I am trying to create an instance with a "Name" tag but it's instantly giving me an error when trying to do start the node:
Launching ami-95a310fc Looking for existing instances: {Filters: {Name: image-id, Values: [ami-95a310fc], }, {Name: availability-zone, Values: [us-east-1a], }, {Name: group-name, Values: [jclouds#jenkins-slave], }, {Name: key-name, Values: [test_ssh_key], }, {Name: instance-type, Values: [m1.large], }, {Name: tag:Name, Values: [Testing], }, {Name: instance-state-name, Values: [stopped, stopping], }, } ERROR: You must specify one or more tags to create
Status Code: 400, AWS Service: AmazonEC2, AWS Request ID: f2a5bfa5-73b0-40f4-b559-f7b7fb909233, AWS Error Code: InvalidParameterValue, AWS Error Message: You must specify one or more tags to create at com.amazonaws.http.AmazonHttpClient.handleErrorResponse(AmazonHttpClient.java:547) at com.amazonaws.http.AmazonHttpClient.executeHelper(AmazonHttpClient.java:284) at com.amazonaws.http.AmazonHttpClient.execute(AmazonHttpClient.java:169) at com.amazonaws.services.ec2.AmazonEC2Client.invoke(AmazonEC2Client.java:5684) at com.amazonaws.services.ec2.AmazonEC2Client.createTags(AmazonEC2Client.java:3102) at hudson.plugins.ec2.SlaveTemplate.provision(SlaveTemplate.java:292) at hudson.plugins.ec2.EC2Cloud.doProvision(EC2Cloud.java:207) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:288) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:151) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:90) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:111) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:574) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:659) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:574) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:659) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:488) at org.kohsuke.stapler.Stapler.service(Stapler.java:162) at javax.servlet.http.HttpServlet.service(HttpServlet.java:803) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:206) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:179) at net.bull.javamelody.PluginMonitoringFilter.doFilter(PluginMonitoringFilter.java:86) at org.jvnet.hudson.plugins.monitoring.HudsonMonitoringFilter.doFilter(HudsonMonitoringFilter.java:84) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98) at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:47) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at
[JIRA] (JENKINS-15121) Invalid URL's on Project/Build pages for deployed artifacts
pickgr1 commented on JENKINS-15121 Invalid URLs on Project/Build pages for deployed artifacts For our specific scenario, we are using shared NFS storage for our artifacts. We have a simple apache front-end setup for users to browse/download the artifacts so we don't place any extra burden on our Jenkins masters. We also have a geographically diverse build environment with masters and slaves distributed at different sites around the world - sometimes the master and slave is not co-located. The slave will always upload it's artifacts to the local "artifact server" which is essentially a NAS with a web front-end. So for our rather complicated environment, we need to provide a URL to the artifacts based on where the slave is located. Ideally, what we need is a way to configure a URL that is based on some environment that is slave-specific. For now, we've just modified the jelly so that the artifacts are just listed without a hypertext reference. If there was a way to just turn this off globally without having to hack the jelly files, that would be a big improvement for us. Thanks for your consideration. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-7214) FilePath.validateAntFileMask too slow for /configure
dogfood commented on JENKINS-7214 FilePath.validateAntFileMask too slow for /configure Integrated in jenkins_main_trunk #1939 FIXED JENKINS-7214 FilePath.validateAntFileMask too slow for /configure. (Revision a885cc2179ea76bced186c3ed223ce50fec58a75) Result = UNSTABLE Jesse Glick : a885cc2179ea76bced186c3ed223ce50fec58a75 Files : core/src/main/java/hudson/FilePath.java core/src/test/java/hudson/FilePathTest.java core/src/main/java/hudson/util/FormFieldValidator.java core/src/main/resources/hudson/util/Messages.properties changelog.html core/src/main/resources/hudson/Messages.properties This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15103) jenkins slave process does not let go of .git\objects\pack\*.pack file causeing Unable to delete when wiping workspace
Danny Gershman commented on JENKINS-15103 jenkins slave process does not let go of .git\objects\pack\*.pack file causeing Unable to delete when wiping workspace I am seeing this same issue, cannot clear the workspace without restarting Jenkins. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
