Skip to content

no more Travis-CI for PR validation, use GitHub Actions [forward port]#10978

Merged
SethTisue merged 2 commits into
2.13.xfrom
no-travis-ci-for-pr-validation
Jan 7, 2025
Merged

no more Travis-CI for PR validation, use GitHub Actions [forward port]#10978
SethTisue merged 2 commits into
2.13.xfrom
no-travis-ci-for-pr-validation

Conversation

@SethTisue

@SethTisue SethTisue commented Jan 7, 2025

Copy link
Copy Markdown
Member

forward port of #10961:

  • do not build the spec during PR validation
  • no more Travis-CI for PR validation, use GitHub Actions

@SethTisue
do not build the spec during PR validation
d2ab49d 
doing so is overkill. it's fine to just build the spec nightly.
spurious failures are vastly more common than real failures in this.

(2.13 forward-port of e9075e1)
@SethTisue
no more Travis-CI for PR validation, use GitHub Actions
f748f82 
(2.13 forward-port of 9761bae)
@SethTisue SethTisue added the internal not resulting in user-visible changes (build changes, tests, internal cleanups) label Jan 7, 2025
@SethTisue SethTisue added this to the 2.13.16 milestone Jan 7, 2025
@SethTisue SethTisue self-assigned this Jan 7, 2025
@SethTisue SethTisue mentioned this pull request Jan 7, 2025
Closed
@SethTisue SethTisue marked this pull request as ready for review January 7, 2025 23:34
@SethTisue SethTisue merged commit 3f6bdae into 2.13.x Jan 7, 2025
@SethTisue SethTisue deleted the no-travis-ci-for-pr-validation branch January 7, 2025 23:34
@SethTisue SethTisue mentioned this pull request Jan 7, 2025
Merged
@SethTisue

SethTisue commented Jan 8, 2025 •
edited
Loading

Copy link
Copy Markdown
Member Author

verified that https://app.travis-ci.com/github/scala/scala/builds/273769168 wasn't affected by this and published 2.13.16-bin-3f6bdae as expected 👍

if anyone wants to compare an old and a new PR validation run,

in addition to the nice speedup per-job, we can also run more PR validations in parallel now (our free Travis-CI account only allowed one at a time)

@SethTisue

SethTisue commented Jan 11, 2025 •
edited
Loading

Copy link
Copy Markdown
Member Author

I seem not to have gotten the type logic right for the update_api and archives modes, at release time, to still work. I'll investigate

hey, at least the actual release publishing itself still worked, though

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

@SethTisue SethTisue

Labels

internal not resulting in user-visible changes (build changes, tests, internal cleanups)

Projects

None yet

Milestone

2.13.16

Development

Successfully merging this pull request may close these issues.

1 participant

@SethTisue