llvm / llvm-iwg

The LLVM Infrastructure Working Group

https://foundation.llvm.org/docs/infrastructure-wg/

Other

18 stars 14 forks source link

Provide a worker for a dylib LLVM build #59

Open tbaederr opened 3 years ago

tbaederr commented 3 years ago

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 commented 3 years ago

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 commented 3 years ago

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

ChristianKuehnel commented 3 years ago

@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.