Hello, Alex. > What do you think about the idea of moving the *BuildSelector* extension point to a separate plugin repository?
Sounds good to me. As you pointed, the build selection feature of CopyArtifact is also useful for other plugins. Though CopyArtifact 2.0 is still in progress (for long time...), I belive we should base on CopyArtifact 2.0: * It outputs diagnostic messages. * It works with `BuildFilter`, which enables us to specify more complicated conditions to pick builds. * Copying features are completely isolated from BuildSelectors. We can start in a following way: * Clone jenkinsci/copyartifact-plugin into ikedam/build-selector-plugin (or alexsomain/build-selector-plugin) * Merge copyartifact-2.0. (#71) * Rename packages and classes, and remove deprecated features. * Ask to fork it to jenkinsci/build-selector-plugin * Release build-selector-plugin 0.1.0. Some issues: * CopyArtifactPermissionProperty. I think it shouldn't moved to build-selector-plugin and build-selector-plugin should provide an alternate mechanism. Regards, ikedam -- 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/263ee5be-8fb8-48f0-8e5e-1981a12b1a31%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
