Skip to content

ci: temporary work-around for Travis issue #21422

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 1 commit into from

Conversation

gkalpak
Copy link
Member

@gkalpak gkalpak commented Jan 9, 2018

@gkalpak gkalpak added state: WIP area: build & ci Related the build and CI infrastructure of the project target: patch This PR is targeted for the next patch release labels Jan 9, 2018
.travis.yml Outdated
@@ -1,5 +1,7 @@
language: node_js
sudo: false
# Work-around for https://github.com/travis-ci/travis-ci/issues/8836#issuecomment-356362524.
# (Restore `sude: false` once that is resolved.)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

sude -> sudo ?

@gkalpak gkalpak force-pushed the ci-workaround-sandbox branch from 2a81a88 to aa4638b Compare January 9, 2018 19:18
@gkalpak gkalpak added action: review The PR is still awaiting reviews from at least one requested reviewer and removed state: WIP labels Jan 9, 2018
Copy link
Contributor

@IgorMinar IgorMinar left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The problem with this change is that we'll not be able to use our pre-paid pool of VMs and instead the jobs will run on VMs belonging to the open source pool that is shared with all the projects on github. This in practice typically means that it might see XX minutes delays before our jobs start.

According to https://www.traviscistatus.com/ there is currently no backlog, so let's get this change in, but I don't think it's a good idea to keep this setting for too long. We should also monitor our job queueing delays more closely during this period.

@kara kara added action: merge The PR is ready for merge by the caretaker and removed action: review The PR is still awaiting reviews from at least one requested reviewer labels Jan 9, 2018
kara pushed a commit that referenced this pull request Jan 9, 2018
@kara kara closed this in 229b76c Jan 9, 2018
@gkalpak gkalpak deleted the ci-workaround-sandbox branch January 9, 2018 22:12
gkalpak added a commit to gkalpak/angular that referenced this pull request Jan 18, 2018
@gkalpak gkalpak mentioned this pull request Jan 18, 2018
3 tasks
gkalpak added a commit to gkalpak/angular that referenced this pull request Jan 18, 2018
gkalpak added a commit to gkalpak/angular that referenced this pull request Jan 19, 2018
gkalpak added a commit to gkalpak/angular that referenced this pull request Jan 19, 2018
gkalpak added a commit to gkalpak/angular that referenced this pull request Jan 19, 2018
gkalpak added a commit to gkalpak/angular that referenced this pull request Jan 19, 2018
mhevery pushed a commit that referenced this pull request Jan 19, 2018
mhevery pushed a commit to mhevery/angular that referenced this pull request Jan 25, 2018
gkalpak added a commit to petebacondarwin/angular that referenced this pull request Feb 11, 2018
gkalpak added a commit to petebacondarwin/angular that referenced this pull request Feb 11, 2018
gkalpak added a commit to petebacondarwin/angular that referenced this pull request Feb 11, 2018
jbogarthyde pushed a commit to jbogarthyde/angular that referenced this pull request Feb 23, 2018
leo6104 pushed a commit to leo6104/angular that referenced this pull request Mar 25, 2018
leo6104 pushed a commit to leo6104/angular that referenced this pull request Mar 25, 2018
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 13, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
action: merge The PR is ready for merge by the caretaker area: build & ci Related the build and CI infrastructure of the project cla: yes target: patch This PR is targeted for the next patch release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants