Eclipse Community Forums: Buckminster » Deliver no source files in p2 site

Help

Home

Home » Archived » Buckminster » Deliver no source files in p2 site

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

Deliver no source files in p2 site [message #668199]

Wed, 04 May 2011 13:26

Lukas L.

Messages: 13
Registered: May 2011

Junior Member

Hello all,

i have a problem: When i am building an p2 update site via hudson + buckminster the corresponding source feautres/bundles are also included. But i want a p2 update site WITHOUT sources.

Manually via Buckminster + Eclipse using a buckminster.properties file and set the cbi.include.source property to false all is working as expected.

Unfortunately not when i am building via Hudson. Maybe Hudson cannot link to the buckminster.properties file? Or maybe i have to add manually a command to buckminster in Hudson?

Thank you!

Best regards,
Lukas L.

Report message to a moderator

Re: Deliver no source files in p2 site [message #668246 is a reply to message #668199]

Wed, 04 May 2011 16:00

Johannes Utzig

Messages: 329
Registered: July 2009

Senior Member

Hi Lukas,

I assume you are using the Hudson Plugin for Buckminster?
The setting for that is in the 'Advanced Options' of the configuration.
You can either use the JVM arguments with -Dcbi.include.source=false or
you can specify the path to a properties file ('Global Properties File',
also in the advanced section) that will be passed to all commands you
are executing in the build step.

Best regards,
Johannes

Report message to a moderator

Re: Deliver no source files in p2 site [message #668320 is a reply to message #668199]

Thu, 05 May 2011 08:00

Lukas L.

Messages: 13
Registered: May 2011

Junior Member

Hi Johannes,

Thank you for your answer.

Yes, I am using the Hudson Plugin (version 3.6) for Buckminster.

I tried both using the JVM arguments with -Dcbi.include.source=false and
linking the properties file. However, the sources are always included.

This is my Buckminster Commmand:

import '${WORKSPACE}/org.plugin.my.buckminster/site.cquery'
build
perform -D target.os=* -D target.ws=* -D target.arch=* org.plugin.my.buckminster#site.p2.zip

And this is the value in JVM Arguments:

-Dcbi.include.source=false

Best regards,
Lukas

Report message to a moderator

Re: Deliver no source files in p2 site [message #668354 is a reply to message #668320]

Thu, 05 May 2011 11:05

Johannes Utzig

Messages: 329
Registered: July 2009

Senior Member

Hi Lukas,

can you post the generated command line invocation of the job's console
output? Just to see if the command line correctly contains the property
(or property file) to determine if it's a bug in the plugin or buckminster.

Best regards,
Johannes

Am 05.05.2011 10:00, schrieb Lukas L.:
> Hi Johannes,
>
> Thank you for your answer.
>
> Yes, I am using the Hudson Plugin (version 3.6) for Buckminster.
>
> I tried both using the JVM arguments with -Dcbi.include.source=false and
> linking the properties file. However, the sources are always included.
>
> This is my Buckminster Commmand:
>
>
> import '${WORKSPACE}/org.plugin.my.buckminster/site.cquery'
> build
> perform -D target.os=* -D target.ws=* -D target.arch=*
> org.plugin.my.buckminster#site.p2.zip
>
>
> And this is the value in JVM Arguments:
>
>
> -Dcbi.include.source=false
>
>
> Best regards,
> Lukas

Report message to a moderator

Re: Deliver no source files in p2 site [message #668360 is a reply to message #668199]

Thu, 05 May 2011 12:06

Lukas L.

Messages: 13
Registered: May 2011

Junior Member

Job console:

[workspace] $ "C:\Program Files\Java\jdk1.6.0_24\bin\java.exe" "-Dbuckminster.output.root=C:\Program Files\Jenkins\jobs\p2 Updatesite\workspace\buckminster.output" "-Dbuckminster.temp.root=C:\Program Files\Jenkins\jobs\p2 Updatesite\workspace\buckminster.temp" -Dcbi.include.source=false -jar "C:\Program Files\Jenkins\tools\buckminster\plugins\org.eclipse.equinox.launcher_1.1.1.R36x_v20101122_1400.jar" -application org.eclipse.buckminster.cmdline.headless -data "C:\Program Files\Jenkins\jobs\p2 Updatesite\workspace" --loglevel info -S "C:\Program Files\Jenkins\jobs\p2 Updatesite\workspace\commands.txt"
INFO: setpref 'targetPlatformPath=/C:/Program Files/Jenkins/jobs/Create Target Platform/builds/2011-05-04_11-02-38/archive//targetPlatform'
INFO: import '/C:/Program Files/Jenkins/jobs/p2 Updatesite/workspace/org.plugin.my.buckminster/site.cquery'
INFO: Import complete. INFO: build 
...

As you can see -Dcbi.include.source=false is included.

Report message to a moderator

Re: Deliver no source files in p2 site [message #668378 is a reply to message #668360]

Thu, 05 May 2011 13:17

Henrik Lindberg

Messages: 2509
Registered: July 2009

Senior Member

All your other -D settings have " " around them... could that be it?
- henrik
On 5/5/11 2:06 PM, Lukas L. wrote:
> Job console:
>
>
> [workspace] $ "C:\Program Files\Java\jdk1.6.0_24\bin\java.exe"
> "-Dbuckminster.output.root=C:\Program Files\Jenkins\jobs\p2
> Updatesite\workspace\buckminster.output"
> "-Dbuckminster.temp.root=C:\Program Files\Jenkins\jobs\p2
> Updatesite\workspace\buckminster.temp" -Dcbi.include.source=false -jar
> "C:\Program
> Files\Jenkins\tools\buckminster\plugins\org.eclipse.equinox. launcher_1.1.1.R36x_v20101122_1400.jar "
> -application org.eclipse.buckminster.cmdline.headless -data "C:\Program
> Files\Jenkins\jobs\p2 Updatesite\workspace" --loglevel info -S
> "C:\Program Files\Jenkins\jobs\p2 Updatesite\workspace\commands.txt"
> INFO: setpref 'targetPlatformPath=/C:/Program Files/Jenkins/jobs/Create
> Target Platform/builds/2011-05-04_11-02-38/archive//targetPlatform'
> INFO: import '/C:/Program Files/Jenkins/jobs/p2
> Updatesite/workspace/org.plugin.my.buckminster/site.cquery'
> INFO: Import complete. INFO: build ...
>
> As you can see -Dcbi.include.source=false is included.

Report message to a moderator

Re: Deliver no source files in p2 site [message #668379 is a reply to message #668378]

Thu, 05 May 2011 13:29

Johannes Utzig

Messages: 329
Registered: July 2009

Senior Member

Am 05.05.2011 15:17, schrieb Henrik Lindberg:
> All your other -D settings have " " around them... could that be it?

Hmm, no, that should work since there is no spaces or anything in that
property.

To me it looks like a buckminster bug unless the cbi.include.source is
not valid as a system property and HAS to be in a properties file (but
you said that didn't work either?)

Report message to a moderator

Re: Deliver no source files in p2 site [message #668394 is a reply to message #668199]

Thu, 05 May 2011 14:29

Lukas L.

Messages: 13
Registered: May 2011

Junior Member

Here the console log with setting the "Global Properties File" property to:

${WORKSPACE}/org.plugin.my.buckminster/buckminster.propertie s

Here the code of my buckminster.properties file:

# Deliver no source files
cbi.include.source = false

target.os=*
target.ws=*
target.arch=*

Same result/problem when referencing the buckminster.properties file:

[workspace] $ "C:\Program Files\Java\jdk1.6.0_24\bin\java.exe" "-Dbuckminster.output.root=C:\Program Files\Jenkins\jobs\p2 Updatesite\workspace\buckminster.output" "-Dbuckminster.temp.root=C:\Program Files\Jenkins\jobs\p2 Updatesite\workspace\buckminster.temp" -jar "C:\Program Files\Jenkins\tools\buckminster\plugins\org.eclipse.equinox.launcher_1.1.1.R36x_v20101122_1400.jar" -application org.eclipse.buckminster.cmdline.headless -data "C:\Program Files\Jenkins\jobs\p2 Updatesite\workspace" --loglevel info -P "/C:/Program Files/Jenkins/jobs/p2 Updatesite/workspace/org.plugin.my.buckminster/buckminster.properties" -S "C:\Program Files\Jenkins\jobs\p2 Updatesite\workspace\commands.txt" INFO: setpref 'targetPlatformPath=/C:/Program Files/Jenkins/jobs/Create Target Platform/builds/2011-05-04_11-02-38/archive//targetPlatform' INFO: import '/C:/Program Files/Jenkins/jobs/p2 Updatesite/workspace/org.plugin.my.buckminster/site.cquery'
INFO: Import complete. INFO: build

Report message to a moderator

Re: Deliver no source files in p2 site [message #668397 is a reply to message #668394]

Thu, 05 May 2011 14:44

Henrik Lindberg

Messages: 2509
Registered: July 2009

Senior Member

Do you have any advisor nodes that may override things?
- henrik

On 5/5/11 4:29 PM, Lukas Ladenberger wrote:
> Here the console log with setting the "Global Properties File" property to:
> ${WORKSPACE}/org.plugin.my.buckminster/buckminster.propertie s
>
> Here the code of my buckminster.properties file:
>
>
> # Deliver no source files
> cbi.include.source = false
>
> target.os=*
> target.ws=*
> target.arch=*
>
>
> Same result/problem when referencing the buckminster.properties file:
>
>
> [workspace] $ "C:\Program Files\Java\jdk1.6.0_24\bin\java.exe"
> "-Dbuckminster.output.root=C:\Program Files\Jenkins\jobs\p2
> Updatesite\workspace\buckminster.output"
> "-Dbuckminster.temp.root=C:\Program Files\Jenkins\jobs\p2
> Updatesite\workspace\buckminster.temp" -jar "C:\Program
> Files\Jenkins\tools\buckminster\plugins\org.eclipse.equinox. launcher_1.1.1.R36x_v20101122_1400.jar "
> -application org.eclipse.buckminster.cmdline.headless -data "C:\Program
> Files\Jenkins\jobs\p2 Updatesite\workspace" --loglevel info -P
> "/C:/Program Files/Jenkins/jobs/p2
> Updatesite/workspace/org.plugin.my.buckminster/buckminster.p roperties "
> -S "C:\Program Files\Jenkins\jobs\p2 Updatesite\workspace\commands.txt"
> INFO: setpref 'targetPlatformPath=/C:/Program Files/Jenkins/jobs/Create
> Target Platform/builds/2011-05-04_11-02-38/archive//targetPlatform'
> INFO: import '/C:/Program Files/Jenkins/jobs/p2
> Updatesite/workspace/org.plugin.my.buckminster/site.cquery'
> INFO: Import complete. INFO: build

Report message to a moderator

Re: Deliver no source files in p2 site [message #668576 is a reply to message #668199]

Fri, 06 May 2011 10:03

Lukas L.

Messages: 13
Registered: May 2011

Junior Member

Hi Henrik,

I have no advisor nodes in my site.cquery.

Strange behaviour ...

- lukas

Report message to a moderator

Re: Deliver no source files in p2 site [message #668728 is a reply to message #668379]

Fri, 06 May 2011 20:53

Thomas Hallgren

Messages: 3240
Registered: July 2009

Senior Member

Please try quoting. This is apparently on Windows and some windows cmd shells will actually split on '='.

- thomas

On 2011-05-05 15:29, Johannes Utzig wrote:
> Am 05.05.2011 15:17, schrieb Henrik Lindberg:
>> All your other -D settings have " " around them... could that be it?
>
> Hmm, no, that should work since there is no spaces or anything in that property.
>
> To me it looks like a buckminster bug unless the cbi.include.source is not valid as a system property and HAS to be in a
> properties file (but you said that didn't work either?)
>

Report message to a moderator

Re: Deliver no source files in p2 site [message #669946 is a reply to message #668199]

Thu, 12 May 2011 07:27

Lukas L.

Messages: 13
Registered: May 2011

Junior Member

Sorry for the late reply.

I tried quoting, however without success ...

Global Properties File --> " ${WORKSPACE}/org.plugin.my.buckminster/buckminster.propertie s "

Report message to a moderator

Re: Deliver no source files in p2 site [message #669996 is a reply to message #669946]

Thu, 12 May 2011 11:07

Daniel Weber

Messages: 51
Registered: July 2009

Member

Hi Lukas,

are you sure buckminster actually creates new source bundles with every
run? Or does it just put "source jars" from previous builds into the
ZIP/p2 repository?

To rule out quoting and other issues, set the property when calling the
action, inside your script:

perform -D cbi.include.source=false ...#site.p2.zip

and see if this changes anything.

Regard,
Daniel

On 12.05.2011 09:27, Lukas Ladenberger wrote:
> Sorry for the late reply.
>
> I tried quoting, however without success ...
>
> Global Properties File --> "
> ${WORKSPACE}/org.plugin.my.buckminster/buckminster.propertie
> s "

Report message to a moderator

Re: Deliver no source files in p2 site [message #670254 is a reply to message #669996]

Fri, 13 May 2011 08:55

Lukas L.

Messages: 13
Registered: May 2011

Junior Member

Hi Daniel,

Yes, I am sure that buckminster creates new source bundles with every new build. Before every new build I delete manually my old builds in order to exclude exactly this case.

I also tried this alternative:

perform -D cbi.include.source=false ...#site.p2.zip

However, without success.

Over again: I have this problem only building via Jenkins (Buckminster is installed automatically via Jenkins). Building manually via Buckminster from my Eclipse Environment works as expected - The sources are not included.

One remark: Roughly in a week I will migrate my Jenkins configuration from my local Windows System to a Mac OS System. Maybe this will solve the problem.

However, it is still a strange behaviour.

Best regards,
Lukas

[Updated on: Fri, 13 May 2011 08:58]

Report message to a moderator

Previous Topic:	syntax for CVS tag in rmap?
Next Topic:	SettingIgnoring Worspace's API Base Line

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Fri Apr 19 15:47:15 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter