#What is `dagger checks`?
1 messages · Page 1 of 1 (latest)
still experimental & hidden but will un-hide and document very soon 😁
Try it on our repo:
dagger -m github.com/dagger/dagger check -l
dagger -m github.com/dagger/dagger check go:lint helm:* installers
I first noticed it on my Dagger PR. I'm excited to read those docs once they come out!
Unlike dagger call, dagger check does not accept arguments. You call a check, or you don't. All arguments to the underlying function must have default values or the check will be disabled. Some defaults cannot be set from within the function sandbox (eg. secrets, host services). But they can be set as user defaults written to a local .env file. This is how you can load secrets and other environment-specific configuration into checks
Excited for these to become stable!
Follow-up question, how do I view them? This link produced by my PR did not load.
Ah, I'm guessing that because the "checks" feature is still hidden behind a flag, that also prevents you from rendering any URL at all behind /checks. Let's see if we can fix this tomorrow when the team starts their day (east coast time).
@north crest @elder linden @shy crow 👆
Thanks @earnest temple!
Here's a screenshot of your check page 🙂
We have a PR incoming that fixes this issue!
We've deployed the change. You should be able to see your checks now. Clicking from the github commit status on your PR should take you to the right place. Let me know if you still see any issues!
Thank you! I was able to load it.
Aside, Dagger Cloud is one of my favorite features of Dagger.
and now my PR is passing, thank you!
The team appreciated that 🙂 Any feature requests?
I think the feature I'd like the most would be cache inspection and management so I can understand whether my Dagger functions are correctly setting up the cache.
BTW, I tried to use the decorator @check as part of this Doc. in Typescript, but it seems the import fails (cannot find name 'check') .
https://docs.dagger.io/getting-started/quickstarts/ci#create-a-check