Opened 5 years ago

Last modified 3 years ago

#2945 assigned enhancement

Add an example of using codebases

Reported by: sa2ajj Owned by: Ben
Priority: patches-accepted Milestone: 0.9.+
Version: master Keywords: docs


While the notion is introduced and all relevant options are documented, it seems to be a good idea to add a separate example where codebases are used.

Change History (6)

comment:1 Changed 5 years ago by Ben

I could help there. Just need an example where it makes sense to use codebases: i.e. It is necessary to checkout multiple repository in order to run a command that need the outcome of each of them.

comment:2 Changed 5 years ago by Ben

  • Owner set to Ben
  • Status changed from new to assigned

It's been suggested on IRC to add a picture about the conversion from changes to sourcestamps to buildset in the introduction chapter. I'll give it a shot.

comment:3 Changed 5 years ago by sa2ajj

Based on the IRC discussion, a couple of different codebase mappings need to be shown and how they are handled by different schedulers should be explained.

comment:4 Changed 5 years ago by sa2ajj

Things to cover:

  • codebase generator
  • scheduler configuration
  • change filter
  • use of codebase in build steps

Ben, an example where it makes sense is a two repo setup (e.g. lib + app) where we want to build both regardless of whether the change is coming to the lib repo or to the app repo. And in this scenario we'd like to build the revision for the change + master/stable of the other repo.

comment:5 Changed 5 years ago by sa2ajj

One seemingly common use case: checkout two branches (of the same or different repositories) -- one according to the change, one according to the configuration. With the "default" configuration, both are checked out with the revision in the change, which causes errors.

Note: See TracTickets for help on using tickets.