Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • nightlies nightlies
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 1
    • Issues 1
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • bob
  • nightliesnightlies
  • Issues
  • #62

Closed
Open
Created Apr 29, 2022 by Tiago de Freitas Pereira@tiago.pereiraOwner

Nightlies on stages

Hi,

I think would be better to split this nightly builds in stages where in each stage we have a set of key packages.

For instance, in the first stage we could have the core packages.

  • bob/bob.extension
  • bob/bob.io.base
  • bob/bob.measure
  • bob/bob.learn.em
  • bob/bob.pipelines So, if one of these five packages (only five :-) ) fails we need to act immediately.

In the second, third or N-th stage we could pack a set of packages to be nightly executed. For instance, we could have a nightly for biometrics with the packages:

  • bob/bob.bio.base
  • bob/bob.bio.face
  • bob/bob.bio.video
  • bob/bob.bio.vein
  • bob/bob.bio.spear
  • bob/bob.pad.base
  • bob/bob.pad.face

If one of these packages fails, we don't need to act urgently.

what do you think?

PS: this was @andre.anjos idea

Assignee
Assign to
Time tracking