-
Notifications
You must be signed in to change notification settings - Fork 1
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
feat: ci/cd #10
feat: ci/cd #10
Conversation
4fc406a
to
24326e4
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.
Just a question and request for code comment.
LGTM
ci/cmd/build/main.go
Outdated
Platform: "linux/amd64", | ||
BuildArgs: []dagger.BuildArg{{Name: Env_EnvTag, Value: envTag}}, | ||
}). | ||
WithRegistryAuth( |
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.
It's strange to me that the registry auth is done at this point, before the image is being pushed.
Is that a convenience or a requirement for the dagger client?
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, it can be moved. The auth token is used during push but I can move the token retrieval closer to the push as well 👍🏼
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.
Will look at the failing test shortly
@stephhuynh18 @3benbox, here's the PR for the CASv5 Scheduler CI/CD. I've also opened a separate PR for changes on the CD Manager side.
There is one ugly part of this code that I'm going to fix in a subsequent PR - the Dagger Go dependencies are mixed in with the actual app dependencies. I'm going to pull the Dagger stuff out into its own repo and pull it in during CI/CD workflows instead of running it from within the repo like it is right now.
Steph, I've commented out the unit test piece until we can figure out why that one test case is failing when run via Dagger 😢