-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
All RegEx Find & Replace tasks in pipelines fail. The reason is that "A parameter cannot be found that matches parameter name 'NoNewLine'." #27
Comments
Since many people are getting hit by this, myself included, I'll take this opportunity to ask if there's a way to freeze the task version to the one before this bug? I can only choose 3.* in the dropdown in the UI. Would I be able to do set a specific version if I were using YAML pipelines? I happen to be using this task inside a Task Group, which I understand comes with some limitations. |
I found an analogue of this library in the marketplace, and replaced them in some places. But updating all pipelines to a new library is difficult. It’s easier to wait for the update. |
I replaced it with some pretty basic PowerShell:
YMMV depending on how advanced your use case is. |
I am also getting this error now all of a sudden. Does anyone know the cause of why this all of a sudden stopped working? |
Same problem here! Version updated 4 hours ago and my build stopped working :( |
What do we think about getting this fixed? Is everyone moving away from this or do we think the author will help us fix it quickly? I need to make a decision and have no developers to lend to this repo at this time. Thoughts from others in this thread? |
I replace the task with PowerShell task:
|
Even in our continuous integration process, it is breaking our build pipeline. I am wondering whether the Author knew about this? is he working on it? we don't have any clue? We can find a work around, However it will be easier to reuse the extension component as it was tested and working before. |
same issue here, thank you for any update. |
Same error here |
I just replaced the plugin with a powershell script that does the same thing. Took me about 15 minutes. |
Thanks folks for raising this! I'm looking for a new way to improve testing (maybe a BETA test ring), so that will not happen again.. As for the fix - working on it today / tomorrow and posting here, when the new version is published! Meanwhile the script posted up there looks good. |
It's quite strange, I use same task on 2 servers , my Windows 2012 didn't work but on my W2019 it work! |
This powershell script does the trick. Lifted directly from a blog post but can no longer find the source, so credit and thanks to that poster whoever you are! Use the preview flag to check whether the script find the appropriate files without actually changing them. $find = "tofind" foreach ($sc in dir -recurse -include |
Can people post the PLATFORM where it doesn't work? Especially the Powershell Version? |
I have now published version 3.3.10, which should fix the bug! Here is what happened (as usually a combination of mistakes)...
Please confirm if people seeing the issue were running Powershell < 5. Again as usual.. a mix of things.. Apologies for that! And if not, please supply your Powershell Version as well! |
For your information, my |
Does it work now? |
Yep! it work, thanks |
This change broke the task for us, we use it on a server which only has PS3.0 installed. Because you added the PS4.0 check it broke (it worked fine before). Unfortunately it's rather difficult for us to upgrade the PowerShell version on this server. |
Let's discuss on the other thread.. |
Image removed
The text was updated successfully, but these errors were encountered: