Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Trigger builds on sub-projects #501

jgebal opened this issue Oct 24, 2017 · 2 comments

Trigger builds on sub-projects #501

jgebal opened this issue Oct 24, 2017 · 2 comments


Copy link

jgebal commented Oct 24, 2017

Whenever a build is executed on develop branch, dependent projects need to be built to assure that they are not failing after changes to the main project.

For details on how to do this see Travis doc
Currently the dependency is:

  • utPLSQL
    • utPLSQL-sql-cli
    • utPLSQL-v2-v3-migration
    • utPLSQL-java-api
      • utPLSQL-cli
      • utPLSQL-maven-plugin - once developed

We should build dependent project pulling sources of the develop branch of utPLSQL.
This way each breaking change in develop should be easy to capture in underlying projects.

@jgebal jgebal added this to the v3.1.0 milestone Oct 24, 2017
@jgebal jgebal removed this from the v3.1.0 milestone Feb 5, 2018
Copy link
Member Author

jgebal commented Apr 29, 2018

Copy link
Member Author

jgebal commented Apr 30, 2018

We should only trigger builds of matrix dedicated to develop branch.
There is an example in documentation: for overriding parts of .travis.yml config on triggered build:

 "request": {
 "message": "Override the commit message: this is an api request",
 "config": {
   "env": {
     "matrix": ["TEST=unit"]
   "script": "echo FOO"

@lwasylow lwasylow self-assigned this Jun 26, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet

No branches or pull requests

2 participants