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
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
I would like to stick with GitLab and support GitLab if possible.
On Monday, February 8, 2016 at 9:18:02 AM UTC-5, Dan Kegel wrote:
>
> I have implemented a similar feature locally, and it's very helpful, but
> my implementation relies on gitlab webhooks triggering buildbot builds, not
> gitlab
I have implemented a similar feature locally, and it's very helpful, but my
implementation relies on gitlab webhooks triggering buildbot builds, not
gitlab ci.
On Feb 8, 2016 5:40 AM, "Brian S" wrote:
>
>> Brian S writes:
>>
>> > I develop several custom applications using core libraries. I manag
>
>
> Brian S writes:
>
> > I develop several custom applications using core libraries. I manage
> > both applications and libraries in Gitlab. However I am struggling
> > with how to setup a Gitlab ci. I would like to test all my
> > applications when pushing to the master branch of my librar
Brian S writes:
> I develop several custom applications using core libraries. I manage
> both applications and libraries in Gitlab. However I am struggling
> with how to setup a Gitlab ci. I would like to test all my
> applications when pushing to the master branch of my libraries.
>
> Any sugges
