Open siddhantdange opened 1 week ago
Hello from your friendly Jenkins Hosting Checker
It appears you have some issues with your hosting request. Please see the list below and correct all issues marked Required. Your hosting request will not be approved until these issues are corrected. Issues marked with Warning or Info are just recommendations and will not stall the hosting process.
You can re-trigger a check by editing your hosting request or by commenting /hosting re-check
/hosting re-check
Hello from your friendly Jenkins Hosting Checker
It looks like you have everything in order for your hosting request. A member of the Jenkins hosting team will check over things that I am not able to check(code review, README content, etc) and process the request as quickly as possible. Thank you for your patience.
Hosting team members can host this request with /hosting host
Security audit, information and commands
The security team is auditing all the hosting requests, to ensure a better security by default.
This message informs you that a Jenkins Security Scan was triggered on your repository. It takes ~10 minutes to complete.
/audit-ok
=> the audit is complete, the hosting can continue :tada:./audit-skip
=> the audit is not necessary, the hosting can continue :tada:./audit-findings
=> the audit reveals some issues that require corrections :pencil2:./request-security-scan
=> the findings from the Jenkins Security Scan were corrected, this command will re-scan your repository :mag:./audit-review
=> the findings from the audit were corrected, this command will ping the security team to review the findings :eyes:.
It's only applicable when the previous audit required changes.(automatically generated message, version: 1.28.6)
:x: Jenkins Security Scan failed. The Security team was notified about this.
Hey @siddhantdange
I think the Security scan is failing because you do not include in the pom.xml the pluginRepository, leading to the failure to find maven-hpi-plugin:3.13
(available in the Jenkins repo)
<pluginRepositories>
<pluginRepository>
<id>repo.jenkins-ci.org</id>
<url>https://repo.jenkins-ci.org/public/</url>
</pluginRepository>
</pluginRepositories>
/request-security-scan
The Jenkins Security Scan discovered 4 finding(s) :mag:.
Please follow the instructions below for every identified issues:
After addressing the findings through one of the above methods:
/request-security-scan
command./audit-review
command.You can find detailed information about this finding here.
You can find detailed information about this finding here.
You can find detailed information about this finding here.
/request-security-scan
The Jenkins Security Scan discovered 3 finding(s) :mag:.
Please follow the instructions below for every identified issues:
After addressing the findings through one of the above methods:
/request-security-scan
command./audit-review
command.You can find detailed information about this finding here.
You can find detailed information about this finding here.
You can find detailed information about this finding here.
/request-security-scan
The Jenkins Security Scan did not find anything dangerous with your plugin, congratulations! :tada:
:bulb: The Security team recommends that you are setting up the scan in your repository by following our guide.
@NotMyFault is there any further action needed?
I'll take a look later the week
Repository URL
https://github.com/buildpulse/buildpulse-jenkins-plugin
New Repository Name
buildpulse-flaky-tests-plugin
Description
Our Jenkins plugin allows one to easily send test results to BuildPulse for CI analytics and flaky test detection.
GitHub users to have commit permission
@siddhantdange
Jenkins project users to have release permission
sidbuildpulse
Issue tracker
GitHub issues