Coder Social home page Coder Social logo

Comments (4)

gctucker avatar gctucker commented on July 26, 2024

I'm actually making a fix for that, as we've seen other issues with / characters. But if it's easy for you to rename the branch then yes please, it would seem a safe thing to do.

There are a couple of things we need to know regarding the extra workload this would add to the builders. I would like to make a Github issue template for other people who want to add a branch, so here's a draft:

  • How much build coverage do you need for your branch?

Generally speaking, it's a good rule to build fewer variants for branches that are further away from mainline and closer to individual developers to scale better and be able to add more branches. This can be fine-tuned with arbitrary filters, but essentially there are 3 main options:

  1. build everything, including allmodconfig, which amounts to about 220 builds, like we do with linux-next
  2. skip a few things such as allmodconfig as it's very long to build and can't be booted, and also architectures that are less useful such as MIPS which saves 80 builds and doesn't have much test platforms in KernelCI, like we do with the media subsystem tree
  3. build only the main defconfig for each architecture to save a lot of build power, get the fastest results and highest boots/builds ratio like we do with the gpio substem tree
  • How often do you expect this branch to be updated?

KernelCI monitors each branch once every hour and builds it every time it finds a new revision. If you push once a week or less, it's easier to allow for many build variants as this reduces the build load on average. Conversely, if you push several times every day then a small set of builds should be used.

It's also possible to increase the build capacity if needed but this comes with a cost. Avoiding unnecessary builds is always a good way to reduce turnaround time and not waste resources.

from kernelci-core.

dlezcano avatar dlezcano commented on July 26, 2024

How much build coverage do you need for your branch?
-> Option 3
How often do you expect this branch to be updated?
-> Should be updated several times per week

from kernelci-core.

gctucker avatar gctucker commented on July 26, 2024

Thanks, see PR #204.

from kernelci-core.

gctucker avatar gctucker commented on July 26, 2024

PR merged, it's all working as expected.

from kernelci-core.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.