-
-
Notifications
You must be signed in to change notification settings - Fork 283
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
Migrate to GitHub actions #672
Changes from 4 commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,49 @@ | ||
name: Check | ||
|
||
on: | ||
pull_request: | ||
|
||
schedule: | ||
- cron: "0 4 * * *" # Nightly build (@daily) | ||
|
||
concurrency: | ||
# Only run once for latest commit per ref and cancel other (previous) runs. | ||
group: ci-${{ github.ref }} | ||
cancel-in-progress: true | ||
|
||
jobs: | ||
check-code-style: | ||
name: Code Style | ||
uses: playframework/.github/.github/workflows/sbt.yml@v1 | ||
with: | ||
cmd: sbt scalafmtCheckAll scalafmtSbtCheck | ||
|
||
check-binary-compatibility: | ||
name: Binary Compatibility | ||
uses: playframework/.github/.github/workflows/binary-check.yml@v1 | ||
|
||
check-docs: | ||
name: Docs | ||
uses: playframework/.github/.github/workflows/sbt.yml@v1 | ||
with: | ||
cmd: sbt docs/scalafmtCheckAll docs/scalafmtSbtCheck docs/test docs/validateDocs | ||
|
||
tests: | ||
name: Tests | ||
needs: # Waiting more lightweight checks | ||
- "check-code-style" | ||
- "check-binary-compatibility" | ||
- "check-docs" | ||
uses: playframework/.github/.github/workflows/sbt-matrix.yml@v1 | ||
with: | ||
java: >- | ||
[ "11", "8" ] | ||
scala: >- | ||
[ "2.12.15", "2.13.8" ] | ||
cmd: sbt ++$SCALA_VERSION test | ||
mkurz marked this conversation as resolved.
Show resolved
Hide resolved
|
||
|
||
finish: | ||
name: Finish | ||
needs: # Should be last | ||
- "tests" | ||
uses: playframework/.github/.github/workflows/rtm.yml@v1 | ||
BillyAutrey marked this conversation as resolved.
Show resolved
Hide resolved
|
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,15 @@ | ||
name: Publish | ||
|
||
on: | ||
push: | ||
tags: ["*"] # Releases | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. One more thing: We should also add |
||
|
||
jobs: | ||
publish-artifacts: | ||
name: Publish / Artifacts | ||
uses: playframework/.github/.github/workflows/publish.yml@v1 | ||
secrets: | ||
username: ${{ secrets.SONATYPE_USERNAME }} | ||
password: ${{ secrets.SONATYPE_PASSWORD }} | ||
pgp_passphrase: ${{ secrets.PGP_PASSPHRASE }} | ||
pgp_secret: ${{ secrets.PGP_SECRET }} | ||
BillyAutrey marked this conversation as resolved.
Show resolved
Hide resolved
|
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -2,8 +2,8 @@ | |
pull_request_rules: | ||
- name: Merge PRs that are ready | ||
conditions: | ||
- status-success=Travis CI - Pull Request | ||
- status-success=typesafe-cla-validator | ||
- check-success~=/ Ready To Merge$ | ||
- check-success=typesafe-cla-validator | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This is not the only thing that needs to be changed in the mergify conf. |
||
- "#approved-reviews-by>=1" | ||
- "#review-requested=0" | ||
- "#changes-requested-reviews-by=0" | ||
|
This file was deleted.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Except for the main play repo we never ran nightly builds. And there we ran them because we do enable additional jobs which take a while, so its better to no have them run for each pull request.
I suggest to remove the
schedule
section here and replace it withinstead (so the build will be triggered after merge again, so we should be pretty safe I guess)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Okay, makes sense. I was mainly concerned with placing the Travis badge, and wasn't sure which approach to take to get valid statuses from
main
.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You mean the GHA badge? I think it just looks at the last run and that's the status it shows.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah! Well that's easier then. Master runs would fix this, I'll change it.