[L2Ork-dev] CI Runners

[Jonathan Wilkes]

> Yep, that's the basic idea. I guess that's what you've been doing all
along, no?

No, I've been merging into master. The problem is that when CI takes
forever its easy to
miss that you've canceled one of the jobs that you needed to test.

So currently the Windows build is broken in master because I canceled a build
in order to finish yours.

So yeah, some scriptable system for merging into a test branch is probably a
good idea.

-Jonathan

On Mon, Mar 19, 2018 at 12:53 PM, Albert Graef <aggraef at gmail.com> wrote:
> Yep, that's the basic idea. I guess that's what you've been doing all
> along, no? You could automatize this to a great extent, so that you
> just need to give the clone url and branch name to a shell script
> (running locally) and that script does all the rest.
>
> On Mon, Mar 19, 2018 at 5:25 PM, Jonathan Wilkes <jon.w.wilkes at gmail.com> wrote:
>> Hm... I guess you mean I'd have my own branch "testing" or something. Then
>> as others make merge requests to the master branch, I would:
>>
>> 1. Merge their requested changes into "testing" to trigger CI
>> 2. If it succeeds, accept their merge request into master.
>> 3. Delete the "testing" branch and create a new one off master.
>> 4. Repeat
>>
>> Something like this?
>>
>> -Jonathan
>> _______________________________________________
>> L2Ork-dev mailing list
>> L2Ork-dev at disis.music.vt.edu
>> https://disis.music.vt.edu/listinfo/l2ork-dev
>
>
>
> --
> Dr. Albert Gr"af
> Computer Music Research Group, JGU Mainz, Germany
> Email:  aggraef at gmail.com
> WWW:    https://plus.google.com/+AlbertGraef
> _______________________________________________
> L2Ork-dev mailing list
> L2Ork-dev at disis.music.vt.edu
> https://disis.music.vt.edu/listinfo/l2ork-dev