Hi,
I checked the updated .setup-files. I am not sure if it is possible to "include" or "inherit" Oomph .setup-files, otherwise I see a risk of these files getting out of sync, since they currently share a big chunk of common settings that now needs to be kept in sync manually. But I guess it is doable to manually maintain the consistency...
But I still do no understand the purpose and expected stakeholder for the two different configuration in the developer .setup-file.
Now the "Nigtly build for testers" configuration installs the latest *release* of the core, profile and tooling parts, i.e. a "fixed" release and not any "nightly" builds of the tooling part. You actually *only* get the 24-hour nightly builds of the code-generator and run-time. Who is the intended user of this configuration? I guess it will be very misleading for anyone that actually expects to get the latest nightly (24 houirs) builds of the tooling as well (but the problem is that no such build configuration exist today).
It looks like we continue to have a rather confusing situation with different repos and different build frequencies of the core/profile/tooling parts vs. the code-generator/run-time parts. To reduce this confusion I have a strong feeling that we need to combine both the builds and the output repos from the different builds. Or if they should continue to be kept separate, then at least make it consistent and have a "24 hour" time-triggered build and a "20 minutes" git-poll-triggered build for *both* the core/profile/tooling part *and* the code-generator/run-time part.
/Peter Cigéhn
PS. Then I saw also that the version range that you had specified was written incorrectly using a "strict" version rage, i.e. [ ]. In this case you should use a "open" version range, i.e. [ ). In the main .setup-file the version range for base Papyrus should be [1.1.3, 1.1.4) with a ) and not ]. The same goes for the version ranges of base Papyrus in the developer .setup-file as well. Another minor thing was that you gave the 0.7.2 configuration the name "0.7.2" whereas the previous ones was named "070" and "071". The label can still be "0.7.2", but the name should not contain dots (.) otherwise they will be exchanged with _ anyway to avoid having dots (.) in directory names in the file system. DS.