MITLibraries / dspace-submission-service

95%

main: 98%

LAST BUILD ON BRANCH deployment-workflows

branch: deployment-workflows

CHANGE BRANCH

x

Reset

• deployment-workflows
• IN-1059-maintenance-08-2024
• IN-1253-pip-audit
• IN-1452-maintenance
• adr-for-full-automation-support
• downgrade_moto
• etd-398-submit-to-dspace
• etd-400-sqs-read-write
• etd-426-result-message-spec
• etd-436-smoke-tests
• etd-443-add-sentry
• etd-444-input-message-checks
• etd-445-confirm-result-message
• etd-458-498-update-specs
• etd-464-add-dspace-timeout-to-config
• etd-495-improve-dspace-error-messages
• etd424-run-model
• etd435-sqs-input-spec
• fixup_adrs
• jmc-test
• legacy
• main
• makefile-update
• makefile-update-build
• makefile-update-prod
• makefile-update2
• quick-test
• refactor_sqs
• sample_result_messages
• uv
• v1.0.0
• v1.0.1
• v1.2.0
• v1.2.1

Build # 5739016619

Build Type

push

github-actions

Committed by cabutlermit

Commit Message

Automation for AWS Organization

Why these changes are being introduced:
We need to deploy/publish automation and the Makefile additions as we
move this application into our AWS Organization.

How this addresses that need:
* Add the three GitHub Actions workflows for dev/stage/prod to
automate publishing the container on PR/Merge/Release
* Remove the stage_ecr_push.yml GitHub Action workflow that is
no longer needed

Side effects of this change:
After this is merged to main, the only way to manage the production
application running in Legacy AWS is to use the "legacy" branch.

Relevant ticket(s):
* https://mitlibraries.atlassian.net/browse/IN-573

Run Details

408 of 431 relevant lines covered (94.66%)

0.95 hits per line