Automated Build Generator

h1. 23022017

{{>TOC}}

h2. Next Steps

# Integrate Robert's template changes
# User meeting
#* Collecting use-case
#* What should the individual modes do (e.g. is "ci-deploy" intended as "fast installation" or "continuous integration with installation"?)
#* How adaptable should modes be without requiring the creation of new modes?
# Turn the following feature ideas into a concrete roadmap in a separate meeting after 20.03.2017

h2. Feature List

h3. Template Hierarchies

h3. Mode-specific Templates Refactoring

* Remove Symlinks

h3. Catkin Templates for ROS Workspaces

h3. YAML Syntax

* Multi-line strings -> recipes will be valid YAML -> recipe authors can use validating editors
* No escaping in literal strings
* Comments
* Less "Comma-Problems"

h3. Deployment / Platform Recipes

* Specify slaves
* Job configuration details (e.g. with or without unit tests)
* OS, CPU, Flags, ...

h3. Platform Dependency Analysis

* Provide downloadable pre-computed descriptions for common platforms

h3. Docker Slaves for Clean Build

h3. Thorough CMake Analysis

h3. Revised Architecture

* Distribution/project Meta-model
** Hierarchical Distributions
** Template Versions of Projects
** Parametrised Project Inclusions
* Dependencies
** Richer version expressions with logical connectives and relation operators
** Phase-aware dependencies

h3. Credentials Store

h3. Further Provisioning of Analysis Results in Templates

h3. Avoid Repetitive Warnings for Missing Dependencies

Group warnings by missing things, not by projects depending on the thing

h3. 3rd Party Generator Modules

* Written in other languages
* Maybe include interpreters for e.g. Python, Javascript in the generator?

h3. GitHub Migration

* Probably good idea for project and distribution recipes; how about templates?
* Templates as Part of Build Generator?

h3. User Documentation

* In general
* Templates should allow documenting their interface