Open yanosz opened 5 years ago
I think it would be helpful to standardize the builds on a gluon-project level instead of community level. Another idea was to specify a Jenkinsfile and have the parameters in place to customize.
For the make dist approach - how would parameters be stored?
In general, there are no paremeters to be saved. Everything can be provided using the environment (i.e. exports or variables when calling make).
Thinking about a re-usable jenkins file I'm still struggeling with the steps (i.e. pipeline) in there. What's the common denominator for building gluon? Is convention over configuration a way to go? What's the convention, then? What has to be configured, though?
Ok, thinking about this for a while, I think, that theses features are missing in Gluons Makefile
If make dist
boils down to that, a jenkins job should be easy.
Hello,
is:
make world
with some parametersmake world
only onceAs an effect, different communities are creating different, elaborate build configurations.
Should:
./dist
including the full tree of all images and packages