Web Listing Proposal
Greetings of the day! I am Vikash, Business Development Manager in India With 45+experienced IT professionals dedicated into website design, web development, Ecommerce Websites, Responsive Websites, Word Press Themes, iPhone App development, Andriod App development, SEO web design, SEO and Content Writing etc. We are using our highly competent technical services at a fraction of the cost of western-based companies. May I know if you are interested in any of these services? If you are interested, then I can send you our past work details, company information, affordable quotation with best offer. Awaiting for your Kind Response, Best Regards; Vikash, Business Development Manager -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ui-changes] (JENKINS-24397) new responsive UI has issues with "longish" build display names
Jay Howard commented on JENKINS-24397 new responsive UI has issues with "longish" build display names Forgot to add: We're using the "Version Number Plugin" version 1.4.1 to get the custom build name functionality: https://wiki.jenkins-ci.org/display/JENKINS/Version+Number+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/d/optout.
[JIRA] [ui-changes] (JENKINS-24397) new responsive UI has issues with "longish" build display names
Jay Howard created JENKINS-24397 new responsive UI has issues with "longish" build display names Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: ui-changes Created: 23/Aug/14 2:53 AM Description: Multiple issues related to "longish" build display names. 1. On the "View" page the table is wider than the available horizontal screen real estate due to longish build display names in the "Last Success" and "Last Failure" columns. The "Last Duration" column is pushed nearly entirely off the right hand side of the screen. 2. On the page for a particular job, the "Build History" box is made too wide due to longish build display names and overlaps the "Permalinks" section. This is also the case on the "Configure" screen for a job since the "Build History" box is present there as well. I'm happy to provide screen shots, but would rather not make them public. Previously we ran Jenkins 1.563 and I don't recall any build-display-name-related UI weirdness with that release. Environment: OS X 10.9.4, both Firefox and Safari affected, display resolution = 1440 x 900 Project: Jenkins Labels: ui browser Priority: Minor Reporter: Jay Howard 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/d/optout.
[JIRA] [unity3d-plugin] (JENKINS-24386) Unity Test Tools package returns 2 or 3 for failed integration testing.
Mark McNeely updated JENKINS-24386 Unity Test Tools package returns 2 or 3 for failed integration testing. Hey, sorry for the delay. I just realized that I was responding to the noreply email for this site. I wasn't able to confidently figure out the structure that was expected for the pull request so I went the sample route. There are two scenes called IntegrationPartialFailTests.unity and IntegrationTotalFailTests.unity The command that should work for these are -batchmode -executeMethod UnityTest.Batch.RunIntegrationTests -testscenes="IntegrationPartialFailTests" -targetPlatform=StandaloneWindows -resultsFileDirectory="YourDirHere" and -batchmode -executeMethod UnityTest.Batch.RunIntegrationTests -testscenes="IntegrationTotalFailTests" -targetPlatform=StandaloneWindows -resultsFileDirectory="YourDirHere" respectively. I've had problems running the integration tests with Jenkins as a service on windows. This is due to the "Session 0" that the services use on windows. If that causes problems for you then I can send you the steps I took to run jenkins outside of a service with windows task scheduler. Change By: Mark McNeely (23/Aug/14 5:54 AM) Attachment: Unity3DIntegrationTests.zip 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/d/optout.
[JIRA] [msbuild] (JENKINS-11069) Paths with spaces are not quoted
Gregory Boissinot resolved JENKINS-11069 as Fixed Paths with spaces are not quoted Should be fixed with in the last versions Change By: Gregory Boissinot (23/Aug/14 8:03 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/d/optout.
[JIRA] [cli] (JENKINS-24385) Jenkins CLI hangs with InvocationTargetException
Marcel Richter commented on JENKINS-24385 Jenkins CLI hangs with InvocationTargetException Yes, Jenkins is running full. CLI worked already fine in the past Jenkins ver. 1.532 After Jenkins update to ver. 1.565.1 und Java7 update, CLI is not working anymore. 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/d/optout.
[JIRA] [github] (JENKINS-23641) Builds are failing due to GitHubCommitNotifier exception
Joshua Moody commented on JENKINS-23641 Builds are failing due to GitHubCommitNotifier exception UPDATE: The project I am working on has submodules. If I remove the Advanced Submodule Processing options (or disable processing), I don't get this NPE. Of course, my build then fails downstream. I am sponsoring a fix for 50USD. 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/d/optout.
[JIRA] [build-pipeline] (JENKINS-20499) unable to retry job execution for failed job in build-pipeline
Dilip M commented on JENKINS-20499 unable to retry job execution for failed job in build-pipeline See in: Core: Jenkins ver. 1.532.2 Build Pipeline Plugin: 1.4.3 Parameterized Trigger Plugin: 2.20 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/d/optout.
[JIRA] [delivery-pipeline] (JENKINS-24392) Manual Build Trigger invoke job on different folder level
Ferzan Rizvi updated JENKINS-24392 Manual Build Trigger invoke job on different folder level Updated stacktrace Change By: Ferzan Rizvi (23/Aug/14 3:51 AM) Attachment: StackTrace.txt 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/d/optout.
[JIRA] [msbuild] (JENKINS-12554) MSBuild: Malformed Command Line due to commas in Build Parameters
Gregory Boissinot resolved JENKINS-12554 as Fixed MSBuild: Malformed Command Line due to commas in Build Parameters Change By: Gregory Boissinot (23/Aug/14 6:12 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/d/optout.
[JIRA] [delivery-pipeline] (JENKINS-24392) Manual Build Trigger invoke job on different folder level
Ferzan Rizvi edited a comment on JENKINS-24392 Manual Build Trigger invoke job on different folder level Updated. It didn't like my leading white space. 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/d/optout.
[JIRA] [git] (JENKINS-15852) Unable to delete workspace
Gregory Boissinot updated JENKINS-15852 Unable to delete workspace Change By: Gregory Boissinot (23/Aug/14 6:08 PM) Component/s: msbuild 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/d/optout.
[JIRA] [delivery-pipeline] (JENKINS-24392) Manual Build Trigger invoke job on different folder level
Ferzan Rizvi updated JENKINS-24392 Manual Build Trigger invoke job on different folder level Change By: Ferzan Rizvi (23/Aug/14 3:40 AM) Description: Job & View Folder Structure:RootFolder/--Continous Delivery View--SubFolder/JobA-InitialJobB-ManualJobA-Initial -> (Manual Trigger) -> JobB-ManualIf the delivery pipeline view is created at a different folder level than where the manually triggered job is located, it throws a null pointer exception.I've tried multiple combinations of specifying the absolute path, relative path from the view but, it will not take. The relative path from the view would probably work to manually trigger the job from the view but it does not display the job in pipeline the CD view because when it reads the trigger chain specified in the jobs job config , the job folder location will be incorrect. 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/d/optout.
[JIRA] [email-ext] (JENKINS-16181) Jenkins does not try to resend a failed e-mail
SCM/JIRA link daemon commented on JENKINS-16181 Jenkins does not try to resend a failed e-mail Code changed in jenkins User: Alex Earl Path: src/main/java/hudson/plugins/emailext/ExtendedEmailPublisher.java http://jenkins-ci.org/commit/email-ext-plugin/99ff8aed9777edfd24420ed3ba91a6d9f322968a Log: Merge pull request #96 from christiangalsterer/JENKINS-16181 JENKINS-16181 Jenkins does not try to resend a failed e-mail Compare: https://github.com/jenkinsci/email-ext-plugin/compare/5a0f29b55751...99ff8aed9777 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/d/optout.
[JIRA] [core] (JENKINS-24294) Very slow UI
Vincent Massol commented on JENKINS-24294 Very slow UI FTR https://groups.google.com/forum/#!topic/jenkinsci-users/L6ZSESU5x6s 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/d/optout.
[JIRA] [email-ext] (JENKINS-16181) Jenkins does not try to resend a failed e-mail
Christian Galsterer commented on JENKINS-16181 Jenkins does not try to resend a failed e-mail Added handling when a MessagingException is caused by ConnectException. Identical retry handling as for SendFailedException. PR available at https://github.com/jenkinsci/email-ext-plugin/pull/96 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/d/optout.
[JIRA] [delivery-pipeline] (JENKINS-24392) Manual Build Trigger invoke job on different folder level
Ferzan Rizvi updated JENKINS-24392 Manual Build Trigger invoke job on different folder level Change By: Ferzan Rizvi (23/Aug/14 3:37 AM) Description: Job & View Folder Structure: RootFolder/--Continous Delivery View--SubFolder/JobA-InitialJobB-ManualJobA-Initial -> (Manual Trigger) -> JobB-Manual If the delivery pipeline view is created at a different folder level than where the manually triggered job is located, it throws a null pointer exception.I've tried multiple combinations of specifying the absolute path, relative path from the view but, it will not take. The relative path from the view would probably work to manually trigger the job from the view but it does not display the job in pipeline view because when it reads the trigger chain specified in the jobs, the job folder location will be incorrect. 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/d/optout.
[JIRA] [msbuild] (JENKINS-10233) Mono compatibility
Gregory Boissinot resolved JENKINS-10233 as Fixed Mono compatibility Duplication issue Change By: Gregory Boissinot (23/Aug/14 6:18 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/d/optout.
[JIRA] [delivery-pipeline] (JENKINS-24392) Manual Build Trigger invoke job on different folder level
Patrik Boström started work on JENKINS-24392 Manual Build Trigger invoke job on different folder level Change By: Patrik Boström (23/Aug/14 6:11 PM) Status: Open In Progress 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/d/optout.
[JIRA] [delivery-pipeline] (JENKINS-24392) Manual Build Trigger invoke job on different folder level
Ferzan Rizvi updated JENKINS-24392 Manual Build Trigger invoke job on different folder level Change By: Ferzan Rizvi (23/Aug/14 3:47 AM) Description: Job & View Folder Structure:RootFolder/--Continous Delivery View--SubFolder/JobA -Initial JobB -Manual JobA- Initial - > (Manual Trigger) -> JobB -Manual If the delivery pipeline view is created at a different folder level than where the manually triggered job is located, it throws a null pointer exception.I've tried multiple combinations of specifying the absolute path, relative path from the view but, it will not take. The relative path from the view would probably work to trigger the manual job from the view but it does not display the manual job in the CD view because when it reads the trigger chain specified in the job config, the job folder location is incorrect. 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/d/optout.
[JIRA] [perforce] (JENKINS-24401) Changelists' submit time in the Jenkins changelog is displayed in the Perforce server's timezone
Daniel Beck commented on JENKINS-24401 Changelists' submit time in the Jenkins changelog is displayed in the Perforce server's timezone Won't this cause users to wonder why the times displayed in Jenkins are different from those displayed in Perforce? 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/d/optout.
[JIRA] [script-security] (JENKINS-24399) Modifying files in class directories can bypass approval in script-security (or class directories are accepted as classpaths)
ikedam commented on JENKINS-24399 Modifying files in class directories can bypass approval in script-security (or class directories are accepted as classpaths) It looks that URL#openStream for directories results file lists in directories. 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/d/optout.
[JIRA] [msbuild] (JENKINS-15029) Update of MSBuild plugin to 1.15 causes Parameterized trigger plugin to fail.
Gregory Boissinot resolved JENKINS-15029 as Incomplete Update of MSBuild plugin to 1.15 causes Parameterized trigger plugin to fail. Mark it as incomplete for now Change By: Gregory Boissinot (23/Aug/14 6:12 PM) Status: Reopened 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/d/optout.
[JIRA] [ansicolor] (JENKINS-24387) Support parsing output of $(tput sgr0)
Daniel Beck commented on JENKINS-24387 Support parsing output of $(tput sgr0) Full output of the command is ^[(B^[[m 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/d/optout.
[JIRA] [msbuild] (JENKINS-19830) Masked Password visible as plain text in Msbuild Plugin
SCM/JIRA link daemon commented on JENKINS-19830 Masked Password visible as plain text in Msbuild Plugin Code changed in jenkins User: Gregory Boissinot Path: src/main/java/hudson/plugins/msbuild/MsBuildBuilder.java src/main/resources/hudson/plugins/msbuild/MsBuildBuilder/help-buildVariablesAsProperties.html src/main/resources/hudson/plugins/msbuild/MsBuildBuilder/help-buildVariablesAsProperties_fr.html http://jenkins-ci.org/commit/msbuild-plugin/03fdb89ecc2dd3a0eb06aae099baf5d90f930f49 Log: Fix JENKINS-19830 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/d/optout.
[JIRA] [xunit] (JENKINS-24382) Convert cunit XML to junit XML in xUnit plugin
Gregory Boissinot started work on JENKINS-24382 Convert cunit XML to junit XML in xUnit plugin Change By: Gregory Boissinot (23/Aug/14 6:30 PM) Status: Open In Progress 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/d/optout.
[JIRA] [ui-changes] (JENKINS-24397) new responsive UI has issues with "longish" build display names
Jay Howard commented on JENKINS-24397 new responsive UI has issues with "longish" build display names Doh. Sorry. It's 1.575. 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/d/optout.
[JIRA] [scm-sync-configuration] (JENKINS-15128) Renaming job doesn't work with Git
SCM/JIRA link daemon commented on JENKINS-15128 Renaming job doesn't work with Git Code changed in jenkins User: Frédéric Camblor Path: src/main/java/hudson/plugins/scm_sync_configuration/SCMManipulator.java src/main/java/hudson/plugins/scm_sync_configuration/ScmSyncConfigurationBusiness.java http://jenkins-ci.org/commit/scm-sync-configuration-plugin/780cf5e7dffe3dd78a2037b99b6cfbde2b158dcf Log: JENKINS-15128: even if updatedFiles are empty, we should consider current commit as checked in in order to remove it from commitsQueue 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/d/optout.
[JIRA] [xunit] (JENKINS-24382) Convert cunit XML to junit XML in xUnit plugin
Daniel Beck commented on JENKINS-24382 Convert cunit XML to junit XML in xUnit plugin You want to make perl a dependency of the xUnit 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/d/optout.
[JIRA] [ui-changes] (JENKINS-24397) new responsive UI has issues with "longish" build display names
Jay Howard commented on JENKINS-24397 new responsive UI has issues with "longish" build display names Does that fix also cover the issue with the "All" view where the too-wide "Last Success" and "Last Failure" columns push the right-most columns past the edge of the viewable area? btw, I scanned the issues listed in association with 1.576 at http://jenkins-ci.org/changelog before creating this issue and didn't see anything about build display names. Is there a more detailed changelog I should be checking, or just do a JIRA search? 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/d/optout.
[JIRA] [msbuild] (JENKINS-18652) Handling of Configuration and Platform parameters
Gregory Boissinot resolved JENKINS-18652 as Fixed Handling of Configuration and Platform parameters Change By: Gregory Boissinot (24/Aug/14 12:56 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/d/optout.
[JIRA] [envinject] (JENKINS-19706) Masked Password Clearly visible as plain text in console output.
Gregory Boissinot resolved JENKINS-19706 as Fixed Masked Password Clearly visible as plain text in console output. Change By: Gregory Boissinot (24/Aug/14 12:56 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/d/optout.
[JIRA] [ui-changes] (JENKINS-24397) new responsive UI has issues with "longish" build display names
Jay Howard commented on JENKINS-24397 new responsive UI has issues with "longish" build display names Let me know if you'd like me to email you screen shots. 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/d/optout.
[JIRA] [scm-sync-configuration] (JENKINS-22820) Changes are not commited when using a recent git client
SCM/JIRA link daemon commented on JENKINS-22820 Changes are not commited when using a recent git client Code changed in jenkins User: Roger Hu Path: pom.xml http://jenkins-ci.org/commit/scm-sync-configuration-plugin/1a6dfc6febbd024ae3b09beea87284932b19f0a5 Log: Bump org.apache.maven.scm dependencies to be able to support Git v1.9.1. Related to issue: https://issues.jenkins-ci.org/browse/JENKINS-22820 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/d/optout.
[JIRA] [msbuild] (JENKINS-10856) Incorrect Cyrillic symbols in Console output
Gregory Boissinot resolved JENKINS-10856 as Fixed Incorrect Cyrillic symbols in Console output Code seems to be merged Change By: Gregory Boissinot (23/Aug/14 6:14 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/d/optout.
[JIRA] [delivery-pipeline] (JENKINS-24392) Manual Build Trigger invoke job on different folder level
Patrik Boström commented on JENKINS-24392 Manual Build Trigger invoke job on different folder level Have created a bugfix in PR: https://github.com/Diabol/delivery-pipeline-plugin/pull/81 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/d/optout.
[JIRA] [delivery-pipeline] (JENKINS-22876) Support for Promoted Builds Plugin
Patrik Boström resolved JENKINS-22876 as Fixed Support for Promoted Builds Plugin Merged to master. Will come in next release. Change By: Patrik Boström (24/Aug/14 5:57 PM) Status: In Progress 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/d/optout.
[JIRA] [core] (JENKINS-23937) No user interface for "-tcp PORT" slave jar option
Daniel Beck commented on JENKINS-23937 No user interface for "-tcp PORT" slave jar option The problem is that an undocumented option seems worse than a documented option nobody needs. It's also difficult to tell whether it's actually unused by everyone – even if not used in Jenkins out of the box, someone may have a custom ComputerLauncher that breaks when removing that option. Maybe for "run a command on the master"? Or can you show it must be unused, because it's actually broken in some way? 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/d/optout.
[JIRA] [msbuild] (JENKINS-19830) Masked Password visible as plain text in Msbuild Plugin
Gregory Boissinot resolved JENKINS-19830 as Fixed Masked Password visible as plain text in Msbuild Plugin Change By: Gregory Boissinot (24/Aug/14 12:56 PM) Status: Reopened 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/d/optout.
[JIRA] [scm-sync-configuration] (JENKINS-15128) Renaming job doesn't work with Git
SCM/JIRA link daemon commented on JENKINS-15128 Renaming job doesn't work with Git Code changed in jenkins User: Frédéric Camblor Path: src/main/java/hudson/plugins/scm_sync_configuration/scms/customproviders/git/gitexe/ScmSyncGitExeScmProvider.java src/main/resources/META-INF/plexus/components.xml http://jenkins-ci.org/commit/scm-sync-configuration-plugin/dbf5431c5cbd19e4674567e9b437a744ac29fe3b Log: JENKINS-15128: Fix job rename with Git by providing a custom GitExeScmProvider allowing to explicitely set "origin" as remote branch during push (in order to update local reference to avoid problem during subsequent call) 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/d/optout.
[JIRA] [msbuild] (JENKINS-15427) Incompatibility of MSBuild and Copy Artifact Plugins
Daniel Beck commented on JENKINS-15427 Incompatibility of MSBuild and Copy Artifact Plugins Gregory: Here's all the information you'll likely need: JENKINS-13412 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/d/optout.
[JIRA] [perforce] (JENKINS-24401) Changelists' submit time in the Jenkins changelog is displayed in the Perforce server's timezone
Daniel Kozar created JENKINS-24401 Changelists' submit time in the Jenkins changelog is displayed in the Perforce server's timezone Issue Type: Improvement Assignee: Daniel Kozar Components: perforce Created: 24/Aug/14 3:03 PM Description: The Perforce server always returns time-related information in the server's timezone. This also applies to the time when changelists were submitted : thus, the Jenkins changelog for a build always shows submit times in the server's timezone. I think it would be preferable if the changes were displayed in the timezone of the Jenkins server. Environment: Xubuntu Linux 14.04.1 amd64 OpenJDK JRE 1.6.0_27 Perforce Plugin 1.3.28 Perforce client : P4/LINUX26X86_64/2013.3/740675 (2013/11/11) Perforce server : P4D/LINUX26X86_64/2011.1/747877 (2013/11/21) Project: Jenkins Priority: Minor Reporter: Daniel Kozar 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/d/optout.
[JIRA] [msbuild] (JENKINS-21585) Pass build variables as properties incorrectly format commandline
Gregory Boissinot resolved JENKINS-21585 as Fixed Pass build variables as properties incorrectly format commandline Change By: Gregory Boissinot (24/Aug/14 12:55 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/d/optout.
[JIRA] [subversion] (JENKINS-24373) Support Redmine repo browsers that don't start at repository root
Daniel Beck updated JENKINS-24373 Support Redmine repo browsers that don't start at repository root Seems like a new feature to be able to use Redmine browser when it doesn't start at the repository root. Change By: Daniel Beck (24/Aug/14 1:35 PM) Summary: Changes - Links to Support Redmine Repo Browser repo browsers that don't work start at repository root Issue Type: Bug New Feature 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/d/optout.
[JIRA] [script-security] (JENKINS-24400) ClasspathEntryTest#pathURLConversion fails on Windows
ikedam created JENKINS-24400 ClasspathEntryTest#pathURLConversion fails on Windows Issue Type: Bug Assignee: ikedam Components: script-security Created: 24/Aug/14 6:18 AM Description: ClasspathEntryTest#pathURLConversion fails on Windows like this: --- Test set: org.jenkinsci.plugins.scriptsecurity.scripts.ClasspathEntryTest --- Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.016 sec <<< FAILURE! pathURLConversion(org.jenkinsci.plugins.scriptsecurity.scripts.ClasspathEntryTest) Time elapsed: 0.016 sec <<< FAILURE! org.junit.ComparisonFailure: expected:<[/tmp/]x.jar> but was:<[C:\tmp\]x.jar> at org.junit.Assert.assertEquals(Assert.java:125) at org.junit.Assert.assertEquals(Assert.java:147) at org.jenkinsci.plugins.scriptsecurity.scripts.ClasspathEntryTest.assertRoundTrip(ClasspathEntryTest.java:38) at org.jenkinsci.plugins.scriptsecurity.scripts.ClasspathEntryTest.pathURLConversion(ClasspathEntryTest.java:34) Environment: script-security-1.5, Windows 8 (64bits) Project: Jenkins Priority: Minor Reporter: ikedam 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/d/optout.
[JIRA] [core] (JENKINS-21749) builds seem to hang forever and can't be canceled, but actually complete
Jay Howard commented on JENKINS-21749 builds seem to hang forever and can't be canceled, but actually complete I apologize, Daniel. I just realized the Jenkins-related JIRA emails were going into a spam folder. Hence my radio silence. As far as I can tell, the issues that prompted this ticket were caused by some underlying network issues that were the result of a poorly configured firewall sitting between our build machine various other machines accessed during our builds. TCP connections were getting borked at the packet level, and apparently the networking code (somewhere, possibly not in Jenkins) doesn't handle the case when a low level socket operation blocks indefinitely. 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/d/optout.
[JIRA] [plugin] (JENKINS-24411) HP ALI plugin not available to download
hari hara sudhan created JENKINS-24411 HP ALI plugin not available to download Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: plugin Created: 25/Aug/14 1:08 PM Description: HP ALI Plugin is not available for download under plugin manager Fix Versions: current Project: Jenkins Priority: Major Reporter: hari hara sudhan 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/d/optout.
[JIRA] [checkstyle] (JENKINS-19932) Publish FindBugs/Checkstyle from slave failed
Julia commented on JENKINS-19932 Publish FindBugs/Checkstyle from slave failed Hi Ulli, i have three Slaves (Unix, AIX, Windows). The Windows slave is connect via JNLP and the Unix/AIX slaves are connect via SSH to the master. I've tried to run a build of each of them and i discover, if the build runs on the AIX-slave the results of Findbugs/Checkstyle can be transfer back to the master. By running on Linux/Windows, Findbugs/Checkstyle will be executed (on slave the results are available), but can't publish on master. I've checked the configurations of the slaves... The only distinguishable (of course) is that on AIX runs an IBM Java and on Linux/Windows Oracle-Java (but both Java 7). The wird thing (in my opinion) is, that the results of JUnit-Tests can be transfer back to the master without problems (on every slave). The Failure occurs only by publishing Findbug/Checkstyle results. Best regards 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/d/optout.
[JIRA] [metadata-plugin] (JENKINS-22532) 404 Error returned by MetadataChecks on configure pages when jenkins not at server root
SCM/JIRA link daemon commented on JENKINS-22532 404 Error returned by MetadataChecks on configure pages when jenkins not at server root Code changed in jenkins User: Bruno P. Kinoshita Path: src/main/resources/com/sonyericsson/hudson/plugins/metadata/model/definitions/DateMetadataDefinition/config.jelly src/main/resources/com/sonyericsson/hudson/plugins/metadata/model/definitions/DateMetadataDefinition/representation.jelly src/main/resources/com/sonyericsson/hudson/plugins/metadata/model/definitions/NumberMetadataDefinition/config.jelly src/main/resources/com/sonyericsson/hudson/plugins/metadata/model/definitions/NumberMetadataDefinition/representation.jelly src/main/resources/com/sonyericsson/hudson/plugins/metadata/model/definitions/StringMetadataDefinition/config.jelly src/main/resources/com/sonyericsson/hudson/plugins/metadata/model/definitions/TreeNodeMetadataDefinition/config.jelly src/main/resources/com/sonyericsson/hudson/plugins/metadata/model/values/DateMetadataValue/config.jelly src/main/resources/com/sonyericsson/hudson/plugins/metadata/model/values/NumberMetadataValue/config.jelly src/main/resources/com/sonyericsson/hudson/plugins/metadata/model/values/StringMetadataValue/config.jelly src/main/resources/com/sonyericsson/hudson/plugins/metadata/model/values/TreeNodeMetadataValue/config.jelly http://jenkins-ci.org/commit/metadata-plugin/ac833220385491b4ba0304719647e7f78d36a519 Log: [FIXED JENKINS-22532] using rootURL in jelly configuration pages 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/d/optout.
[JIRA] [email-ext] (JENKINS-24395) Fatal error with coming Jenkins ver. 1.577
Daniel Beck commented on JENKINS-24395 Fatal error with coming Jenkins ver. 1.577 Maybe call this one via reflection while required Jenkins < 1.577? Not nice, but still nicer than this error on all new Jenkins versions, and it's absolutely temporary. 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/d/optout.
[JIRA] [delivery-pipeline] (JENKINS-24392) Manual Build Trigger invoke job on different folder level
Ferzan Rizvi commented on JENKINS-24392 Manual Build Trigger invoke job on different folder level Thank you for the quick turnaround! 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/d/optout.
[JIRA] [perforce] (JENKINS-24401) Changelists' submit time in the Jenkins changelog is displayed in the Perforce server's timezone
Oleg Nenashev started work on JENKINS-24401 Changelists' submit time in the Jenkins changelog is displayed in the Perforce server's timezone Change By: Oleg Nenashev (24/Aug/14 3:14 PM) Status: Open In Progress 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/d/optout.
[JIRA] [ui-changes] (JENKINS-24397) new responsive UI has issues with "longish" build display names
Daniel Beck resolved JENKINS-24397 as Duplicate new responsive UI has issues with "longish" build display names Fixed in 1.576 as JENKINS-23829. Read the changelog. Change By: Daniel Beck (24/Aug/14 11:22 AM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [msbuild] (JENKINS-15427) Incompatibility of MSBuild and Copy Artifact Plugins
Gregory Boissinot commented on JENKINS-15427 Incompatibility of MSBuild and Copy Artifact Plugins @ikedam Could you give more information? 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/d/optout.
[JIRA] [scm-sync-configuration] (JENKINS-15898) Subversion back-end cannot handle renaming of jobs
Frédéric Camblor commented on JENKINS-15898 Subversion back-end cannot handle renaming of jobs FYI, JENKINS-15128 was fixed in 0.0.8 Could someone test this version (once it will have poped in jenkins plugin repos) to see if scm-api update from 1.6 to 1.9.1 wouldn't fix the issue for svn ? 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/d/optout.
[JIRA] [cluster-stats] (JENKINS-23712) Exceptions in multi-conf jobs and concurrents executions
toomasr commented on JENKINS-23712 Exceptions in multi-conf jobs and concurrents executions I did some changes: Had to bump the dependency version to 1.557 I thought 1.520 is enough but then I stumbled on JENKINS-23712 Also synchronized the file saving that should fix the problem Release 0.4.5 version 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/d/optout.
[JIRA] [cluster-stats] (JENKINS-23712) Exceptions in multi-conf jobs and concurrents executions
SCM/JIRA link daemon commented on JENKINS-23712 Exceptions in multi-conf jobs and concurrents executions Code changed in jenkins User: Toomas Romer Path: src/main/java/org/zeroturnaround/stats/ClusterStatisticsPlugin.java src/main/java/org/zeroturnaround/stats/model/StatsData.java http://jenkins-ci.org/commit/cluster-stats/cd77bff3a1aee1d1da084377ff2c638e80393d83 Log: JENKINS-23712 Syncrhonizing file saving Compare: https://github.com/jenkinsci/cluster-stats/compare/fca409901858...cd77bff3a1ae 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/d/optout.
[JIRA] [description-setter] (JENKINS-24398) Support for Token Macro Plugin in description
Christian Galsterer created JENKINS-24398 Support for Token Macro Plugin in description Issue Type: New Feature Assignee: Christian Galsterer Components: description-setter Created: 23/Aug/14 6:17 AM Description: Allow to evaluate a macro in the description if there is no regex defined. Project: Jenkins Priority: Major Reporter: Christian Galsterer 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/d/optout.
[JIRA] [jobconfighistory] (JENKINS-24412) Do not save config for matrix configurations
Oliver Gondža commented on JENKINS-24412 Do not save config for matrix configurations As saveModuleConfiguration defaults to false now, skipping matrix configs probably does not need to be configurable at all. 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/d/optout.
[JIRA] [copyartifact] (JENKINS-24084) Slave file leak build is interrupted during Copy Artifacts build step
mrobinet updated JENKINS-24084 Slave file leak build is interrupted during Copy Artifacts build step Change By: mrobinet (25/Aug/14 1:13 PM) Summary: Slave file leak when build is interrupted builds during Copy Artifacts build step 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/d/optout.
[JIRA] [maven2] (JENKINS-4861) Post-build deployment of Maven artifacts does not work with scpexe-type repository
SCM/JIRA link daemon commented on JENKINS-4861 Post-build deployment of Maven artifacts does not work with scpexe-type repository Code changed in jenkins User: Olivier Lamy Path: pom.xml http://jenkins-ci.org/commit/maven-plugin/c074ac3cab43ba450ed69be6ba8610771a707396 Log: Merge pull request #28 from rwegmann/JENKINS-4861 JENKINS-4861: Fix post-build deployment of Maven artifacts with scpexe-type repository Compare: https://github.com/jenkinsci/maven-plugin/compare/4d1f9cc3014a...c074ac3cab43 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/d/optout.
[JIRA] [msbuild] (JENKINS-18652) Handling of Configuration and Platform parameters
SCM/JIRA link daemon commented on JENKINS-18652 Handling of Configuration and Platform parameters Code changed in jenkins User: Gregory Boissinot Path: src/main/java/hudson/plugins/msbuild/MsBuildBuilder.java http://jenkins-ci.org/commit/msbuild-plugin/2d0e7f3e3ddd6eef5ae2886067ba1258eb811efb Log: Fix JENKINS-21585 and JENKINS-18652 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/d/optout.
[JIRA] [subversion] (JENKINS-14157) allow to set subversion workspace version per slave
Tom Ghyselinck updated JENKINS-14157 allow to set subversion workspace version per slave Change By: Tom Ghyselinck (25/Aug/14 8:34 AM) Priority: Major Critical 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/d/optout.
[JIRA] [maven2] (JENKINS-4861) Post-build deployment of Maven artifacts does not work with scpexe-type repository
SCM/JIRA link daemon resolved JENKINS-4861 as Fixed Post-build deployment of Maven artifacts does not work with scpexe-type repository Change By: SCM/JIRA link daemon (25/Aug/14 5:33 AM) Status: Reopened 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/d/optout.
[JIRA] [core] (JENKINS-19031) com.thoughtworks.xstream.converters.ConversionException: Array index out of range: -1 : Array index out of range: -1
SCM/JIRA link daemon commented on JENKINS-19031 com.thoughtworks.xstream.converters.ConversionException: Array index out of range: -1 : Array index out of range: -1 Code changed in jenkins User: Toomas Romer Path: pom.xml http://jenkins-ci.org/commit/cluster-stats/0824d108caac8778eb3ffa7a4591ca9d07d69c5b Log: Bumped dep to get it compiled wo missing com.github.jnr:jffi, bumped again JENKINS-19031 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/d/optout.
[JIRA] [jobconfighistory] (JENKINS-24410) Job config change not saved for maven and matrix projects
Oliver Gondža assigned JENKINS-24410 to Oliver Gondža Job config change not saved for maven and matrix projects Change By: Oliver Gondža (25/Aug/14 1:27 PM) Assignee: Mirko Friedenhagen Oliver Gondža 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/d/optout.
[JIRA] [core] (JENKINS-23330) Spaces in project names are not encoded on IDs
Dominique Brice commented on JENKINS-23330 Spaces in project names are not encoded on IDs html id are useful, for instance when using automated UI validation with framework like Selenium. Or, when they're used by plugin Let's keep it simple: keep the ids so that the Keyboard plugin works, and add a space-stripping static method in the Functions class to avoid polluting the object model for that purpose. This function can be revisited later if other issues arise in the html ids. 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/d/optout.
[JIRA] [github] (JENKINS-23641) Builds are failing due to GitHubCommitNotifier exception
Jason Parraga commented on JENKINS-23641 Builds are failing due to GitHubCommitNotifier exception +1 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/d/optout.
[JIRA] [script-security] (JENKINS-24399) Modifying files in class directories can bypass approval in script-security (or class directories are accepted as classpaths)
ikedam created JENKINS-24399 Modifying files in class directories can bypass approval in script-security (or class directories are accepted as classpaths) Issue Type: Bug Assignee: Jesse Glick Components: script-security Created: 24/Aug/14 12:44 AM Description: script-security 1.5 introduced "Additional classpath". Those classpaths require administrators' approval. Class directories are valid for "Additional classpath". Once class directories are appoved, adding or replacing files in sub directories of those class directories no longer require approval. This should allow users to use classes that administrators doesn't want to allow. Possible resolution: Don't allow class directories for "Additional classpath" This doesn't cause critical regressions as it is easy to create jar file from class directories. When a class directory is specified, check all files in the class directory. Leave this as a limitation. I'll add a test and send a pull request to see this behavior. Environment: Jenkins 1.509.4, script-security 1.5, Java 1.7.0_45, Windows 8 (64bit) Project: Jenkins Priority: Major Reporter: ikedam 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/d/optout.
[JIRA] [jobconfighistory] (JENKINS-24412) Do not save config for matrix configurations
Oliver Gondža created JENKINS-24412 Do not save config for matrix configurations Issue Type: Bug Assignee: Oliver Gondža Components: jobconfighistory Created: 25/Aug/14 1:29 PM Description: This is not user-editable configuration so it is pointless to backup. The same problem there ware with maven modules. Project: Jenkins Priority: Major Reporter: Oliver Gondža 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/d/optout.
[JIRA] [promoted-builds] (JENKINS-11972) Cannot create job with promoted build plugin automatically using jenkins API
Jesse Glick resolved JENKINS-11972 as Duplicate Cannot create job with promoted build plugin automatically using jenkins API Change By: Jesse Glick (25/Aug/14 2:37 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/d/optout.
[JIRA] [copyartifact] (JENKINS-24084) Slave file leak when interrupted builds
mrobinet updated JENKINS-24084 Slave file leak when interrupted builds Change By: mrobinet (25/Aug/14 1:12 PM) Summary: Slave file leak when interrupted builds Description: Random slave Slave processes are having file locks to files in the workspace hanging around after builds complete are interrupted during copy artifacts step .I used http://file-leak-detector.kohsuke.org/ to get a stack trace of the lock:# 20 12 C:\jenkins\workspace\Browser Tests ( Smoke QA )\BrowserType\ Firefox InternetExplorer32 \OS\windows\TestCategory\ BrowserRegistration JourneyTest02 \Bin\Release\Test\ System Quartz . Net.Http.Extensions.xml pdb by thread:pool-1-thread- 728 1178 for channel on Wed Jul 30 13 Thu Aug 21 07 : 23 28 : 30 35 CDT 2014 at java.io.FileOutputStream.(Unknown Source) at java.io.FileOutputStream.(Unknown Source) at hudson.FilePath$32.call(FilePath.java:1715) at hudson.FilePath$32.call(FilePath.java:1710) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:328) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at hudson.remoting.Engine$1$1.run(Engine.java:63) at java.lang.Thread.run(Unknown Source) I can reproduce it within a few days usually The build log shows:ERROR: Failed to copy artifacts from Build Empower with filter: Bin/*/Test/**/*.* , so let me know if Build/**/*.*,Bin/*.runsettingshudson.util.IOException2: Failed to copy C:\jenkins\jobs\Build Empower\builds\2014-08-20_13-38-06\archive\Bin\Release\Test\Quartz.pdb to C:\jenkins\workspace\Browser Tests (QA)\BrowserType\InternetExplorer32\OS\windows\TestCategory\JourneyTest02\Bin\Release\Test\Quartz.pdb at hudson.plugins.copyartifact.FingerprintingCopyMethod.copyOne(FingerprintingCopyMethod.java:107) at hudson.plugins.copyartifact.FingerprintingCopyMethod.copyAll(FingerprintingCopyMethod.java:68) at hudson.plugins.copyartifact.CopyArtifact.perform(CopyArtifact.java:396) at hudson.plugins.copyartifact.CopyArtifact.perform(CopyArtifact.java:327) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:772) at hudson.model.Build$BuildExecution.build(Build.java:199) at hudson.model.Build$BuildExecution.doRun(Build.java:160) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:535) at hudson.model.Run.execute(Run.java:1732) at hudson.matrix.MatrixRun.run(MatrixRun.java:146) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:234)Caused by: java.io.InterruptedIOException at org.jenkinsci.remoting.nio.NioChannelHub$NioTransport.writeBlock(NioChannelHub.java:212) at hudson.remoting.AbstractByteArrayCommandTransport.write(AbstractByteArrayCommandTransport.java:83) at hudson.remoting.Channel.send(Channel.java:545) at hudson.remoting.ProxyOutputStream._write(ProxyOutputStream.java:163) at hudson.remoting.ProxyOutputStream.write(ProxyOutputStream.java:109) at hudson.remoting.RemoteOutputStream.write(RemoteOutputStream.java:110) at java.security.DigestOutputStream.write(Unknown Source) at hudson.remoting.RemoteOutputStream.write(RemoteOutputStream.java:110) at hudson.Util.copyStream(Util.java:461) at hudson.FilePath$37.invoke(FilePath.java:1845) at hudson.FilePath$37.invoke(FilePath.java:1839) at hudson.FilePath.act(FilePath.java:922) at hudson.FilePath.act(FilePath.java:895) at hudson.FilePath.copyTo(FilePath.java:1839) at hudson.plugins.copyartifact.FingerprintingCopyMethod.copyOne(FingerprintingCopyMethod.java:79) ... 12 more information Caused by: java.lang.InterruptedException at java.lang.Object.wait(Native Method) at java.lang.Object.wait(Object.java:503) at org.jenkinsci.remoting.nio.FifoBuffer.write(FifoBuffer.java:336) at org.jenkinsci.remoting.nio.NioChannelHub$NioTransport.writeBloc
[JIRA] [delivery-pipeline] (JENKINS-24392) Manual Build Trigger invoke job on different folder level
Ferzan Rizvi updated JENKINS-24392 Manual Build Trigger invoke job on different folder level Change By: Ferzan Rizvi (23/Aug/14 3:36 AM) Description: Job & View Folder Structure:RootFolder/ CD --Continous Delivery View -- SubFolder/ JobA-Initial JobB-ManualJobA-Initial -> (Manual Trigger) -> JobB-ManualIf the delivery pipeline view is created at a different folder level than where the manually triggered job is located, it throws a null pointer exception.I've tried multiple combinations of specifying the absolute path, relative path from the view but, it will not take. The relative path from the view would probably work to manually trigger the job from the view but it does not display the job in pipeline view because when it reads the trigger chain specified in the jobs, the job folder location will be incorrect. 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/d/optout.
[JIRA] [jobconfighistory] (JENKINS-24410) Job config change not saved for maven and matrix projects
Oliver Gondža commented on JENKINS-24410 Job config change not saved for maven and matrix projects Maven projects are fixed since 2.8: https://github.com/jenkinsci/jobConfigHistory-plugin/commit/eb85bf560af838de0738e24d7823c13b676a512b Matrix project yet to be 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/d/optout.
[JIRA] [metadata-plugin] (JENKINS-22532) 404 Error returned by MetadataChecks on configure pages when jenkins not at server root
SCM/JIRA link daemon commented on JENKINS-22532 404 Error returned by MetadataChecks on configure pages when jenkins not at server root Code changed in jenkins User: Tomas Westling Path: src/main/resources/com/sonyericsson/hudson/plugins/metadata/model/definitions/DateMetadataDefinition/config.jelly src/main/resources/com/sonyericsson/hudson/plugins/metadata/model/definitions/DateMetadataDefinition/representation.jelly src/main/resources/com/sonyericsson/hudson/plugins/metadata/model/definitions/NumberMetadataDefinition/config.jelly src/main/resources/com/sonyericsson/hudson/plugins/metadata/model/definitions/NumberMetadataDefinition/representation.jelly src/main/resources/com/sonyericsson/hudson/plugins/metadata/model/definitions/StringMetadataDefinition/config.jelly src/main/resources/com/sonyericsson/hudson/plugins/metadata/model/definitions/TreeNodeMetadataDefinition/config.jelly src/main/resources/com/sonyericsson/hudson/plugins/metadata/model/values/DateMetadataValue/config.jelly src/main/resources/com/sonyericsson/hudson/plugins/metadata/model/values/NumberMetadataValue/config.jelly src/main/resources/com/sonyericsson/hudson/plugins/metadata/model/values/StringMetadataValue/config.jelly src/main/resources/com/sonyericsson/hudson/plugins/metadata/model/values/TreeNodeMetadataValue/config.jelly http://jenkins-ci.org/commit/metadata-plugin/0a780cfd6ce11aba43bcd5e220bd3a318f0b33e9 Log: Merge pull request #3 from kinow/issue-22532 [FIXED JENKINS-22532] using rootURL in jelly configuration pages Compare: https://github.com/jenkinsci/metadata-plugin/compare/992322906d42...0a780cfd6ce1 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/d/optout.
[JIRA] [ui-changes] (JENKINS-24397) new responsive UI has issues with "longish" build display names
Daniel Beck commented on JENKINS-24397 new responsive UI has issues with "longish" build display names You forgot to mention which Jenkins version this is. 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/d/optout.
[JIRA] [delivery-pipeline] (JENKINS-24392) Manual Build Trigger invoke job on different folder level
Ferzan Rizvi updated JENKINS-24392 Manual Build Trigger invoke job on different folder level Change By: Ferzan Rizvi (23/Aug/14 3:43 AM) Description: Job & View Folder Structure:RootFolder/--Continous Delivery View--SubFolder/JobA-InitialJobB-ManualJobA-Initial -> (Manual Trigger) -> JobB-ManualIf the delivery pipeline view is created at a different folder level than where the manually triggered job is located, it throws a null pointer exception.I've tried multiple combinations of specifying the absolute path, relative path from the view but, it will not take. The relative path from the view would probably work to manually trigger the manual job from the view but it does not display the manual job in the CD view because when it reads the trigger chain specified in the job config, the job folder location will be is incorrect. 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/d/optout.
[JIRA] [description-setter] (JENKINS-24398) Support for Token Macro Plugin in description
Christian Galsterer started work on JENKINS-24398 Support for Token Macro Plugin in description Change By: Christian Galsterer (23/Aug/14 6:17 AM) Status: Open In Progress 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/d/optout.
[JIRA] [core] (JENKINS-23925) SSL weak ciphers
aeschbacher commented on JENKINS-23925 SSL weak ciphers After further investigation, it appears that sslscan discovers weak ciphers only if jenkins.war is started with java6. It is not the case with java7. For Debian Wheezy, this means java 6: 1.6.0_32 (weak ciphers discovered by sslscan) java 7: 1.7.0_65 (no weak ciphers) So I guess the ticket can be 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/d/optout.
[JIRA] [matrix-project] (JENKINS-23902) Matrix parent takes executor slot and blocks children
Oleg Nenashev commented on JENKINS-23902 Matrix parent takes executor slot and blocks children Throttle Concurrent Builds plugin seems to be responsible. See https://github.com/jenkinsci/throttle-concurrent-builds-plugin/pull/22 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/d/optout.
[JIRA] [ansicolor] (JENKINS-24387) Support parsing output of $(tput sgr0)
Daniel Beck commented on JENKINS-24387 Support parsing output of $(tput sgr0) Filed with the jansi project as https://github.com/fusesource/jansi/issues/29 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/d/optout.
[JIRA] [scm-sync-configuration] (JENKINS-22820) Changes are not commited when using a recent git client
SCM/JIRA link daemon commented on JENKINS-22820 Changes are not commited when using a recent git client Code changed in jenkins User: Frédéric Camblor Path: pom.xml src/main/resources/META-INF/plexus/components.xml http://jenkins-ci.org/commit/scm-sync-configuration-plugin/5fd7d4b3e6a8c293529cd7db3dca667d460c1306 Log: Merge pull request #21 from rogerhu/jenkins_22820 JENKINS-22820 fix - Bump maven.scm to 1.9.1 to avoid issues with Git v1.9 upgrades. Compare: https://github.com/jenkinsci/scm-sync-configuration-plugin/compare/a6d775bbaafa...5fd7d4b3e6a8 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/d/optout.
[JIRA] [jobconfighistory] (JENKINS-24410) Job config change not saved for maven and matrix projects
Oliver Gondža created JENKINS-24410 Job config change not saved for maven and matrix projects Issue Type: Bug Assignee: Mirko Friedenhagen Components: jobconfighistory Created: 25/Aug/14 12:44 PM Project: Jenkins Priority: Major Reporter: Oliver Gondža 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/d/optout.
[JIRA] [scm-sync-configuration] (JENKINS-15128) Renaming job doesn't work with Git
SCM/JIRA link daemon commented on JENKINS-15128 Renaming job doesn't work with Git Code changed in jenkins User: fcamblor Path: src/test/java/hudson/plugins/scm_sync_configuration/repository/HudsonExtensionsGitTest.java http://jenkins-ci.org/commit/scm-sync-configuration-plugin/b794c1a45f487e8579d8303ec1c0a31319fcb7d9 Log: JENKINS-15128: Re-activated shouldJobRenameBeCorrectlyImpactedOnSCM Compare: https://github.com/jenkinsci/scm-sync-configuration-plugin/compare/5fd7d4b3e6a8...b794c1a45f48 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/d/optout.
[JIRA] [jobconfighistory] (JENKINS-24410) Job config change not saved for maven and matrix projects
SCM/JIRA link daemon commented on JENKINS-24410 Job config change not saved for maven and matrix projects Code changed in jenkins User: Oliver Gondža Path: src/test/java/plugins/JobConfigHistoryPluginTest.java http://jenkins-ci.org/commit/acceptance-test-harness/7db17dcc6cb5ae954bfd0e18f76731ff2754c49a Log: JobConfigHistory: Reproduce JENKINS-24410 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/d/optout.
[JIRA] [msbuild] (JENKINS-24132) MSBuild Output encoding vs Jenkins' encoding vs Browser Encoding
Gregory Boissinot resolved JENKINS-24132 as Not A Defect MSBuild Output encoding vs Jenkins' encoding vs Browser Encoding Please check you encoding on Jenkins build node. Change By: Gregory Boissinot (23/Aug/14 5:31 PM) Status: Open Resolved Resolution: Not A Defect 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/d/optout.
[JIRA] [description-setter] (JENKINS-24398) Support for Token Macro Plugin in description
Christian Galsterer updated JENKINS-24398 Support for Token Macro Plugin in description Change By: Christian Galsterer (23/Aug/14 7:01 AM) Description: Allow Allows to evaluate a macro in the description provided via the Token Macro plugin if there is no regex defined. 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/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-22892) DSL for initial Base ClearCase support
Christian Galsterer closed JENKINS-22892 as Fixed DSL for initial Base ClearCase support Change By: Christian Galsterer (23/Aug/14 6:13 AM) 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/d/optout.
[JIRA] [p4] (JENKINS-24187) Perforce Credential 'Trust' field needs explantion ( ie implement the '?')
dan tran commented on JENKINS-24187 Perforce Credential 'Trust' field needs explantion ( ie implement the '?') I think I can guess my way through 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/d/optout.
[JIRA] [core] (JENKINS-21437) Failed to update /computer/xxxxxxxxxxx/builds
Jesse Glick started work on JENKINS-21437 Failed to update /computer/xxx/builds Change By: Jesse Glick (25/Aug/14 2:03 PM) Status: Open In Progress 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/d/optout.
[JIRA] [sbt] (JENKINS-24346) Cannot launch sbt when either java or sbt-launcher path contains spaces in Windows
SCM/JIRA link daemon commented on JENKINS-24346 Cannot launch sbt when either java or sbt-launcher path contains spaces in Windows Code changed in jenkins User: Spyros Kapnissis Path: src/main/java/org/jvnet/hudson/plugins/SbtPluginBuilder.java http://jenkins-ci.org/commit/sbt-plugin/e9875fec697b72bd61867967f8447bce70d72fdb Log: JENKINS-24346: add an extra set of quotes after cmd/c to handle paths with spaces in Windows. 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/d/optout.
[JIRA] [mstest] (JENKINS-18632) Jenkins hangs during builds
Gregory Boissinot updated JENKINS-18632 Jenkins hangs during builds Change By: Gregory Boissinot (23/Aug/14 6:07 PM) Component/s: msbuild 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/d/optout.
[JIRA] [msbuild] (JENKINS-21585) Pass build variables as properties incorrectly format commandline
SCM/JIRA link daemon commented on JENKINS-21585 Pass build variables as properties incorrectly format commandline Code changed in jenkins User: Gregory Boissinot Path: src/main/java/hudson/plugins/msbuild/MsBuildBuilder.java http://jenkins-ci.org/commit/msbuild-plugin/2d0e7f3e3ddd6eef5ae2886067ba1258eb811efb Log: Fix JENKINS-21585 and JENKINS-18652 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/d/optout.
[JIRA] [maven2] (JENKINS-4861) Post-build deployment of Maven artifacts does not work with scpexe-type repository
SCM/JIRA link daemon commented on JENKINS-4861 Post-build deployment of Maven artifacts does not work with scpexe-type repository Code changed in jenkins User: Raúl Wegmann Path: pom.xml http://jenkins-ci.org/commit/maven-plugin/7f6145d8faead72a999d69f9bed36d601b193508 Log: [FIXED JENKINS-4861] Use newer version of transitive plexus-utils dependency that allows to correctly deploy artifacts using scpexe. 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/d/optout.
[JIRA] [scm-sync-configuration] (JENKINS-15128) Renaming job doesn't work with Git
Frédéric Camblor resolved JENKINS-15128 as Fixed Renaming job doesn't work with Git fixed in v0.0.8 Change By: Frédéric Camblor (24/Aug/14 9:07 AM) Status: Open Resolved Assignee: Frédéric Camblor 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/d/optout.
[JIRA] [script-security] (JENKINS-24399) Modifying files in class directories can bypass approval in script-security (or class directories are accepted as classpaths)
ikedam commented on JENKINS-24399 Modifying files in class directories can bypass approval in script-security (or class directories are accepted as classpaths) Pull request to demonstrate this problem: https://github.com/jenkinsci/script-security-plugin/pull/4 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/d/optout.
[JIRA] [msbuild] (JENKINS-12350) Characters missing or wrongly displayed in MSBuild Output in Jenkins
Gregory Boissinot resolved JENKINS-12350 as Not A Defect Characters missing or wrongly displayed in MSBuild Output in Jenkins Not a Jenkins Msbuild plugin issue Change By: Gregory Boissinot (23/Aug/14 8:10 PM) Status: Open Resolved Resolution: Not A Defect 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/d/optout.
[JIRA] [scm-sync-configuration] (JENKINS-19229) Git repo: fails when we delete the jobs.
Frédéric Camblor resolved JENKINS-19229 as Duplicate Git repo: fails when we delete the jobs. FYI, JENKINS-15128 was fixed in 0.0.8 Change By: Frédéric Camblor (24/Aug/14 9:20 AM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [copyartifact] (JENKINS-24084) Slave file leak build is interrupted during Copy Artifacts build step
mrobinet commented on JENKINS-24084 Slave file leak build is interrupted during Copy Artifacts build step I've updated this bug with quite a bit more information and believe I have found the root cause. I believe it is specific to the Copy Artifacts 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/d/optout.
[JIRA] [delivery-pipeline] (JENKINS-24392) Manual Build Trigger invoke job on different folder level
Ferzan Rizvi commented on JENKINS-24392 Manual Build Trigger invoke job on different folder level Updated 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/d/optout.
