summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorBundlerbot <bot@bundler.io>2019-11-04 15:24:50 +0000
committerBundlerbot <bot@bundler.io>2019-11-04 15:24:50 +0000
commit674966e21cc7257dd52797ef56ee9628c3ce1bc6 (patch)
treeb9dccb256b6762b6b4bedc7dd5ecc45fda337e96
parent3aa03910cdc95ef87e6cb1ccf298e0959e98d351 (diff)
parent9ad43915b73e7d96bd5bc04048c8896dccee584e (diff)
downloadbundler-674966e21cc7257dd52797ef56ee9628c3ce1bc6.tar.gz
Merge #7411
7411: Try out specs against MRI 2.6 + Rubygems 3.0 r=deivid-rodriguez a=deivid-rodriguez ### What was the end-user problem that led to this PR? The problem was that our Azure build was using outdated versions of ruby and rubygems. ### What was your diagnosis of the problem? My diagnosis was that we should update them. ### What is your fix for the problem, implemented in this PR? My fix is to update them. With the latest versions, failures go down to 319. Co-authored-by: David Rodríguez <deivid.rodriguez@riseup.net>
-rw-r--r--.azure-pipelines/steps.yml2
-rw-r--r--azure-pipelines.yml2
2 files changed, 3 insertions, 1 deletions
diff --git a/.azure-pipelines/steps.yml b/.azure-pipelines/steps.yml
index 1aedc8a4f8..3c8f2f9512 100644
--- a/.azure-pipelines/steps.yml
+++ b/.azure-pipelines/steps.yml
@@ -2,7 +2,7 @@ steps:
- task: UseRubyVersion@0
inputs:
- versionSpec: '= 2.4'
+ versionSpec: '= 2.6'
- script: |
ruby -v
diff --git a/azure-pipelines.yml b/azure-pipelines.yml
index d8bb61e6f3..d954482840 100644
--- a/azure-pipelines.yml
+++ b/azure-pipelines.yml
@@ -2,6 +2,8 @@ jobs:
- job: Windows
pool:
vmImage: 'vs2017-win2016'
+ variables:
+ rgv: v3.0.6
steps:
- template: .azure-pipelines/steps.yml
timeoutInMinutes: 0