Devcontainer-based CI flow #586
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- initial devcontainer configuration - postgres and mysql database initialization scripts - database startup scripts and permission fixes - password and connectivity configuration
- workarounds for volume relabeling issues - podman-specific configurations - devcontainer re-engineering for podman compatibility - missing scripts and permission fixes
- mysql user and permission fixes - database role creation - test database setup
- job selection logic fix - suppress missing table warnings in tests - disable dag generation during duplicate piece test - resolve record changed since last read errors
- use v2 action - reorder steps for fast fail - remove stray files
parkan
force-pushed
the
local/devcontainer-rebased
branch
from
934cfa8 to
ed21663
Compare
parkan
force-pushed
the
local/devcontainer-rebased
branch
from
ee6e85f to
ccfaccd
Compare
This reverts commit ed21663.
parkan
force-pushed
the
local/devcontainer-rebased
branch
from
ccfaccd to
cf692f7
Compare
lanzafame
approved these changes
Oct 21, 2025
| // GenerateUniqueName creates a unique name for testing by combining a prefix with a random suffix | ||
| // GenerateUniqueName creates a unique name for testing by combining a prefix with a UUID suffix | ||
| func GenerateUniqueName(prefix string) string { | ||
| return prefix + "-" + RandomLetterString(8) + "-" + RandomLetterString(4) |
There was a problem hiding this comment.
@parkan Are we able to get rid of the RandomLetterString function while we are at it?
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
(cleaned up version of #585 -- the history got so hairy that internal rebasing broke on that branch)
MOTIVATION
the workflows in this repo were historically based on PL templates/work patterns, with complex matrix builds, multi-container orchestration, and a huge number of action dependencies
this resulted in repeated breakage due to actions changing, versions not being pinned fully/going out of sync, new golang releases changing linting rules, etc
numerous efforts were made to get that CI workflow working reliably (#443, #436, #467, #581, etc) but ultimately this all feels like threading water at best
to make matters worse, testing the workflows locally is a giant headache because even
actdoesn't provide an isomorphic environment to what happens on the runners and is not feature complete; normalmake testoutput diverges heavily between local dev and CIPROPOSAL
NOTE: we're using https://github.com/parkan/github-actions to run a rootless podman devcontainer because:
NOTES/REMAINING