[PoC] ci: Homebrew strikes again, let's try some workarounds on an older version

[szeder]

Just another small experiment.

[dscho]

@szeder why two PRs with identical patches?

[szeder]

On Fri, Oct 11, 2019 at 02:49:43PM -0700, Johannes Schindelin wrote: @szeder why two PRs with identical patches?

While the patches are identical, they are based on different commits. I wanted to check whether `brew cask install perforce` works on Azure Pipelines as well, in particular: - without a previous `brew update`, i.e. on whatever Homebrew state is present in the Azure Pipelines macOS images. This was checked in that other PR. - after a `brew update`, i.e. without commit f2f4715 (ci: don't update Homebrew, 2019-07-03), hence this PR based on v2.22.0, However, after having slept on it I finally realized what should have been obvious from the beginning: the CI builds my PR merged into master, i.e. with f2f4715 anyway... oh, well.

[dscho]

While the patches are identical, they are based on different commits.

... but the CI of course runs on the merge commit, which makes that difference rather pointless.

[szeder]

On Sun, Oct 13, 2019 at 03:21:41PM -0700, Johannes Schindelin wrote: > While the patches are identical, they are based on different commits. ... but the CI of course runs on the merge commit, which makes that difference rather pointless.

Yeah; as I said I realized that the next day...

[dscho]

... but the CI of course runs on the merge commit, which makes that difference rather pointless.
Yeah; as I said I realized that the next day...

My common workaround is to use a different target branch.