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 gh actions #1591
migrate to gh actions #1591
Conversation
bec4501
to
b2041da
Compare
d8111dc
to
9f9def6
Compare
9f9def6
to
79a2da9
Compare
Thanks so much! Maybe you have the credential of it that we can use for ci release? |
I've added these repository secrets (using the 'scanamo' sonatype user, and this PGP key. I'll merge now and try to perform a release... |
I tagged the latest commit (c84bf78) as v1.0.0-M21, and I can see that a release step occurred, it's still running... https://github.com/scanamo/scanamo/actions/runs/3339137076/jobs/5527814974 |
Thanks so much Tyley! I got a M22 release. |
@rtyley Thank you! |
@rtyley Do you have right to generate credentials for https://s01.oss.sonatype.org ? I think creds for s01.oss.sonatype.org is needed to publish snapshot artifacts. rel |
I think we can disable snapshot publish for now ( we don't have frequent bug fixes or features, and it's very easy to release a new milestone) if s01.oss.sonatype.org is too much |
I agree! Disabled in #1594. |
prepare for #1465 ,#1577
This PR migrates ci from Travis to GitHub Actions.
I found current ci does not publish docsite, so I keep it as is.
I guess it takes much to find out how docsite is published currently and incorporate into ci workflow. Therefore, I put publishing docsite aside for now.
Workflow runs format check, lint and tests against Scala version 2.15.16 and 2.13.8.
To enable auto release, please set the environment variables bellow from settings page
After setting secrets, GitHub Actions will publish pre-release artifact on every PR(after lint and test) and release artifact on tag.
If you have trouble, see https://github.com/sbt/sbt-ci-release