Hi Hazen,
That’s exactly how I do it though: trial and error :-)
If you worry about the commit history, then I recommend you do this in a
separate branch, open a PR, commit until you get it right and then use “squash
and merge”. In fact I recommend you make master a protected branch meaning that
no direct commits can be made into it, only via the PR system. This also ensure
that no disasters via “git push —force” happen :-)
But before you do any of this, make sure that Travis-CI is properly configured
in Settings -> Integrations & Services. On the Travis-CI page you will also
have to activate support for PRs (or maybe that is the default, not sure).
Best regards,
Tom
> On 20 Nov 2016, at 15:58, Hazen Babcock wrote:
>
>
> Hi Tom,
>
> Any pointers for getting started with continuous integration? I'm planning to
> set this up on the Github PLplot mirror using Travis-CI to start.
>
> In particular I'd like to know what you think is the best way to go about
> debugging the Travis scripts? It appears to me that this is going to involve
> lots of cycles of editing, pushing and waiting for Travis results, along with
> a lot of commit noise. Is there a better way?
>
> best,
> -Hazen
--
___
Plplot-devel mailing list
Plplot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/plplot-devel
