That is indeed a valid concern.
The default behaviour would probably be either the “run on the oldest version” or “run on the latest version”.
I’m unable to tell what the default behaviour should be. I’m unsure what best practices for this setting are. Personally I prefer to run on the latest version but I perfectly understand those who would prefer the oldest version. Someone else would have to chime in on this.
Whatever the default behaviour may be you should be able to override this setting in the
circle.yml file if you don’t agree with the default setting.
Regarding running on all versions from
I think CircleCi would have to impose some sort of restrictions in order to avoid having jobs that over time would take forever to run (just imagine today if you for some reason specify
I doubt free users would ever have access to a “run on all versions in the range”. It could be a thing for paying customers, Free users could be offered something like:
- Run on the oldest version specified
- Run on the latest version specified/available
- Run on the calculated median version
I.e. let’s say you’ve specified something like
>=0.9 and today the latest version is
4.2 (disregarding build versions for ease of example), the median would be version
I don’t know if that would make sense for anyone to use.