Spike: A way to catch JS assets that are not hashed

Description

There are a number of approaches we might use, with various benefits and drawbacks:

  • We can find this via sitespeed, but it would be great to find it in PRs themselves

  • If we are OK to catch this post-release, we can do it via a splunk report/alert.

  • Another approach is to run collectstatic and then make sure that every .js file has a corresponding hashed version?

    • Perhaps overload some paver task that already collected static (e.g. bok-choy)?

    • Or maybe we need to keep this isolated and discreet

Steps to Reproduce

None

Current Behavior

None

Expected Behavior

None

Reason for Variance

None

Release Notes

None

User Impact Summary

None

Status

Assignee

Unassigned

Reporter

Ben Patterson

Labels

Reach

None

Impact

None

Customer

None

Partner Manager

None

URL

None

Contributor Name

None

Groups with Read-Only Access

None

Actual Points

None

Category of Work

None

Stakeholders

None

Story Points

3

Priority

Unset
Configure