-
Bug
-
Resolution: Fixed
-
Major
-
Linux version 3.2.0-4-amd64 (debian-kernel@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-14) ) #1 SMP Debian 3.2.57-3+deb7u1
-
-
git client plugin 4.0.0
I have carefully named my project paths and folders so I can use JOB_NAME substitutions when cloning templates to create new jobs. All I have to do is copy a similar test (selenium/jmeter/junit/etc) and set the name of the job.
I just started using sparse checkout feature of git-client, to reduce the workspace bloat.
I want to use variable substitution to checkout the path 'test/${JOB_NAME}'.
The ${JOB_NAME} is not expanding, I get an error from the git-client, and the checkout fails. When I hardcode the jobname in the sparse checkout path field, it all works beautifully.
- is related to
-
JENKINS-27508 Cannot use ENV variable for repository url in Git Publisher
-
- Closed
-
-
JENKINS-49758 when passing in ref_spec with build parameters, the exact string "$REF_SPEC" is used rather then the value
-
- Open
-
- links to
We see the same situation:
we using some maven jobs and prepare the environment with some predefind variables like
project_rel_path=maven/parents/web-parent
Then we want to use in sparse-checkout path this variable like ${project_rel_path}. But we get then errors like
*
stderr: error: Sparse checkout leaves no entry on working directory*
We need such "central" point of configuration for our project definitions, because if we sparse checkout such path, the path is checked out as it is. So the workspace contains a folder like
/maven/parents/web-parent/
As for a standard maven job, we need to define where to find the pom.xml ... in such way with sparse checkout, we need to configure, that the pom can be found under maven/parents/web-parent/pom.xml (and we cannot rely on default maven job behaviour, that the pom.xml is in root of workspace).
One possible solution would be to provide a option to sparse checkout to root ... or to honor environment/build variables like ${xyz} and expand them.
Environment:
Windows 64, git client 2.7.0, jenkins 1.643, git plugin 2.4.1