evennia/docs/1.0-dev/_sources/Coding/Continuous-Integration.md.txt

36 lines
1.3 KiB
Text
Raw Normal View History

2020-06-13 00:36:45 +02:00
# Continuous Integration
2022-02-06 18:34:09 +00:00
One of the advantages of Evennia over traditional MU* development systems is that Evennia can
integrate into enterprise-level integration environments and source control.
2020-06-13 00:36:45 +02:00
2022-02-06 18:34:09 +00:00
## What is Continuous Integration (CI)?
2020-06-13 00:36:45 +02:00
[Continuous Integration (CI)](https://www.thoughtworks.com/continuous-integration) is a development
2022-02-06 18:34:09 +00:00
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.
2020-06-13 00:36:45 +02:00
For Evennia, continuous integration allows an automated build process to:
2022-02-06 18:34:09 +00:00
2020-06-13 00:36:45 +02:00
* Pull down a latest build from Source Control.
* Run migrations on the backing SQL database.
* Automate additional unique tasks for that project.
* Run unit tests.
* Publish those files to the server directory
* Reload the game.
2022-02-06 18:34:09 +00:00
## List of continuous integration tools
2020-06-13 00:36:45 +02:00
2022-02-06 18:34:09 +00:00
There are a lot of tools and services providing CI functionality. Here are a few that people have used
with Evennia:
2020-06-13 00:36:45 +02:00
2022-02-06 18:34:09 +00:00
```{toctree}
:maxdepth: 1
2020-06-13 00:36:45 +02:00
2022-02-06 18:34:09 +00:00
Continuous-Integration-Travis.md
Continuous-Integration-TeamCity.md
2020-06-13 00:36:45 +02:00
2022-02-06 18:34:09 +00:00
```
2020-06-13 00:36:45 +02:00
2022-02-06 18:34:09 +00:00
[This is an overview of other tools](https://www.atlassian.com/continuous-delivery/continuous-integration/tools)
(external link).