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

lab-cip #361

Open
Tracked by #351
padovan opened this issue May 15, 2024 · 5 comments
Open
Tracked by #351

lab-cip #361

padovan opened this issue May 15, 2024 · 5 comments
Assignees

Comments

@padovan
Copy link
Contributor

padovan commented May 15, 2024

Execute the work to enable the the CIP lab in the new system.

@padovan
Copy link
Contributor Author

padovan commented May 15, 2024

@patersonc is your lab a LAVA lab? If yes, we will just follow the same process as the other labs.

@patersonc
Copy link
Collaborator

@patersonc is your lab a LAVA lab? If yes, we will just follow the same process as the other labs.

Yep. Let me know if there's anything I need to do my end.

@JenySadadia
Copy link
Contributor

Hello @patersonc,
To enable CIP lab in KernelCI, we would need a lab token and its description.
Please have a look at https://github.com/kernelci/kernelci-pipeline/blob/main/doc/connecting-lab.md#token-setup.
Could you please create one for KernelCI?
You can send me the details on IRC. My IRC nickname is "jenysadadia".
Thanks.

@padovan
Copy link
Contributor Author

padovan commented Jul 5, 2024

@patersonc can we close this already?

@patersonc
Copy link
Collaborator

Yea I guess so - although it doesn't look like many jobs are coming our way these days. But then I haven't done anything about re-adding any using the new approach yet...

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

4 participants