CI: Disabling dev docs push from azure-pipelines while we fix it

[datapythonista]

master builds are failing, this temporary fixes them while we figure out why the ssh key is not working.

See: #26591

CC: @jreback

[jreback]

hmm https://github.com/pandas-dev/pandas/pull/26602/checks?check_run_id=139942806

it didn't like this?

[datapythonista]

@vtbassmatt @davidstaheli @infin8x we're getting random errors like the one that happened here since we started using the task InstallSSHKey@0. The file mentioned in the error does exist, and there is nothing wrong in the configuration here. The only change is that in one of the steps we stop making a git push.

I saw the same error before, because the InstallSSHKey@0 task couldn't find the key, even if it was not running because the specified condition was not met.

Can you please assist?

[codecov]

Codecov Report

❗ No coverage uploaded for pull request base (master@2c6d005). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master   #26602   +/-   ##
=========================================
  Coverage          ?   91.84%           
=========================================
  Files             ?      174           
  Lines             ?    50668           
  Branches          ?        0           
=========================================
  Hits              ?    46535           
  Misses            ?     4133           
  Partials          ?        0

Flag	Coverage Δ
#multiple	90.38% <ø> (?)
#single	41.7% <ø> (?)

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 2c6d005...7abae60. Read the comment docs.

[codecov]

Codecov Report

❗ No coverage uploaded for pull request base (master@2c6d005). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master   #26602   +/-   ##
=========================================
  Coverage          ?   91.84%           
=========================================
  Files             ?      174           
  Lines             ?    50668           
  Branches          ?        0           
=========================================
  Hits              ?    46535           
  Misses            ?     4133           
  Partials          ?        0

Flag	Coverage Δ
#multiple	90.38% <ø> (?)
#single	41.7% <ø> (?)

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 2c6d005...7abae60. Read the comment docs.

[datapythonista]

We're also receiving another weird error here: https://dev.azure.com/pandas-dev/pandas/_build/results?buildId=12100

This build has the same exact configuration than this one that failed with the Host key verification failed (which I think it's a correct error): https://dev.azure.com/pandas-dev/pandas/_build/results?buildId=12093

And one more weird error here with a correct configuration: https://dev.azure.com/pandas-dev/pandas/_build/results?buildId=12106&view=results

It's quite worrying to see azure pipelines giving random errors like this, that don't inform which is the actual problem, and that happen in unrelated changes that are correct. Let's see if those can be fixed by azure, otherwise I'll leave the doc build in travis, and hope that pipeline becomes stable again.

CC: @pandas-dev/pandas-core

[davidstaheli]

Hi @datapythonista . For the first error about the file "not found," we're working with GitHub on the problem. It's caused by GitHub sending Azure Pipelines a "pull_request" webhook event, but when Azure Pipelines tries to fetch the files to build, the commit hasn't replicated to all of GitHub's databases yet, so GitHub returns 404 - Not Found. In addition to GitHub working on this, I'm hopeful Azure Pipelines will have better wait+retry logic within a week as a workaround.

On the 2nd weird error, I don't know the full history, but it started when a dependency was updated. It was fixed on May 29, 2019 here. I'll find out how soon we can get that fix deployed to production and push for ASAP.

[datapythonista]

Thanks for the update @davidstaheli

In case it helps, I'm not aware of seeing those errors since we added the InstallSSHKey@0 task to our jobs. Which didn't work anyway. If you can ping us when all this is fixed, we can give another try on building the docs and pushing them to a gihub repo from azure, which we had to revert.