User:Catlee/BuildScripts: Difference between revisions

Jump to navigation Jump to search
no edit summary
(Created page with 'This page is an exploration of some ideas of how to clean up our build infrastructure, in particular the set of commands that get run to produce a build, or run a set of tests. …')
 
No edit summary
Line 19: Line 19:


The "build configuration", which contains things like which revision to build, gets written somewhere (like /tmp?).  An environment variable is set to indicate this location ($BUILD_CONFIG).  It could be nice to have this configuration written out in multiple formats, e.g. config.sh suitable for source'ing in a bash script, config.py suitable for importing in a python script, and config.json suitable for other purposes.
The "build configuration", which contains things like which revision to build, gets written somewhere (like /tmp?).  An environment variable is set to indicate this location ($BUILD_CONFIG).  It could be nice to have this configuration written out in multiple formats, e.g. config.sh suitable for source'ing in a bash script, config.py suitable for importing in a python script, and config.json suitable for other purposes.
The harness will also create a temporary working directory where scripts are free to save data for use later in the build, e.g. recording changesets, hashes, or package urls.


=== Example ===
=== Example ===
Line 73: Line 75:
To run this build, you would run:
To run this build, you would run:
  harness.py -f mozilla-central/linux/depend/config.ini -C build/mozilla-central/depend HGURL=http://hg.mozilla.org/mozilla-central REV=123456
  harness.py -f mozilla-central/linux/depend/config.ini -C build/mozilla-central/depend HGURL=http://hg.mozilla.org/mozilla-central REV=123456
=== Open Questions ===
* We'd lose per-step logging and status as far as buildbot is concerned.  Does this matter?
* How to share common scripts and configs?
Confirmed users
2,456

edits

Navigation menu