Content
View differences
Updated by Oliver Günther over 10 years ago
We need to ensure that we test our pull requests along with the plugins of community edition. This is to ensure that development does not break with any additional plugins. Ideally we would test a PR against all configurations but this is currently not possible.
**Scope**
- create script that fetches `Gemfile.plugins` from community edition
- check for all plugins if there is branch with the same name as of the current PR: if yes then replace branch definition.
- builds on branches (e.g., dev) are being tested core only (this can be identified with usage of travis environment variables) in order to test both CE (on PRs) and core-only.
**Implications**
- do not work on forks of plugins any longer
- in case changes in plugins are required the branch has to have the same name as the core branch
**Scope**
- create script that fetches `Gemfile.plugins` from community edition
- check for all plugins if there is branch with the same name as of the current PR: if yes then replace branch definition.
- builds on branches (e.g., dev) are being tested core only (this can be identified with usage of travis environment variables) in order to test both CE (on PRs) and core-only.
**Implications**
- do not work on forks of plugins any longer
- in case changes in plugins are required the branch has to have the same name as the core branch