From Fedora Project Wiki
Questions
- Is the long term plan to make the compose in Jenkins or here as well is it a temporary approach? --Pingou (talk) 14:39, 25 April 2017 (UTC)
- Is there plans on re-using the exact same tools for these steps as in prod? (pungi?) --Pingou ([[User
talk:Pingou|talk]]) 14:39, 25 April 2017 (UTC)
- A: One of the goals of this effort is to be able to learn from it and modify/replace parts that don't work. Implementation details like this should not be set in stone. But we also don't need to have a plan for replacing each component before we know how they fulfill their use case. This also means that inter-component communication/interface mechanisms should be general enough to iterate on the implementation behind them. --Stefw (talk) 09:37, 26 April 2017 (UTC)
- How will we map dist-git changes to bodhi updates? --Pingou (talk) 14:39, 25 April 2017 (UTC)
- How is the packager going to choose which test/test-suite gate the package? By turning them on/off or would there be a way to flag a test as: "allowed to fail"? --Pingou (talk) 14:39, 25 April 2017 (UTC)
- Stage 2 says: Build result on the fedmsg bus will be plumbed through to bodhi via resultsDB, but there potentially no bodhi update to report to here since not all dist-git commits are followed by a build and not all build are submitted to be updates. --Pingou (talk) 07:03, 26 April 2017 (UTC)