This repository has been archived by the owner on Jul 17, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 72
Continous Integration (CI)
ponceta edited this page Oct 6, 2014
·
1 revision
Travis is used for continous integration. It's great to check
- project can be build
- functional unit tests are succesfull
It does NOT:
- run integration tests (chsdi3)
- run browserstack tests (ga3, current solution not satisfying)
To adress the above, an internal ci server (jenkins) could be installed.
- github support (trigger builds on push, for branches and for pull requests)
- environment same/similar to mf0[t|i|p] to be able to build the project
- optional: db trigger (when db is deployed to test, run chsdi3 tests)
- being able to connect the databases for integration tests
- browserstack needs public access to a fully hosted build (similar to user based builds or branches that are deployed), each build needs a unique and temporary address. This will be used to run the browserstack tests. How could we achieve this?
- can't be used right now because the environment does not allow a build (tooling not complet)
- install Jenkins on mf0t (same configuration as the GeoCat instance) and go from here.