Andreas/evennia
1
0
Fork 0
mirror of https://github.com/evennia/evennia.git synced 2026-03-18 13:56:30 +01:00
Code Issues Projects Releases Packages Wiki Activity Actions

Fix unit test. Update/remove more coding docs

Browse source
This commit is contained in:
Griatch 2022-11-25 21:22:34 +01:00
parent a77d568709
commit a99fb7bcc4
11 changed files with 33 additions and 841 deletions
Download patch file Download diff file Expand all files Collapse all files

6
docs/source/Coding/Continuous-Integration.md
View file

@ -1,7 +1,5 @@
# Continuous Integration (CI)
One of the advantages of Evennia over traditional MU* development systems is that Evennia can integrate into enterprise-level integration environments and source control.
[Continuous Integration (CI)](https://www.thoughtworks.com/continuous-integration) is a development practice that requires developers to integrate code into a shared repository. Each check-in is then verified by an automated build, allowing teams to detect problems early. This can be set up to safely deploy data to a production server only after tests have passed, for example.
For Evennia, continuous integration allows an automated build process to:
@ -13,7 +11,7 @@ For Evennia, continuous integration allows an automated build process to:
* Publish those files to the server directory
* Reload the game.
## List of CI Evennia tutorials
## Continuous-Integration guides
There are a lot of tools and services providing CI functionality. Here are a few that people have used with Evennia:
@ -25,4 +23,6 @@ Continuous-Integration-TeamCity.md
```
- Evennia is itself making heavy use of [github actions]()
[This is an overview of other tools](https://www.atlassian.com/continuous-delivery/continuous-integration/tools) (external link).