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

Provide a worker for a dylib LLVM build #59

Open
tbaederr opened this issue Jul 30, 2021 · 3 comments
Open

Provide a worker for a dylib LLVM build #59

tbaederr opened this issue Jul 30, 2021 · 3 comments

Comments

@tbaederr
Copy link

Hi,

we would like to add a new builder to https://github.com/llvm/llvm-zorg/blob/main/buildbot/osuosl/master/config/builders.py to test building the libLLVM.so. This should be public and outside of Red Hat's control. As far as I understand, I would have to add a worker to the workers.py as well, which will then get picked up by actual hardware. Can the IWG help here?

Thanks

@ChristianKuehnel
Copy link
Collaborator

Hi @tbaederr ,

what do you mean with "public and outside of Red Hat's control"?
I added some of the machines configs (as Docker imagesI here: https://github.com/llvm/llvm-zorg/tree/main/buildbot/google/docker

The general steps are explained in https://llvm.org/docs/HowToAddABuilder.html

Best,
Christian

@tstellar
Copy link
Collaborator

tstellar commented Aug 2, 2021

@ChristianKuehnel This is a request for something like in #32 , but for use with buildbot.

@ChristianKuehnel
Copy link
Collaborator

@tstellar thx for the context.

#32 was a one-off decision. So far we don't really have a policy of providing hardware for buildbots or running these.

Personal opinion: I do think it would be great if we had a contractor (paid for by the LLVM foundation) who would setup and maintain an agreed set of machines/configurations. This would allow us to consolidate the machines, remove redundancy and reuse scripts/tools across all these configs. However we're not there yet. This would require a change in the policy, a contractor and an agreement on the funding.

My proposal: Let's revisit this topic once we have the Admin #27 on board.

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

No branches or pull requests

3 participants