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

[Feature Request] Build system: trigger a build on pull request #225

Open
shun2wang opened this issue Dec 13, 2024 · 2 comments
Open

[Feature Request] Build system: trigger a build on pull request #225

shun2wang opened this issue Dec 13, 2024 · 2 comments
Labels
maintain Maintain problems about server and packages

Comments

@shun2wang
Copy link
Contributor

In some cases, we can quickly trigger some builds by issuing PRs and commits without waiting to be merged into the main branch. The advantage of this is that build errors can be excluded during the PR stage. A feasible solution is to set up a GitHub workflow and associate it with the build server to wait for the build server to return the status, so as to feedback to the developer.

I have no experience with building on Arch, so forgive my ignorance here. I have some experience setting up Github workflows, so if there is some guidance I might know how to do it.

@starsareintherose
Copy link
Member

@lilydjwg could we build a CI using lilac for github action?

Actually you can also access our server to try to build on our server. If you pm me the ssh key

@lilydjwg
Copy link
Contributor

This issue is that the build environment isn't fully contained---Due to the way devtools is implemented, privilege escalation could be done. And if that's too hard for script kids, resource exhaustion would be no problem.

However, you can use triggerabuild to manually trigger a lilac build for select people (i.e. people in a github organization). The code needs to be on master though.

@starsareintherose starsareintherose added the maintain Maintain problems about server and packages label Dec 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
maintain Maintain problems about server and packages
Projects
None yet
Development

No branches or pull requests

3 participants