Skip to content
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

Change travis setup to only deploy once #789

Merged
merged 1 commit into from
Jul 25, 2018

Conversation

betatim
Copy link
Member

@betatim betatim commented Jul 25, 2018

Follow up #762

Since adding a build matrix testing several kubernetes versions we are
deploying twice, once for each kube version. This changes our deploy
setup so it only deploys once.

SInce adding a build matrix testing several kubernetes versions we are
deploying twice, once for each kube version. This changes our deploy
setup so it only deploys once.
@consideRatio
Copy link
Member

@betatim Thank you sorry for causing some headache!

From this travis documentation it seems like we could solve this if we do...

deploy:
  provider: script
  skip_cleanup: true
  script: ./ci/deploy.sh
  on:
    branch:
      - master
      - v0.7-dev
    condition: "$KUBE_VERSION = 1.9.4"

@consideRatio
Copy link
Member

Yikes... Perhaps I can blame the jetlag I'm having, I thought you simply reduced the env-matrix to one version but you are attempting to do the same thing i suggested but in a much nicer way.

Let's try it!

@consideRatio consideRatio merged commit c453dad into jupyterhub:master Jul 25, 2018
@consideRatio
Copy link
Member

consideRatio commented Jul 25, 2018

@betatim from https://travis-ci.org/jupyterhub/zero-to-jupyterhub-k8s/builds/407953966 it seems that deploy.sh still is run for both 1.10 or 1.9.4.

Attempting the solution from the travis documentation.

@betatim betatim deleted the deploy-job branch July 25, 2018 11:20
@manics manics mentioned this pull request Aug 15, 2018
7 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants