Skip to content

add PR validation to https://github.com/scala/community-builds #92

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

Closed
adriaanm opened this issue Jul 1, 2015 · 5 comments
Closed

Comments

@adriaanm
Copy link
Contributor

adriaanm commented Jul 1, 2015

We should run the community build (on the last commit only) of PRs submitted. Should be a matter of adding a scabot.conf section.

@SethTisue
Copy link
Member

perhaps this should be triggered by an explicit command, rather than automatically on every PR.

@SethTisue
Copy link
Member

closely related: #8

@SethTisue SethTisue removed their assignment Sep 2, 2015
@SethTisue SethTisue self-assigned this Sep 28, 2016
@SethTisue
Copy link
Member

I'm more and more tempted to tackle this

@adriaanm
Copy link
Contributor Author

We could use the integrate-main flow for this. It can be configured to do a minimal bootstrap using jenkins params and then trigger a community build. I guess we could also just use a fixed Scala version since we're validating the community build here, not the compiler.

@SethTisue
Copy link
Member

not worth doing on Jenkins. if we move the community build to GitHub Actions, I could maybe get interested again. but as long as the community build is basically a one man show, some kind of automation just aren't worth the trouble

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

No branches or pull requests

2 participants