Skip to content

lab-cip #361

Closed
Closed

Description

@padovan

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

Activity

  1. padovan commented on May 15, 2024

    @padovan
    Author

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

  2. patersonc commented on May 16, 2024

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

  3. JenySadadia commented on May 22, 2024

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

  4. padovan commented on Jul 5, 2024

    @padovan
    Author

    @patersonc can we close this already?

  5. patersonc commented on Jul 8, 2024

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

  6. nuclearcat commented on Aug 31, 2026

    @nuclearcat
    Member

    Closing as completed. CIP lab support was merged in kernelci-pipeline PR #618, lava-cip remains in the current production configuration, and the lab owner agreed in this thread that this issue could be closed. Any desired increase in job coverage can be tracked separately from lab enablement.

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

Metadata

Metadata

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions