-
Improvement
-
Resolution: Fixed
-
Major
-
None
-
Platform: All, OS: All
It appears that the VSS plugin can only download from a single path. It is
common for VSS projects to be setup so that sources are downloaded from more
than one VSS project. Adding the ability to allow multiple VSS locations would
be a very useful enhancement to the VSS plugin
- is duplicated by
-
-
- Closed
-
[JENKINS-810] Allowed multiple VSS project locations in Hudson project
rioch
added a comment - There is a bug in my fix above meaning that not all folders are created. The fix is to replace line 286 in VSSSCM.java with:
(new File(localPath)).mkdirs();
I wish this would be integrated into the actual plugin.
rioch
added a comment - There is a bug in my fix above meaning that not all folders are created. The fix is to replace line 286 in VSSSCM.java with:
(new File(localPath)).mkdirs();
I wish this would be integrated into the actual plugin. 
James VanDernoot
added a comment - It looks like this code change was made? This feature would be a HUGE help. Is there another build scheduled that would include this change?
Thanks,
Jamie
James VanDernoot
added a comment - It looks like this code change was made? This feature would be a HUGE help. Is there another build scheduled that would include this change?
Thanks,
Jamie rioch
added a comment - It's indeed a shame this fix isn't in yet. Currently there is no maintainer, and I don't know how or if I can apply the patch myself. I did email kohsuke a while ago pointing him in this direction, but I guess it's slipped off the list.
You can always apply the patch yourself and run your own copy of the plugin. You just have to be careful not to update it as we're doing. It's certainly far from ideal though, and a bit depressing when this community driven project ignores you.
rioch
added a comment - It's indeed a shame this fix isn't in yet. Currently there is no maintainer, and I don't know how or if I can apply the patch myself. I did email kohsuke a while ago pointing him in this direction, but I guess it's slipped off the list.
You can always apply the patch yourself and run your own copy of the plugin. You just have to be careful not to update it as we're doing. It's certainly far from ideal though, and a bit depressing when this community driven project ignores you. Code changed in jenkins
User: Jon Black
Path:
.gitignore
pom.xml
src/main/java/scm/vss/VSSSCM.java
src/main/resources/scm/vss/VSSSCM/config.jelly
http://jenkins-ci.org/commit/vss-plugin/71bc246f076590c839d8121ed62a0374d277d2ae
Log:
Fixed JENKINS-810. Support for multiple VSS paths.
Code changed in jenkins
User: Jon Black
Path:
.gitignore
pom.xml
src/main/java/scm/vss/VSSSCM.java
src/main/resources/scm/vss/VSSSCM/config.jelly
http://jenkins-ci.org/commit/vss-plugin/71bc246f076590c839d8121ed62a0374d277d2ae
Log:
Fixed JENKINS-810. Support for multiple VSS paths.
I've made some changes to the VSS plugin:
1. VSS Folder Path accepts a comma separated list of paths to retrieve from sourcesafe. e.g. $/Folder1,$/Folder2
2. The resulting workspace includes the folders listed in VSS Folder Path. So, assuming the workspace is c:\workspace, the above paths would result in c:\workspace\Folder1\<contents> and c:\workspace\Folder2\<contents>.
This is useful in the case that project dependencies are not under the same root project directory.
I posted this a while back to the mailing list and was subsequently ignored, so I'm trying my luck here.
Regards,
rioch