FreeStyle Project Plugin

[slide]

Repository URL

https://github.com/slide/freestyle-project

New Repository Name

freestyle-project-plugin

Description

This is a breakout of the FreeStyle project from Jenkins into a plugin.

GitHub users to have commit permission

@slide

Jenkins project users to have release permission

slide_o_mix

Issue tracker

Jira

[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.31.144)

[github-actions]

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.

• ⛔ Required: You must add a 'groupId' in your pom.xml with the value io.jenkins.plugins.
• ⛔ Required: The pom.xml file in the root of the origin repository is not valid
• ⛔ Required: Please add a license file to your repo, GitHub provides an easy mechanism to do this from their user interface.

You can re-trigger a check by editing your hosting request or by commenting /hosting re-check

[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.

[slide]

/hosting re-check

[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

[timja]

@jglick any thoughts on this?

[daniel-beck]

@core should be co-maintainers IMO.

[timja]

Not sure if the checks will handle that but can be added at hosting time

[timja]

/hosting host

[slide]

I will follow-up with a PR to core to make the plugin detached.

[timja]

/hosting host

[timja]

/hosting host

[jglick]

https://github.com/slide/freestyle-project/blob/8e20b062fc37a0213c154475016cf2292f7bcfad/src/main/resources/index.jelly#L3

My only concern is the impact on tests:

• Core tests referring to FreeStyleProject seem to all be moved to the plugin? Or just selected ones, with jenkins/test/pom.xml to keep a test-scoped dep on the plugin (as it already does for a few other plugins)?
• jenkins-test-harness has some APIs referring to FreeStyleProject (like JenkinsRule.createProject()) which would not even compile without this plugin. We could proactively rewrite those all to e.g. createProject(Class) but there would be a lot of callers. JTH’s own tests could be left alone if it gets a test-scoped dep. Maybe we provisionally keep it in compile scope but optional?

[timja]

/hosting host

[timja]

/hosting host

[jenkins-infra-bot]

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

A Jira component named [freestyle-project-plugin](https://issues.jenkins.io/issues/?jql=project+%3D+JENKINS+AND+component+%3D+ freestyle-project-plugin)has also been created with slide_o_mix as the default assignee for issues.

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, please contact GitHub support to make the jenkinsci repo the root of the fork network (mention that Jenkins approval was given in support request 569994). 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!