|
| Re: Jenkins/Hudson -> Buckminster plugin support. [message #1019359 is a reply to message #1019297] |
Fri, 15 March 2013 14:27   |
|
On 03/15/2013 12:48 PM, Christophe Bouhier wrote:
> Hi Lorenzo,
>
> I noticed you took over support for the Jenkins/Hudson-buckminster plugin.
>
> I checked out the (Jenkins) plugin website, but couldn't find some forum
> or mailing list for support. Is this Eclipse forum the right place?
If no one complains we can discuss it here :)
see comments below
>
> In case it is, here is a question I have.
>
> Buckminster has capabilities to take in properties.
> It's not clear to me how this works in the bucky plugin.
> properties seem to be fixed when buckminster is run as shown below, but
> I would like to customize it. Can this be done with an external
> properties file (Which is checked-in in repo).
>
>
> java
> -Dbuckminster.output.root=/var/lib/jenkins/workspace/netxstudio.git.p2/buckminster.output
> -Dbuckminster.temp.root=/var/lib/jenkins/workspace/netxstudio.git.p2/buckminster.temp
> -Xmx256m -jar
> /var/lib/jenkins/tools/Buckminster/4.2/buckminster/plugins/org.eclipse.equinox.launcher_1.3.0.v20120522-1813.jar
> -application org.eclipse.buckminster.cmdline.headless -data
> /var/lib/jenkins/workspace/netxstudio.git.p2 --loglevel info -S
> /var/lib/jenkins/workspace/netxstudio.git.p2/commands.txt
If you click on "Advanced" in the "Run Buckminster" build step, you can
specify properties (with -D<key>=<value>) in the "JVM Arguments"
section, this is the help
"Enter a list of additional JVM args (usually properties). Hudson
Environment Variables can be used and will be expanded. Example:
-DtargetPlatformPath=${WORKSPACE}/targetPlatform "
If on the contrary you meant the -P buckminster's command line argument,
then, still in the "Advanced" section, there is "Global Properties File"
"The path or URL to a properties file. The properties in that file are
made available globally, for every executed Buckminster command "
For some typical buckminster properties, like buckminster.output.root,
there are text fields still in the "Advanced" section, e.g.,
Change Output Dir
"Change the output directory of buckminster (buckminster.output.root).
By default the output directory of buckminster will be set to
${WORKSPACE}/buckminster.output
Use this setting if you want to create the output directory at a
different location (relative to the workspace of the build job) "
hope this helps
cheers
Lorenzo
--
Lorenzo Bettini, PhD in Computer Science, DI, Univ. Torino
HOME: http://www.lorenzobettini.it
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
|
|
|
| Re: Jenkins/Hudson -> Buckminster plugin support. [message #1019372 is a reply to message #1019359] |
Fri, 15 March 2013 15:03 |
 Christophe Bouhier
Messages: 937
Registered: July 2009 |
Senior Member |
|
|
Yes it does help! (I should have noticed this button, sorry...!).
On 15-03-13 15:27, Lorenzo Bettini wrote:
> On 03/15/2013 12:48 PM, Christophe Bouhier wrote:
>> Hi Lorenzo,
>>
>> I noticed you took over support for the Jenkins/Hudson-buckminster plugin.
>>
>> I checked out the (Jenkins) plugin website, but couldn't find some forum
>> or mailing list for support. Is this Eclipse forum the right place?
>
> If no one complains we can discuss it here :)
>
> see comments below
>
>>
>> In case it is, here is a question I have.
>>
>> Buckminster has capabilities to take in properties.
>> It's not clear to me how this works in the bucky plugin.
>> properties seem to be fixed when buckminster is run as shown below, but
>> I would like to customize it. Can this be done with an external
>> properties file (Which is checked-in in repo).
>>
>>
>> java
>> -Dbuckminster.output.root=/var/lib/jenkins/workspace/netxstudio.git.p2/buckminster.output
>> -Dbuckminster.temp.root=/var/lib/jenkins/workspace/netxstudio.git.p2/buckminster.temp
>> -Xmx256m -jar
>> /var/lib/jenkins/tools/Buckminster/4.2/buckminster/plugins/org.eclipse.equinox.launcher_1.3.0.v20120522-1813.jar
>> -application org.eclipse.buckminster.cmdline.headless -data
>> /var/lib/jenkins/workspace/netxstudio.git.p2 --loglevel info -S
>> /var/lib/jenkins/workspace/netxstudio.git.p2/commands.txt
>
> If you click on "Advanced" in the "Run Buckminster" build step, you can
> specify properties (with -D<key>=<value>) in the "JVM Arguments"
> section, this is the help
>
> "Enter a list of additional JVM args (usually properties). Hudson
> Environment Variables can be used and will be expanded. Example:
>
> -DtargetPlatformPath=${WORKSPACE}/targetPlatform "
>
> If on the contrary you meant the -P buckminster's command line argument,
> then, still in the "Advanced" section, there is "Global Properties File"
>
> "The path or URL to a properties file. The properties in that file are
> made available globally, for every executed Buckminster command "
>
> For some typical buckminster properties, like buckminster.output.root,
> there are text fields still in the "Advanced" section, e.g.,
>
> Change Output Dir
>
> "Change the output directory of buckminster (buckminster.output.root).
>
> By default the output directory of buckminster will be set to
> ${WORKSPACE}/buckminster.output
> Use this setting if you want to create the output directory at a
> different location (relative to the workspace of the build job) "
>
> hope this helps
> cheers
> Lorenzo
>
>
>
>
|
|
|
Powered by
FUDForum. Page generated in 0.03394 seconds
] 
Search
Help
Register
Login
Home
