-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Possible features for this SBT Plug-in? #3
Comments
This will be provided by the GitBucket plugin build farm. Since the build farm is still in testing phase, it hosts only limited plugins currently.
I think that plugins will have to be identified by
In my plan, the plugin build farm will build plugins for each GitBucket version automatically. Plugin developers need to only register their plugins to the build farm. |
What about company internal plug-ins?
That would guarantee uniqueness - unless some plug-ins are hosted on GitLab or alternative repos.
I see, however IMHO there still must be some sort of manual vetto-ing, since completely automating this stuff would allow malware to sneak in very easily. |
I think that copying assembly jar is enough solution for such company internal plugins. Network installation wouldn't be necessary for them.
Yes. It would be impossible to guarantee by a sbt plugin, anyway.
As I explained, the build farm is still experimental. When it's ready to release for third parties, it will come with the exact documentation for the plugin developers. |
Other possible features that might belong to this SBT plug-in:
The text was updated successfully, but these errors were encountered: