Hello Anthony, Are there any other possible use-cases excepting the pyblishing to your server? If no, what about changing the plugin's name to codedx-publisher?
Best regards, Oleg Nenashev пятница, 26 сентября 2014 г., 22:50:58 UTC+4 пользователь Anthony DeMartini написал: > > Greetings, > > > > I’m with the CodeDx development team at Secure Decisions ( > http://codedx.com/) and we are developing a plugin for Jenkins to publish > builds to our software assurance analysis tool. Our current plugin is > located here: > > > > https://github.com/secdec/codedx-jenkins-plugin > > > > and my github handle is ademartini. > > > > We have chosen a groupid of org.jenkins-ci.plugins and an artifactid of > codedx. From the documentation it looks like the next step would be to > move our code into the Jenkins github area. We are not necessarily opposed > to this but want to know if there are any limitations if we were to keep > our code in its current github repo. Would we still be able to publish it > and have a wiki page and be listed as an official plugin? > > > > Thank You, > > Anthony DeMartini > > Senior Software Engineer > > Applied Visions, Inc. > > 631-759-3914 > > > -- 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.
