Linking executables/results to multiple codebases

[Tim Besard]

Hi all,

I'm in the process of setting-up a Codespeed instance, but I'm running into an issue due to how we've split up code into different codebases. The problem is that executables are built from multiple repositories, and consequently results should be linked to each of these repositories.

Currently, I'm only submitting the commitid of one of these repositories, but this causes a loss of information. For example, having executable foo built from repositories A and B. If I only submit the commitid of repository A, results for changes in B overwrite previous results.

Is there any way of configuring Codespeed to handle this? Or should I tackle this at the source, i.e. create some merged repository containing all code?

Best,
Tim

[Miquel Torres]

Hi Tim,

that is quite a coplex dependency situation. Are really both repos
changing frequently? If at least one of the repos was the main one,
and the other could be treated as a dependency, you could create
variations of executables.

If both repos are integral to building the executable and you want to
track changes in both, I really can't think of anything better than a
combined repository.

Cheers,
Miquel

> --
> You received this message because you are subscribed to the Google Groups
> "codespeed" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to codespeed+...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.