On Thu, Dec 4, 2014 at 2:36 PM, Alec Ten Harmsel <a...@alectenharmsel.com> wrote: > > It'd be cool if Gentoo had some sort of automated workflow (with > Jenkins, buildbot, whatever) like this: > > 1. Receive pull request > 2. Detect changed ebuild > 3. test ebuild with etest > > This will take a lot of work to set up, and depending on how my workload > is next semester, I would love to help out as much as possible. >
I've wondered the same thing, and maybe after sufficient bikeshedding something like this would be a good GSoC project as well. Running repoman is another possibility. One trick is that a pull request could impact multiple packages (eclass changes, dependency updates, etc). In these cases running repoman probably adds more value than full tests. Either way there will potentially be a high cost to do the testing, which could create a backlog if we queue things up (not queuing things creates other problems). Repoman false-alarms is another potential issue with this. So, it may not be a trivial thing to do, but some kind of CI workflow would be a wonderful thing to have. -- Rich
