simple-priority-sorter-plugin

[jonesbusy]

Repository URL

https://github.com/jonesbusy/simple-priority-sorter-plugin

New Repository Name

simple-priority-sorter-plugin

Description

A very simple plugin that allow to set job priorities to reorder the queue

I didn't found anything simple to achieve adding a simple priority jobs first in queue

There is the https://plugins.jenkins.io/PrioritySorter/ but is over complicated

It forces to have system/extra configuration to define job groups. With the CI I have is difficult to find a common convention that all develop should follow.

I prefer just to allow them to set (if they need) a priority by JobDSL or directly on pipeline script

GitHub users to have commit permission

@jonesbusy

Jenkins project users to have release permission

jonesbusy

Issue tracker

GitHub issues

[jenkins-cert-app]

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.

Commands

The bot will parse all comments, and it will check if any line start with a command.

Security team only:

• /audit-ok => the audit is complete, the hosting can continue 🎉.
• /audit-skip => the audit is not necessary, the hosting can continue 🎉.
• /audit-findings => the audit reveals some issues that require corrections ✏️.

Anyone:

• /request-security-scan => the findings from the Jenkins Security Scan were corrected, this command will re-scan your repository 🔍.
• /audit-review => the findings from the audit were corrected, this command will ping the security team to review the findings 👀. It's only applicable when the previous audit required changes.

Only one command can be requested per comment.

(automatically generated message, version: 1.34.6)

[github-actions]

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

[jenkins-cert-app]

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.

[mawinter69]

• https://github.com/jonesbusy/simple-priority-sorter-plugin/blob/f18f9b9cde7be47962575eb64996ebad632ec206/src/main/java/io/jenkins/plugins/simpleprioritysorter/BasicPriorityProperty.java#L15 maybe use https://javadoc.jenkins.io/jenkins/model/OptionalJobProperty.html
• https://github.com/jonesbusy/simple-priority-sorter-plugin/blob/f18f9b9cde7be47962575eb64996ebad632ec206/src/main/resources/io/jenkins/plugins/simpleprioritysorter/BasicPriorityProperty/help-priority.html#L2 I would mention here that the default priority for jobs without the property is 10

[jonesbusy]

Thanks! Applied. Much better with OptionalJobProperty

[mawinter69]

• https://github.com/jonesbusy/simple-priority-sorter-plugin/blob/ce61953aef987fdfd5bc4af4d9cab004ef2918b9/pom.xml#L59 unused dependency I think

[jonesbusy]

Right. I was trying to display an icon with tooltip when the job is on the queue but didn't achieve it without overriding completly the widget. Removed

[mawinter69]

/hosting host

[jenkins-infra-bot]

Hosting request complete, the code has been forked into the jenkinsci project on GitHub as https://github.com/jenkinsci/simple-priority-sorter-plugin

GitHub issues has been selected for issue tracking and was enabled for the forked repo.

A pull request has been created against the repository permissions updater to setup release permissions. Additional users can be added by modifying the created file.

Please delete your original repository (if there are no other forks), under 'Danger Zone', so that the jenkinsci organization repository is the definitive source for the code. If there are other forks, then use the 'Leave fork network' action in the 'Danger Zone' on the settings page of your new jenkinsci repository. Also, please make sure you properly follow the documentation on documenting your plugin so that your plugin is correctly documented.

You will also need to do the following in order to push changes and release your plugin:

• Accept the invitation to the Jenkins CI Org on Github
• Add additional users for upload permissions, if needed
• Releasing your plugin

Welcome aboard!