continues -> continuous (#3895)
This commit is contained in:
parent
dfa9f52e44
commit
e310ef7943
|
@ -30,7 +30,7 @@ Important note - we now use submodules:
|
||||||
* [Simulator](/simulator) win32 or posix version of firmware allows to explore without any hardware
|
* [Simulator](/simulator) win32 or posix version of firmware allows to explore without any hardware
|
||||||
* [Unit Tests](/unit_tests) Unit tests of firmware pieces
|
* [Unit Tests](/unit_tests) Unit tests of firmware pieces
|
||||||
* [Misc tools](/java_tools) Misc development utilities
|
* [Misc tools](/java_tools) Misc development utilities
|
||||||
* [misc/Jenkins](/misc/jenkins) Jenkins Continues Integration scripts
|
* [misc/Jenkins](/misc/jenkins) Jenkins Continuous Integration scripts
|
||||||
* [Software Development process](misc/SoftwareDevelopmentProcess.md)
|
* [Software Development process](misc/SoftwareDevelopmentProcess.md)
|
||||||
* [Work in progress status](work_in_progress.md)
|
* [Work in progress status](work_in_progress.md)
|
||||||
|
|
||||||
|
|
|
@ -280,7 +280,7 @@ public class StartupFrame {
|
||||||
|
|
||||||
/**
|
/**
|
||||||
* Here we listen to keystrokes while console start-up frame is being displayed and if magic "test" word is typed
|
* Here we listen to keystrokes while console start-up frame is being displayed and if magic "test" word is typed
|
||||||
* we launch a functional test on real hardware, same as Jenkins runs within continues integration
|
* we launch a functional test on real hardware, same as Jenkins runs within continuous integration
|
||||||
*/
|
*/
|
||||||
@NotNull
|
@NotNull
|
||||||
private KeyListener functionalTestEasterEgg() {
|
private KeyListener functionalTestEasterEgg() {
|
||||||
|
@ -349,4 +349,4 @@ public class StartupFrame {
|
||||||
combo.setSelectedItem(defaultSpeed);
|
combo.setSelectedItem(defaultSpeed);
|
||||||
return combo;
|
return combo;
|
||||||
}
|
}
|
||||||
}
|
}
|
||||||
|
|
|
@ -1,7 +1,7 @@
|
||||||
|
|
||||||
|
|
||||||
rusEfi firmware development model is "stable master". We do not have release branches, we only have master with
|
rusEfi firmware development model is "stable master". We do not have release branches, we only have master with
|
||||||
continues integration and *limited* automated testing.
|
continuous integration and *limited* automated testing.
|
||||||
|
|
||||||
By default, each Pull Request is expected to be complete and expected to not break existing functionality.
|
By default, each Pull Request is expected to be complete and expected to not break existing functionality.
|
||||||
If a Pull Request is a work-in-progress or draft or not intended for merge yet, it should be clearly marked with "[WIP]" prefix in the title.
|
If a Pull Request is a work-in-progress or draft or not intended for merge yet, it should be clearly marked with "[WIP]" prefix in the title.
|
||||||
|
@ -13,8 +13,8 @@ It is usually helpful to discuss proposed changes prior to Pull Requests - we ha
|
||||||
|
|
||||||
TODO: we have an urgent need to make gate check more reliable & expand what's included into gate check
|
TODO: we have an urgent need to make gate check more reliable & expand what's included into gate check
|
||||||
|
|
||||||
The primary hardware platform for rusEfi is stm32f4 - as of November 2019, only stm32f4 has hardware test continues integration.
|
The primary hardware platform for rusEfi is stm32f4 - as of November 2019, only stm32f4 has hardware test continuous integration.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
See also [Functional tests CI info](jenkins/functional_test_and_build_bundle/readme.md)
|
See also [Functional tests CI info](jenkins/functional_test_and_build_bundle/readme.md)
|
||||||
|
|
Loading…
Reference in New Issue