Eclipse Community Forums: Buckminster » buckminster jenkins with -data

Help

Home

Home » Archived » Buckminster » buckminster jenkins with -data

Show: Today's Messages :: Show Polls :: Message Navigator

buckminster jenkins with -data [message #1404473]

Fri, 01 August 2014 15:05

Felix Dorner

Messages: 295
Registered: March 2012

Senior Member

Hi,

The jenkins buckminster page says:

The working and data directory of buckminster is set to the directory of
the job workspace. This is especially useful if you want your code to be
checked out with Jenkins and only do a local resolution of the already
checked-out source code from within buckminster.

I'm not sure to understand the advantage of that. Is it supposed that I
checkout/clone directly into the job workspace root? The result is
that .git and .metadata are siblings. Is that really a good idea?

I would like to have the git checkout in job_workspace/git
and the bucky workspace in job_workspace_/workspace and the bucky output
in job_workspace/output, not everything mangled together. Maybe I miss a
piece?

Felix

Report message to a moderator

Re: buckminster jenkins with -data [message #1404561 is a reply to message #1404473]

Mon, 04 August 2014 07:56

Lorenzo Bettini

Messages: 1808
Registered: July 2009
Location: Firenze, Italy

Senior Member

On 01/08/2014 17:05, Felix Dorner wrote:
> Hi,
>
> The jenkins buckminster page says:
>
> The working and data directory of buckminster is set to the directory of
> the job workspace. This is especially useful if you want your code to be
> checked out with Jenkins and only do a local resolution of the already
> checked-out source code from within buckminster.
>
> I'm not sure to understand the advantage of that. Is it supposed that I
> checkout/clone directly into the job workspace root? The result is
> that .git and .metadata are siblings. Is that really a good idea?

Hi

I think that for the jenkins build is not that bad (while for
development IIRC having the data and the metadata in the same directory
is discouraged).

>
> I would like to have the git checkout in job_workspace/git
> and the bucky workspace in job_workspace_/workspace and the bucky output
> in job_workspace/output, not everything mangled together. Maybe I miss a
> piece?

I think you can still specify the arguments to achieve that...

cheers
Lorenzo

--
Lorenzo Bettini, PhD in Computer Science, DI, Univ. Torino
HOME: http://www.lorenzobettini.it
Xtext Book:
http://www.packtpub.com/implementing-domain-specific-languages-with-xtext-and-xtend/book

HOME: http://www.lorenzobettini.it
TDD Book: https://leanpub.com/tdd-buildautomation-ci
Xtext Book: https://www.packtpub.com/application-development/implementing-domain-specific-languages-xtext-and-xtend-second-edition

Report message to a moderator

Re: buckminster jenkins with -data [message #1404567 is a reply to message #1404561]

Mon, 04 August 2014 08:11

Felix Dorner

Messages: 295
Registered: March 2012

Senior Member

On 04/08/2014 09:56, Lorenzo Bettini wrote:
> On 01/08/2014 17:05, Felix Dorner wrote:
>> Hi,
>>
>> The jenkins buckminster page says:
>>
>> The working and data directory of buckminster is set to the directory of
>> the job workspace. This is especially useful if you want your code to be
>> checked out with Jenkins and only do a local resolution of the already
>> checked-out source code from within buckminster.
>>
>> I'm not sure to understand the advantage of that. Is it supposed that I
>> checkout/clone directly into the job workspace root? The result is
>> that .git and .metadata are siblings. Is that really a good idea?
>

Ciao Lorenzo,

> I think that for the jenkins build is not that bad (while for
> development IIRC having the data and the metadata in the same directory
> is discouraged).
>

Maybe. I just want to keep it clean.

>> I would like to have the git checkout in job_workspace/git
>> and the bucky workspace in job_workspace_/workspace and the bucky output
>> in job_workspace/output, not everything mangled together. Maybe I miss a
>> piece?
>
> I think you can still specify the arguments to achieve that...

I'll have a look at the code later.

Grazie,
Felix

> cheers
> Lorenzo
>

Report message to a moderator

Previous Topic:	[Resolved] - Buckminster 4.4 (headless) - Error during installation
Next Topic:	buckminster jenkins generates empty source feature and no source bundles.

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Sat Jun 03 06:15:31 GMT 2023

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter