| [buckminster-dev] tips on headless buckminster in CI environment? [message #9598] |
Fri, 14 March 2008 14:07 |
 Todd Lee
Messages: 44
Registered: July 2009 |
Member |
|
|
Many thanks to the community at large (especially Thomas & Adrian) whose
help has got us to the point of resolving a workspace headlessly :D
As you can probably tell from the deluge of posts to this forum, we're
currently on our way from 0 to 60 in getting an autobuild system up and
running, so thanks in advance for your patience!
I'm wondering at this point if anyone would have any tips as to best
practices using buckminster for headless builds? Looking to those who've
successfully implemented similar systems, I guess I'm asking, "what do you
wish someone told you when you were starting out that would have saved some
bruising on your forehead..."?
We're building an eclipse IDE based product which uses alot of external
stuff. We're automating using a Pulse CI build server and looking to
buckminster to solve our 'middleware' issues (resolving/materializing
workspaces and dependencies). The current build is PDE based.
Specific questions:
1) what's the best entry point for buckminster in a real-world build setup
- standalone or ant integration?
2) once the workspace is materialized, is buckminster's role finished? ie -
is it best to just hand off to ant from there and execute the build or is
it better to use buckminster's 'perform' command to execute actions to
accomplish build tasks?
3) artifacts/cacheing - cleaning vs. retention - given the large amount of
caching that buckminster seems to use, is there any concern about clean up
post-build? Do people clear caches or just let them accumulate. And related
to products of buckminster, is there anything that you'd really suggest
keeping for posterity (obviously the bomfile comes to mind...)
4) specifically to those using pde builds - any tips/pitfalls with
buckminster?
Any suggestions are certainly appreciated!
Also, as an aside - any plans to include tutorials on this subject on the
wiki? Seems like a good candidate for a walk through. The documentation is
a big help and I know for me, it would be great to see buckminster at work
in the context of a sample build from beginning to end to demonstrate full
scope.
Thanks again!
T
AMI Semiconductor - "Silicon Solutions for the Real World"
NOTICE:
This electronic message contains information that may be confidential or privileged. The information is intended for the use of the individual or entity named above. If you are not the intended recipient, please be aware that any disclosure, copying, distribution or use of the contents of this information is prohibited. If you received this electronic message in error, please notify the sender and delete the copy you received.
|
|
|
Powered by
FUDForum. Page generated in 0.02675 seconds
] 
Search
Help
Register
Login
Home
