Hey, I'm trying to provide a way to control automatic assignment of job ownership and/or item specific security for branch jobs in MultiBranchProjects.
At first I thought I could allow this by applying a JobOwnerJobProperty in a Pipeline `properties` step. But, if I understand correctly, this could let any committer change ownership of the branch job (am I right about this?) At jglick's suggestion, I went about a BranchProperty to assign JobOwnerJobProperty. This has the added advantage of not having to run the job before permissions and ownership are assigned. This would allow anyone with configuration permissions on the MultiBranchProject to control ownership on derived branch jobs. Is this a good thing? I assume ownership configuration was taken out of items' configuration views deliberately for this reason. I suggest MultiBranchProjects get an extra section in the `Manage Ownership` view for configuring branch job ownership. This Branch Job ownership section would allow configuring a BranchPropertyStrategy, and the aforementioned BranchProperty to the Project. Come to think of it, maybe this is what jglick had in mind and I only understood now after digging through the code. Am I missing anything? How does this sound to you? Any suggestions for Branch Property Strategies? Cheers, Jordan -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/a3186039-6ed2-402d-9c52-7a3df0cc68ad%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
