Thanks Stuart!
Nick.
On Wednesday, October 29, 2014 12:43:56 PM UTC-7, Stuart Rowe wrote:
>
> Here you go :)
>
>
> import javax.mail.Message
> import hudson.model.*
> import com.cloudbees.plugins.flow.*
> import hudson.tasks.MailAddressResolver
>
> def getUpstreamBuild(AbstractBuild curBuild)
> {
Hi Cristoph,
I see that a fix was commited , thank you so much.
Do you have any plans for a new release of the irc plugin ?
Best Regards.
On Tuesday, October 28, 2014 10:50:39 PM UTC, Luciano Rodrigues Furtado
wrote:
>
> Hey Cristoph,
>
>
> I have opened the ticket as requested JENKINS-25349 -
Would be great if you could test the build, I linked to the issue,
before I cut a new release.
Am 01.11.2014 um 12:24 schrieb Luciano Furtado:
Hi Cristoph,
I see that a fix was commited , thank you so much.
Do you have any plans for a new release of the irc plugin ?
Best Regards.
On Tuesday
I've just inherited a complex product suite build environment, and am in
the process of moving it from a custom build hack into a Jenkins build
environment. Company politics aside, it seems like a more scalable way to
do things. The product suite runs on and is also built on multiple
releases
I wonder if you could use a series of docker images to provide a location
which can be polluted by installed copies of build articles. It seems like
a docker image (container based virtualization, available in Debian Jessie)
would let you contaminate the specific virtual machine you need, without
