|
I don't think those issues will be fixed any time soon. I work on the git plugin and the git client plugin in my personal time, trying my best to carefully advance those two plugins without regressing them.
I think that the use case you're describing is quite different from the use case which the plugin implements. I doubt that the use case you're describing could be implemented without major risks of incompatibility with existing use cases.
You might want to evaluate other alternatives, like one of the multi-branch plugins. I'm currently using a multi-branch plugin that automatically creates and deletes jobs for each branch that matches a pattern specified in the job definition. I'm not sure that will be enough to resolve your use case, but I think it is a more likely chance that you could start with that, and then propose pull requests as necessary to the git plugin to give it the exclude capability you want, but in the context of a multi-branch use case.
I find the automatically created and deleted jobs easier to understand than the git plugin's intermixing of multiple branches into the history of a single job.
If that isn't workable for you, then you could consider paying someone to implement what you're seeking. I'm not available in that way, since my employer won't allow that, but there are probably others who are available. You could approach Cloudbees or Praqma or one of the other companies which provide commercial support for Jenkins, and could negotiate with them to seek the solution for your use case.
|
