Open RohitKBhatnagar opened 6 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.0)
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.277.1</jenkins.version>
to at least 2.426.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
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.
/hosting re-check Upgraded plugin parent pom version as well as Jenkins version as per the guidance. Additionally updated the repository name to include -plugin or 'folder-tear-down-plugin' repository name. Thanks
/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.
You can re-trigger a check by editing your hosting request or by commenting /hosting re-check
Hey,
could you fill out the README.md with details how this plugin works, what it aims for to solve etc.? That would facilitate reviewing a lot. An example, how a well-written plugin description can look like, can be found here: https://plugins.jenkins.io/jetbrains-space/
/hosting re-check Sorry about that somehow I missed providing the necessary details. I have updated the ReadMe.md and also insured that the pom specifies the repository name with -plugin as suffix. New Repository Name - folder-tear-down-plugin
Thank you for guiding me here! I have updated the ReadMe.md and checked in the code. Can you please review.ThanksRohitOn Mar 17, 2024, at 2:51 AM, Alexander Brandes @.***> wrote: Hey, could you fill out the README.md with details how this plugin works, what it aims for to solve etc.? That would facilitate reviewing a lot. An example, how a well-written plugin description can look like, can be found here: https://plugins.jenkins.io/jetbrains-space/
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>
/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.
You can re-trigger a check by editing your hosting request or by commenting /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
I still do not understand, what this plugin is supposed to solve. Nor am I confident that you have tested your functionality boldly because the existing folder structure basically blows up your Jenkins instance, if you tried to create a pipeline job.
/hosting re-check Hello, Sorry for all the confusions at my end. I thought just simply updating the parent pom with suffix of plugin would be sufficient. I didn't realize my GitHub repository is not created with -plugin suffix. My apologies for any inconvenience. I have updated the ReadMe.md file with the purpose of this plugin including how to run the same. GitHub URL - https://github.com/RohitKBhatnagar/folder-tear-down-plugin Kindly review the same Thanks
/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
Repository URL
https://github.com/RohitKBhatnagar/folder-tear-down
New Repository Name
folder-tear-down-plugin
Description
Folder-Tear-Down plugin will allow tearing of entire folder which may host workflow type pipelines including multi-branch pipelines as well as credentials if any defined within that folder. Primary purpose would be to allow proper cleanup of entire folder as specified. Plugin may be extended to allow various job types for tear down.
GitHub users to have commit permission
@RohitKBhatnagar
Jenkins project users to have release permission
RohitKBhatnagar
Issue tracker
Jira