[JIRA] [clang-scanbuild-plugin] (JENKINS-32008) Failure with Xcode 7.2 with iphonesimulator Target SDK and Debug Build Configuration
Title: Message Title Francis Labrie commented on JENKINS-32008 Re: Failure with Xcode 7.2 with iphonesimulator Target SDK and Debug Build Configuration Yes: adding the -destination Xcode parameter fix the problem. Would it be possible to manage this automatically in the plugin? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [clang-scanbuild-plugin] (JENKINS-32008) Failure with Xcode 7.2 with iphonesimulator Target SDK and Debug Build Configuration
Title: Message Title Francis Labrie created an issue Jenkins / JENKINS-32008 Failure with Xcode 7.2 with iphonesimulator Target SDK and Debug Build Configuration Issue Type: Bug Assignee: Josh Kennedy Components: clang-scanbuild-plugin Created: 10/Dec/15 4:27 PM Environment: OS X El Capitan 10.11.2 Xcode 7.2 iOS SDK 9.2 Priority: Blocker Reporter: Francis Labrie Since Xcode 7.2 upgrade including iOS SDK 9.2, Clang Scan-Build plugin can't perform task using the following parameters: Target SDK: iphonesimulator Build Configuration: Debug The iphonesimulator target SDK causes import errors like these: While building module 'UIKit' imported from /Users/jenkins/Home/jobs/eVA Mobile iOS Application/workspace/iOS-Application/Submodules/eVA Core iOS Library/Submodules/CGI Extensions iOS
[JIRA] [clang-scanbuild-plugin] (JENKINS-32008) Failure with Xcode 7.2 with iphonesimulator Target SDK and Debug Build Configuration
Title: Message Title Francis Labrie updated an issue Jenkins / JENKINS-32008 Failure with Xcode 7.2 with iphonesimulator Target SDK and Debug Build Configuration Change By: Francis Labrie Environment: OS X El Capitan 10.11.2Xcode 7.2iOS SDK 9.2 checker 277 (October 28, 2015) Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [backup-plugin] (JENKINS-8282) Backup Plugin: cannot use tar in OS X
Title: Message Title Francis Labrie commented on JENKINS-8282 Re: Backup Plugin: cannot use tar in OS X I have the exact same problem. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [xcode-plugin] (JENKINS-30591) Xcode 7: Unit Test failure related to unparseable date
Title: Message Title
Francis Labrie updated an issue
Jenkins / JENKINS-30591
Xcode 7: Unit Test failure related to unparseable date
Change By:
Francis Labrie
All Unit Test build fails since *Xcode 7* update: it seems related to a date format change. Now, the date have the floating milliseconds part appended to the second value, and there is not more timezone value at the end. See the difference below:h3. Xcode 6.4{code}[FooBar] $ /usr/bin/xcodebuild -versionXcode 6.4Build version 6E35b...Test Suite 'All tests' started at 2015-08-31 19:10:25 +Test Suite 'FooBarTests.xctest' started at 2015-08-31 19:10:25 +Test Suite 'FooBarAccessManagerTests' started at 2015-08-31 19:10:25 +Test Case '-[FooBarAccessManagerTests testActionInitialization]' started.{code}h3. Xcode 7.0{code}[FooBar] $ /usr/bin/xcodebuild -versionXcode 7.0Build version 7A220...Test Suite 'All tests' started at 2015-09-21 14:54:54.990FATAL: Unparseable date: "2015-09-21 14:54:54.990"{code}For *Xcode 7*, we need to use the {{"-MM-dd HH:mm:ss.SSS"}} _SimpleDateFormat_ instead of {{"-MM-dd HH:mm:ss z"}} one for the _au.com.rayh.XCodeBuildOutputParser.dateFormat_ static property. Would it be possible to add a multiple date format parser to the plugin, to support both version of *Xcode*?
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
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
[JIRA] [xcode-plugin] (JENKINS-30591) Xcode 7: Unit Test failure related to unparseable date
Title: Message Title Francis Labrie created an issue Jenkins / JENKINS-30591 Xcode 7: Unit Test failure related to unparseable date Issue Type: Bug Assignee: Unassigned Components: xcode-plugin Created: 22/Sep/15 2:10 PM Environment: OS X Server 10.10.5 Yosemite Jenkins 1.630 Xcode Plugin 1.4.8 Priority: Blocker Reporter: Francis Labrie All Unit Test build fails since Xcode 7 update: it seems related to a date format change. Now, the date have the floating milliseconds part appended to the second value, and there is not more timezone value at the end. See the difference below: Xcode 6.4 [FooBar] $ /usr/bin/xcodebuild -version Xcode 6.4 Build version 6E35b ... Test Suite 'All tests' started at 2015-08-31 19:10:25 + Test Suite 'FooBarTests.xctest' started at 2015-08-31 19:10:25 + Test Suite 'FooBarAccessManagerTests' started at 2015-08-31 19:10:25 + Test Case '-[FooBarAccessManagerTests testActionInitialization]' started. Xcode 7.0
[JIRA] [managed-scripts-plugin] (JENKINS-30417) Add a description field for each argument
Title: Message Title Francis Labrie created an issue Jenkins / JENKINS-30417 Add a description field for each argument Issue Type: Improvement Assignee: Dominik Bartholdi Components: managed-scripts-plugin Created: 11/Sep/15 5:48 PM Priority: Minor Reporter: Francis Labrie It would be very handy to get a Description field for each argument. This description could then be shown on the right of the field name. Example: Product Names: List of all build product names, separated with comma. (Required) Add Comment
[JIRA] [managed-scripts-plugin] (JENKINS-30416) Comment should not be appended to the Name in the popup menu
Title: Message Title Francis Labrie updated an issue Jenkins / JENKINS-30416 Comment should not be appended to the Name in the popup menu Change By: Francis Labrie *Comment* should not be appended to the *Name* in the popup menu. Long comments make this popup hard to read. Instead, the *Comment:* label and value should be available under this component, just above the *Required arguments:* line. It would be handy to have the value wrapped with a reveal / hide control, hidden by default.This would be useful to write simple documentation for scripts. By the way, maybe *Description* should be a better name than *Comment*. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [managed-scripts-plugin] (JENKINS-30416) Comment should not be appended to the Name in the popup menu
Title: Message Title Francis Labrie created an issue Jenkins / JENKINS-30416 Comment should not be appended to the Name in the popup menu Issue Type: Improvement Assignee: Dominik Bartholdi Components: managed-scripts-plugin Created: 11/Sep/15 5:42 PM Priority: Minor Reporter: Francis Labrie Comment should not be appended to the Name in the popup menu. Long comments make this popup hard to read. Instead, the Comment: label and value should be available under this component, just above the Required arguments: line. It would be handy to have the value wrapped with a reveal / hide control, hidden by default. This would be useful to write simple documentation for scripts. Add Comment
[JIRA] [clang-scanbuild-plugin] (JENKINS-28130) Latest (1.5) Clang scan-build plugin fails to publish
Francis Labrie edited a comment on JENKINS-28130 Latest (1.5) Clang scan-build plugin fails to publish I get the same error, I had to go back to version 1.4. Xcode version is: $ /usr/bin/xcodebuild -version Xcode 6.2 Build version 6C131e This message is automatically generated by JIRA. 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] [clang-scanbuild-plugin] (JENKINS-28130) Latest (1.5) Clang scan-build plugin fails to publish
Francis Labrie commented on JENKINS-28130 Latest (1.5) Clang scan-build plugin fails to publish I get the same error, I have to revert to version 1.4. Xcode version is: $ /usr/bin/xcodebuild -version Xcode 6.2 Build version 6C131e This message is automatically generated by JIRA. 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-26690) Build stats throws illegal argument exception on dashboard view
Francis Labrie commented on JENKINS-26690 Build stats throws illegal argument exception on dashboard view I have the same problem with Jenkins 1.599 on OS X 10.9 Server. This message is automatically generated by JIRA. 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] [dashboard-view-plugin] (JENKINS-18880) Build statistics does not display result with regex .* filter
Francis Labrie commented on JENKINS-18880 Build statistics does not display result with regex .* filter Yes, it's the same thing as described in JENKINS-26690. févr. 26, 2015 10:51:25 AM AVERTISSEMENT hudson.ExpressionFactory2$JexlExpression evaluate Caught exception evaluating: it.getBuildStat(jobs) in /. Reason: java.lang.IllegalArgumentException: fromKey toKey java.lang.IllegalArgumentException: fromKey toKey at java.util.TreeMap$NavigableSubMap.init(TreeMap.java:1364) at java.util.TreeMap$AscendingSubMap.init(TreeMap.java:1851) at java.util.TreeMap.subMap(TreeMap.java:909) at java.util.TreeMap.subMap(TreeMap.java:950) at jenkins.model.lazy.AbstractLazyLoadRunMap.subMap(AbstractLazyLoadRunMap.java:250) at jenkins.model.lazy.AbstractLazyLoadRunMap.headMap(AbstractLazyLoadRunMap.java:254) at jenkins.model.lazy.AbstractLazyLoadRunMap.headMap(AbstractLazyLoadRunMap.java:88) at java.util.Collections$UnmodifiableSortedMap.headMap(Collections.java:1863) at hudson.plugins.view.dashboard.stats.StatBuilds.getBuildStat(StatBuilds.java:48) ... This message is automatically generated by JIRA. 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-22519) Jenkins Build History page: Build Status table is always empty on Safari
Francis Labrie commented on JENKINS-22519 Jenkins Build History page: Build Status table is always empty on Safari The original French strings are OK: there is no apostrophe in that version: https://github.com/jenkinsci/jenkins/blob/master/core/src/main/resources/lib/hudson/buildListTable_fr.properties This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-22519) Jenkins Build History page: Build Status table is always empty on Safari
Francis Labrie
updated JENKINS-22519
Jenkins Build History page: Build Status table is always empty on Safari
Change By:
Francis Labrie
(25/Feb/15 7:54 PM)
Summary:
JenkinsBuildHistorypage:BuildStatustableisalwaysempty
onSafari
Environment:
Jenkins1.
557
544to1.599
runningonOSXServer10.9.2WebBrowsers:
Allmajor,
Safari8.0.3
on
Mac
OSX
andWindows
10
.
10.
Description:
SinceJenkins1.544,the*BuildStatus*sectionbelowthetimelinegraphiconthe*JenkinsBuildHistory*pageisalwaysempty
onSafari8
.
0.3.
Seescreenshotbelow.Buildjobsappearsuccessfullyinthetimeline,butnothingisshowninthe*BuildStatus*tablebelow.ThisissueisstillpresentincurrentJenkins1.
577
599
.
BelowaretheerrorsloggedintheSafaribrowserConsole:{code}[Log]localesettoen(common-content.js,line98)[Error]SyntaxError:Unexpectedidentifierévénement.Expected}toendaobjectliteral. (fonctionanonyme)(builds,line153)[Error]ReferenceError:Cantfindvariable:displayBuilds globalcode(builds,line166)[Log]localesettoen(common-content.js,line98)[Error]Failedtoloadresource:theserverrespondedwithastatusof404(NotFound)(__history__.html,line0)[Error]Failedtoloadresource:theserverrespondedwithastatusof404(NotFound)(message-left.png,line0)[Error]Failedtoloadresource:theserverrespondedwithastatusof404(NotFound)(message-right.png,line0)[Log]localesettoen(common-content.js,line98){code}The*BuildStatus*tableisnotemptyusingFirefox36.0onMacOSX10.10,andonlyoneerrorisloggedintheConsole:{code}aucunélémenttrouvéstart:1:1GEThttps://jenkins.mobile.cgi.com/view/Dashboard/__history__.html[HTTP/1.1404NotFound31ms]{code}
Component/s:
dashboard-view-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] [core] (JENKINS-22519) Jenkins Build History page: Build Status table is always empty on Safari
Francis Labrie resolved JENKINS-22519 as Not A Defect Jenkins Build History page: Build Status table is always empty on Safari Forget this report, the issue was finally related to a French localization. The following string: Click to center timeline on event Was translated to: Cliquer afin de centrer le calendrier sur l''événement But this was breaking the _javascript_ code. Adding a backslash \ prefix fix the problem: Cliquer afin de centrer le calendrier sur l\''événement Change By: Francis Labrie (25/Feb/15 8:11 PM) Status: Open Resolved Resolution: NotADefect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [dashboard-view-plugin] (JENKINS-18880) Build statistics does not display result with regex .* filter
Francis Labrie updated JENKINS-18880 Build statistics does not display result with regex .* filter Change By: Francis Labrie (25/Feb/15 7:27 PM) Attachment: Captured’écran2015-02-25à2.23.00PM.png This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [dashboard-view-plugin] (JENKINS-18880) Build statistics does not display result with regex .* filter
Francis Labrie reopened JENKINS-18880 Build statistics does not display result with regex .* filter This problem has been fixed in the past, but since a month or two, Build statistics are still empty in the Jenkins 1.599 Dashboard Portlet when using a regular _expression_ filter like .*. Change By: Francis Labrie (25/Feb/15 7:26 PM) Resolution: Fixed Status: Resolved Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [dashboard-view-plugin] (JENKINS-18880) Build statistics does not display result with regex .* filter
Francis Labrie edited a comment on JENKINS-18880 Build statistics does not display result with regex .* filter This problem has been fixed in the past, but since a month or two, Build statistics are still empty in the Jenkins 1.599 Dashboard Portlet when using a regular _expression_ filter like .*. It only work if I select jobs individually. This message is automatically generated by JIRA. 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] [hue-light-plugin] (JENKINS-22048) Hue-Light plugin doesn't work with Maven jobs
Francis Labrie resolved JENKINS-22048 as Fixed Hue-Light plugin doesnt work with Maven jobs In version 1.1. Change By: Francis Labrie (25/Feb/15 8:39 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] [tasks-plugin] (JENKINS-27112) Layout issue in Task Build History
Francis Labrie created JENKINS-27112 Layout issue in Task Build History Issue Type: Bug Assignee: Ulli Hafner Attachments: Capture d’écran 2015-02-24 à 3.32.30 PM.png, Capture d’écran 2015-02-24 à 3.33.12 PM.png Components: tasks-plugin Created: 24/Feb/15 8:33 PM Description: A layout issue in Task Build History make it unreadable and hard to navigate. See screenshots. Environment: Jenkins 1.599, OS X 10.10 (Yosemite), Safari 8.0.3, Firefox 35.0.1 Project: Jenkins Priority: Major Reporter: Francis Labrie This message is automatically generated by JIRA. 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] [analysis-collector] (JENKINS-24603) Bad URL encoding generated on redirection to warnings analysis reports
Francis Labrie reopened JENKINS-24603 Bad URL encoding generated on redirection to warnings analysis reports Unfortunately, the change in version 1.60 doesn't fix the problem: I get the exact same behaviour when selecting warnings report links on the left menu. Change By: Francis Labrie (23/Sep/14 11:52 AM) Resolution: Fixed Status: Resolved Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [analysis-collector] (JENKINS-24603) Bad URL encoding generated on redirection to warnings analysis reports
Francis Labrie commented on JENKINS-24603 Bad URL encoding generated on redirection to warnings analysis reports I did perform test with both Safari 7.1 application and Curl 7.30.0 command line tool on Mac OS X 10.9.5. This message is automatically generated by JIRA. 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] [analysis-collector] (JENKINS-24603) Bad URL encoding generated on redirection to warnings analysis reports
Francis Labrie updated JENKINS-24603 Bad URL encoding generated on redirection to warnings analysis reports You'll find the Curl logs here. Change By: Francis Labrie (22/Sep/14 2:06 PM) Attachment: curl.log This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [analysis-collector] (JENKINS-24603) Bad URL encoding generated on redirection to warnings analysis reports
Francis Labrie commented on JENKINS-24603 Bad URL encoding generated on redirection to warnings analysis reports This is a production server and we don't have a test nor staging one for Jenkins. But if I can quickly install the new plugin, perform tests and restore the previous one if anything goes wrong, it should be OK. This message is automatically generated by JIRA. 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] [analysis-collector] (JENKINS-24603) Bad URL encoding generated on redirection to warnings analysis reports
Francis Labrie commented on JENKINS-24603 Bad URL encoding generated on redirection to warnings analysis reports Our current Jenkins version is 1.580. It's running on Mac OS X 10.9.5 Server using the default container provided by the installer / JAR. This issue is reproductible in both environment: 1) using a direct access on the 8080 port; 2) using the nginx proxy host. There is no reverse proxy warning in the /manage page. This message is automatically generated by JIRA. 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] [analysis-collector] (JENKINS-24603) Bad URL encoding generated on redirection to warnings analysis reports
Francis Labrie commented on JENKINS-24603 Bad URL encoding generated on redirection to warnings analysis reports I don't know if it could be a factor: I don't think so. But for your information, on Mac OS X, the default UTF-8 encoding used on HFS+ filesystem uses NFD (Normalization Form D), and not NFC (Normalization Form C) like Windows and Linux. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [analysis-collector] (JENKINS-24603) Bad URL encoding generated on redirection to warnings analysis reports
Francis Labrie created JENKINS-24603 Bad URL encoding generated on redirection to warnings analysis reports Issue Type: Bug Affects Versions: current Assignee: Ulli Hafner Components: analysis-collector, core, warnings Created: 05/Sep/14 4:42 PM Description: When a job name contains non-ASCII characters (Montréal for example), the URL generated for the redirection process to the last build analysis reports get bad encoding. For example: Job name: Montréal Hyperlinks on main job page: Static Analysis Warning: /job/Ville%20de%20Montr%C3%A9al%20Reporter%20iOS%20Application/warnings10 This URL is correctly encoded using UTF-8. So clicking on this link perform the expected result. Unfortunately, by clicking this hyperlink, Jenkins redirect the request to the last build warning result, generating new URL with bad encoding. These are the detailed header of the multiple requests following the redirection: GET /job/Ville%20de%20Montr%C3%A9al%20Reporter%20iOS%20Application/warnings10 HTTP/1.1 301 Moved Permanently Server: nginx Date: Fri, 05 Sep 2014 16:28:28 GMT Content-Type: text/html Content-Length: 178 Connection: keep-alive Location: https://jenkins.foobar.com/job/Ville%20de%20Montr%E9al%20Reporter%20iOS%20Application/43/warnings10Result GET /job/Ville%20de%20Montr%E9al%20Reporter%20iOS%20Application/43/warnings10Result HTTP/1.1 502 Bad Gateway Server: nginx Date: Fri, 05 Sep 2014 16:35:25 GMT Content-Type: text/html Content-Length: 537 Connection: keep-alive ETag: "51fbbaa1-219" h1An error occurred./h1 pSorry, the page you are looking for is currently unavailable.br/ Please try again later./p If you check at the URLs, you'll see that in the first request, the é is encoded into %C3%A9 code (which is correct in UTF-8). But the Location: header in the response change this encoding to %E9 (ISO-8859-1), which is incorrect. That's why the redirection fail with this 502 HTTP status message: An error occurred. Sorry, the page you are looking for is currently unavailable. Please try again later. Environment: OS X Server 10.9.4 Project: Jenkins Priority: Blocker Reporter: Francis Labrie This message is automatically generated by JIRA. 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-17268) Post build task plugin: Passing arguments does not work as documented
Francis Labrie
commented on JENKINS-17268
Post build task plugin: Passing arguments does not work as documented
This functionality doesn't work on Linux and OS X either. Group captures are not available as script arguments. Example:
Regular _expression_
(?m)^.*: warning: (Incomplete '.+' bundle copy detected.)$
Script
echo "Info: Post Build Task did detect a recoverable error:\n\t${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] [xcode] (JENKINS-19955) Support for XCTest
Francis Labrie commented on JENKINS-19955 Support for XCTest This seems to be required with Xcode 5.1.1, because we can get anymore OCUnit output when executing test scheme and the Xcode Plugin just can't create an JUnit XML report. I thing the best would be to translate the DerivedData/Product Identifier/TestResults/Timestamp.xctestresults/results.plist Plist file into JUnit XML report. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [xcode] (JENKINS-19955) Support for XCTest
Francis Labrie edited a comment on JENKINS-19955 Support for XCTest This seems to be required with Xcode 5.1.1, because we can get anymore OCUnit output when executing test scheme and the Xcode Plugin just can't create an JUnit XML report. All we get is this: ** TEST SUCCEEDED ** I thing the best would be to translate the DerivedData/Product Identifier/TestResults/Timestamp.xctestresults/results.plist Plist file into JUnit XML report. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22519) Jenkins Build History page: Build Status table is always empty
Francis Labrie created JENKINS-22519 Jenkins Build History page: Build Status table is always empty Issue Type: Bug Affects Versions: current Assignee: Unassigned Attachments: Jenkins Build History section - 1.557.png Components: core Created: 07/Apr/14 12:06 PM Description: Since Jenkins 1.544, the Build Status section below the timeline graphic on the Jenkins Build History page is always empty. See screenshot below. Build jobs appear successfully in the timeline, but nothing is shown in the Build Status table below. This issue is still present in current Jenkins 1.577. Environment: Jenkins 1.557 running on OS X Server 10.9.2 Web Browsers: All major, on OS X and Windows. Project: Jenkins Priority: Major Reporter: Francis Labrie This message is automatically generated by JIRA. 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] [postbuild-task] (JENKINS-22181) Using the Escalate script execution status to job status delete all tasks except the first one
Francis Labrie created JENKINS-22181 Using the Escalate script execution status to job status delete all tasks except the first one Issue Type: Bug Affects Versions: current Assignee: Unassigned Attachments: Image_2014-03-13_16_51_collée.png, Image_2014-03-13_16_52_collée.png Components: postbuild-task Created: 13/Mar/14 8:54 PM Description: When having multiple post build tasks, selecting the "Escalate script execution status to job status" setting checkbox delete all tasks on save, keeping only the first one. Environment: Jenkins 1.554 OS X 10.9.1 Mavericks Project: Jenkins Priority: Blocker Reporter: Francis Labrie This message is automatically generated by JIRA. 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-22096) Raw HTML Description: Can't use custom URL scheme
Francis Labrie created JENKINS-22096 Raw HTML Description: Cant use custom URL scheme Issue Type: Improvement Affects Versions: current Assignee: Unassigned Components: core Created: 08/Mar/14 3:06 PM Description: When rendered, all custom URL schemes used in a tags are erased. For example, the docs-for-xcode scheme below: pClick to a href="" class="code-quote">"docs-for-xcode://http%3A%2F%2Fcocoadocs.org%2Fdocsets%2FAFNetworking%2Fxcode-docset.atom"add to Xcode/a (via a href="" class="code-quote">"http://documancer.com/xcode/"Docs for Xcode/a)/p It would be useful to allow them to ease some tool interactions. This support could be controlled with a checkbox in the security settings. Environment: OS X 10.9.2 Mavericks Project: Jenkins Priority: Major Reporter: Francis Labrie This message is automatically generated by JIRA. 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] [hue-light] (JENKINS-22048) Hue-Light plugin doesn't work with Maven jobs
Francis Labrie created JENKINS-22048 Hue-Light plugin doesnt work with Maven jobs Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: hue-light Created: 05/Mar/14 5:18 PM Description: The Hue-Light plugin doesn't work with Maven 2/3 type of job because the LightNotifier.prebuild() method that create doesn't seem to be called to initialize the lightController attribute. ERROR: Publisher org.jenkinsci.plugins.hue_light.LightNotifier aborted due to exception java.lang.NullPointerException at org.jenkinsci.plugins.hue_light.LightNotifier.perform(LightNotifier.java:47) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:804) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:776) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.cleanUp(MavenModuleSetBuild.java:1054) at hudson.model.Run.execute(Run.java:1721) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:519) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:231) Finished: FAILURE Environment: OS X 10.9.2 Mavericks, Jenkins 1.553 Project: Jenkins Priority: Blocker Reporter: Francis Labrie This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [analysis-core] (JENKINS-21769) NoClassDefFoundError on Job page when checkstyle not installed
Francis Labrie edited a comment on JENKINS-21769 NoClassDefFoundError on Job page when checkstyle not installed I have the same problem on Mac OS X 10.9 Mavericks, and I get it whenever the CheckStyle plugin is installed or not. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [analysis-core] (JENKINS-21769) NoClassDefFoundError on Job page when checkstyle not installed
Francis Labrie commented on JENKINS-21769 NoClassDefFoundError on Job page when checkstyle not installed I have the same problem on Mac OS X 10.9 Mavericks. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [xcode] (JENKINS-15941) Xcode PlugIn can't properly build an IPA when the Info.plist File build setting contains a variable
Francis Labrie commented on JENKINS-15941 Xcode PlugIn cant properly build an IPA when the Info.plist File build setting contains a variable Will this new release appear in updates in Jenkins PlugIns Manager? I can't build and install it myself. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-15941) Xcode PlugIn can't properly build an IPA when the Info.plist File build setting contains a variable
Francis Labrie created JENKINS-15941 Xcode PlugIn cant properly build an IPA when the Info.plist File build setting contains a variable Issue Type: Bug Assignee: Unassigned Components: xcode Created: 27/Nov/12 2:41 PM Description: Xcode PlugIn can't properly build an IPA when the "Info.plist File" build setting contains a variable like this: Info.plist File $(PROJECT_NAME)/Resources/Info.plist When using a such setting, we got this in the log: Output directory: '/Users/Shared/Jenkins/Home/jobs/FooBar Mobile Application/workspace/build/FooBarMobile-Release-$(PROJECT_NAME)/Resources/Info.plist.ipa' ... + /usr/bin/zip --symlinks --verbose --recurse-paths /Users/Shared/Jenkins/Home/jobs/FooBar Mobile Application/workspace/build/FooBarMobile-Release-$(PROJECT_NAME)/Resources/Info.plist.ipa . Program /usr/bin/zip returned 15 : [zip I/O error: No such file or directory zip error: Could not create output file (/Users/Shared/Jenkins/Home/jobs/FooBar Mobile Application/workspace/build/FooBarMobile-Release-$(PROJECT_NAME)/Resources/Info.plist.ipa) ] error: Unable to create '/Users/Shared/Jenkins/Home/jobs/FooBar Mobile Application/workspace/build/FooBarMobile-Release-$(PROJECT_NAME)/Resources/Info.plist.ipa' Failed to build /Users/Shared/Jenkins/Home/jobs/FooBar Mobile Application/workspace/build/FooBarMobile-Release-$(PROJECT_NAME)/Resources/Info.plist.ipa So could you add variable support for this build IPA task, please? Thank you very much. Project: Jenkins Priority: Critical Reporter: Francis Labrie This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15902) Add support for custom xcodebuild arguments
Francis Labrie created JENKINS-15902 Add support for custom xcodebuild arguments Issue Type: Improvement Assignee: Josh Kennedy Components: clang-scanbuild Created: 22/Nov/12 6:37 PM Description: It would like very useful to add a parameter field to this plugin to be able to set custom xcodebuild arguments. Just like the Xcode plugin. These arguments are typically build settings like FOO_BAR=YES. We need these to avoid some Xcode build phase when performing the C language analysis. Thank you very much. Project: Jenkins Priority: Major Reporter: Francis Labrie This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12920) LDAP autentication has incorrect credentials for user
Francis Labrie
commented on JENKINS-12920
LDAP autentication has incorrect credentials for user
I have the same problem here, but the warning seems to be a log string format problem in class org.acegisecurity.providers.ldap.authenticator.BindAuthenticator2 only:
@Override
void handleBindException(String userDn, String username, Throwable cause) {
LOGGER.log(hadSuccessfulAuthentication? Level.FINE : Level.WARNING,
"Failed to bind to LDAP: userDn"+userDn+" username="+username,cause);
super.handleBindException(userDn, username, cause);
}
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12920) LDAP autentication has incorrect credentials for user
Francis Labrie
edited a comment on JENKINS-12920
LDAP autentication has incorrect credentials for user
I have the same problem here, but the warning seems to be a log string format problem in class org.acegisecurity.providers.ldap.authenticator.BindAuthenticator2 only:
@Override
void handleBindException(String userDn, String username, Throwable cause) {
LOGGER.log(hadSuccessfulAuthentication? Level.FINE : Level.WARNING,
"Failed to bind to LDAP: userDn"+userDn+" username="+username,cause);
super.handleBindException(userDn, username, cause);
}
Personnaly, I've fixed the problem by setting User search base to ou=people and Group search base to ou=groups.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14375) Xcode plugin: Can't use environment variable in Custom xcodebuild arguments field
Francis Labrie
created JENKINS-14375
Xcode plugin: Cant use environment variable in Custom xcodebuild arguments field
Issue Type:
Bug
Assignee:
Unassigned
Components:
xcode
Created:
10/Jul/12 5:39 PM
Description:
When we set environment variables in the "Custom xcodebuild arguments" field using a standard $ prefixed format ($VARIABLE or ${VARIABLE}), the Xcode Plugin doesn't substitute the variable placeholders with the current values.
For exemple, when I try to securely pass a password using the "Mask Passwords Plugin" (https://wiki.jenkins-ci.org/display/JENKINS/Mask+Passwords+Plugin), I get the literal placeholder as value instead of the masked password:
Custom xcodebuild arguments: TEST_PASSWORD=${TEST_PASSWORD}
Would it be possible to replace the variable placeholders in this field by the related environment variable values, please? Thank you very much.
Environment:
Mac OS X Server 10.7.4, Jenkins 1.473, Xcode Plugin 1.3.1
Project:
Jenkins
Priority:
Major
Reporter:
Francis Labrie
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14375) Xcode plugin: Can't use environment variable in Custom xcodebuild arguments field
Francis Labrie
updated JENKINS-14375
Xcode plugin: Cant use environment variable in Custom xcodebuild arguments field
Change By:
Francis Labrie
(10/Jul/12 5:57 PM)
Description:
WhenwesetenvironmentvariablesintheCustomxcodebuildargumentsfieldusingastandard$prefixedformat($VARIABLEor${VARIABLE}),theXcodePlugindoesntsubstitutethevariableplaceholderswiththecurrentvalues.Forexemple,whenItrytosecurelypassapasswordusingtheMaskPasswordsPlugin(https://wiki.jenkins-ci.org/display/JENKINS/Mask+Passwords+Plugin),Igettheliteralplaceholderasvalueinsteadofthemaskedpassword:Customxcodebuildarguments:TEST_PASSWORD=${TEST_PASSWORD}Woulditbepossibletoreplacethevariableplaceholdersinthisfieldbytherelatedenvironmentvariablevalues,please?Thankyouverymuch.
Herearesomesolutions:-hudson.Util.replaceMacro(...)JavamethodsinmainJenkinspackage;-http://stackoverflow.com/questions/4752817/expand-environment-variables-in-text
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
