Deploy 'nightly' versions of ESCET
Without nightlies, we get the following issues:
- We can't see the current development website. See #474 (closed).
- We don't have a deployed update site for the current
develop
branch until the next milestone, release candidate, or final release. If people require a bug fix, they either have to wait a long time, or we have to continuously push out extra milestone releases, or they have to build ESCET themselves.
If we release nightly releases of ESCET, these issues are solved. That is:
- We choose option 1 for #474 (closed).
- We have a nightly update site that people can (temporarily) depend on.
My idea is to simply deploy develop
on every build of the develop
branch:
-
develop
gets built only when a merge request is merged. - We build
develop
already, and just need to enable signing and deployment. This requires not that much extra build time. - This is easier than building once a night, as then we need to check whether there are any changes, to prevent having to do a full build and deploy again. Deploying an unchanged version again, may lead to subtle changes in file dates/times in certain built artifacts, etc, and should thus be avoided in case update sites are proxied and cached by others.
- We currently have 658 merged merge requests, merged since the last 3 years and 3 days (about 1098 days). That is about 658 / 1098 = 0.6 merge requests a day being merged. Hence, we'll likely reduce build effort if we deploy for every build of
develop
, rather than once a day.
Proposed URLs:
- Nightly website:
https://eclipse.dev/escet/nightly
. - Nightly update site:
https://download.eclipse.org/escet/nightly
.