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

Travis-CI/publishing: our publishing stuff doesn't work on dist: bionic but generating spec PDF requires it #764

Closed
SethTisue opened this issue Feb 22, 2021 · 5 comments · Fixed by scala/scala#9516
Assignees

Comments

@SethTisue
Copy link
Member

some gory details at #762

@SethTisue SethTisue self-assigned this Feb 22, 2021
@SethTisue SethTisue mentioned this issue Feb 22, 2021
69 tasks
@dwijnand
Copy link
Member

dwijnand commented Feb 22, 2021

Move the dist to the language spec (Jekyll) job, leaving the other jobs (e.g. publishing) to use the default. Now the default might've also changed since Dec 2020, but it might fix it for you.

@SethTisue
Copy link
Member Author

do you know for sure whether you're allowed to set dist: at the job level and not the build level?

@dwijnand
Copy link
Member

I'm fairly sure because this example seems to suggest it:

https://docs.travis-ci.com/user/multi-os/#example-multi-os-build-matrix

jobs:
  include:
    - os: linux
      dist: trusty
    - os: osx
      osx_image: xcode7.2

seeing as you can define a matrix of not even linux, makes sense that the linux distribution is matrixable.

@SethTisue
Copy link
Member Author

nice. okay, trying it here: scala/scala#9516

@SethTisue
Copy link
Member Author

This appears to be working. This seems satisfactory for now, actually. Xenial will likely remain available for a while yet to come on Travis-CI. If they ever drop it, or if we move to GitHub Actions, we might need to figure out something else, but it seems like a bridge we can cross when we come to it.

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 a pull request may close this issue.

2 participants