-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(workflows): remove dupe, update workflows for bulding main, workflow_dispatch, repo_dispatch 🥟 #56
Conversation
Update GitHub workflows to incorporate repository dispatch and workflow dispatch for service builds. Refactor packer job configuration for both - changes trigger and specific service build. Add service and version as configurable dispatch inputs.
6e1effe
to
ae5adb0
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great to me! Thank you for getting our build process ironed out!
- uses: actions/checkout@v4 | ||
|
||
- name: Set up Packer | ||
uses: hashicorp/setup-packer@1aa358be5cf73883762b302a3a03abd66e75b232 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Random question...(non-blocking, no action required)...is there a reason why we're using the hash value for this instead of a version? I noticed this pop up, and I wasn't sure if it was intentional or a new best practice that I missed.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The practice of using the commit hash does seem to be preferred these days. This was changed because of this alert: https://github.com/CDCgov/dibbs-vm/security/code-scanning/7
We may want to decide how to approach this as a team, but I have started pinning with a commit hashes.
.github/workflows/packMachines.yml
Outdated
# Needed for ISO builder | ||
- name: Set up QEMU | ||
uses: docker/setup-qemu-action@4574d27a4764455b42196d70a065bc6853246a25 | ||
# - name: Set up QEMU |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry for all the trouble on this...I should have tested before I threw this in as a framework. 😭
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No worries!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me... Great work Alis
ae5adb0
to
ffc0541
Compare
Changes Proposed
docker-setup-qemu
action to work in this context, if anybody knows how to fix this issue LMK!)Additional Information
Testing
Run workflow
alis/workflow_fix_1
branchmain
should work