redhatinsights/insights-frontend-builder-common

Common stuff for the frontend builder

Frontend Builder Common

The repo responsible for building all of the frontends on cloud.redhat.com.

Akamai Cache Buster

This script is run automatically from Jenkins each time a frontend is deployed to Prod. It clears out all of the old cached versions of the application to make sure users are served up-to-date content.

To Run

python bustCache.py /path/to/your/.edgerc appName

Some Notes and Requirements

• Your edgerc needs read/write permission for the eccu API on akamai (not open CCU)
• The script only works on production akamai (no way to clear the cache on staging)
• Requests take about 30 minutes to finish
• Will not work on apps that don't have paths listed in the source of truth

insights-frontend-builder-common's Issues

Let users define their own release section

Lines 23 - end after_success.sh can be written to not assume what branch maps to what.
We can write a light pluggable system of sorts to let users override the default behavior

Irrelevant user references merged PRs?

Please check RedHatInsights/vulnerability-ui#68 or any other merged PR. I'm afraid that 'Kinlaw pushed a commit to ...' is no longer correct behavior as Josh does not work here anymore?

Remove useless clone

I think this line does nothing: https://github.com/RedHatInsights/insights-frontend-builder-common/blob/master/src/release.sh#L8

It clones the build repo, and then we cd dist and immediately git init a new git tree and force push to the build repo.

Sooo I am pretty sure it just does an unnecessary clone. That seem right to you Josh?

deployment scripts blow away history of the target branch

The reason this happens is because it does a git init in the directory, then an initial commit, then a force push into the target branch. Since the commit was not built on previous history, everything in history is lost.

cc @iphands

Use DEPLOY_REPO instead of REPO in the release.sh

Support both for some time, but REPO is confusing.