Open brooke-hamilton opened 1 month ago
:wave: @brooke-hamilton Thanks for filing this issue.
A project maintainer will review this issue and get back to you soon.
We also welcome community contributions! If you would like to pick this item up sooner and submit a pull request, please visit our contribution guidelines and assign this to yourself by commenting "/assign" on this issue.
For more information on our triage process please visit our triage overview
:+1: We've reviewed this issue and have agreed to add it to our backlog. Please subscribe to this issue for notifications, we'll provide updates when we pick it up.
We also welcome community contributions! If you would like to pick this item up sooner and submit a pull request, please visit our contribution guidelines and assign this to yourself by commenting "/assign" on this issue.
For more information on our triage process please visit our triage overview
Area for Improvement
The dev container is our standardized engineering environment. It is subject to dependabot upgrades, changes to platform dependencies, and configuration changes due to evolving software development needs. We therefore need an automated PR validation build and a weekly scheduled build to ensure that the container continues to function as expected.
Observed behavior
Currently, the dev container is tested manually by running a local dev container build.
Desired behavior
We need a dev container build workflow that validates that the dev container can be built and that it functions as expected.
Proposed Fix
The dev container build should do the following using the
devcontainer
CLI:MAKE
command within the container, e.g.make build lint
to act as a validation test.rad Version
N/A
Operating system
No response
Additional context
No response
Would you like to support us?
AB#13503