Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between pages "Equinox Slingshot" and "WTP Build Process and Procedures"
(→Background and Further Reading References) |
|||
| Line 1: | Line 1: | ||
| − | The | + | This page is to collect general information and references about the WTP build process and procedures. The idea is that any WTP committer can update it, pretty much "on the fly" or "as you go", or "as needed", so that there will often be a bit of a disorganized, stream of consciousness flavor to it. Hopefully, occasionally, some kind-hearted committer will stop and organize all the miscellaneous notes and tips and references that are provided, into fun-to-read treasure that you just can't put down. |
| − | + | Note: since only committers can edit these pages, if anyone from the community has contributions or suggestions for additions, please open a [[https://bugs.eclipse.org/bugs/enter_bug.cgi?product=Web%20Tools;component=releng feature request]] on our releng component. | |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| + | Thanks, [[User:David williams|David Williams]] 01:42, 2 February 2006 (EST) | ||
| + | == Build Schedules == | ||
| + | As of February 1, 2006 | ||
| + | Our WTP 1.0.1 contributions are due by EOD on Monday's, we smoke test that build on Tuesday's, and plan to declare it by Wednesday's at noon (eastern time). | ||
| − | '' | + | Our WTP 1.5 contributions are due by EOD Wednesday's, we smoke test that build on Thursday's, and plan to declare it by Friday's at noon (eastern time). |
| − | + | ||
| − | + | ||
| − | |||
| − | + | == Build mechanics == | |
| + | The platform's releng tool should be used to "release" projects to the map files. | ||
| + | Be sure to have the appropriate branch of releng project (which has the map files) | ||
| + | loaded in your workspace. | ||
| + | R1_0_maintenance for 1.0.x builds, and HEAD for 1.5 builds. | ||
| + | As projects are versioned, please use the "standard" format, in UTC time, following | ||
| + | vYYYYMMDD_HHMM. | ||
| + | This is important as these cvs tags become the qualifier field of the plugin's version. | ||
| − | + | == Background and Further Reading References == | |
| − | + | ||
| − | - | + | We in WTP following the basic process and recommendations for versioning as the base Eclipse platform. |
| + | [http://www.eclipse.org/equinox/documents/plugin-versioning.html Plugin Versioning] | ||
| − | + | Very helpful guide to builds and automatic testing. | |
| − | + | [http://www.eclipse.org/articles/Article-PDE-Automation/automation.html Build and Test Automation for plug-ins and features] | |
| − | + | Good step-by-step on how to do updates. [http://www.eclipse.org/articles/Article-Update/keeping-up-to-date.html How To Keep Up To Date] | |
| + | We base our builds on the Eclipse platform's "basebuilder". | ||
| + | [http://wiki.eclipse.org/index.php/Platform-releng Platform-releng] | ||
| − | + | With our WTP specific needs addressed in the WTP project called releng.wtpbuilder. | |
| + | While slightly out of date, see the [[https://bugs.eclipse.org/bugs/attachment.cgi?id=26584 attachment]] to [[https://bugs.eclipse.org/bugs/show_bug.cgi?id=108259 bug 108259]] | ||
| − | + | Our basic server configuration and cruise control triggers is handled by the WTP project called releng.builder (see especially the tools/cruise directory in that project). | |
| − | + | And ... never forget [http://help.eclipse.org/help31/index.jsp Eclipse Help] ... search for things related to update manager, PDE, features, site.xml, etc. | |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
Revision as of 17:10, 4 February 2006
This page is to collect general information and references about the WTP build process and procedures. The idea is that any WTP committer can update it, pretty much "on the fly" or "as you go", or "as needed", so that there will often be a bit of a disorganized, stream of consciousness flavor to it. Hopefully, occasionally, some kind-hearted committer will stop and organize all the miscellaneous notes and tips and references that are provided, into fun-to-read treasure that you just can't put down.
Note: since only committers can edit these pages, if anyone from the community has contributions or suggestions for additions, please open a [feature request] on our releng component.
Thanks, David Williams 01:42, 2 February 2006 (EST)
Build Schedules
As of February 1, 2006
Our WTP 1.0.1 contributions are due by EOD on Monday's, we smoke test that build on Tuesday's, and plan to declare it by Wednesday's at noon (eastern time).
Our WTP 1.5 contributions are due by EOD Wednesday's, we smoke test that build on Thursday's, and plan to declare it by Friday's at noon (eastern time).
Build mechanics
The platform's releng tool should be used to "release" projects to the map files. Be sure to have the appropriate branch of releng project (which has the map files) loaded in your workspace. R1_0_maintenance for 1.0.x builds, and HEAD for 1.5 builds.
As projects are versioned, please use the "standard" format, in UTC time, following vYYYYMMDD_HHMM. This is important as these cvs tags become the qualifier field of the plugin's version.
Background and Further Reading References
We in WTP following the basic process and recommendations for versioning as the base Eclipse platform. Plugin Versioning
Very helpful guide to builds and automatic testing. Build and Test Automation for plug-ins and features
Good step-by-step on how to do updates. How To Keep Up To Date
We base our builds on the Eclipse platform's "basebuilder". Platform-releng
With our WTP specific needs addressed in the WTP project called releng.wtpbuilder. While slightly out of date, see the [attachment] to [bug 108259]
Our basic server configuration and cruise control triggers is handled by the WTP project called releng.builder (see especially the tools/cruise directory in that project).
And ... never forget Eclipse Help ... search for things related to update manager, PDE, features, site.xml, etc.