First-class multibranch project recogniser

[jglick]

If you implement https://javadoc.jenkins.io/plugin/workflow-multibranch/org/jenkinsci/plugins/workflow/multibranch/AbstractWorkflowBranchProjectFactory.html and https://javadoc.jenkins.io/plugin/workflow-multibranch/org/jenkinsci/plugins/workflow/multibranch/AbstractWorkflowMultiBranchProjectFactory.html in a Jenkins plugin, you can create an org folder with the specified project recogniser (.travis.yml) without needing any job generation. Commits adding or modifying this file will be honoured immediately.

[samrocketman]

Nice! I currently have the following plugin which filters for branches. It would be great to create projects too https://github.com/jenkinsci/scm-filter-jervis-plugin

I hadn't known this before. I'll work on implementing it.

[jglick]

If you implement the project recognizer, you do not need a custom trait like that—branches (or PRs) will be mapped to branch projects iff they have the right file.

Check https://www.jenkins.io/doc/developer/extensions/branch-api/#branchprojectfactory & https://www.jenkins.io/doc/developer/extensions/branch-api/#multibranchprojectfactory for ideas, as well as the proprietary https://docs.cloudbees.com/docs/admin-resources/latest/pipelines/pipeline-as-code#custom-pac-scripts

[jglick]

Filed as https://issues.jenkins.io/browse/JENKINS-67363 since that is probably more precise.

[samrocketman]

There's still YAML filtering in the .jervis.yml such as https://github.com/jenkinsci/scm-filter-jervis-plugin#whitelist-or-blacklist-branches-and-tags

It will need to parse the YAML to determine if the branch or tag is buildable or excluded via filter.

[samrocketman]

I haven't forgotten this. It has just taken me a while to get this project up to date with 100% coverage. I prefer to release with full coverage and I'm going to work toward smaller releases. This next release is going to be a major one.