For each commit, Travis-ci runs 2 integrations tests pr and push. One of the test build geppetto from the branch the commit was created. The second test checkouts development, then merges with the branch the commit was produced and finally build the docker images on the result of the merge.
To keep track of these 2 test, we Travis-ci adds env variables.
TRAVIS_BRANCH
TRAVIS_PULL_REQUEST_BRANCH
Currently we have a shell script to understand in which Travis test we are and which branches to pull and merge for each org.geppetto.* repository.
The script is hard to read / modify / debug. We need a python script that builds on top of gitpython package.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
For each commit, Travis-ci runs 2 integrations tests
pr
andpush
. One of the test build geppetto from the branch the commit was created. The second test checkoutsdevelopment
, then merges with the branch the commit was produced and finally build the docker images on the result of the merge. To keep track of these 2 test, we Travis-ci adds env variables.Currently we have a shell script to understand in which Travis test we are and which branches to pull and merge for each org.geppetto.* repository.
The script is hard to read / modify / debug. We need a python script that builds on top of gitpython package.