Hey, I think we might have a little missunderstanding here ;).
Many libraries are not held in subfolders of the sourcecode, that means
they are not in C:\Source\bar1\lib\*.dll or something like that, they are
libraries from third party tools like APEX True DB.
AS you only can register a .dll-file once via regsvr32.exe and the third
party programs need to be functional on the workstation, we have the
problem that these libraries are in folder like C:\Program Files
(x86)\thirdparty_solution\lib\*.dll and connect be cut out to another
location, but copied - which might be a bad solution also
That means that my reference to this file in the Visual Studio .vbp might
look like this:
=*\G{GUID}#Version#..\..\thirdparty\bin\file.exe
So the reference is asuming that the .vbp file is being checked out to
C:\Source\bar1 and from there it goes up to C:\. As you already stated, it
is not an option to hardcode the reference to C:\Program Filex
(x86)\thirdparty\bin\file.exe
So what now happens is that the .vbp file doesn't exist in C:\Source\bar1\,
but in C:\source\bar1\Solution\Project\foo\bar\ as it copies the structure
of the VCM. Now the reference is searching for file.exe in the folder
C:\source\bar1\Solution\Project, where it is not.
So the only solutions I might think if is get jenkins to stop copying the
VSS structure or to copy the needed libraries via batch-file to
C:\Source\bar1\Solution\Project and call the batch by jenkins before
compiling. But it seems a bit messy to me to solve it this way.
Am Mittwoch, 25. September 2013 17:06:43 UTC+2 schrieb LesMikesell:
>
> On Wed, Sep 25, 2013 at 9:29 AM, Al Jay
> <abusem...@googlemail.com<javascript:>>
> wrote:
> > I am using Jenkings 1.531 on Windows 8 for evaluation. I am trying to
> build
> > VB6.NET Software with it.
> > I installed the Visual Source Safe plugin as this still is the version
> > control we are using. i set it as the SCM in the job I created
> > I have a Job in which I use the version control path
> > $/Solution/Project1/foo1/bar1
> >
> > In advanced Settings of the job I set the workfolder to be
> C:\Source\bar1
> >
> > In C:\Source I have a batch file which I am calling with jenkins as
> build
> > action, which again calls vb6.exe C:\Source\bar1\bar.vpb /make
> >
> > Then Jenkins does the following: It creates the folders
> > C:\Source\bar1\Solution\Project1\foo1\bar1 and checks out the files in
> this
> > folder. So my whole project doesn't work.
> >
> > I would leave the workfolder to standard and just change my batch file,
> but
> > then I had to change the bar.vbp project file which is referencing the
> > libraries I need for compiling. All the other developers are checkoung
> out
> > the source code at C:\Source. When my build system checksout out the
> bar.vbp
> > that mans that the references to the libraries are broken because their
> > bar.vbp is referencing them in C:\Source and if I wanted it to work on
> > Jenkins, I would have to change it to
> > C:\path_to_jenkins\jobs\jobname\workspace\Solution\Project1\foo1\bar1 or
> to
> > C:\Source\bar1\Solution\Project1\foo1\bar1. Then again if I accidentally
> > check in my bar.vbp to the Source Control and the other developers are
> > checking it to their working folders, that means that they are no longer
> > able to compile the project via Visual Studio.
> >
> > So my question in general is: How do I tell Jenkins to stop mirroring
> out
> > the structure of the Source control and just check out the sources to be
> in
> > C:\Source\bar1\?
>
> With most source control systems you would want your project to use
> relative paths and environment settings to find all of its components
> so you could build in a different location (even without jenkins you
> might want the workspace on a different drive or to have 2 slightly
> different versions checked out at once. Unless this is a problem with
> Visual Source Safe I'd try that approach instead of trying to make
> jenkins do it the wrong way.
>
> --
> Les Mikesell
> lesmi...@gmail.com <javascript:>
>
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
