On Thu, Sep 10, 2015 at 9:17 AM, Paul Allen wrote:
> I added two break points in SCM.buildEnvVars and my own buildEnvVars and
> neither get hit during a Workflow build.
Of course not; pending JENKINS-24141 the API does not permit an SCM to
contribute environment variables to Workflow.
--
You r
Hi Jesse,
Yes, it extends SCMStep…
https://github.com/jenkinsci/p4-plugin/blob/master/src/main/java/org/jenkinsci/plugins/p4/workflow/P4Step.java#LC24
I added two break points in SCM.buildEnvVars and my own buildEnvVars and
neither get hit during a Workflow build.
I’ll do a bit of hacking,
On Wed, Sep 9, 2015 at 1:21 PM, pallen wrote:
> The TODO suggests that something is missing for Run/Workflow!
https://issues.jenkins-ci.org/browse/JENKINS-24141
Is `p4sync` just extending `SCMStep`?
--
You received this message because you are subscribed to the Google Groups
"Jenkins Develope
Looking at the SCM class:
// TODO is an equivalent for Run needed?
public void buildEnvVars(AbstractBuild build, Map
env) {
// default implementation is noop.
}
The TODO suggests that something is missing for Run/Workflow!
--
You received this message because you are sub
Hi Guys,
There seems to be an issues accessing the Environment variables from the
'p4' plugin?
node {
p4sync charset: 'none', credential: '----x',
depotPath: '//depot'
echo env.P4_CHANGELIST
echo env.JOB_NAME
}
JOB_NAME gets displayed, but P4_CHANGELIST is
