Skip to content
GitLab
    • GitLab: the DevOps platform
    • Explore GitLab
    • Install GitLab
    • How GitLab compares
    • Get started
    • GitLab docs
    • GitLab Learn
  • Pricing
  • Talk to an expert
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    • Switch to GitLab Next
    Projects Groups Topics Snippets
  • Register
  • Sign in
  • T testing
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Insights
    • Issue
  • External wiki
    • External wiki
  • Snippets
    • Snippets
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • cip-projectcip-project
  • cip-testing
  • testing
  • Issues
  • #167
Closed
Open
Issue created Nov 03, 2017 by Tom Pollard@tpollardDeveloper

Build & test iw20gm kernel outside of cip-core/bitbake env

Issue Background

Currently iw20gm (Renesas rz/g1m) testing with b@d has required output (uimage, dtb & cpio minimal image) from cip-core https://gitlab.com/cip-project/cip-core. cip-core uses KAS (build configuration wrapped around bitbake) to produce the cip kernel & minimal image based off meta-debian deby(poky).

Issue description

As it stands b@d is about testing the kernel, b@d should use kernel-ci to provision the kernel without the overhead of bitbake/docker. Taking the config for the kernel from cip-core & applying it as is to kernel-ci build.py should be tested. After that the issue of the minimal image / ramfs can be discussed

Acceptance criteria

kernel generated via kernel-ci to produce the same test outcome as of that achieved by existing cip-core testing

Edited Nov 03, 2017 by Tom Pollard
Assignee
Assign to
Time tracking