Deploying and compiling code

[mpiraux]

There is currently no way to instruct mpf how to deploy and compile the code we would like it to evaluate. I'm not sure how this should be abstracted. This probably requires to:

• Obtain the source code, either from a git repo or through rsync/scp. I tend to use the latter the most.
• Install dependencies to build the code. This depends on the Linux distribution. I feel that if we allow to install Debian/Ubuntu packages and Fedora/RHEL packages, we cover all current use cases.
• Build the code, which can require very different step (autoconf, cmake, ninja, etc..). So an open-format, e.g., bash commands would be quickly required
• Install the code somewhere practical for mpf, if needed

What is not needed for me at this stage:

• Figure out whether changes occured and this process should be triggered again. When using rsync and make, they can figure it out quite quickly
• Compile once and deploy everywhere. To me parallel compilation is the simplest way to go, at the cost of having to deploy the code everywhere its needed. I don't have a strong use case for that but you're mileage may vary.

[nrybowski]

This feature is provided by DUNE. It requires that users provide one or multiple Containerfiles defining the building environments. It is then able to produce the artifacts for each targeted platform.
Either the artifacts are directly loaded on phynodes by DUNE or MPF could scp the required binaries.