|
Re: Buckminster and Jenkins [message #755834 is a reply to message #755804] |
Wed, 09 November 2011 18:33 |
|
Hi Jesper,
you can call dependent actions by adding
cs:prerequisites to your action declaration something like:
<cs:public name="doStuff" actor="ant">
....
<cs:prerequisites>
<cs:attribute name="generate.index" alias="index" />
<cs:attribute name="some.more.action" alias="myaction" />
<cs:attribute name="site.p2" alias="repository"/>
<cs:prerequisites>
....
Regards,
Dennis.
Am 09.11.11 17:09, schrieb Jesper Eskilson:
> Hi,
>
> I'm trying to cleanup our Jenkins-job which runs Buckminster from being
> a messy ant-script to be a nice thing which is nothing more than a
> single action to invoke on a specific Eclipse feature. I would like to
> be able to run a complete build job by simply right-clicking on the
> top-level feature and selecting "Invoke Action...".
>
> At the moment we build the site by invoking a number of actions defined
> in a scriptfile, something like this:
>
> resolve feature.cquery
> build
> perform feature#generate.index
> perform feature#some.more.action
> perform feature#site.p2
>
> Is there a way to define an action in the feature which does all of
> these things? I have my a couple of custom actions in the feature's
> buckminster.cspex, but I can't figure out how to invoke other actions.
>
> --
> /Jesper
+Dennis Huebner
Get professional support from the Xtext committers at www.typefox.io
|
|
|
|
Re: Buckminster and Jenkins [message #755908 is a reply to message #755804] |
Thu, 10 November 2011 07:01 |
|
On 2011-11-09 17:09, Jesper Eskilson wrote:
> Hi,
>
> I'm trying to cleanup our Jenkins-job which runs Buckminster from being a messy ant-script to be a nice thing which is
> nothing more than a single action to invoke on a specific Eclipse feature. I would like to be able to run a complete
> build job by simply right-clicking on the top-level feature and selecting "Invoke Action...".
>
> At the moment we build the site by invoking a number of actions defined in a scriptfile, something like this:
>
> resolve feature.cquery
> build
> perform feature#generate.index
> perform feature#some.more.action
> perform feature#site.p2
>
> Is there a way to define an action in the feature which does all of these things? I have my a couple of custom actions
> in the feature's buckminster.cspex, but I can't figure out how to invoke other actions.
>
As others in this thread has noted already, the three perform commands can be expressed as prerequisites to one single
command. A prerequisite for any Buckminster perform command is that you have a consistent workspace. So the answer to
your questions is no, you'll need at least three distinct commands; resolve, build, and perform. Grouping them together
in a script file like you do today is the optimal solution.
- thomas
|
|
|
|
Re: Buckminster and Jenkins [message #755941 is a reply to message #755922] |
Thu, 10 November 2011 09:25 |
|
On 2011-11-10 09:36, Jesper Eskilson wrote:
> Thomas Hallgren skrev 2011-11-10 08:01:
>
>> As others in this thread has noted already, the three perform commands
>> can be expressed as prerequisites to one single command. A prerequisite
>> for any Buckminster perform command is that you have a consistent
>> workspace. So the answer to your questions is no, you'll need at least
>> three distinct commands; resolve, build, and perform. Grouping them
>> together in a script file like you do today is the optimal solution.
>
> Ok, so resolve and build needs to be done as separate commands. That kind of make sense. But any other "custom" steps
> should be possible to implement as actions, right?
>
Yes.
- thomas
|
|
|
Powered by
FUDForum. Page generated in 0.02579 seconds