As a user of the ATT&CK Website, I want to be able to build the site with the dockerfile even if built-in tests produce non-breaking warnings.
Currently the attack-website build fails in the dockerfile because the website test warnings for internal links cause a non-zero exit code. Adding the --no-test-existstatus flag when the build script is executed in the dockerfile may fix this issue since it will suppress those status-codes when the tests produce a warning.
As a user of the ATT&CK Website, I want to be able to build the site with the dockerfile even if built-in tests produce non-breaking warnings.
Currently the attack-website build fails in the dockerfile because the website test warnings for internal links cause a non-zero exit code. Adding the
--no-test-existstatusflag when the build script is executed in the dockerfile may fix this issue since it will suppress those status-codes when the tests produce a warning.