Build is an instance of AbstractBuild.
On Thu, Jul 26, 2012 at 6:46 AM, Varghese Renny
wrote:
> I checked the archives and all. It's not pointing to which .groovy file will
> be created for each job we are creating..In email-ext plugin home page, it's
> only showing 4 variables are available- can
I checked the archives and all. It's not pointing to which .groovy file
will be created for each job we are creating..In email-ext plugin home
page, it's only showing 4 variables are available- cancel,msg,build..it's
not saying where it belongs to..is it an object, if yes, which groovy class
it is
Check the archives, I've written about this type of thing before.
On Thu, Jul 26, 2012 at 6:02 AM, Varghese Renny
wrote:
> So if it is represented using xml then how can i check the condition like
> build reason of this job is due to upstream cause..
> Actually i needed to write like that in pre
re two dependent job relation can seen in jenkins folder
>
>
>So if it is represented using xml then how can i check the condition like
>build reason of this job is due to upstream cause..
>Actually i needed to write like that in pre script of email-ext plugin.
>
>
>
>
>
>
>Thanks in Advance,
>varghese
>
>
>
So if it is represented using xml then how can i check the condition like
build reason of this job is due to upstream cause..
Actually i needed to write like that in pre script of email-ext plugin.
Thanks in Advance,
varghese
.
Mark Waite
>
> From: Varghese Renny
>To: jenkinsci-users@googlegroups.com
>Sent: Thursday, July 26, 2012 6:23 AM
>Subject: Where two dependent job relation can seen in jenkins folder
>
>
>
>I wanted to see the file corresponding to t
I wanted to see the file corresponding to two dependent job of jenkins?
Like if we mention two jobs are dependent, what file it will generate for
dependency?
Thanks in Advance,
varghese
