Closed mhoffrog closed 2 months ago
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)
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.
<developerConnection>
tag in your <developerConnection>scm:git:https://github.com/jenkinsci/${project.artifactId}-plugin</developerConnection>
io.jenkins.plugins
instead of com.itemis.jenkins.plugins
You can re-trigger a check by editing your hosting request or by commenting /hosting re-check
:x: Jenkins Security Scan failed. The Security team was notified about this.
/hosting re-check
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.
<jenkins.version>2.426.3</jenkins.version>
to at least 2.440.3 in your pom.xml. Take a look at the baseline recommendations.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
/request-security-scan
The Jenkins Security Scan discovered 5 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.
/request-security-scan
The Jenkins Security Scan discovered 2 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.
/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.
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
/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.
Hi, can you instead send a pull request to add yourself to the existing repository please:
We can then get your access sorted out
Hi, can you instead send a pull request to add yourself to the existing repository please:
@timja - Done - many thanks for your support!
Repository URL
https://github.com/mavenplugins/jenkins-unleash-plugin
New Repository Name
unleash-plugin
Description
This is to followup maintaining the already existing unleash-plugin repo. Due to the original founder did discontinue maintaining the maven-unleash-plugin I would like to continue with this one. Currently I have forked the existing repo at the URL mentioned above. unleash-plugin fork. Update by 10-Jul-2024: The fork relation has already been detached by GitHub support based upon my request.
You can find up to date implementations of the
unleash-maven-plugin
there as well: unleash-maven-plugin.So I would like you to assign me appropriate commit access to repo https://github.com/jenkinsci/unleash-plugin.
GitHub users to have commit permission
@mhoffrog
Jenkins project users to have release permission
mhoffrog
Issue tracker
Jira