Hi Rich,
Brilliant, thank you for the update.

Regards,
Paul

Hi Alana,
Proxy support has fixed the list of templates now being available;

But the deployment fails, I guess this request is not hitting the proxy;

Thanks,
Paul

@rhessinger said in BuildMaster v2023 PSCall:

Hi @paul_6112,

What version of the Scripting extension do you have installed? This bug should be fixed in v2.4.0 of the Scripting extension. If it is not currently version 2.4.0, can you try updating that extension and see if that fixes the issue?

Thanks,
Rich

Thanks Rich,
This does appear to work okay on BuildMaster 2023.5 and Scripting 2.4.0

Hi Rich,
Tested this on 2023.5;
The extension page does now load and can see the extensions, and appears to work okay to update an extension.
However, the Icon list appears to be broken as these are not proxied via BuildMaster, but its direct Browser access.
You did fix this on a previous ticket on BM 7 ; so don't know if the same fix can be applied to BM 2023 please?

Thanks,
Paul

Hi Alana,
Using IIS was the simplest repro I could come up with for you to easily replicate, sorry..

I can confirm that something as basic as Get-Date does work;
$PSEval(Get-Date)

This is a 'raw' powershell example output;

We did try adding ' | out-string' to force any formatting for PSEval but this didn't make a difference.

I've tried your example and tried to come up with something else you should have by default (although you will have to change the InterfaceAlias to whatever yours is called..

Raw PowerShell Output;

BuildMaster 2023 Script;

Build Output;

So why does your example want to return a String (?) and my example want to return a List (?)

Thanks,
Paul

Hi Rich,
Ah, its 2.0.3 ; and due to the Proxy issue doesn't report that there was a newer version..
I note v2023.5 is now released, will see if can upgrade and get a newer version of the extension;

Thanks,
Paul

Hi Support,
When adding a PSCall in the editor, it appears there is an unexpected error;

Thanks,
Paul

Hi Support,
Given this Otterscript;

Set-BuildVariable Web
(
    Value: $PSEval("(Get-Website -Name MyWebSite).PhysicalPath")
);

This correctly sets the Variable;

After upgrading to BuildMaster v2023; it seems this is broken with the Variable output being;

Also the engine syntax highlighting is not happy with the brackets;

BuildMaster 7, the text in quotes is picked including the brackets is highlighted in green;

Vs BuildMaster 2023, the syntax highlight is not correctly following the brackets within the quotes, i.e. the middle bracket is white..

Thanks,
Paul

Hi Alana,

Well.... technically none of your software is supported since you are a free user

https://inedo.com/buildmaster/pricing

I'm currently getting my money's worth on this forum after an upgrade to v2023

Thanks,
Paul

Hi Rich,
Brilliant, thank you for the update.

Regards,
Paul

Hi Rich,
Super, thank you.

Regards,
Paul