As far as I am concerned, my plugin can POST the actual artifacts as part of a multipart POST to the endpoint. The other plugin could only notify about a build, or am I wrong? Am 17.07.2014 19:33 schrieb "[email protected]" <[email protected]>:
> What is the plugin all about? Any thing in common with the notification > plugin? > https://wiki.jenkins-ci.org/display/JENKINS/Notification+Plugin > Domi > > On 17 Jul 2014, at 14:28, Christian Becker < > [email protected]> wrote: > > After some thoughts, I'm also fine with *http-post* for the plugin name, > so that the repo might be named: *http-post-plugin*. > > Am Donnerstag, 17. Juli 2014 13:44:50 UTC+2 schrieb Christian Becker: >> >> Hi, >> I would like to get commit access to a new Plugin repository named >> *http-post-publisher*. My GitHub name is *ChristianBecker*. There is >> currently no GitHub repo to clone from. >> >> Thanks in advance, >> Christian >> > > -- > 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. > > > -- > You received this message because you are subscribed to a topic in the > Google Groups "Jenkins Developers" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/jenkinsci-dev/DPN0dmF8LXY/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- 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.
