TST: Add azure CI testing to 1.15.x branch.

[charris]

The appveyor webhook is deactivated, so we need to use azure to
test backports on windows before the next 1.15.x release. This
also add testing on the Mac.

[charris]

This didn't activate azure. I don't see anything in the app that is branch specific, I wonder if we need to put something in the yml file or change something on the pipeline. @chrisrpatterson Thoughts?

[tylerjereddy]

The website settings are definitely on master branch -- not sure if we can easily add more branches for triggering builds without i.e., adding a new pipeline associated with the maintenance branch.

[charris]

Maybe the branch needed the yml file when I set up the pipeline. IIRC, the presence of yml files was checked for. At some point I will try deleting and reinstalling the app -- might be a chance to rename the pipeline also.

[charris]

The tests can be run for 1.15.x manually by specifying the commit, but it cannot be done automatically. This seems to be a design fault, as the default branch is set as part of the pipeline, and it seems we can only have one (free) pipeline attached to numpy.

[charris]

Solved.

• Navigate to your project in Azure Pipelines or TFS. Select Pipelines, and then select Builds. Locate your build, and select Edit.
• Select Triggers. Enable the Pull request validation trigger. Ensure you include the master branch under Branch filters. Add maintenance/1.15.x (will be a pulldown selection).

[charris]

I think we can also add triggers to the *.yml file in a trigger section.