Closed MortenRa closed 2 years ago
@waldo1001 can you check if this is on your site, currently stuck for compiling any apps
@waldo1001 Same here, before that i got a failed pipeline stating that a potential virus or threat found. I put the whole agent folder in defenders exclusion list.
Finishing: ALOPS - Compile Extension: App
After that we also get the above error about a missing ps1 script.
Update: After setting exclusion the files must also be restored so the pipelines start working again
Please read the previous issue: https://github.com/HodorNV/ALOps/issues/531
I think it's the same "issue" .. where defender is enabled and wrongfully accusing the script to be malicious.. . We don't have defender "under control" .. and the script hasn't changed for ages.
If you have tips on how to prevent this, I'm all ears.
We simply have an exclusion on the build-directory .. which prevents this behaviour..
@waldo1001 Same here, before that i got a failed pipeline stating that a potential virus or threat found. I put the whole agent folder in defenders exclusion list.
[error]The term '.\5b0df20d-fb55-4c26-a587-35fca8680bac.ps1' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again. Finishing: ALOPS - Compile Extension: App
After that we also get the above error about a missing ps1 script.
Update: After setting exclusion the files must also be restored so the pipelines start working again
@panas78 what do you mean when you write it should be restored?
@MortenRa Defender had them on quarantine so you must restore the "infected" files after you set the folder to exclusion list
@panas78 okey files are restored, but still get errors in pipeline in regards to missing .ps1
@MortenRa Don't know, after doing the same process on all agents every pipeline started working again
I have 2 build agent server, on the first I had file that was "infected" but on build server 2 which runs in the weekend no "infected" files but still error, I have added agent folders to exclusion list but still get this error
Can you try to rebuild the agent?
Remove service, remove folder, re-install the agent.. ?
@waldo1001 after cleaning and remove service etc. I´m back on track again.
Thanks for letting me know! have a nice weekend!
Describe the bug Getting this error in our nightly pipeline, no changes in my setup and tried to run this right now still same error
The term 'New-ALOpsV2Compilation' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
the used yaml please provide the yaml that you used. It helps you put the yaml like this:
the output Also the complete output is necessary for us to see what is going on. Also use backtics:
Expected behavior not to fail