non-recursively checkout out an svn tree

classic Classic list List threaded Threaded
8 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

non-recursively checkout out an svn tree

Chris Withers
Hi All,

I have a project with a tree structure roughly like this:

source
source/Makefile
source/python
source/cpp
source/sql
source/lotsofotherstuff

I have a job that builds the C++ release and then runs its unit tests.
This requires:

source/Makefile
source/cpp

Since Makefile is a file, not a folder, and one that for arcane reasons
I can't move from its location, I can't *only* checkout Makefile and the
cpp folder. This is resulting in loads of spurious executions of this
build job as a result of changes to other parts of the tree that don't
affect the C++ release at all.

How can I *just* checkout the Makefile and cpp folders and have those
used as the things that jenkins looks at for changes?

cheers,

Chris

--
Simplistix - Content Management, Batch Processing & Python Consulting
             - http://www.simplistix.co.uk
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

Re: non-recursively checkout out an svn tree

Didier Durand
Hi,

Is it possible for you to create a dir source/Makedir and move
Makefile into it ?
At least can you create Makedir and make a symlink to makefile into
it.

Then, you configure 2 checkout location in you jenkins job config: 1
for source/cpp and 1 for source/Makedir and you've reached your
objective.

regards

didier

On Feb 21, 6:30 pm, Chris Withers <[hidden email]> wrote:

> Hi All,
>
> I have a project with a tree structure roughly like this:
>
> source
> source/Makefile
> source/python
> source/cpp
> source/sql
> source/lotsofotherstuff
>
> I have a job that builds the C++ release and then runs its unit tests.
> This requires:
>
> source/Makefile
> source/cpp
>
> Since Makefile is a file, not a folder, and one that for arcane reasons
> I can't move from its location, I can't *only* checkout Makefile and the
> cpp folder. This is resulting in loads of spurious executions of this
> build job as a result of changes to other parts of the tree that don't
> affect the C++ release at all.
>
> How can I *just* checkout the Makefile and cpp folders and have those
> used as the things that jenkins looks at for changes?
>
> cheers,
>
> Chris
>
> --
> Simplistix - Content Management, Batch Processing & Python Consulting
>              -http://www.simplistix.co.uk
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

Re: non-recursively checkout out an svn tree

Jesse Farinacci
In reply to this post by Chris Withers
Greetings,

On Tue, Feb 21, 2012 at 12:30 PM, Chris Withers <[hidden email]> wrote:
> How can I *just* checkout the Makefile and cpp folders and have those used
> as the things that jenkins looks at for changes?

https://issues.jenkins-ci.org/browse/JENKINS-777

-Jesse

--
There are 10 types of people in this world, those
that can read binary and those that can not.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

Re: non-recursively checkout out an svn tree

Chris Withers
On 22/02/2012 05:08, Jesse Farinacci wrote:
> Greetings,
>
> On Tue, Feb 21, 2012 at 12:30 PM, Chris Withers<[hidden email]>  wrote:
>> How can I *just* checkout the Makefile and cpp folders and have those used
>> as the things that jenkins looks at for changes?
>
> https://issues.jenkins-ci.org/browse/JENKINS-777

Damn. Any likelihood of that bug being moved forward any time soon?

Chris

--
Simplistix - Content Management, Batch Processing & Python Consulting
             - http://www.simplistix.co.uk
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

Re: non-recursively checkout out an svn tree

danny staple
Can you use the "included regions" setting on the subversion config to only include that file when polling? That should save some of the ache. It would still be nice if sparse checkouts were supported in jenkins too.

On 22 February 2012 09:38, Chris Withers <[hidden email]> wrote:
On 22/02/2012 05:08, Jesse Farinacci wrote:
Greetings,

On Tue, Feb 21, 2012 at 12:30 PM, Chris Withers<[hidden email]>  wrote:
How can I *just* checkout the Makefile and cpp folders and have those used
as the things that jenkins looks at for changes?

https://issues.jenkins-ci.org/browse/JENKINS-777

Damn. Any likelihood of that bug being moved forward any time soon?


Chris

--
Simplistix - Content Management, Batch Processing & Python Consulting
           - http://www.simplistix.co.uk



--
Danny Staple

Director, ODM Solutions Ltd
w: http://www.odmsolutions.co.uk
Blog: http://orionrobots.co.uk/blog1-Danny-Staple


Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

Re: non-recursively checkout out an svn tree

Chris Withers
On 22/02/2012 10:46, danny staple wrote:
> Can you use the "included regions" setting on the subversion config

Which subversion config are you referring to?

cheers,

Chris

--
Simplistix - Content Management, Batch Processing & Python Consulting
             - http://www.simplistix.co.uk
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

Re: non-recursively checkout out an svn tree

danny staple
In the SCM section on the job configuration, under the SVN, advanced you have "excluded regions", "included regions" and a number of other settings. This is in my versino of Jenkins (1.424.2) with the 1.37 version of the subversion plugin installed.

Thanks,
Danny

On 22 February 2012 13:59, Chris Withers <[hidden email]> wrote:
On 22/02/2012 10:46, danny staple wrote:
Can you use the "included regions" setting on the subversion config

Which subversion config are you referring to?

cheers,


Chris

--
Simplistix - Content Management, Batch Processing & Python Consulting
           - http://www.simplistix.co.uk



--
Danny Staple

Director, ODM Solutions Ltd
w: http://www.odmsolutions.co.uk
Blog: http://orionrobots.co.uk/blog1-Danny-Staple


Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

Re: non-recursively checkout out an svn tree

Chris Withers
This looks great, just a shame the same thing can't be used to limit
what it checked, and so what triggers a job to be built...

Chris

On 22/02/2012 16:37, danny staple wrote:

> In the SCM section on the job configuration, under the SVN, advanced you
> have "excluded regions", "included regions" and a number of other
> settings. This is in my versino of Jenkins (1.424.2) with the 1.37
> version of the subversion plugin installed.
>
> Thanks,
> Danny
>
> On 22 February 2012 13:59, Chris Withers <[hidden email]
> <mailto:[hidden email]>> wrote:
>
>     On 22/02/2012 10:46, danny staple wrote:
>
>         Can you use the "included regions" setting on the subversion config
>
>
>     Which subversion config are you referring to?
>
>     cheers,
>
>
>     Chris
>
>     --
>     Simplistix - Content Management, Batch Processing & Python Consulting
>                 - http://www.simplistix.co.uk
>
>
>
>
> --
> Danny Staple
>
> Director, ODM Solutions Ltd
> w: http://www.odmsolutions.co.uk
> Blog: http://orionrobots.co.uk/blog1-Danny-Staple
>
>
>
> ______________________________________________________________________
> This email has been scanned by the Symantec Email Security.cloud service.
> For more information please visit http://www.symanteccloud.com
> ______________________________________________________________________

--
Simplistix - Content Management, Batch Processing & Python Consulting
             - http://www.simplistix.co.uk
Loading...