Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • lava lava
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 94
    • Issues 94
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 45
    • Merge requests 45
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • lava
  • lavalava
  • Issues
  • #552

Closed
Open
Created Jun 30, 2022 by Larry Shen@atlineContributor

About skip some validate failure.

We have next scenario:

deploy:
  - dtb1

boot:
  - with dtb1

test:
  - test with dtb1

deploy:
  - dtb2

boot:
  - with dtb2

test:
  - test with dtb2

For yocto build issue, some artifacts can't be built out sometimes. E.g. in above example, dtb1 failed to build, while dtb2 ok.

But when validate, the whole job fail due to miss of dtb1.

If possible we could ignore the lack of dtb1, let lava still continue to execute deploy, boot, test with dtb2? A fine granular control to exit the job?

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking