Documentation added On Wed, Mar 28, 2012 at 7:19 PM, domi <d...@fortysix.ch> wrote:
> Actually the the env-inject plugin does this - i'm not sure why this is > not documented > Its implemented like this: > - BUILD_CAUSE contains a coma separated list of all causes > - each active cause gets its own envvariable by this convention: > BUILD_CAUSE_XXXX=true (there will never by a false, so not existing means > false) > for well known causes, there is a fix name, for all others there is a > convention: > https://github.com/jenkinsci/envinject-plugin/blob/master/src/main/java/org/jenkinsci/plugins/envinject/service/BuildCauseRetriever.java > You can do a little test: > - add a shell step to a build and just add "set" as the only command to > execute within. > /imod > > > On 28.03.2012, at 01:00, Omair-Inam Abdul-Matin wrote: > > > Hi all, > > > > Is it possible to distinguish between a job triggered by an SCM > > trigger/periodic trigger/etc... based on a system property set by > > Jenkins? > > > > The list of properties mentioned here: > > > http://wiki.hudson-ci.org/display/HUDSON/Building+a+software+project#Buildingasoftwareproject-HudsonSetEnvironmentVariables > > does not make any mention of any property that might do this? > > > > Omair > >
