Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Platform-releng-faq"
m (removed extra ']') |
|||
Line 25: | Line 25: | ||
: [[Platform-releng/Automated_Testing| automated (production) testing]] | : [[Platform-releng/Automated_Testing| automated (production) testing]] | ||
: [[Performance/Automated_Tests| performance testing]] | : [[Performance/Automated_Tests| performance testing]] | ||
+ | |||
+ | == What are common build problems? == | ||
+ | Common build problems are documented here | ||
+ | : [[Platform_Releng/Common_build_issues| Common build issues]] | ||
[Feel free to add more items to this document, when questions are frequently asked.] | [Feel free to add more items to this document, when questions are frequently asked.] |
Revision as of 00:13, 18 September 2018
Contents
Where are the basics of the Platform build documented?
In Platform Build.
Does that Platform Build document describe the so-called Production Build?
No, not exactly. It forms the heart of the production build, but there are other things done in the production build. Those are described in Platform Build Automated. So in general, anyone wanting to learn or reproduce our build should first read Platform Build and then read Platform Build Automated.
What other tasks does Platform Releng do?
Other tasks are described in several other documents, each has various degrees of accuracy or being up do date:
Are there documents that Platform committers should read or be aware of?
The following are good, though some sections may need to be brought up to date.
- the Eclipse Projects rhythm
- incrementing version numbers
- automated (production) testing
- performance testing
What are common build problems?
Common build problems are documented here
[Feel free to add more items to this document, when questions are frequently asked.]