[JIRA] (JENKINS-60772) Microsoft Edge identified as Chrome
Title: Message Title Jo Shields created an issue Jenkins / JENKINS-60772 Microsoft Edge identified as Chrome Issue Type: Improvement Assignee: evernat Components: monitoring-plugin Created: 2020-01-14 21:04 Priority: Minor Reporter: Jo Shields Microsoft are dumping the EdgeHTML engine, and switching to a Chromium derivative. The suffix `Edg/` identifies the new browser. Old example: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.140 Safari/537.36 Edge/18.17763 New example: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/81.0.3993.0 Safari/537.36 Edg/81.0.369.0 Both are likely to exist in the wild for a while. Add Comment
[JIRA] (JENKINS-60771) "Country" column is misleading
Title: Message Title Jo Shields created an issue Jenkins / JENKINS-60771 "Country" column is misleading Issue Type: Improvement Assignee: evernat Components: monitoring-plugin Created: 2020-01-14 20:59 Priority: Minor Reporter: Jo Shields "Country" in the sessions pane implies something about the geographic location of the user. This column would be more accurately descriptive as something like "Locale" if it's intending to convey that information, or a GeoIP lookup rather than locale match if it's intending to really identify the country. Add Comment
[JIRA] (JENKINS-56506) Cannot upload files larger than 100MB since 0.3.12
Title: Message Title Jo Shields updated an issue Jenkins / JENKINS-56506 Cannot upload files larger than 100MB since 0.3.12 Change By: Jo Shields Priority: Minor Major Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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] (JENKINS-56506) Cannot upload files larger than 100MB since 0.3.12
Title: Message Title Jo Shields updated an issue Jenkins / JENKINS-56506 Cannot upload files larger than 100MB since 0.3.12 Change By: Jo Shields Summary: Uploading fails, with multiple Cannot upload files of varying sizes, larger than 100MB since 0.3.12 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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] (JENKINS-56506) Uploading fails, with multiple files of varying sizes, since 0.3.12
Title: Message Title Jo Shields commented on JENKINS-56506 Re: Uploading fails, with multiple files of varying sizes, since 0.3.12 As per https://docs.microsoft.com/en-us/rest/api/storageservices/put-block there's a 100MB limit on uploads in the REST API Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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] (JENKINS-56506) Uploading fails, with multiple files of varying sizes, since 0.3.12
Title: Message Title Jo Shields commented on JENKINS-56506 Re: Uploading fails, with multiple files of varying sizes, since 0.3.12 The un-uploaded files are HTTP 413 returns (Payload too large) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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] (JENKINS-56506) Uploading fails, with multiple files of varying sizes, since 0.3.12
Title: Message Title Jo Shields created an issue Jenkins / JENKINS-56506 Uploading fails, with multiple files of varying sizes, since 0.3.12 Issue Type: Bug Assignee: Azure DevOps Components: windows-azure-storage-plugin Created: 2019-03-11 18:08 Priority: Minor Reporter: Jo Shields This is probably the same issues experienced in JENKINS-55814 Since this version, we now see text like the following in a lot of our builds: [2019-03-11T13:51:57.733Z] MicrosoftAzureStorage - Need uploaded/archived file count = 11 [2019-03-11T13:51:57.733Z] MicrosoftAzureStorage - Uploaded/archived file count = 10 The missing file is almost always the largest one out of a set. I'm able to reproduce the effect locally, and the "missing" file upload appears to happen at the end of the upload - i.e. lots of data is transferred, but never reflected in the blob container. I'm going to continue working through the problem in a debugger to better isolate exactly what broke. Please ping me via Teams if it helps speed up tracking the problem, it's badly affecting multiple groups for us here. For an "easy" repro, try a job which uploads one very small file, and one very large file (hundreds of megabytes) Add Comment
[JIRA] (JENKINS-53752) Block PRs from forks from untrusted users
Title: Message Title Jo Shields commented on JENKINS-53752 Re: Block PRs from forks from untrusted users No. That's the point. That setting determines whether pull requests should use Jenkinsfile from origin/ or from the fork - it has no functionality to block pull requests from users under any circumstance. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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] (JENKINS-52842) xUnit plugin blocks PingThread responses
Title: Message Title
Jo Shields created an issue
Jenkins / JENKINS-52842
xUnit plugin blocks PingThread responses
Issue Type:
Bug
Assignee:
Nikolas Falco
Components:
xunit-plugin
Created:
2018-08-01 19:02
Priority:
Minor
Reporter:
Jo Shields
If your xUnit parsing takes a long time (don't ask), the entire build agent can be kicked offline, by passing the timeout threshhold on pings (default 4 minutes). Agent: 12:39:02 [xUnit] [INFO] - [NUnit-2 (default)] - 110 test report file(s) were found with the pattern '*/TestResult.xml' relative to '/home/builder/jenkins/workspace/foo' for the testing framework 'NUnit-2 (default)'. 12:44:28 [xUnit] [ERROR] - The plugin hasn't been performed correctly: Remote call on JNLP4-connect connection from 1.1.1.1/1.1.1.1:1880 failed Server: INFO: Ping failed. Terminating the channel JNLP4-connect connection from 1.1.1.1/1.1.1.1:7468. java.util.concurrent.TimeoutException: Ping started at 1532979041327 hasn't completed by 1532979281327 {{ at hudson.remoting.PingThread.ping(PingThread.java:134)}} {{ at hudson.remoting.PingThread.run(PingThread.java:90)}}
Add Comment
[JIRA] (JENKINS-52842) xUnit plugin blocks PingThread responses
Title: Message Title
Jo Shields updated an issue
Jenkins / JENKINS-52842
xUnit plugin blocks PingThread responses
Change By:
Jo Shields
If your xUnit parsing takes a long time (don't ask), the entire build agent can be kicked offline, by passing the timeout threshhold on pings (default 4 minutes). Agent:{{12:39:02 [xUnit] [INFO] - [NUnit-2 (default)] - 110 test report file(s) were found with the pattern '**/TestResult*.xml' relative to '/home/builder/jenkins/workspace/foo' for the testing framework 'NUnit-2 (default)'.}}{{12:44:28 [xUnit] [ERROR] - The plugin hasn't been performed correctly: Remote call on JNLP4-connect connection from 1.1.1.1/1.1.1.1:1880 failed}}Server:{{INFO: Ping failed. Terminating the channel JNLP4-connect connection from 1.1.1.1/1.1.1.1:7468.}}{{java.util.concurrent.TimeoutException: Ping started at 1532979041327 hasn't completed by 1532979281327}}{{ at hudson.remoting.PingThread.ping(PingThread.java:134)}}{{ at hudson.remoting.PingThread.run(PingThread.java:90)}}
Add Comment
This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)
--
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] (JENKINS-49725) Windows SSH init broken, as of 2018-02-22
Title: Message Title Jo Shields created an issue Jenkins / JENKINS-49725 Windows SSH init broken, as of 2018-02-22 Issue Type: Bug Assignee: Azure DevOps Components: azure-vm-agents-plugin Created: 2018-02-24 02:16 Priority: Critical Reporter: Jo Shields GitHub has turned off support for TLS versions before 1.2, on all of https://github.com - https://githubengineering.com/crypto-removal-notice/ The Azure VM Agents plugin hardcodes a URL on github.com in its Windows SSH init script, and downloads it using System.Web.WebClient - https://github.com/jenkinsci/azure-vm-agents-plugin/blob/0e57250114b29b14ae787928b6debeafbf9d67ff/src/main/resources/scripts/sshInit.ps1#L3 Unless directed otherwise, PowerShell will always use TLS 1.0 - https://blog.pauby.com/post/force-powershell-to-use-tls-1-2/ As a result, initialization of Windows SSH agents is 100% broken, as of yesterday, because the sshInit.ps1 script does not override the TLS version on WebClient to 1.2, causing the script to fail. This cannot be worked around, without a custom compile of the plugin with a fixed PowerShell script. Add Comment
[JIRA] (JENKINS-49675) screenResolution cookie set without explicit permission, likely GDPR violation
Title: Message Title
Jo Shields created an issue
Jenkins / JENKINS-49675
screenResolution cookie set without explicit permission, likely GDPR violation
Issue Type:
Bug
Assignee:
Unassigned
Components:
core
Created:
2018-02-21 14:40
Priority:
Minor
Reporter:
Jo Shields
A new European regulation on the collection of identifying information, General Data Protection Regulation ("GDPR"), combines with existing legislation regarding consent being required before saving of cookies on any given domain. As stupid as it may seem, screen resolution is regarded as identifying information, and it's stored immediately upon loading a Jenkins server, courtesy https://github.com/jenkinsci/jenkins/blob/master/core/src/main/resources/hudson/model/View/index.jelly#L48 This needs to be optional, pending implementation of a "Cookie Consent" feature, for any Jenkins server accessible in Europe to be legally compliant.
Add Comment
[JIRA] (JENKINS-43223) Make "Open Blue Ocean" button hideable
Title: Message Title Jo Shields created an issue Jenkins / JENKINS-43223 Make "Open Blue Ocean" button hideable Issue Type: Bug Assignee: Unassigned Components: blueocean-plugin Created: 2017/Mar/30 10:21 AM Priority: Minor Reporter: Jo Shields We'd like to be able to show Blue Ocean to some of our developers, so they can assess its suitability for their projects. However, we'd like to do that without a big honking "Open Blue Ocean" button at the top of every single page for every single random third party site visitor. We'd like to be able to hide that button, either for everyone or for Anonymous, so we can be selective on our showing off of the feature. I don't know enough about using _javascript_ in Jenkins plugins to make it a conditional - seems it's blueocean-web/src/main/js/try.js which does the insertion, but I'm not sure how to use that knowledge Add Comment
[JIRA] (JENKINS-42799) Add support for Cloud Statistics Plugin
Title: Message Title Jo Shields created an issue Jenkins / JENKINS-42799 Add support for Cloud Statistics Plugin Issue Type: Improvement Assignee: Azure DevOps Components: azure-vm-agents-plugin Created: 2017/Mar/15 9:41 AM Priority: Minor Reporter: Jo Shields https://github.com/jenkinsci/cloud-stats-plugin It would be nice for Azure VMs to get reported by this plugin.I'd be interested in some of the statistics cloud-stats-plugin tracks Add Comment This message was sent by Atlassian JIRA
[JIRA] (JENKINS-42766) Job with emoji in the name not treated correctly
Title: Message Title Jo Shields commented on JENKINS-42766 Re: Job with emoji in the name not treated correctly This seems to be a mishandling of wide characters, not non-ascii in general. U+0402 CYRILLIC CAPITAL LETTER DJE no problem, U+10398 UGARITIC LETTER THANNA 404. And, again, JIRA throws exceptions on trying to include said characters directly in my bug. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-42766) Job with emoji in the name not treated correctly
Title: Message Title Jo Shields commented on JENKINS-42766 Re: Job with emoji in the name not treated correctly I was going to add text illustrating how the Chrome address bar shows the character as expected, not the %foo escape sequence. But that made Jira throw an exception. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-42766) Job with emoji in the name not treated correctly
Title: Message Title Jo Shields created an issue Jenkins / JENKINS-42766 Job with emoji in the name not treated correctly Issue Type: Bug Assignee: Unassigned Components: core Created: 2017/Mar/14 6:13 PM Environment: Jenkins 2.50 Priority: Minor Reporter: Jo Shields Don't laugh. Due to the painfully short MAX_PATH on Windows, we have a bunch of jobs with single-character job names, and user-friendly display names. Since that limits the number of jobs we can create for Windows, I tried creating a job with a valid Unicode character as the job name. I got a 404 from this, when it forwarded to the job config - however, the job WAS created. Similarly the job shows in the view, but clicking it throws a 404 - but manually editing the URL works. It seems Unicode characters are stripped from whichever method creates a /job/JOBNAME/ url? e.g. links which should read http://localhost:8080/job/%F0%9F%90%A7/ instead read http://localhost:8080/job// Add Comment
[JIRA] (JENKINS-42726) Artifact download links no longer work
Title: Message Title Jo Shields created an issue Jenkins / JENKINS-42726 Artifact download links no longer work Issue Type: Bug Assignee: Azure DevOps Components: windows-azure-storage-plugin Created: 2017/Mar/13 8:25 PM Environment: Jenkins 2.32.3 Azure blob plugin 0.3.3 Labels: regression Priority: Major Reporter: Jo Shields Since b1e1bd761d7b258118fd645512851b7ba76a753e, links in Jenkins (i.e. URLs containing /Azure/processDownloadRequest/) no longer work. ERROR 500: Azure Storage account global configuration is missing. This is because in 0.3.2, there was a "global" set of credentials gone in 0.3.3 - and this global value is checked in https://github.com/jenkinsci/windows-azure-storage-plugin/blob/master/src/main/java/com/microsoftopentechnologies/windowsazurestorage/AzureBlobAction.java#L102-L105 Add
[JIRA] (JENKINS-42341) UNSTABLE status when filtering downloads from a matrix job completely filters a matrix configuration
Title: Message Title
Jo Shields updated an issue
Jenkins / JENKINS-42341
UNSTABLE status when filtering downloads from a matrix job completely filters a matrix configuration
Change By:
Jo Shields
Let's say I have a matrix job with two configurations: ARM and x86.I have files uploaded from each job, such that I have:ARM/output_armx86/output_x86x86/output_genericI then have a second job, configured to download files from an Azure storage container of output from the first job - and I have a "Files to download (ant syntax)" set to " \ * \ */ \ *_x86"The Azure Storage plugin iterates each configuration of a matrix job separately, and considers an empty "Download from Azure Blob storage" set as an UNSTABLE-grade error - so this job would be marked UNSTABLE, because 0 files are downloaded in the ARM configuration.{code}17:51:31 MicrosoftAzureStorage - Downloading files from Azure Blob storage17:51:31 MicrosoftAzureStorage - Failed to download files from Azure storage.17:51:31 Verify that files exists with specified blob name 17:51:31 Build step 'Download from Azure Blob storage' changed build result to UNSTABLE{code}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-42341) UNSTABLE status when filtering downloads from a matrix job completely filters a matrix configuration
Title: Message Title
Jo Shields updated an issue
Jenkins / JENKINS-42341
UNSTABLE status when filtering downloads from a matrix job completely filters a matrix configuration
Change By:
Jo Shields
Let's say I have a matrix job with two configurations: ARM and x86.I have files uploaded from each job, such that I have:ARM/output_armx86/output_x86x86/output_genericI then have a second job, configured to download files from an Azure storage container of output from the first job - and I have a "Files to download (ant syntax)" set to "**/*_x86"The Azure Storage plugin iterates each configuration of a matrix job separately, and considers an empty "Download from Azure Blob storage" set as an UNSTABLE-grade error - so this job would be marked UNSTABLE, because 0 files are downloaded in the ARM configuration.{ { code} 17:51:31 MicrosoftAzureStorage - Downloading files from Azure Blob storage17:51:31 MicrosoftAzureStorage - Failed to download files from Azure storage.17:51:31 Verify that files exists with specified blob name 17:51:31 Build step 'Download from Azure Blob storage' changed build result to UNSTABLE {code } }
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-42341) UNSTABLE status when filtering downloads from a matrix job completely filters a matrix configuration
Title: Message Title
Jo Shields updated an issue
Jenkins / JENKINS-42341
UNSTABLE status when filtering downloads from a matrix job completely filters a matrix configuration
Change By:
Jo Shields
Let's say I have a matrix job with two configurations: ARM and x86.I have files uploaded from each job, such that I have:ARM/output_armx86/output_x86x86/output_genericI then have a second job, configured to download files from an Azure storage container of output from the first job - and I have a "Files to download (ant syntax)" set to "**/*_x86"The Azure Storage plugin iterates each configuration of a matrix job separately, and considers an empty "Download from Azure Blob storage" set as an UNSTABLE-grade error - so this job would be marked UNSTABLE, because 0 files are downloaded in the ARM configuration.{{ 17:51:31 MicrosoftAzureStorage - Downloading files from Azure Blob storage17:51:31 MicrosoftAzureStorage - Failed to download files from Azure storage.17:51:31 Verify that files exists with specified blob name 17:51:31 Build step 'Download from Azure Blob storage' changed build result to UNSTABLE }}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-41922) "Minimum instances" support
Title: Message Title Jo Shields commented on JENKINS-41922 Re: "Minimum instances" support A co-worker proposes an interesting similar-but-different proposal: minimum idle VM instances under load - i.e. if I set the value to 2, and i have jobs running on 2 of a given VM type, then 2 more get started up to pre-fulfil the requirements of subsequent job submissions whilst the first 2 are still in use. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-41922) "Minimum instances" support
Title: Message Title Jo Shields created an issue Jenkins / JENKINS-41922 "Minimum instances" support Issue Type: Improvement Assignee: Claudiu Guiman Components: azure-vm-agents-plugin Created: 2017/Feb/10 11:39 AM Environment: Jenkins ver. 2.32.2 Priority: Minor Reporter: Jo Shields Sometimes it can take a long time to spin up a VM. It would be nice if we could set a number-of-VMs threshold where retention time does not apply. For example, I could keep two of my "general" VMs running at all times so jobs start immediately under light load, and new VMs only start getting created under heavier load. Looks like the logic is in main/java/com/microsoft/azure/AzureVMCloudRetensionStrategy.java ? Add Comment
[JIRA] (JENKINS-41379) Cannot provision Windows agent
Title: Message Title Jo Shields commented on JENKINS-41379 Re: Cannot provision Windows agent I'm looking at the activity log, but I'm not sure how to interpret the data. It's failing on a Write Deployments sub-step of Write VirtualMachines. I've attached the raw JSON from the activity log for the failed step. I'm not near to any limits in the subscription quotas page - internal-use subscription, with very few limits. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-41379) Cannot provision Windows agent
Title: Message Title Jo Shields updated an issue Jenkins / JENKINS-41379 Cannot provision Windows agent Change By: Jo Shields Attachment: error.json Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-41379) Cannot provision Windows agent
Title: Message Title
Jo Shields created an issue
Jenkins / JENKINS-41379
Cannot provision Windows agent
Issue Type:
New Feature
Assignee:
Claudiu Guiman
Attachments:
linuxazure.xml, windowsazure.xml
Components:
azure-vm-agents-plugin
Created:
2017/Jan/24 4:57 PM
Environment:
Jenkins 2.42 Azure VM Agents 0.4.1
Priority:
Minor
Reporter:
Jo Shields
I'm testing a migration from the old Azure Slaves plugin to the new ARM plugin. I've got a Linux deployment working properly, with SSH & an an init script on top of a fresh Ubuntu VM (i.e. NOT using disk capture on a previously configured VM). Trying to achieve similar on Windows, however, yields the following: {{INFO: AzureVMCloud: createProvisionedAgent: Waiting for deployment wintest0124162232263 to be completed Jan 24, 2017 4:23:13 PM com.microsoft.azure.AzureVMCloud$3 call SEVERE: Failure creating provisioned agent 'wintest9c51a0' com.microsoft.azure.exceptions.AzureCloudException: AzureVMCloud: createProvisionedAgent: Deployment Failed: Microsoft.Compute/virtualMachines:wintest9c51a0 - BadRequest at com.microsoft.azure.AzureVMCloud.createProvisionedAgent(AzureVMCloud.java:410) at com.microsoft.azure.AzureVMCloud.access$100(AzureVMCloud.java:69) at com.microsoft.azure.AzureVMCloud$3.call(AzureVMCloud.java:547) at com.microsoft.azure.AzureVMCloud$3.call(AzureVMCloud.java:533) at jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at
[JIRA] (JENKINS-38726) Does not allow "execute shell" scripts without #!/bin/foo header
Title: Message Title Jo Shields created an issue Jenkins / JENKINS-38726 Does not allow "execute shell" scripts without #!/bin/foo header Issue Type: New Feature Assignee: Unassigned Components: cygpath-plugin Created: 2016/Oct/05 9:00 AM Priority: Minor Reporter: Jo Shields A recent update to Jenkins means the "Execute shell" script no longer executes "/bin/sh" by default - it executes "sh" As a result, the CygPath plugin no longer works, for any scripts which don't include a #!/bin/foo shell as an explicit override. Add Comment
