Read about our upcoming Code of Conduct on this issue

This instance will be upgraded to Heptapod 0.28.1 on 2022-01-26 at 16:00 UTC+1 (a few minutes of down time)

Commit 4aa88502 authored by Georges Racinet's avatar Georges Racinet 🦑
Browse files

heptapod-ci: providing frontend assets

Closes #318.

Some tests will trigger templating that doesn't like assets
to be missing. This is what happens with pipeline tests because
of the content of email notifications are produced.

We'll readd the pipeline tests separately

--HG--
branch : heptapod
parent 162692d88547
......@@ -23,6 +23,10 @@
- vendor/ruby/
- vendor/gitaly-ruby/
- .go/pkg/mod/
# Heptapod specific: frontend assets don't change much within
# a given upstream version
- public/assets
- node_modules
policy: pull
.static-analysis-cache:
......
......@@ -49,6 +49,15 @@ rspec:
script:
- rm -rf tmp/tests/gitaly # stale files from previous builds can prevent proper installation
- run_timed_command "bundle exec ruby -I. -e 'require \"config/environment\"; TestEnv.init'"
# copied from compile-assets-base. The day we want several jobs, this
# will be one prime candidate to do like upstream and just produce an
# artifact instead
- node --version
- run_timed_command "retry yarn install --frozen-lockfile"
- free -m
- run_timed_command "bin/rake gitlab:assets:compile > assets-compile.log 2>&1"
- run_timed_command "scripts/clean-old-cached-assets"
# end of assets production
- run_timed_command "python3 scripts/prepare_build_py_heptapod.py"
- ls -al tmp/tests/*
- run_timed_command "scripts/gitaly-test-build" # Do not use 'bundle exec' here
......
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