-
-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hosting request for CloudAEye Plugin #4131
Comments
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. CommandsThe bot will parse all comments, and it will check if any line start with a command. Security team only:
Anyone:
Only one command can be requested per comment. (automatically generated message, version: 1.29.20) |
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 |
The Jenkins Security Scan discovered 5 finding(s) 🔍. For every identified issue, please do one of the following:
After addressing the findings through one of the above methods:
Stapler: Missing permission checkYou can find detailed information about this finding here. GlobalKeyConfiguration.java#91
Jenkins: Plaintext password storageYou can find detailed information about this finding here. CloudAEyeNotifications.java#36
CloudAEyeNotifications.java#34
GlobalKeyConfiguration.java#35
GlobalKeyConfiguration.java#34
|
/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 |
/request-security-scan |
The Jenkins Security Scan did not find anything dangerous with your plugin, congratulations! 🎉 💡 The Security team recommends that you are setting up the scan in your repository by following our guide. |
/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 |
|
|
Please provide a meaningful description here: https://github.com/CloudAEye/cloudaeye-plugin/blob/a26b6638f8375a81ab4a6d12dbe46b77c302f92b/src/main/resources/index.jelly#L3 |
No our plugin for both free-style and pipeline, you can find it in implementation ( https://github.com/CloudAEye/cloudaeye-plugin/blob/a26b6638f8375a81ab4a6d12dbe46b77c302f92b/src/main/java/io/jenkins/plugins/cloudaeye/CloudAEyeNotifications.java#L198) and also in README instructions on how to use it pipeline |
Sure will update it. |
@mawinter69 are there any other suggestions that we need to improve on so that we can finish all of them together at once and resubmit for review ? |
Done |
Committed most of the suggested changes. Here are few that we did not / failed to:
Regards, |
but you don't want to execute anything afterwards so if you don't add a return statement the rest of the method will still be executed so it should look like this I think
You could use |
Yes thanks for pointing it out, I also was thinking in same lines that the logs can be huge, is there a way to identify the failed step and only extract logs of that failed step ? I could achieve this with github workflows and AWS codebuild, not sure how to do it with jenkins |
New updates:
|
@mawinter69 Can you please review the updated code and let us know any changes required |
Repository URL
https://github.com/CloudAEye/cloudaeye-plugin
New Repository Name
cloudaeye-plugin
Description
The CloudAEye Plugin is designed to enhance CI/CD pipelines by seamlessly exporting job details and build logs from Jenkins to the CloudAEye platform. CloudAEye analyzes test failure logs to identify root causes and suggests actionable code fixes, helping developers resolve issues more efficiently. By providing real-time insights into build failures, the plugin enables faster troubleshooting and minimizes downtime in software delivery pipelines.
Key Features:
GitHub users to have commit permission
@bhavyalatha26
Jenkins project users to have release permission
cloudaeye
Issue tracker
GitHub issues
The text was updated successfully, but these errors were encountered: