Skip to content

Conversation

@jhutchison-nava
Copy link

@jhutchison-nava jhutchison-nava commented Nov 10, 2025

JIRA Ticket:
BB2-4099

What Does This PR Do?

Update pre-prod deploy script to pull in and deploy uswds-redesign so we can see the redesign on staging

What Should Reviewers Watch For?

  • uswds-redesign branch is cheked out correctly
  • Updated build step and build output
  • Pulling in CSS repo is no longer needed

Validation

Successful deploy https://ci.backends.cms.gov/non-oc/job/Blue%20Button/job/DEPLOY%20-%20Static%20Site%20(Akamai)/view/change-requests/job/PR-425/

What Security Implications Does This PR Have?

Please indicate if this PR does any of the following:

  • Adds any new software dependencies
  • Modifies any security controls
  • Adds new transmission or storage of data
  • Any other changes that could possibly affect security?
  • Yes, one or more of the above security implications apply. This PR must not be merged without the ISSO or team security engineer's approval.

@jhutchison-nava jhutchison-nava marked this pull request as ready for review November 13, 2025 15:07
@jimmyfagan jimmyfagan self-assigned this Nov 13, 2025
rsync -av -e "ssh -oHostKeyAlgorithms=+ssh-dss -oStrictHostKeyChecking=no -i ${AKAMAI_SCP_SSH_KEY}" ./dist/static-main.css ${AKAMAI_SSH_USER}@bluebuttoncms.rsync.upload.akamai.com:${UPLOAD_LOCATION}assets/css/
rsync -av -e "ssh -oHostKeyAlgorithms=+ssh-dss -oStrictHostKeyChecking=no -i ${AKAMAI_SCP_SSH_KEY}" ./dist/ ${AKAMAI_SSH_USER}@bluebuttoncms.rsync.upload.akamai.com:${UPLOAD_LOCATION} --delete
"""
}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks like we lose the ability to deploy CSS here, is that expected/impactful? Other than that, everything looks good, just want to make sure I understand the impact of taking CSS stuff out here.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Unless there is another external resource consuming that CSS, it shouldn't be an issue. The site bundles all the static assets it needs inside ./dist/, so there's no need to manually include anything else

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks like this is meant for pulling in CSS from the CSS repo: https://github.com/CMSgov/bluebutton-site-static/pull/425/files/0e8322630371fe95380c72760e62110eaf58e705#diff-67342a76a94d7dd761a7996be3137839eb4f22c3915b904c942ed61bfac63f61L88-L96

We don't reference that CSS in the new site, so fine to drop this step

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Tagged in @clewellyn-nava to hopefully assess whether or not the server depends on this CSS deploy step, but I believe most of what we look for from the server side is in s3 and not in netstorage, so this should be okay, and if anything, we should have this as part of the server deployment, not tied to this new static site deploy. I'll go ahead and approve, we can always revert or make a new pipeline for that piece if needed later.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants