Hi,
On Saturday 23 March 2013 19:12:48 Matt Solnit wrote:
> In some ways that makes sense, but then how does validation work for *any*
> path? Jenkins knows enough to return a value for
> project.getSomeWorkspace(), which implies choosing a build machine.
if you want to follow this approach (choose some slave, where the build
already run and validate against it), something like this should work:
EnvVars ev = new
EnvVars(project.getSomeBuildWithWorkspace().getEnvironment(null));
String fullPath = ev.expand(value);
However, from the code you've provided, it seems to me that the path should be
relative to the workspace, so if there's ${WORKSPACE} in the path, I would
consider it as an error
HTH
Vojta
--
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/groups/opt_out.
