|
|
Re: first builder job executed [message #514794 is a reply to message #514738] |
Tue, 16 February 2010 11:34 |
Henrik Lindberg Messages: 2509 Registered: July 2009 |
Senior Member |
|
|
Hi Sebastian,
Short answer - the builder that was executed was just test code - it
returned a fixed build result (a .txt file).
Longer answer - B3 has the notion of BuildUnit (the thing you are
building), and Builder the thing that operates on a BuildUnit to produce
some result.
A Builder is an asynchronous function with declarative dependencies on
other Builders (i.e. other build results from other BuildUnits).
When calling a Builder, it returns an Eclipse Job. When this job is run,
it collects the result of all the declarative dependencies and executes
its specific build step.
My first run (using a toy example) managed to run one of these builders.
Here is (part of) the toy model in b3 DSL:
unit fruitsallad version 1.0.0 {
builder make {
input {
unit/apple/1.0.0#dice;
unit/banana/1.0.0#dice;
unit/orange/1.0.0#dice;
}
}
}
unit apple version 1.0.0 implements Fruit {
builder peel {
output { applepeel.txt; }
}
builder seeds {
output { appleseeds.txt; }
}
builder pulp {
output { applepulp.txt; }
}
}
Will write a lot more about how this all works once I have it working...
Regards
- henrik
On 2/16/10 2:50 PM, Sebastian Zarnekow wrote:
> Hi Henrik, hello builder,
>
> that's great news!
> Can you provide some more information about this builder job? What did
> you have to do? What did you achtually build?
>
> - Sebastian
>
> Am 16.02.10 14:24, schrieb Henrik Lindberg:
>> I am happy to announce that the very first b3 Builder job was just
>> executed!
>>
>> (And in case you wonder - no, it did not do much :)
>>
>>
>> Regards
>> - henrik
>
|
|
|
|
Re: first builder job executed [message #596249 is a reply to message #514738] |
Tue, 16 February 2010 16:23 |
Henrik Lindberg Messages: 2509 Registered: July 2009 |
Senior Member |
|
|
Hi Sebastian,
Short answer - the builder that was executed was just test code - it
returned a fixed build result (a .txt file).
Longer answer - B3 has the notion of BuildUnit (the thing you are
building), and Builder the thing that operates on a BuildUnit to produce
some result.
A Builder is an asynchronous function with declarative dependencies on
other Builders (i.e. other build results from other BuildUnits).
When calling a Builder, it returns an Eclipse Job. When this job is run,
it collects the result of all the declarative dependencies and executes
its specific build step.
My first run (using a toy example) managed to run one of these builders.
Here is (part of) the toy model in b3 DSL:
unit fruitsallad version 1.0.0 {
builder make {
input {
unit/apple/1.0.0#dice;
unit/banana/1.0.0#dice;
unit/orange/1.0.0#dice;
}
}
}
unit apple version 1.0.0 implements Fruit {
builder peel {
output { applepeel.txt; }
}
builder seeds {
output { appleseeds.txt; }
}
builder pulp {
output { applepulp.txt; }
}
}
Will write a lot more about how this all works once I have it working...
Regards
- henrik
On 2/16/10 2:50 PM, Sebastian Zarnekow wrote:
> Hi Henrik, hello builder,
>
> that's great news!
> Can you provide some more information about this builder job? What did
> you have to do? What did you achtually build?
>
> - Sebastian
>
> Am 16.02.10 14:24, schrieb Henrik Lindberg:
>> I am happy to announce that the very first b3 Builder job was just
>> executed!
>>
>> (And in case you wonder - no, it did not do much :)
>>
>>
>> Regards
>> - henrik
>
|
|
|
Powered by
FUDForum. Page generated in 0.03441 seconds