Re: Appveyor Builds & Testing
Ramiro Morales <[email protected]>
| Newsgroups | gmane.comp.db.tds.freetds |
|---|---|
| Message-ID | <CAO7PdF8g-2oURnbWMhxPQn1M5Zeia1M4rymow_V1kcNgETG8bw@mail.gmail.com> |
On Fri, Jul 24, 2015 at 2:03 PM, Frediano Ziglio <[email protected]> wrote: > 2015-07-22 12:25 GMT+01:00 Ramiro Morales <[email protected]>: ill be merged. > >> This causes for example that once a regression occurs there is no >> granularity to know which of the intermediate commit (between the >> merges/rebases) is the culprit. See item 5 above for an example. >> > > Not clear here what you mean. > What I tried to say was that in the manual-merge-from-master-from-time-to-time setup it was hard to spot the individual commit that introduced a build error/test regression because in that case Appveyor performed only one build with the changes of all intermediate commits. But you've fixed this and Appveyor already is bulding from master. -- Ramiro Morales @ramiromorales