Testing Pull Requests

[Colin Finck]

Hi all!
Apart from basic build testing through AppVeyor and Travis-CI, you can
now also run all regression tests for the code belonging to a Pull Request.
Just log in to our BuildBot at https://build.reactos.org with your
development account credentials (formerly "SVN credentials"), select a
builder in the waterfall view and fill the field "Branch" in the "Force
a Build" section. You have two options here:
* "refs/pull/<ID>/head"
  Builds your branch, unmodified.
  That means, if you haven't kept your branch up to date with the main
  ReactOS repo, latest changes won't be included.
* "refs/pull/<ID>/merge"
  Builds the changes of your branch merged to the main ReactOS repo.
  That means, latest changes in the main ReactOS repo will be included.
Replace <ID> by the number of your Pull Request.
As the resulting hash may be hard to predict, the "prepare source" step
will now give detailed information about the latest commit included in
your build:
https://build.reactos.org/builders/Build%20GCCLin_x86/builds/19201/steps/pr…
Have fun!
Colin

[James Tabor]

Can we still use the ID for patches from Jara?
On Thu, Oct 12, 2017 at 6:04 AM, Colin Finck <colin(a)reactos.org> wrote:
>   Hi all!
>  Apart from basic build testing through AppVeyor and Travis-CI, you can
>  now also run all regression tests for the code belonging to a Pull Request.
>  Just log in to our BuildBot at https://build.reactos.org with your
>  development account credentials (formerly "SVN credentials"), select a
>  builder in the waterfall view and fill the field "Branch" in the "Force
>  a Build" section. You have two options here:
>  * "refs/pull/<ID>/head"
>    Builds your branch, unmodified.
>    That means, if you haven't kept your branch up to date with the main
>    ReactOS repo, latest changes won't be included.
>  * "refs/pull/<ID>/merge"
>    Builds the changes of your branch merged to the main ReactOS repo.
>    That means, latest changes in the main ReactOS repo will be included.
>  Replace <ID> by the number of your Pull Request.
>  As the resulting hash may be hard to predict, the "prepare source" step
>  will now give detailed information about the latest commit included in
>  your build:
>  https://build.reactos.org/builders/Build%20GCCLin_x86/
>  builds/19201/steps/preparing%20source/logs/stdio
>  Have fun!
>  Colin
>  _______________________________________________
>  Ros-dev mailing list
>  Ros-dev(a)reactos.org
>  http://www.reactos.org/mailman/listinfo/ros-dev

[Colin Finck]

Am 14. Oktober 2017 01:26:09 MESZ schrieb James Tabor <jimtabor.rosdev(a)gmail.com>om>:
>  Can we still use the ID for patches from Jara? 
Sure! They are processed using "git apply" now.
- Colin

[James Tabor]

It seems to work like before,
https://reactos.org/testman/compare.php?ids=55960,55962
Not bad.
On Sat, Oct 14, 2017 at 1:49 AM, Colin Finck <mail(a)colinfinck.de> wrote:
>  Am 14. Oktober 2017 01:26:09 MESZ schrieb James Tabor <
>  jimtabor.rosdev(a)gmail.com&gt;gt;:
> >  Can we still use the ID for patches from Jara?
>  Sure! They are processed using "git apply" now.
>  - Colin
>  _______________________________________________
>  Ros-dev mailing list
>  Ros-dev(a)reactos.org
>  http://www.reactos.org/mailman/listinfo/ros-dev
>