Skip to content
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

Consider Outputs Requirements #192

Open
CodeGat opened this issue Feb 14, 2025 · 0 comments
Open

Consider Outputs Requirements #192

CodeGat opened this issue Feb 14, 2025 · 0 comments
Assignees
Labels
CI 2.0 Relating to the second iteration of build-ci priority:high A high priority issue - has an impact on core functionality type:investigation look into options, do some research!

Comments

@CodeGat
Copy link
Member

CodeGat commented Feb 14, 2025

We should give decently useful output from our Entrypoint Workflows. Expect that different Model Component Repositories may want to go further with whatever is installed by our workflows. This will definitely need to be workshopped with MCR maintainers.

Considerations

  • Is just installing into an image enough anymore? Should we attempt to make testing infrastructure endpoints?
@CodeGat CodeGat added CI 2.0 Relating to the second iteration of build-ci priority:high A high priority issue - has an impact on core functionality type:investigation look into options, do some research! labels Feb 14, 2025
@CodeGat CodeGat self-assigned this Feb 14, 2025
@github-project-automation github-project-automation bot moved this to New Issues 🌅 in Build-ci 2.0 Feb 14, 2025
@CodeGat CodeGat moved this from New Issues 🌅 to Todo ⏳ in Build-ci 2.0 Feb 19, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CI 2.0 Relating to the second iteration of build-ci priority:high A high priority issue - has an impact on core functionality type:investigation look into options, do some research!
Projects
Status: Todo ⏳
Development

No branches or pull requests

1 participant