You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please can we enable appveyor builds for jelmer/dulwich. This has to be done by @jelmer. The setup is similar to setting up travis, and is free of charge for FLOS projects.
The reporting in pull request will show the results from both travis, and from appveyor. Here is an example of a PR for a project that uses both travis and appveyor: inklesspen/montague#12
On Mon, May 25, 2015 at 09:20:03AM -0700, Gary van der Merwe wrote:
Please can we enable appveyor builds for jelmer/dulwich. This has to be done by @jelmer. The setup is similar to setting up travis, and is free of charge for FLOS projects.
The reporting in pull request will show the results from both travis, and from appveyor. Here is an example of a PR for a project that uses both travis and appveyor: inklesspen/montague#12
That said, I'm a bit ambivalent about this, as I don't want to be responsible for the Windows builds...
I understand. I'm sure that once I get the tree green (almost there), it will be easy to maintain it, now that we have a windows CI. However, if we regress, you can ignore it, or turn it off.
Please can we enable appveyor builds for jelmer/dulwich. This has to be done by @jelmer. The setup is similar to setting up travis, and is free of charge for FLOS projects.
The reporting in pull request will show the results from both travis, and from appveyor. Here is an example of a PR for a project that uses both travis and appveyor: inklesspen/montague#12
https://ci.appveyor.com/login
The text was updated successfully, but these errors were encountered: