Open cotovanu-cristian opened 3 hours ago
pom.xml
<execution> <id>Generate help files</id> <phase>generate-resources</phase> <goals> <goal>run</goal> </goals> <configuration> <target> <exec executable="powershell.exe"> <arg value=".\GenerateHelpFiles.ps1 " /> </exec> </target> </configuration> </execution>
Expected the Scan to execute
The scan failed cause the agent did not have powershell.exe
powershell.exe
In the pom.xml we run a powershell script running in the build goals, but the agent building the plugin in the security scan script is a linux agent thus it won't be capable of building the plugin used for the security assesment (https://github.com/jenkinsci/uipath-automation-package-plugin/blob/develop/pom.xml#L120C1-L126C41). What can we do to onboard to the Jenkins Security Scan?
Jenkins Security Scan
scan example: https://github.com/jenkinsci/uipath-automation-package-plugin/actions/runs/11416380208/job/31767532043
Reproduction steps
pom.xml
run a powershell script e.g:Expected Results
Expected the Scan to execute
Actual Results
The scan failed cause the agent did not have
powershell.exe
Anything else?
In the
pom.xml
we run a powershell script running in the build goals, but the agent building the plugin in the security scan script is a linux agent thus it won't be capable of building the plugin used for the security assesment (https://github.com/jenkinsci/uipath-automation-package-plugin/blob/develop/pom.xml#L120C1-L126C41). What can we do to onboard to theJenkins Security Scan
?