Commit 0487463f authored by Peter Serwylo's avatar Peter Serwylo

Only deploy GP repo to

When deploying feature branches to, don't try to deploy the
entire repo of apps. This results in about 80MiB for each
language we translate the website into, and quickly goes above the
100MiB limit on

This still gets deployed to GitLab pages if you push to master, and it
also builds the entire repo during the test stage to make
sure there are no bugs with it.
parent ad4c3071
......@@ -74,9 +74,12 @@ build:
# Ideally we would use GitLab pages for this, but until they suupport deploying feature
# branches alongside master branches (
# this is the next best option.
# Note that although we are building the entire F-Droid repo in the `build` stage, this `preview`
# stage only builds the GP repo. This is because i18n versions of increase the size
# well beyond the 100MiB limit of
stage: deploy
image: node:wheezy
except: [ master ]
# This is allowed to fail because only those who have setup $SURGE_LOGIN and $SURGE_TOKEN
......@@ -84,7 +87,15 @@ preview:
allow_failure: true
- *setup_for_jekyll
- 'echo "url: https://$STAGING_URL" > userconfig.yml'
- 'echo baseurl: /$CI_PROJECT_NAME >> userconfig.yml'
- 'echo fdroid-repo: >> userconfig.yml'
- echo "Additional Jekyll config used for CI:" && cat userconfig.yml
- bundle exec jekyll build -d $OUT_DIR/$CI_PROJECT_NAME --config _config.yml,userconfig.yml --verbose --trace
- apt-get install -y npm
- npm install -g surge
- update-alternatives --install /usr/bin/node node /usr/bin/nodejs 10
- surge --project $OUT_DIR --domain $STAGING_URL
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment