5. Configuration Management
| Data | Versão | Descrição | Responsavel |
|---|---|---|---|
| 17/03/2017 | 0.1.0 | Ferramentas Utilizadas para Gerência de Configuração | Jessica e Tulio Coelho |
| 17/03/2017 | 0.1.1 | Papéis | Jessica e Tulio Coelho |
| 18/03/2017 | 0.1.2 | Processo de Gerência de Configuração | Jessica e Tulio Coelho |
| 19/03/2017 | 0.1.3 | Translation | Tulio Coelho |
1. Configuration Management Tools
3. Configuration Management Process
We're going to use Travis for configuration management. The main role of travis in this project is execute test commands, and validation of 'commits' done by our developers.
Each development environment will have a different travis configuration. Travis will be configured differently for our backend environment, and our frontend environment.
Zenhub will be used to do issues tracking on the project. Each user story described on zenhub will be related with some issue or feature on github.
CodeClimate will be used for static analysis of our code, also to guide our programming techniques implementation.
We're going to use Atom with ESLINT to integrate our code editor with the airbnb's stylesheet for javascript and reactJS.
There are two roles for configuration management on our project:
-
Developers:
The developers will be responsible to implement the code according to the project's stylesheet.
-
Scrum Master:
The Scrum Master will be responsible to verify if the rules are being used correctly according to the project's stylesheet.
