[JIRA] [fxcop-runner] (JENKINS-18151) FxCop-Runner sets build results to unstable when FxCop runs succesfully
Pete W commented on JENKINS-18151 FxCop-Runner sets build results to unstable when FxCop runs succesfully @Ryan Yes I tried those tips, didn't seem to help. Unfortunately I don't have time to investigate further to solve my FxCop warnings, so as a workaround I just run FxCop as a "Exceute Windows batch command" and add a "exit 0" line at the end... bit of a cheat but gives me some data at least for now... 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [subversion] (JENKINS-20623) Subversion postcommit hook dont take last revision
monica diez
created JENKINS-20623
Subversion postcommit hook dont take last revision
Issue Type:
Bug
Assignee:
Unassigned
Components:
subversion
Created:
18/Nov/13 9:07 AM
Description:
I have
'http://localhost/jenkins/subversion/${uuid}/notifyCommit?rev=$REV'
in my postcommit hook code, but my $REV is empty and when hooks execute the jenkins update but the penultimate revision. ¿Why dont update the last one?
If anyone could help me...
Thanks
Due Date:
18/Nov/13 12:00 AM
Project:
Jenkins
Priority:
Major
Reporter:
monica diez
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
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [clearcase-ucm] (JENKINS-19824) Sanitize changelog layout, case 10098
Mads Nielsen resolved JENKINS-19824 as Fixed Sanitize changelog layout, case 10098 Fixed in 1.4.4 Change By: Mads Nielsen (18/Nov/13 9:17 AM) Status: Open Resolved Fix Version/s: current 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [clearcase-ucm] (JENKINS-19800) Improve the performance when selecting the baseline, case 9879
Mads Nielsen resolved JENKINS-19800 as Fixed Improve the performance when selecting the baseline, case 9879 Fixed in 1.4.4 Change By: Mads Nielsen (18/Nov/13 9:53 AM) Status: Open Resolved Fix Version/s: current 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [clearcase-ucm] (JENKINS-19405) Build execution time increases for each build (Praqma Case 9918 )
Mads Nielsen resolved JENKINS-19405 as Fixed Build execution time increases for each build (Praqma Case 9918 ) Fixed in 1.4.4 Change By: Mads Nielsen (18/Nov/13 9:56 AM) Status: Open Resolved Fix Version/s: current 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [active-directory] (JENKINS-16429) ComThread is leaking even when its peer is dead
Dennys Hsieh commented on JENKINS-16429 ComThread is leaking even when its peer is dead We have this issue and need to restart Jenkins 1~2 times every day, is there any work around for it? 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [testlink] (JENKINS-20624) TAP result seeker's include test notes adds poor values
Javier Delgado created JENKINS-20624 TAP result seekers include test notes adds poor values Issue Type: Bug Assignee: Javier Delgado Components: testlink Created: 18/Nov/13 10:01 AM Description: It saves at TestLink notes a testSet key, whereas it could include a field from the TAP stream such as TestLink: Notes: Some note formatted to be inserted Project: Jenkins Priority: Major Reporter: Javier Delgado 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [clearcase-ucm] (JENKINS-19069) Missing group id for pom, case 9811
Mads Nielsen resolved JENKINS-19069 as Not A Defect Missing group id for pom, case 9811 Closing case. Change By: Mads Nielsen (18/Nov/13 10:03 AM) Status: Open Resolved Fix Version/s: current 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [gui] (JENKINS-13978) Add posibility to copy view
SCM/JIRA link daemon commented on JENKINS-13978 Add posibility to copy view Code changed in jenkins User: Nicolas De Loof Path: changelog.html core/src/main/java/hudson/model/View.java core/src/main/resources/jenkins/model/Jenkins/newView.jelly http://jenkins-ci.org/commit/jenkins/1067585a49517414398b3becbebed09abf496761 Log: JENKINS-13978 option to copy a view 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [clearcase-ucm] (JENKINS-19823) Improve performance when generating change log, case 10097
Mads Nielsen resolved JENKINS-19823 as Fixed Improve performance when generating change log, case 10097 Fixed in 1.4.4 Change By: Mads Nielsen (18/Nov/13 10:13 AM) Status: Open Resolved Fix Version/s: current 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [clearcase-ucm] (JENKINS-19809) Better comparison of baselines in poll child and sibling mode, case 10095
Mads Nielsen resolved JENKINS-19809 as Fixed Better comparison of baselines in poll child and sibling mode, case 10095 Fixed in 1.4.4 Change By: Mads Nielsen (18/Nov/13 10:18 AM) Status: Open Resolved Fix Version/s: current 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [clearcase-ucm] (JENKINS-18026) Baseline not loaded when paramerized, case 9320
Mads Nielsen resolved JENKINS-18026 as Fixed Baseline not loaded when paramerized, case 9320 Fixed in 1.4.4. Change By: Mads Nielsen (18/Nov/13 10:21 AM) Status: Open Resolved Fix Version/s: current 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [gui] (JENKINS-13978) Add posibility to copy view
dogfood commented on JENKINS-13978 Add posibility to copy view Integrated in jenkins_main_trunk #3059 JENKINS-13978 option to copy a view (Revision 1067585a49517414398b3becbebed09abf496761) Result = UNSTABLE Nicolas De Loof : 1067585a49517414398b3becbebed09abf496761 Files : changelog.html core/src/main/java/hudson/model/View.java core/src/main/resources/jenkins/model/Jenkins/newView.jelly 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [xcode] (JENKINS-14719) Support building xcarchive files
Daniela Dias commented on JENKINS-14719 Support building xcarchive files Hi, I am experiencing some issues when selecting this option and sending the .dSYM file to Testflight. I get the error 400 with the following message: "The .dSYM does not correspond with this build. Are you sure you uploaded the correct one?" I am using the last version of xCode, Jenkins and the plugins. If I disable the option to generate the .xcarchive everything works fine. Is this a normal behaviour? Thanks! 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [testlink] (JENKINS-20624) TAP result seeker's include test notes adds poor values
Javier Delgado started work on JENKINS-20624 TAP result seekers include test notes adds poor values Change By: Javier Delgado (18/Nov/13 11:24 AM) 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-20625) Resurrect 'git clone --reference' in git plugin
Thomas Pasch created JENKINS-20625 Resurrect git clone --reference in git plugin Issue Type: Improvement Affects Versions: current Assignee: Nicolas De Loof Components: git Created: 18/Nov/13 11:24 AM Description: With Version 2.0 (Oct 22, 2013) of the git plugin, the advanced option 'Path of the reference repo to use during clone' for using a '--reference' git repository disappeared. Please resurrect it! Project: Jenkins Priority: Minor Reporter: Thomas Pasch 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jenkinswalldisplay] (JENKINS-20551) Claim border moves text out of line
howama updated JENKINS-20551 Claim border moves text out of line Attached output from howama:master fork which fixes the text alignment by using a background Change By: howama (18/Nov/13 11:45 AM) Attachment: jenkins.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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [clearcase-ucm] (JENKINS-19824) Sanitize changelog layout, case 10098
SCM/JIRA link daemon commented on JENKINS-19824 Sanitize changelog layout, case 10098 Code changed in jenkins User: Christian Wolfgang Path: src/main/resources/net/praqma/hudson/scm/ChangeLogSetImpl/digest.jelly src/main/resources/net/praqma/hudson/scm/ChangeLogSetImpl/index.jelly http://jenkins-ci.org/commit/clearcase-ucm-plugin/34f04ff9a6cdb98598da22ed9ec63d27878844ba Log: fixed JENKINS-19824 Updated layout 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [clearcase-ucm] (JENKINS-19823) Improve performance when generating change log, case 10097
SCM/JIRA link daemon commented on JENKINS-19823 Improve performance when generating change log, case 10097 Code changed in jenkins User: Christian Wolfgang Path: src/main/java/net/praqma/hudson/remoting/deliver/GetChanges.java http://jenkins-ci.org/commit/clearcase-ucm-plugin/356dfb6a0e003cc7e8e709b0d8b366603fcf23ba Log: JENKINS-19823 Updating the parser inputs 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [clearcase-ucm] (JENKINS-19823) Improve performance when generating change log, case 10097
SCM/JIRA link daemon commented on JENKINS-19823 Improve performance when generating change log, case 10097 Code changed in jenkins User: Christian Wolfgang Path: pom.xml src/main/java/net/praqma/hudson/remoting/deliver/GetChanges.java http://jenkins-ci.org/commit/clearcase-ucm-plugin/77a79842c3caed450e13b35766951d1e4905cebd Log: JENKINS-19823 Utilizing new activity parser 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [clearcase-ucm] (JENKINS-19800) Improve the performance when selecting the baseline, case 9879
SCM/JIRA link daemon commented on JENKINS-19800 Improve the performance when selecting the baseline, case 9879 Code changed in jenkins User: Christian Wolfgang Path: pom.xml src/main/java/net/praqma/hudson/remoting/GetRemoteBaselineFromStream.java src/main/java/net/praqma/hudson/scm/CCUCMScm.java src/test/java/net/praqma/hudson/test/integration/child/BaselinesFound.java http://jenkins-ci.org/commit/clearcase-ucm-plugin/0b1a165df5a6f414dfc90a6cf3607161632c6091 Log: JENKINS-19800 Updating cool and loading only the baseline selected 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-20407) Installation of Debian package v1.538 fails: chown: cannot access `/var/run/jenkins': No such file or directory
Marc Schoechlin commented on JENKINS-20407 Installation of Debian package v1.538 fails: chown: cannot access `/var/run/jenkins: No such file or directory Unfortunately this breaks out automated jenkins installation. Release 1.539 still seems to have this problem and there is new newer release at "deb http://pkg.jenkins-ci.org/debian binary/". 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [performance-plugin] (JENKINS-11359) If you stop a build while syncing to Perforce, the process continues to sync on the build machine.
Manuel Carrasco commented on JENKINS-11359 If you stop a build while syncing to Perforce, the process continues to sync on the build machine. Could you add more info to the report? 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [scm-sync-configuration] (JENKINS-20626) SCM-sync-configuration plugin: make root directory in repository configurable
Sven Keller created JENKINS-20626 SCM-sync-configuration plugin: make root directory in repository configurable Issue Type: Improvement Affects Versions: current Assignee: Frédéric Camblor Components: scm-sync-configuration Created: 18/Nov/13 12:38 PM Description: currently jenkins configuration files are synched directly to the root directory of a repository, which is creating quite a mess having all of them at the same level with other sources in one single repo. It should be possible to define e.g. the relative path inside the repo where the configuration is synched to. This configuration should be done when configuring the plugin. focus should be on git (if separate implementation is necessary) Environment: non OS dependent Fix Versions: current Project: Jenkins Labels: plugin scm Priority: Major Reporter: Sven Keller 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [claim] (JENKINS-19820) Claim plugin serializes concurrent builds
Daniel Beck commented on JENKINS-19820 Claim plugin serializes concurrent builds Probably because of: "Claims may be made sticky to follow the user claiming the failure until the build is successful again." If build N fails and is claimed sticky, result of build N+1 needs to be known to determine whether the claim extends to N+2; so the latter cannot finish before the former. 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [claim] (JENKINS-19820) Claim plugin serializes concurrent builds
Christian Åkerström resolved JENKINS-19820 as Wont Fix Claim plugin serializes concurrent builds This issue can't be fixed without removing the sticky functionality Change By: Christian Åkerström (18/Nov/13 12:49 PM) Status: Open Resolved Resolution: WontFix 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [scm-sync-configuration] (JENKINS-20626) SCM-sync-configuration plugin: make root directory in repository configurable
Frédéric Camblor commented on JENKINS-20626 SCM-sync-configuration plugin: make root directory in repository configurable I don't think separate implementation for each SCM is necessary. Providing a new relative path at scm-sync-configuration config section (which then could be used in ScmSyncConfigBusiness. getCheckoutScmDirectoryAbsolutePath()) would be sufficient. 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jenkinswalldisplay] (JENKINS-20551) Claim border moves text out of line
SCM/JIRA link daemon commented on JENKINS-20551 Claim border moves text out of line Code changed in jenkins User: Pelle Pelster Path: src/main/webapp/walldisplay.css src/main/webapp/walldisplay.html http://jenkins-ci.org/commit/walldisplay-plugin/02c9ddb7e74d199c409a7d181ee582a5b46a53cc Log: Merge pull request #29 from howama/master JENKINS-20551 - Display improvements for claimed builds and progress views Compare: https://github.com/jenkinsci/walldisplay-plugin/compare/16f60e74be0e...02c9ddb7e74d 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [subversion] (JENKINS-19507) Jenkins runs out of threads when using SVN post commit hook with svn+ssh URL
Roland Gruber commented on JENKINS-19507 Jenkins runs out of threads when using SVN post commit hook with svn+ssh URL -Xss does not work because the problem is the number of threads (unable to create new native thread). The operating system limits the number of threads to 1024. Of course, we could increase that limit. But running multiple thousand threads in parallel with Subversion calls seems not a good idea. In my opinion, there should be a queue that executes the SVN commands. Just like the SVN configuration for polling option (e.g. max 5 parallel). 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-20625) Resurrect 'git clone --reference' in git plugin
Mark Waite resolved JENKINS-20625 as Not A Defect Resurrect git clone --reference in git plugin It is available under the "Advanced clone behaviours". You can insert a reference repository in the field there. Change By: Mark Waite (18/Nov/13 1:26 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [maven2] (JENKINS-18030) Unable to parameterized Maven module build
Adrien Vercoutere assigned JENKINS-18030 to Mads Nielsen Unable to parameterized Maven module build Change By: Adrien Vercoutere (18/Nov/13 1:43 PM) Assignee: huybrechts MadsNielsen 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [maven2] (JENKINS-18030) Unable to parameterized Maven module build
Mads Nielsen assigned JENKINS-18030 to Adrien Vercoutere Unable to parameterized Maven module build I think im not resposible for this? You might want to reassign this. Change By: Mads Nielsen (18/Nov/13 1:48 PM) Assignee: MadsNielsen AdrienVercoutere 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [claim] (JENKINS-19820) Claim plugin serializes concurrent builds
Daniel Beck commented on JENKINS-19820 Claim plugin serializes concurrent builds Christian: Would it be possible to make this conditional on sticky being enabled? 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [template-workflows] (JENKINS-20627) Updating a workflow overwrites exisiting jobs participating to the workflow
Frederic Chateau created JENKINS-20627 Updating a workflow overwrites exisiting jobs participating to the workflow Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: template-workflows Created: 18/Nov/13 2:24 PM Description: Here is a setup to reproduce the problem: Create a free-style job, with some useful setup: template-job declare it as a building block of the "test-workflow1" workflows Create a free-style job, without any useful setup (it will be associated to an existing job, it is just a placeholder): template-dependency declare it as a building block of the "test-workflow1" workflow Create a free-style job named "jobA", and configure some stuff. Create a "Template Workflow Job" named "MyWorkflows". Create a workflow named "jobB" based on "test-workflow1", with template-dependency=jobA and template-job=jobB, check "Allow the Use of Existing Jobs" Check jobB: ok Check jobA: ok Click on jobB inside MyWorkflows, click update. Check jobB: ok Check jobA: everything has been replaced by the content of the placeholder job "template-dependency" PS: Basically I experienced this problem with a more complex setup where I have one workflow for each project I work on. As most of these projects have dependencies on the others, I use some "placeholder" template jobs to inject references to upstream projects belonging to other worflows (and that have already been generated). The problem is that the upstream projects generated by other worflows get erased when I update their direct downstream workflow. So, currently, in order to fix that I need to update the whole hierarchy starting from the downstream-most projects to the upstream-most projects, which is a real pain and makes this plugin lose most of its interest (if each workflow has to work in isolation from the other workflows and projects, it greatly limits what can be done). I think it used to work fine with an older Jenkins version, but at some point, I noticed this problem. So it might have been around not since the beginning but only for a few revisions. Environment: Jenkins 1.539, Template-workflows 1.2 running on Ubuntu 12.04 LTS, Java 1.6.0_26 Project: Jenkins Priority: Major Reporter: Frederic Chateau 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [template-workflows] (JENKINS-20627) Updating a workflow overwrites exisiting jobs participating to the workflow
Frederic Chateau updated JENKINS-20627 Updating a workflow overwrites exisiting jobs participating to the workflow Change By: Frederic Chateau (18/Nov/13 2:25 PM) Description: Hereisasetuptoreproducetheproblem:Createafree-stylejob,withsomeusefulsetup:template-job*declareitasabuildingblockofthetest-workflow1workflows Createafree-stylejob,withoutanyusefulsetup(itwillbeassociatedtoanexistingjob,itisjustaplaceholder):template-dependency*declareitasabuildingblockofthetest-workflow1workflowCreateafree-stylejobnamedjobA,andconfiguresomestuff.CreateaTemplateWorkflowJobnamedMyWorkflows.CreateaworkflownamedjobBbasedontest-workflow1,withtemplate-dependency=jobAandtemplate-job=jobB,checkAllowtheUseofExistingJobsCheckjobB:okCheckjobA:okClickonjobBinsideMyWorkflows,clickupdate.CheckjobB:okCheckjobA:everythinghasbeenreplacedbythecontentoftheplaceholderjobtemplate-dependencyPS:BasicallyIexperiencedthisproblemwithamorecomplexsetupwhereIhaveoneworkflowforeachprojectIworkon.Asmostoftheseprojectshavedependenciesontheothers,Iusesomeplaceholdertemplatejobstoinjectreferencestoupstreamprojectsbelongingtootherworflows(andthathavealreadybeengenerated).TheproblemisthattheupstreamprojectsgeneratedbyotherworflowsgeterasedwhenIupdatetheirdirectdownstreamworkflow.So,currently,inordertofixthatIneedtoupdatethewholehierarchystartingfromthedownstream-mostprojectstotheupstream-mostprojects,whichisarealpainandmakesthispluginlosemostofitsinterest(ifeachworkflowhastoworkinisolationfromtheotherworkflowsandprojects,itgreatlylimitswhatcanbedone).IthinkitusedtoworkfinewithanolderJenkinsversion,butatsomepoint,Inoticedthisproblem.Soitmighthavebeenaroundnotsincethebeginningbutonlyforafewrevisions. 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [claim] (JENKINS-19820) Claim plugin serializes concurrent builds
Christian Åkerström commented on JENKINS-19820 Claim plugin serializes concurrent builds I think it is possible, although as I see it the sticky functionality is very central and something that most(if not all) users would like. A user already has the option to not use that claim plugin at all if it wants true concurrents builds. 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [maven2] (JENKINS-18030) Unable to parameterized Maven module build
Adrien Vercoutere assigned JENKINS-18030 to Kohsuke Kawaguchi Unable to parameterized Maven module build Assigning this to you, as huybrechts is MIA Change By: Adrien Vercoutere (18/Nov/13 2:33 PM) Assignee: AdrienVercoutere KohsukeKawaguchi 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-20610) FileAlreadyExistsException upon deleted symlink while (re)creating it
SCM/JIRA link daemon resolved JENKINS-20610 as Fixed FileAlreadyExistsException upon deleted symlink while (re)creating it Change By: SCM/JIRA link daemon (18/Nov/13 2:33 PM) Status: InProgress 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-20610) FileAlreadyExistsException upon deleted symlink while (re)creating it
SCM/JIRA link daemon commented on JENKINS-20610 FileAlreadyExistsException upon deleted symlink while (re)creating it Code changed in jenkins User: Jesse Glick Path: changelog.html http://jenkins-ci.org/commit/jenkins/65548d138158faff02c8000fb422080e650eeaf7 Log: JENKINS-20610 Noting merge of #1019. Compare: https://github.com/jenkinsci/jenkins/compare/1067585a4951...65548d138158 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-20610) FileAlreadyExistsException upon deleted symlink while (re)creating it
SCM/JIRA link daemon commented on JENKINS-20610 FileAlreadyExistsException upon deleted symlink while (re)creating it Code changed in jenkins User: Marco Miller Path: core/src/main/java/hudson/Util.java http://jenkins-ci.org/commit/jenkins/d0f84c2e5314eb1f6448f0aa325e75adbfba020c Log: FIXED JENKINS-20610 symlink FileAlreadyExistsException Retrying 3 times while waiting for 100 millis between retries (at recreating symlink after "deleting" it). Ends up throwing FAE exception if thrown for a 4th time in a row - as not much can be done at that point. A warning is logged in that case, prior to throwing the last FAE. 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [teamconcert] (JENKINS-18421) Teamconcert plugin to trigger Post-Build Events configured in RTC Build Definition
Scott Cowan commented on JENKINS-18421 Teamconcert plugin to trigger Post-Build Events configured in RTC Build Definition Hi Praveen, The Team Concert Plugin for Jenkins does not currently support starting post-build options in RTC. That is what this enhancement is intended to address. Would you mind detailing your build at https://jazz.net/forum and asking your questions there? You'll have a wider audience of Jazz developers to respond. 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-20610) FileAlreadyExistsException upon deleted symlink while (re)creating it
Marco Miller closed JENKINS-20610 as Fixed FileAlreadyExistsException upon deleted symlink while (re)creating it Change By: Marco Miller (18/Nov/13 3:17 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [parameters] (JENKINS-11596) File uploaded as file parameter should default to filename in the root of the workspace
Andre Stone commented on JENKINS-11596 File uploaded as file parameter should default to filename in the root of the workspace Hello @all, i have the same issue: Started by user anonymous Building in workspace C:\.jenkins\jobs\Test_file_upload\workspace Copying file to C:\TestFolder FATAL: C:\TestFolder (Access is denied) java.io.FileNotFoundException: C:\TestFolder (Access is denied) at java.io.FileOutputStream.open(Native Method) at java.io.FileOutputStream.init(Unknown Source) at java.io.FileOutputStream.init(Unknown Source) at org.apache.commons.fileupload.disk.DiskFileItem.write(DiskFileItem.java:416) at hudson.FilePath.copyFrom(FilePath.java:842) at hudson.model.FileParameterValue$2.setUp(FileParameterValue.java:140) at hudson.model.Build$BuildExecution.doRun(Build.java:154) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:562) at hudson.model.Run.execute(Run.java:1679) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:230) My Jenkins is running on a Win7. Is there any solution? Thx in Advance Andre 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-20610) FileAlreadyExistsException upon deleted symlink while (re)creating it
dogfood commented on JENKINS-20610 FileAlreadyExistsException upon deleted symlink while (re)creating it Integrated in jenkins_main_trunk #3060 FIXED JENKINS-20610 symlink FileAlreadyExistsException (Revision d0f84c2e5314eb1f6448f0aa325e75adbfba020c) JENKINS-20610 Noting merge of #1019. (Revision 65548d138158faff02c8000fb422080e650eeaf7) Result = UNSTABLE marco.miller : d0f84c2e5314eb1f6448f0aa325e75adbfba020c Files : core/src/main/java/hudson/Util.java Jesse Glick : 65548d138158faff02c8000fb422080e650eeaf7 Files : changelog.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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [slave-status] (JENKINS-19445) Jobs randomly stuck with building remotely on slave-name message
Valentin Marin edited a comment on JENKINS-19445 Jobs randomly stuck with building remotely on slave-name message So I've set Jenkins up to run on Tomcat 7 up and upgraded 'archive artifacts' plug-in to latest version for a good measure (since all of my builds are using that and it is known to be greedy with RAM) and what do you know, 3 days without stalled builds and counting. Will let you guys know if the issue indeed went away. 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [slave-status] (JENKINS-19445) Jobs randomly stuck with building remotely on slave-name message
Valentin Marin commented on JENKINS-19445 Jobs randomly stuck with building remotely on slave-name message So I've set Jenkins up to run on Tomcat 7 up and upgraded 'archive artifacts' plug-in to latest version for a good measure and what do you know, 3 days without stalled builds and counting. Will let you guys know if the issue indeed went away. 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-15796) NoClassDefFoundError in monitoring Windows slave
Oleg Nenashev commented on JENKINS-15796 NoClassDefFoundError in monitoring Windows slave Fix for https://issues.jenkins-ci.org/browse/JENKINS-19453 may resolve this issue. BTW, symptoms are quite similar 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [artifactdeployer] (JENKINS-20554) The version 0.27 of the ArtifactDeployer Plugin breaks all Maven 2 jobs
Holger Lehmann
updated JENKINS-20554
The version 0.27 of the ArtifactDeployer Plugin breaks all Maven 2 jobs
Disabling ArtifactDeployer (Artifactory) for the builds is a workaround to get, at least, Jenkins up and running again.
I will evaluate the 0.28 version today.
Change By:
Holger Lehmann
(18/Nov/13 5:10 PM)
Summary:
The
current
version
0.27
of
Jenkins
theArtifactDeployerPlugin
breaksallMaven2jobs
Description:
ThecurrentversionofJenkinsisonlycapableofrunningMaven3Tasks
whentheArtifactDeployerpluginisinstalled
.AnyMaven2Itriedfailswiththejavaexceptionfrombelow.Thisbreaks*all*ofourjobssincewedevelopAtlassianJIRA/ConfluencepluginsandthusneedAtlassiansMaven2(orequivalent).Googlingdidnotproduceanythingsuitable:-(Iwillattachanylogfilesifrequired,pleaseletmeknow.Thisfailureoccurred*after*upgradingtothelatestversionfrom(Ithink)1.531(RPM)JenkinsisrunningasuserjenkinsThisistheJavastacktrace:---{noformat}java.io.IOException:RemotecallonChanneltoMaven[java,-Djava.awt.headless=true,-cp,/var/lib/jenkins/plugins/maven-plugin/WEB-INF/lib/maven-agent-1.4.jar:/var/lib/jenkins/tools/hudson.tasks.Maven_MavenInstallation/Default_Maven_2/boot/classworlds-1.1.jar,hudson.maven.agent.Main,/var/lib/jenkins/tools/hudson.tasks.Maven_MavenInstallation/Default_Maven_2,/tmp/jetty-0.0.0.0-9080-jenkins.war-_jenkins-any-/webapp/WEB-INF/lib/remoting-2.32.jar,/var/lib/jenkins/plugins/maven-plugin/WEB-INF/lib/maven-interceptor-1.4.jar,58820,/var/lib/jenkins/plugins/maven-plugin/WEB-INF/lib/maven2.1-interceptor-1.2.jar]failed athudson.remoting.Channel.call(Channel.java:723) athudson.maven.ProcessCache$MavenProcess.call(ProcessCache.java:160) athudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:823) athudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:562) athudson.model.Run.execute(Run.java:1679) athudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:509) athudson.model.ResourceController.execute(ResourceController.java:88) athudson.model.Executor.run(Executor.java:230)Causedby:java.lang.LinkageError:loaderconstraintviolation:loader(instanceoforg/codehaus/classworlds/RealmClassLoader)previouslyinitiatedloadingforadifferenttypewithnameorg/codehaus/plexus/configuration/PlexusConfiguration atjava.lang.ClassLoader.defineClass1(NativeMethod) atjava.lang.ClassLoader.defineClassCond(ClassLoader.java:631) atjava.lang.ClassLoader.defineClass(ClassLoader.java:615) atjava.security.SecureClassLoader.defineClass(SecureClassLoader.java:141) atjava.net.URLClassLoader.defineClass(URLClassLoader.java:283) atjava.net.URLClassLoader.access$000(URLClassLoader.java:58) atjava.net.URLClassLoader$1.run(URLClassLoader.java:197) atjava.security.AccessController.doPrivileged(NativeMethod) atjava.net.URLClassLoader.findClass(URLClassLoader.java:190) atjava.lang.ClassLoader.loadClass(ClassLoader.java:306) atorg.codehaus.classworlds.RealmClassLoader.loadClassDirect(RealmClassLoader.java:195) atorg.codehaus.classworlds.DefaultClassRealm.loadClass(DefaultClassRealm.java:255) atorg.codehaus.classworlds.RealmClassLoader.loadClass(RealmClassLoader.java:214) atjava.lang.ClassLoader.loadClass(ClassLoader.java:247) atjava.lang.Class.getDeclaredMethods0(NativeMethod) atjava.lang.Class.privateGetDeclaredMethods(Class.java:2436) atjava.lang.Class.getMethod0(Class.java:2679) atjava.lang.Class.getMethod(Class.java:1605) athudson.maven.MavenBuilder.callSetListenerWithReflectOnInterceptors(MavenBuilder.java:211) athudson.maven.MavenBuilder.callSetListenerWithReflectOnInterceptorsQuietly(MavenBuilder.java:231) athudson.maven.MavenBuilder.call(MavenBuilder.java:199) athudson.maven.Maven2Builder.call(Maven2Builder.java:79) athudson.maven.Maven2Builder.call(Maven2Builder.java:55) athudson.remoting.UserRequest.perform(UserRequest.java:118) athudson.remoting.UserRequest.perform(UserRequest.java:48) athudson.remoting.Request$2.run(Request.java:326) athudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) atjava.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
[JIRA] [artifactory] (JENKINS-20554) The version 2.2.1 of the Artifactory Plugin breaks all Maven 2 jobs
Holger Lehmann edited a comment on JENKINS-20554 The version 2.2.1 of the Artifactory Plugin breaks all Maven 2 jobs (void) 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [artifactory] (JENKINS-20554) The version 2.2.1 of the Artifactory Plugin breaks all Maven 2 jobs
Holger Lehmann updated JENKINS-20554 The version 2.2.1 of the Artifactory Plugin breaks all Maven 2 jobs Change By: Holger Lehmann (18/Nov/13 5:14 PM) Component/s: artifactdeployer This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [artifactory] (JENKINS-20554) The version 2.2.1 of the Artifactory Plugin breaks all Maven 2 jobs
Holger Lehmann
updated JENKINS-20554
The version 2.2.1 of the Artifactory Plugin breaks all Maven 2 jobs
Proir to the upgrade I had 2.1.8 installed
Change By:
Holger Lehmann
(18/Nov/13 5:13 PM)
Summary:
Theversion
0
2
.
27
2.1
ofthe
ArtifactDeployer
Artifactory
PluginbreaksallMaven2jobs
Description:
ThecurrentversionofJenkinsisonlycapableofrunningMaven3Taskswhenthe
ArtifactDeployerplugin
ArtifactoryPluginversion2.2.1
isinstalled.AnyMaven2Itriedfailswiththejavaexceptionfrombelow.Thisbreaks*all*ofourjobssincewedevelopAtlassianJIRA/ConfluencepluginsandthusneedAtlassiansMaven2(orequivalent).Googlingdidnotproduceanythingsuitable:-(Iwillattachanylogfilesifrequired,pleaseletmeknow.Thisfailureoccurred*after*upgradingtothelatestversionfrom(Ithink)1.531(RPM)JenkinsisrunningasuserjenkinsThisistheJavastacktrace:---{noformat}java.io.IOException:RemotecallonChanneltoMaven[java,-Djava.awt.headless=true,-cp,/var/lib/jenkins/plugins/maven-plugin/WEB-INF/lib/maven-agent-1.4.jar:/var/lib/jenkins/tools/hudson.tasks.Maven_MavenInstallation/Default_Maven_2/boot/classworlds-1.1.jar,hudson.maven.agent.Main,/var/lib/jenkins/tools/hudson.tasks.Maven_MavenInstallation/Default_Maven_2,/tmp/jetty-0.0.0.0-9080-jenkins.war-_jenkins-any-/webapp/WEB-INF/lib/remoting-2.32.jar,/var/lib/jenkins/plugins/maven-plugin/WEB-INF/lib/maven-interceptor-1.4.jar,58820,/var/lib/jenkins/plugins/maven-plugin/WEB-INF/lib/maven2.1-interceptor-1.2.jar]failed athudson.remoting.Channel.call(Channel.java:723) athudson.maven.ProcessCache$MavenProcess.call(ProcessCache.java:160) athudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:823) athudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:562) athudson.model.Run.execute(Run.java:1679) athudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:509) athudson.model.ResourceController.execute(ResourceController.java:88) athudson.model.Executor.run(Executor.java:230)Causedby:java.lang.LinkageError:loaderconstraintviolation:loader(instanceoforg/codehaus/classworlds/RealmClassLoader)previouslyinitiatedloadingforadifferenttypewithnameorg/codehaus/plexus/configuration/PlexusConfiguration atjava.lang.ClassLoader.defineClass1(NativeMethod) atjava.lang.ClassLoader.defineClassCond(ClassLoader.java:631) atjava.lang.ClassLoader.defineClass(ClassLoader.java:615) atjava.security.SecureClassLoader.defineClass(SecureClassLoader.java:141) atjava.net.URLClassLoader.defineClass(URLClassLoader.java:283) atjava.net.URLClassLoader.access$000(URLClassLoader.java:58) atjava.net.URLClassLoader$1.run(URLClassLoader.java:197) atjava.security.AccessController.doPrivileged(NativeMethod) atjava.net.URLClassLoader.findClass(URLClassLoader.java:190) atjava.lang.ClassLoader.loadClass(ClassLoader.java:306) atorg.codehaus.classworlds.RealmClassLoader.loadClassDirect(RealmClassLoader.java:195) atorg.codehaus.classworlds.DefaultClassRealm.loadClass(DefaultClassRealm.java:255) atorg.codehaus.classworlds.RealmClassLoader.loadClass(RealmClassLoader.java:214) atjava.lang.ClassLoader.loadClass(ClassLoader.java:247) atjava.lang.Class.getDeclaredMethods0(NativeMethod) atjava.lang.Class.privateGetDeclaredMethods(Class.java:2436) atjava.lang.Class.getMethod0(Class.java:2679) atjava.lang.Class.getMethod(Class.java:1605) athudson.maven.MavenBuilder.callSetListenerWithReflectOnInterceptors(MavenBuilder.java:211) athudson.maven.MavenBuilder.callSetListenerWithReflectOnInterceptorsQuietly(MavenBuilder.java:231) athudson.maven.MavenBuilder.call(MavenBuilder.java:199) athudson.maven.Maven2Builder.call(Maven2Builder.java:79) athudson.maven.Maven2Builder.call(Maven2Builder.java:55) athudson.remoting.UserRequest.perform(UserRequest.java:118) athudson.remoting.UserRequest.perform(UserRequest.java:48) athudson.remoting.Request$2.run(Request.java:326) athudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) atjava.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) atjava.util.concurrent.FutureTask.run(FutureTask.java:138)
[JIRA] [core] (JENKINS-20628) Downstream builds are triggered before archiving is finished
chris_mh3 created JENKINS-20628 Downstream builds are triggered before archiving is finished Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: core Created: 18/Nov/13 5:42 PM Description: I have a job that archives a large artifact (a zip file). The build also triggers a downstream job that fetches the artifact via ANT (get...). Since about 1.537 the artifact is often the old one, not the last succesfull build. Project: Jenkins Priority: Major Reporter: chris_mh3 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-20629) Multiconfig build fails even though individual jobs passed
Will Daly created JENKINS-20629 Multiconfig build fails even though individual jobs passed Issue Type: Bug Assignee: Unassigned Attachments: System Information [Jenkins].pdf Components: core Created: 18/Nov/13 5:52 PM Description: Upgrading from Jenkins 1.530 to 1.539 caused an issue for a multiconfig job that used ssh slaves (through the EC2 plugin). I observed: 1) The multiconfig job reported status failure even though all the individual jobs passed. 2) Individual jobs reported status failure even though the console output reported status passed. 3) Individual jobs reported status failure before the job finished; the console output continued to update even though the job had failed. I've attached the system information, including the installed plugins. Once I downgraded to 1.530, the issue stopped occurring. Project: Jenkins Priority: Major Reporter: Will Daly 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-20628) Downstream builds are triggered before archiving is finished
chris_mh3 updated JENKINS-20628 Downstream builds are triggered before archiving is finished Change By: chris_mh3 (18/Nov/13 5:52 PM) Description: Ihaveajobthatarchivesalargeartifact(azipfile).ThebuildalsotriggersadownstreamjobthatfetchestheartifactviaANT(get...).Sinceabout1.537theartifactisoftentheoldone,notthelastsuccesfullbuild. Thearchivingjobisamavenproject.ThearchivingisdoneinaPost-buildActionthatisbeforetheBuildotherprojectsaction. 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [transifex] (JENKINS-20432) Configure location of tx client
SCM/JIRA link daemon commented on JENKINS-20432 Configure location of tx client Code changed in jenkins User: Hakan Tandogan Path: src/main/java/com/gurkensalat/jenkinsci/plugins/transifex/TransifexTool.java src/main/resources/com/gurkensalat/jenkinsci/plugins/transifex/Messages.properties src/main/resources/com/gurkensalat/jenkinsci/plugins/transifex/TransifexTool/config.jelly src/main/resources/com/gurkensalat/jenkinsci/plugins/transifex/TransifexTool/config.properties src/main/resources/com/gurkensalat/jenkinsci/plugins/transifex/TransifexTool/global.jelly src/main/resources/com/gurkensalat/jenkinsci/plugins/transifex/TransifexTool/help-home.html http://jenkins-ci.org/commit/transifex-plugin/97f4318b1051519dd6d723b41d1e0c0aaa19fbca Log: JENKINS-20432 - Configurable tx client 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-20630) Jenkins fails to start
Matt Kraai created JENKINS-20630 Jenkins fails to start Issue Type: Bug Assignee: Unassigned Attachments: jenkins 1.539.err.log, jenkins 1.540.err.log Components: core Created: 18/Nov/13 5:59 PM Description: When I try to start Jenkins 1.540, it attempts to do so and eventually fails. When it fails, it tries to start again, which then fails. This repeats indefinitely. I've attached a log file from one such iteration. I am able to start 1.539 successfully. I've attached the log file from this as well. Environment: Microsoft Windows Server 2003 R2 Project: Jenkins Priority: Major Reporter: Matt Kraai 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-20630) Jenkins fails to start
Matt Kraai updated JENKINS-20630 Jenkins fails to start Change By: Matt Kraai (18/Nov/13 6:07 PM) Attachment: hs_err_pid1788.log 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [testlink] (JENKINS-20587) TAP result seeker filters files with a fixed char
SCM/JIRA link daemon commented on JENKINS-20587 TAP result seeker filters files with a fixed char Code changed in jenkins User: Bruno P. Kinoshita Path: pom.xml src/main/java/hudson/plugins/testlink/result/TAPFileNameResultSeeker.java http://jenkins-ci.org/commit/testlink-plugin/6bfecb9b85945fd552e1531241fce35432cd687a Log: Merge pull request #11 from witokondoria/JENKINS-20587 FIXED JENKINS-20587 Compare: https://github.com/jenkinsci/testlink-plugin/compare/aff9bdef7def...6bfecb9b8594 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [sectioned-view] (JENKINS-20631) View Listing Section shows only current level's sections for Nested View
Aleksandr Baramykov created JENKINS-20631 View Listing Section shows only current levels sections for Nested View Issue Type: Bug Affects Versions: current Assignee: Timothy Bingaman Attachments: comparison.png Components: sectioned-view Created: 18/Nov/13 6:31 PM Description: If current view is a subview of the Nested View then View Listing Section doesn't allow select all views tree but only siblings of the current view. Example. Views structure: Group1 Group1_view1 Group1_view2 Group2 Group2_view1 Group2_view2 If you try to add View Listing section to the Group1_view1 - only Group1_view1 and Group1_view2 are allowed to show. Aattached screenshot shows how this example looks in v.1.17 and v.1.18. Environment: Win 2003 server Jenkins 1.509.4 SectionedView 1.18 NestedView 1.10 Project: Jenkins Priority: Major Reporter: Aleksandr Baramykov 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [copyartifact] (JENKINS-14999) Copy Artifact plugin: Unable to find project for artifact copy when using a build parameter
ikedam reopened JENKINS-14999 Copy Artifact plugin: Unable to find project for artifact copy when using a build parameter As described in https://github.com/jenkinsci/copyartifact-plugin/pull/24 , we should resolve this issue using QueueItemAuthenticater. Above commits are merged by some accidents, and should be reverted. Change By: ikedam (18/Nov/13 6:34 PM) Resolution: Fixed 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [promoted-builds] (JENKINS-20166) Promoted Build NullPointer when not manual promotion
Bruce Edge commented on JENKINS-20166 Promoted Build NullPointer when not manual promotion Still waiting for 2.15 to show up on the jenkins plugin updater. Does this need a push to get propagated? 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [managed-scripts] (JENKINS-17766) Support git(scm) revision control for managed files
Sam Xiao edited a comment on JENKINS-17766 Support git(scm) revision control for managed files +1 for this. It would be nice to allow it to integrate with Github or something. 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [managed-scripts] (JENKINS-17766) Support git(scm) revision control for managed files
Sam Xiao commented on JENKINS-17766 Support git(scm) revision control for managed files +1 for 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [coverity] (JENKINS-20632) Conditionally execute Coverity plugin fails during publish.
Greg Domjan
created JENKINS-20632
Conditionally execute Coverity plugin fails during publish.
Issue Type:
Bug
Affects Versions:
current
Assignee:
bap
Components:
coverity, flexible-publish
Created:
18/Nov/13 7:22 PM
Description:
Had a project with Coverity plugin installed and configured, successfully publishing results.
Tried to make it conditional following instructions "importing existing publishers" https://wiki.jenkins-ci.org/display/JENKINS/Flexible+Publish+Plugin
```
import static org.jenkins_ci.plugins.flexible_publish.JobUpdater.*
def job = hudson.model.Hudson.instance.getItem('modulesJavaDatastore')
list job
movePublisher job,'Coverity'
list job
```
Maven build completed successfully, then follows following exception in console log.
Strings match run condition: string 1=clean, string 2=clean
Run condition Strings match enabling perform for step Coverity
ERROR: Publisher org.jenkins_ci.plugins.flexible_publish.FlexiblePublisher aborted due to exception
java.lang.NullPointerException
at jenkins.plugins.coverity.CoverityPublisher.perform(CoverityPublisher.java:404)
at org.jenkins_ci.plugins.run_condition.BuildStepRunner$2.run(BuildStepRunner.java:110)
at org.jenkins_ci.plugins.run_condition.BuildStepRunner$DontRun.conditionalRun(BuildStepRunner.java:264)
at org.jenkins_ci.plugins.run_condition.BuildStepRunner.perform(BuildStepRunner.java:105)
at org.jenkins_ci.plugins.flexible_publish.ConditionalPublisher.perform(ConditionalPublisher.java:134)
at org.jenkins_ci.plugins.flexible_publish.FlexiblePublisher.perform(FlexiblePublisher.java:111)
at hudson.tasks.BuildStepMonitor$2.perform(BuildStepMonitor.java:32)
at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:782)
at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:754)
at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.post2(MavenModuleSetBuild.java:1020)
at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:707)
at hudson.model.Run.execute(Run.java:1690)
at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:509)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:246)
WARNINGS Skipping publisher since build result is FAILURE
Environment:
Jenkins ver. 1.533, Windows 2008 R2 64.
Maven style job, maven 2.2.1
cygwin present
Project:
Jenkins
Labels:
plugin
exception
Priority:
Major
Reporter:
Greg Domjan
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
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [coverity] (JENKINS-20633) Configuration, Provide indication of dynamic content/download action while retrieving Project(s), Stream(s) and Filters
Greg Domjan created JENKINS-20633 Configuration, Provide indication of dynamic content/download action while retrieving Project(s), Stream(s) and Filters Issue Type: Improvement Affects Versions: current Assignee: Unassigned Components: coverity Created: 18/Nov/13 7:56 PM Description: After selecting a new Integrity Manager Instance it can several minutes before the Projects are downloaded. There is a further significant delay on selecting a Project before the relevant streams are available to select, and similarly a delay in selecting a stream before the filters section is updated. While getting this dynamic content the Project/Stream list and filters section all appear empty and no indication that they will be filled, when or how. Perhaps Stream and filter download should be more lazily done as it appears on selecting the CIM the first Project, first stream and related filters are all selected which could be taking additional time. Environment: Jenkins ver. 1.533 Project: Jenkins Priority: Major Reporter: Greg Domjan 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [promoted-builds] (JENKINS-20634) promoted builds plugin copying wrong build job artifacts
Bruce Edge created JENKINS-20634 promoted builds plugin copying wrong build job artifacts Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: promoted-builds Created: 18/Nov/13 7:56 PM Description: If I want a build to promote immediately after completion, the promotion will block on queued up builds of the same job. IOW, if I start a build of job foo, with automated promotion on completion, then, while the foo build is running, another foo job gets queued up, the promotion for the first job will not run until the queued up foo build also completes. And then, it copies the artifacts from the last completed build rather than the one prior. I'm using 'spec by permalink' and 'latest promotion'. So there are 2 problems here. 1) promotion blocks on queued builds of same job 2) promotion copies wring artifacts. Note this is with 2.13 as 2.14 has the NPE bug that renders it unusable. Environment: Ubuntu 13.10 64 bit Jenkins 1.539 Project: Jenkins Priority: Major Reporter: Bruce Edge 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [customtools-plugin] (JENKINS-20635) Add Run Command for Windows
Ronen Peleg created JENKINS-20635 Add Run Command for Windows Issue Type: Task Assignee: Oleg Nenashev Components: customtools-plugin Created: 18/Nov/13 8:27 PM Description: Hi, As I understand and checked, The current "Run Command" option work only on Linux (ssh/shell) OS. It will be great if you can add "Run Command" for Windows (cmd) OS. Thanks, Ronen. Environment: Jenkins Master on Linux machine with Windows 2008 slave machine Project: Jenkins Priority: Major Reporter: Ronen Peleg 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [promoted-builds] (JENKINS-20166) Promoted Build NullPointer when not manual promotion
Mads Mohr Christensen commented on JENKINS-20166 Promoted Build NullPointer when not manual promotion I don't think that this has been merged and that 2.15 has been released yet. 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-20607) GIT Plugin 2.0: Polling ignores commit from certain users not working
Carl von Buelow commented on JENKINS-20607 GIT Plugin 2.0: Polling ignores commit from certain users not working Having the same issue. Also, the "Polling ignores commits in certain paths" feature is not working as well. 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [nodejs] (JENKINS-20636) RVM and NodeJS plugins are incompatible
Ben Butler-Cole
updated JENKINS-20636
RVM and NodeJS plugins are incompatible
Change By:
Ben Butler-Cole
(18/Nov/13 9:18 PM)
Description:
WhenboththeNodeJSandRVMpluginsareenabledforasinglebuild,thebuildfailstorun.ItappearsthatthePATHaccessibletotheRVMpluginwhenitissettinguptheenvironmentisincorrect.
Wehaveusedeachofthepluginsseparatelyinourenvironmentandtheyworkfine.
Hereisexampleoutputfromabuildwithnothingdefinedinitapartfromenablingthetwoplugins.
Wehaveusedeachofthepluginsseparatelyinourenvironmentandtheyworkfine.
{code}StartedbyuserBenButler-Cole[EnvInject]-Loadingnodeenvironmentvariables.Buildingremotelyoncivm02inworkspace/var/tmp/workspace/bbc-testCapturingenvironmentvariablesproducedbyrvmuse1.9.3@release$bash-cexport$bash-ctest-f~/.rvm/scripts/rvm[bbc-test]$bash-csource~/.rvm/scripts/rvmrvmuse--install--create1.9.3@releaseexportrvm.env/home/ubuntu/.rvm/scripts/rvm:line67:dirname:commandnotfound/home/ubuntu/.rvm/scripts/rvm:line96:dirname:commandnotfoundERROR:Missingproperwhichcommand.MakesureitisinstalledbeforeusingRVM!ERROR:FailedtosetupRVMenvironment[BFA]Scanningbuildforknowncauses...[BFA]Done.0sNotifyingupstreamprojectsofjobcompletionFinished:FAILURE{code}Ihaveattachedthesysteminfoforoursystem.
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
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [nodejs] (JENKINS-20636) RVM and NodeJS plugins are incompatible
Ben Butler-Cole created JENKINS-20636 RVM and NodeJS plugins are incompatible Issue Type: Bug Assignee: Unassigned Attachments: systemInfo.txt Components: nodejs, rvm Created: 18/Nov/13 9:17 PM Description: When both the NodeJS and RVM plugins are enabled for a single build, the build fails to run. It appears that the PATH accessible to the RVM plugin when it is setting up the environment is incorrect. Here is example output from a build with nothing defined in it apart from enabling the two plugins. We have used each of the plugins separately in our environment and they work fine. Started by user Ben Butler-Cole [EnvInject] - Loading node environment variables. Building remotely on civm02 in workspace /var/tmp/workspace/bbc-test Capturing environment variables produced by 'rvm use 1.9.3@release' $ bash -c export $ bash -c "test -f ~/.rvm/scripts/rvm" [bbc-test] $ bash -c " source ~/.rvm/scripts/rvm rvm use --install --create 1.9.3@release export rvm.env" /home/ubuntu/.rvm/scripts/rvm: line 67: dirname: command not found /home/ubuntu/.rvm/scripts/rvm: line 96: dirname: command not found ERROR: Missing proper 'which' command. Make sure it is installed before using RVM! ERROR: Failed to setup RVM environment [BFA] Scanning build for known causes... [BFA] Done. 0s Notifying upstream projects of job completion Finished: FAILURE I have attached the system info for our system. Environment: U Project: Jenkins Priority: Major Reporter: Ben Butler-Cole 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jenkinswalldisplay] (JENKINS-20551) Claim border moves text out of line
howama resolved JENKINS-20551 as Fixed Claim border moves text out of line Change By: howama (18/Nov/13 9:19 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [ssh-credentials] (JENKINS-20637) SSH Keys are only usable on master, not replicated on slaves
Florian Zschocke created JENKINS-20637 SSH Keys are only usable on master, not replicated on slaves Issue Type: Bug Affects Versions: current Assignee: stephenconnolly Components: ssh-credentials Created: 18/Nov/13 9:26 PM Description: Adding a SSH key credential enables an executor on the master to use the credential for cloning a Git repository via SSH using the provided credentials. The private key is stored in ~/.ssh of the Jenkins user. Running the same job on a SSH slave, the expectation is that this will work as on the master without any further configuration action. This is not the case, the job will fail with the following in the log: stdout: Cloning into '/home/jenkins/workspace/Begin_Release'... stderr: Permission denied, please try again. Permission denied, please try again. Permission denied (publickey,password). fatal: The remote end hung up unexpectedly I would expect the SSH key credentials to be transferred to the slave so that they can be used there, too. Instead, the private key has to be installed in the ~/.ssh directory on the slave, too. Project: Jenkins Priority: Major Reporter: Florian Zschocke 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [ssh-credentials] (JENKINS-20638) SSH key credential doesn't work with key passphrase
Florian Zschocke created JENKINS-20638 SSH key credential doesnt work with key passphrase Issue Type: Bug Affects Versions: current Assignee: stephenconnolly Components: ssh-credentials Created: 18/Nov/13 9:31 PM Description: I added a SSH key credential with a passphrase set on the key. This credential was used in a job as credentials for a Git clone via ssh. The job was not able to execute the Git clone. It failed with the following error in the log: stdout: Cloning into '/var/lib/jenkins/jobs/Begin_Release/workspace'... stderr: Permission denied, please try again. Permission denied, please try again. Permission denied (publickey,password). fatal: The remote end hung up unexpectedly Inspecting the SSH log on the repository server revealed that the publickey method was never attempted. Executing the command as the Jenkins user from the commandline worked. This could only resolved by removing the passphrase from the key after which the job was able to clone the repository and execute as expected. Project: Jenkins Priority: Major Reporter: Florian Zschocke 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-20639) Jenkins is very slow and something hit proxy error when opening a configuration page
Sam Xiao created JENKINS-20639 Jenkins is very slow and something hit proxy error when opening a configuration page Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: core Created: 18/Nov/13 9:33 PM Description: Jenkins version: 1.539 WARNING: /job/ABC/buildHistory/ajax org.apache.commons.jelly.JellyTagException: jar:file:/tmp/jetty-127.0.0.1-8080-jenkins.war--any-/webapp/WEB-INF/lib/jenkins-core-1.539.jar!/lib/layout/layout.jelly:75:72: st:include finished at org.apache.commons.jelly.impl.TagScript.handleException(TagScript.java:726) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:279) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161) at org.apache.commons.jelly.tags.core.ForEachTag.doTag(ForEachTag.java:150) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$1.run(CoreTagLibrary.java:98) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.JellyViewScript.run(JellyViewScript.java:81) at org.kohsuke.stapler.jelly.DefaultScriptInvoker.invokeScript(DefaultScriptInvoker.java:63) at org.kohsuke.stapler.jelly.DefaultScriptInvoker.invokeScript(DefaultScriptInvoker.java:53) at org.kohsuke.stapler.jelly.JellyFacet$1.dispatch(JellyFacet.java:95) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:631) at hudson.init.impl.InstallUncaughtExceptionHandler$1.reportException(InstallUncaughtExceptionHandler.java:25) at org.kohsuke.stapler.compression.CompressionFilter.reportException(CompressionFilter.java:63) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:49) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1474) at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:499) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:137) at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:533) at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:231) at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1086) at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:428) at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:193) at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1020) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:135) at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:116) at org.eclipse.jetty.server.Server.handle(Server.java:370) at org.eclipse.jetty.server.AbstractHttpConnection.handleRequest(AbstractHttpConnection.java:489) at org.eclipse.jetty.server.AbstractHttpConnection.headerComplete(AbstractHttpConnection.java:949) at org.eclipse.jetty.server.AbstractHttpConnection$RequestHandler.headerComplete(AbstractHttpConnection.java:1011) at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:644) at org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:235) at org.eclipse.jetty.server.AsyncHttpConnection.handle(AsyncHttpConnection.java:82) at org.eclipse.jetty.io.nio.SelectChannelEndPoint.handle(SelectChannelEndPoint.java:668) at
[JIRA] [throttle-concurrents] (JENKINS-19986) Throttle Concurrent Builds plugin doesn't appear to work
Jon Hyman commented on JENKINS-19986 Throttle Concurrent Builds plugin doesnt appear to work Same here - it seems to have broken after updating from Jenkins 1.533 to 1.539. I tried updating to 1.540 to see if that fixes it but it is still broken. 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-20640) Jenkins become very slow and had 'proxy error'
Sam Xiao created JENKINS-20640 Jenkins become very slow and had proxy error Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: core, monitoring Created: 18/Nov/13 9:40 PM Description: Jenkins version : 1.539 Proxy Error The proxy server received an invalid response from an upstream server. The proxy server could not handle the request GET /monitoring. Reason: Error reading from remote server WARNING: /monitoring org.apache.commons.jelly.JellyTagException: jar:file:/tmp/jetty-127.0.0.1-8080-jenkins.war--any-/webapp/WEB-INF/lib/jenkins-core-1.539.jar!/lib/layout/layout.jelly:75:72: st:include org.eclipse.jetty.io.EofException at org.apache.commons.jelly.impl.TagScript.handleException(TagScript.java:726) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:279) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161) at org.apache.commons.jelly.tags.core.ForEachTag.doTag(ForEachTag.java:150) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$1.run(CoreTagLibrary.java:98) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.JellyViewScript.run(JellyViewScript.java:81) at org.kohsuke.stapler.jelly.DefaultScriptInvoker.invokeScript(DefaultScriptInvoker.java:63) at org.kohsuke.stapler.jelly.DefaultScriptInvoker.invokeScript(DefaultScriptInvoker.java:53) at org.kohsuke.stapler.jelly.JellyFacet$1.dispatch(JellyFacet.java:95) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:631) at hudson.init.impl.InstallUncaughtExceptionHandler$1.reportException(InstallUncaughtExceptionHandler.java:25) at org.kohsuke.stapler.compression.CompressionFilter.reportException(CompressionFilter.java:63) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:49) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1474) at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:499) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:137) at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:533) at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:231) at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1086) at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:428) at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:193) at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1020) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:135) at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:116) at org.eclipse.jetty.server.Server.handle(Server.java:370) at org.eclipse.jetty.server.AbstractHttpConnection.handleRequest(AbstractHttpConnection.java:489) at org.eclipse.jetty.server.AbstractHttpConnection.headerComplete(AbstractHttpConnection.java:949) at
[JIRA] [jenkinswalldisplay] (JENKINS-13556) Unprintable character in executor name in JSON API output
howama resolved JENKINS-13556 as Duplicate Unprintable character in executor name in JSON API output Seem to be a duplicate of JENKINS-13865, which is fixed Change By: howama (18/Nov/13 9:41 PM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jenkinswalldisplay] (JENKINS-18987) View crashes when last known failure does not exist
howama commented on JENKINS-18987 View crashes when last known failure does not exist Do you have the _javascript_ error for this or results of the json api call? This sounds like an error with core jenkins rather than the plugin 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [throttle-concurrents] (JENKINS-19986) Throttle Concurrent Builds plugin doesn't appear to work
Marcel Beister commented on JENKINS-19986 Throttle Concurrent Builds plugin doesnt appear to work at least I'm not the only one 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jenkinswalldisplay] (JENKINS-16657) Wall Display JS Error: Cannot read property 'claimed' of null
howama resolved JENKINS-16657 as Fixed Wall Display JS Error: Cannot read property claimed of null Change By: howama (18/Nov/13 9:44 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jenkinswalldisplay] (JENKINS-16370) Deleting oldest build, deletes the build but not removes the link and results in 404 error
howama resolved JENKINS-16370 as Incomplete Deleting oldest build, deletes the build but not removes the link and results in 404 error The wall display plugin doesn't include any functionality to delete a build. Please could you give more details of the location of links that you clicked on to delete the build and then to view the build Change By: howama (18/Nov/13 9:46 PM) Status: Open Resolved Resolution: Incomplete 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-13381) NPE from GitTool.onLoaded
Axel Uhl commented on JENKINS-13381 NPE from GitTool.onLoaded Am on Jenkins 1.540 and am seeing the same problem. analysis-collector isn't installed, the "Dashboard view" plugin is available. Installing it didn't help. Here again goes the exception I'm seeing after restart: org.jvnet.hudson.reactor.ReactorException: java.lang.Error: java.lang.reflect.InvocationTargetException at org.jvnet.hudson.reactor.Reactor.execute(Reactor.java:269) at jenkins.InitReactorRunner.run(InitReactorRunner.java:43) at jenkins.model.Jenkins.executeReactor(Jenkins.java:915) at jenkins.model.Jenkins.init(Jenkins.java:811) at hudson.model.Hudson.init(Hudson.java:81) at hudson.model.Hudson.init(Hudson.java:77) at hudson.WebAppMain$3.run(WebAppMain.java:221) Caused by: java.lang.Error: java.lang.reflect.InvocationTargetException at hudson.init.TaskMethodFinder.invoke(TaskMethodFinder.java:109) at hudson.init.TaskMethodFinder$TaskImpl.run(TaskMethodFinder.java:169) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282) at jenkins.model.Jenkins$7.runTask(Jenkins.java:904) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:722) Caused by: java.lang.reflect.InvocationTargetException 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:601) at hudson.init.TaskMethodFinder.invoke(TaskMethodFinder.java:105) ... 8 more Caused by: java.lang.NullPointerException at hudson.plugins.git.GitTool.onLoaded(GitTool.java:105) ... 13 more This problem has been going on for months now. Guys... we need this git support! 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [throttle-concurrents] (JENKINS-19986) Throttle Concurrent Builds plugin doesn't appear to work
abayer commented on JENKINS-19986 Throttle Concurrent Builds plugin doesnt appear to work Sorry, I haven't looked at newer versions of Jenkins lately - I'll try to give this a look in the next week. 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jenkinswalldisplay] (JENKINS-16857) Doesn't list all builds
howama commented on JENKINS-16857 Doesnt list all builds This always works fine for me - the wall display shows the same as the list views. Can anyone else confirm this bug or add more details? 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jenkinswalldisplay] (JENKINS-20552) Show system messages
SCM/JIRA link daemon commented on JENKINS-20552 Show system messages Code changed in jenkins User: Mark Howard Path: src/main/webapp/walldisplay.js http://jenkins-ci.org/commit/walldisplay-plugin/3f6663f615a39a3cd62088daae1b34dd9a63256a Log: JENKINS-20552: ensure shutdown message is based on json response 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jenkinswalldisplay] (JENKINS-16180) Make paintInterval configurable via URL
howama resolved JENKINS-16180 as Fixed Make paintInterval configurable via URL See previous commit comment. Also works via the jenkinsPaintInterval= query parameter Change By: howama (18/Nov/13 9:47 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [throttle-concurrents] (JENKINS-19986) Throttle Concurrent Builds plugin doesn't appear to work
Marcel Beister commented on JENKINS-19986 Throttle Concurrent Builds plugin doesnt appear to work That would be great! Thanks a lot... 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-20630) Jenkins fails to start
Michael H. edited a comment on JENKINS-20630 Jenkins fails to start Jenkins 1.540 also fails to start for me. I am running it on Windows 7 x64 as a Service. While 1.539 starts up fine 1.540 just dies at some point. I cannot find anything related to it in any of the log 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-20630) Jenkins fails to start
Michael H. commented on JENKINS-20630 Jenkins fails to start Jenkins 1.540 also fails to start for me. I am running it on Windows 8 x64 as a Service. While 1.539 starts up fine 1.540 just dies at some point. I cannot find anything related to it in any of the log 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jenkinswalldisplay] (JENKINS-20552) Show system messages
SCM/JIRA link daemon commented on JENKINS-20552 Show system messages Code changed in jenkins User: Mark Howard Path: src/main/webapp/walldisplay.css src/main/webapp/walldisplay.js http://jenkins-ci.org/commit/walldisplay-plugin/7c6641190cde4e4bb180f143f5f2727b848d0f24 Log: JENKINS-20552: Add jenkins is going to shut down message 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-20183) NPE for email-ext with =1.535
Alex Earl commented on JENKINS-20183 NPE for email-ext with =1.535 Sadly, you may have to setup each job again. There was a change in a version of core that basically wiped out the configuration for email-ext triggers. 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-20630) Jenkins fails to start
Michael H. commented on JENKINS-20630 Jenkins fails to start All clean install on another Windows-7 machine using the 1.540 installer also fails for me. So it cannot be related to an old Jenkins installation. 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-20630) Jenkins fails to start
Michael H. edited a comment on JENKINS-20630 Jenkins fails to start A clean install on another Windows-7 machine using the 1.540 installer also fails for me. So it cannot be related to an old Jenkins installation. 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [build-timeout] (JENKINS-7832) Hudson build time is calculated from the time job enters the queue while it should be when job actually starts to run
Eric Griswold commented on JENKINS-7832 Hudson build time is calculated from the time job enters the queue while it should be when job actually starts to run I tried to duplicate this problem on 1.509.1 but was unable to do so. 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [build-timeout] (JENKINS-7832) Hudson build time is calculated from the time job enters the queue while it should be when job actually starts to run
Eric Griswold edited a comment on JENKINS-7832 Hudson build time is calculated from the time job enters the queue while it should be when job actually starts to run I tried to duplicate this problem on Jenkins 1.509.1 but was unable to do so. 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-20641) Jenkins and jenkins plugins not available for download via HTTPS
Kohsuke Kawaguchi commented on JENKINS-20641 Jenkins and jenkins plugins not available for download via HTTPS I'm moving this to the public project since this issue doesn't discuss vulnerability. 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-20641) Jenkins and jenkins plugins not available for download via HTTPS
Kohsuke Kawaguchi moved JENKINS-20641 Jenkins and jenkins plugins not available for download via HTTPS Change By: Kohsuke Kawaguchi (18/Nov/13 11:47 PM) Project: SecurityIssues Jenkins Key: SECURITY JENKINS - 99 20641 Workflow: jira JNJira Component/s: core Component/s: 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-20641) Jenkins and jenkins plugins not available for download via HTTPS
Kohsuke Kawaguchi commented on JENKINS-20641 Jenkins and jenkins plugins not available for download via HTTPS OSUOSL is not the only mirror, so an integrity check that relies on HTTPS would be tricky. I think an easier thing to do is to provide cryptographic checksums in update center metadata, which is already digitally signed. 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-20642) Add SHA2 and SHA3 hashes to update center metadata.
Kohsuke Kawaguchi moved JENKINS-20642 Add SHA2 and SHA3 hashes to update center metadata. Change By: Kohsuke Kawaguchi (18/Nov/13 11:50 PM) Project: SecurityIssues Jenkins Key: SECURITY JENKINS - 98 20642 Issue Type: Bug Improvement Workflow: jira JNJira Component/s: core Component/s: 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
