Need to sign binaries inside gauge_bin folder in postbuild action.

[ayankumaar]

I have the following gauge setup in my system.
Gauge version: 1.1.7

Plugins

dotnet (0.3.1)
html-report (4.0.12)
screenshot (0.0.1)

While I am trying to run my script the binaries inside the gauge_bin folder are getting blocked. I need to code sign those to unblock. How can I do that in post build action with gauge ?

[sriv]

Gauge does not have a bost build hook (yet). But you can have your own build system and point to the binaries by setting GAUGE_CUSTOM_BUILD_PATH

[ayankumaar]

@sriv Even after setting GAUGE_CUSTOM_BUILD_PATH as an environment variable while executing the tests gauge is creating the gauge_bin folder at the project level. I want to prevent the gauge_bin folder from getting created. How to achieve that ?

[ayankumaar]

@sriv is there any update on this ?

[sriv]

Sorry, got distracted into other things.

I just tried with:

Gauge version: 1.2.1
Commit Hash: fa7918b5

Plugins
-------
dotnet (0.3.1)
html-report (4.0.12)
screenshot (0.0.1)

And I can see that setting GAUGE_CUSTOM_BUILD_PATH skips building the project and does not create gauge_bin for me. I am on windows 10.

[sriv]

And I tried setting environment variable in powershell, as well as setting GAUGE_CUSTOM_BUILD_PATH as a property in env\default\default.properties. Both options worked for me.

[ayankumaar]

@sriv I have setup GAUGE_CUSTOM_BUILD_PATH at env\default\default.properties. I have tried with both absolute and relative path to the binaries. For ex. I have setup the path like: C:\MyProj\Workspace\MyProj\bin\Debug\netcoreapp3.1 and as well as bin\Debug\netcoreapp3.1.

But, after setting the path I keep getting the error the gauge server crashed 5 times

I am on the following version:

Gauge version: 1.2.1
Commit Hash: fa7918b

Plugins

dotnet (0.4.1)
html-report (4.0.12)
screenshot (0.0.1)

[sriv]

Do you see any errors in the logs? the gauge server crashed 5 times is thrown by vscode, and it indicates that gauge could not run on your project.

Try running gauge daemon --lsp in your terminal and see if you are seeing any errors there.

[ayankumaar]

@sriv is there any update on my query ?

[sriv]

@ayankumaar we seem to be going around in circles. I had already mentioned that these are side effects of using GAUGE_CUSTOM_BUILD_PATH and there is no workaround at the moment.

[ayankumaar]

@sriv I got what you said. I was expecting a fix to this because these are existing issues. That is why I was checking if there is a fix available.

[sriv]

@ayankumaar - no, there is no fix for this yet.

[ayankumaar]

@sriv Got it thanks.