On 15 September 2014 16:07, Jesse Glick <[email protected]> wrote:
> On Thu, Sep 11, 2014 at 4:21 AM, Stephen Connolly > <[email protected]> wrote: > > So my plan for literate is to have a REST or socket exposed to the build > > which allows the maven build to notify the actions it undertook. > > Would suffice to have the extension print some messages using a > special syntax, e.g. > > [INFO] [JENKINS] {"attachedArtifacts": ["target/x.war"]} > > which the builder would scan for, notifying listeners inside Jenkins, > and possibly also stripping this output from the main build log. That > saves you from dealing with a new socket, firewalls, etc. > No issue with firewalls if you have the slave.jar open a temp socket bound to localhost only using an unused port for each build. > > (Of course if you want Jenkins to be able to interact with the Maven > process you need something more.) > > -- > 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 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.
