1
edit
Changes
Created page with '== Project Name == ScriptFactory == Project Description == Imagine that we did not have to touch the Mozilla buildbot factories but instead we maintained a bunch of script for…'
== Project Name ==
ScriptFactory
== Project Description ==
Imagine that we did not have to touch the Mozilla buildbot factories but instead we maintained a bunch of script for all the different jobs they run?
It would be good if we could create scripts that told a machine how to generate an optimized build, a debug build, unit tests, talos runs, locale repackages. If you look in the tools/scripts repo you can see that we have a simple shell file to do this for the fuzzing automation. The buildbot factory that calls it is called ScriptFactory and it is very simple.
== Project Leader(s) ==
Adrian Pruteanu [http://zenit.senecac.on.ca/wiki/index.php/User:Atpruteanu]
Mustafa Redha [http://zenit.senecac.on.ca/wiki/index.php/User:Mredha]
Jing Yang [http://zenit.senecac.on.ca/wiki/index.php/User:Jing_yang]
== Project Contributor(s) ==
Name(s) of people casually working on the project, or who have contributed significant help. Include links to personal pages within wiki
NOTE: only Project Leader(s) should add names here. You '''can’t''' add your own name to the Contributor list.
== Project Details ==
Provides more depth than the Project Description. This is the place for technical discussions, project specs, or other details. If this gets very long, you might consider breaking this part into multiple pages and linking to them.
== Project Plan ==
Goals for each release:
* 0.1
* 0.2
* 0.3
== Project News ==
This is where your regular updates will go. In these you should discuss the status or your work, your interactions with other members of the community (e.g., Seneca and Mozilla), problems you have encountered, etc.
Put detailed technical information into the Project Details page (i.e., update it as you go), and save this section for news about participation in the project.
ScriptFactory
== Project Description ==
Imagine that we did not have to touch the Mozilla buildbot factories but instead we maintained a bunch of script for all the different jobs they run?
It would be good if we could create scripts that told a machine how to generate an optimized build, a debug build, unit tests, talos runs, locale repackages. If you look in the tools/scripts repo you can see that we have a simple shell file to do this for the fuzzing automation. The buildbot factory that calls it is called ScriptFactory and it is very simple.
== Project Leader(s) ==
Adrian Pruteanu [http://zenit.senecac.on.ca/wiki/index.php/User:Atpruteanu]
Mustafa Redha [http://zenit.senecac.on.ca/wiki/index.php/User:Mredha]
Jing Yang [http://zenit.senecac.on.ca/wiki/index.php/User:Jing_yang]
== Project Contributor(s) ==
Name(s) of people casually working on the project, or who have contributed significant help. Include links to personal pages within wiki
NOTE: only Project Leader(s) should add names here. You '''can’t''' add your own name to the Contributor list.
== Project Details ==
Provides more depth than the Project Description. This is the place for technical discussions, project specs, or other details. If this gets very long, you might consider breaking this part into multiple pages and linking to them.
== Project Plan ==
Goals for each release:
* 0.1
* 0.2
* 0.3
== Project News ==
This is where your regular updates will go. In these you should discuss the status or your work, your interactions with other members of the community (e.g., Seneca and Mozilla), problems you have encountered, etc.
Put detailed technical information into the Project Details page (i.e., update it as you go), and save this section for news about participation in the project.
