-
Notifications
You must be signed in to change notification settings - Fork 21
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
test: introduce new uds task file & ci structure #14
Conversation
* Initial commit * update .gitignore * bump config chart to 0.1.0 and remove zarf package version * Add loki to uds-core (packages/standard) and add run task for build/test of uds-core package * remove tasks.yaml that was being used for local dev, Remove require:true from loki base package components * remove neuvector required:true references * remove unnecessary imagepullsecrets value from loki values --------- Co-authored-by: Michael-Kruggel <[email protected]>
* Add commit lint workflow * add commitlint config
Preliminary thought on this is that what you have in this pr right now is pretty much 100% tracking towards what i envisioned, only caveat being that there isn't a root level run task that can do all the things if you are doing local dev. That would be trivial to add in the future and would basically emulate the flow you have orchestrated in github workflows on local. |
To your last commit message. You can do a fun bash one liner or use this https://github.com/philips-labs/list-folder-action and inline the filter instead of using the yaml file 🫠 I thought the yaml file was the clearest option, albeit verbose |
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.
I don't really have much to say since I've been commenting on the progress along this journey... 🤣 LGTM! 🚀🦄
lol yeah yaml wasn't bad really, just started feel like one more area for us to keep up with, but probably not that big of a deal |
Description
Utilize UDS CLI task runner for all local/remote jobs. This allows us to use the same commands locally or remotely. Also introducing per-capability and complete UDS Core testing in parallel, with fail-fast + custom runners for speed.
Type of change
Checklist before merging