I suppose there won't be additional ThreadFix plugins, hence the short name (threadfix) seems to be OK. If somebody creates ThreadFix build steps or other such stuff, he can just integrate it into this plugin.
понедельник, 23 июня 2014 г., 5:14:44 UTC+4 пользователь Brandon Spruth написал: > > Thanks for the quick reply. The plugin repository is now public and is > located here https://github.com/automationdomination/threadfix-plugin.git > <https://www.google.com/url?q=https%3A%2F%2Fgithub.com%2Fautomationdomination%2Fthreadfix-plugin.git&sa=D&sntz=1&usg=AFQjCNEnmcsxU_npI0Ctwv4spyIY8sYZAQ>. > > > > I updated my README.md and wiki, however you will find the plugin > description as follows: > > *Jenkins ThreadFix Plugin Publisher provides the ability to upload any > supported scan artefact file types, from your Jenkins server to your > ThreadFix deployment. Allowing complete integration between your continuous > integration (CI) environment to your centralized software vulnerability > management system.* > > The artifact ID is simply "threadfix". Let me know if you need any > further information? > > On Saturday, June 21, 2014 4:07:13 PM UTC-5, Brandon Spruth wrote: >> >> I wish to publish a new Jenkins plugin for ThreadFix. My ID is >> automationdomination for jenkins-ci.org and the plugin source will be >> located here https://github.com/automationdomination/threadfix-plugin. >> I plan on publishing within a couple of days if possible? >> > -- 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]. For more options, visit https://groups.google.com/d/optout.
