On Wednesday, February 10, 2016 at 4:23:20 AM UTC-5, Achilleas Pipis wrote: > > On 02/08/2016 03:39 PM, Brian S wrote: > > > > My repositories are organized in two groups (Libaries and Applications) > > > > It is easy enough to test the library on it's own but testing the > > applications is more difficult for two reasons. > > > > 1. It appears as though I need to clone the library when running tests > > on the application > > 2. When a change is made in the library I want to run the application > tests. > > > > You can make use of triggers > http://doc.gitlab.com/ce/ci/triggers/README.html > > --- > > If I understand your issue correctly, you should create a trigger token > in the application project and then in the .gitlab-ci.yml of the library > you can have a job like: > > run_app: > stage: build > script: > - "curl -X POST -F token=TOKEN -F ref=master > https://gitlab.example.com/api/v3/projects/9/trigger/builds"; > > where 9 is the ID of the application project. > > -- > Blog: http://axilleas.me >
Triggers via token looks promising. I am going to research this further. Regarding building an application that depends on a library. (For Examples, App A depends on Lib B) Is the correct method for building App A in GitLab CI to checkout Lib B Inside App A? Something similar to the following. AppBuild: script: - git clone https://gitlab.example.com/projects/LibB - cd LibB - build LibB - cd AppA - build AppA linking to LibB -- You received this message because you are subscribed to the Google Groups "GitLab" group. To unsubscribe from this group and stop receiving emails from it, send an email to gitlabhq+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/gitlabhq/0481e862-d740-486b-b369-fa3019834918%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
