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

Switch build to using private registries (ECR & GitLab) only #4032

Closed
hannes-ucsc opened this issue Apr 2, 2022 · 2 comments
Closed

Switch build to using private registries (ECR & GitLab) only #4032

hannes-ucsc opened this issue Apr 2, 2022 · 2 comments
Assignees
Labels
+ [priority] High compliance [subject] Information and software security demo [process] To be demonstrated at the end of the sprint demoed [process] Successfully demonstrated to team enh [type] New feature or request infra [subject] Project infrastructure like CI/CD, build and deployment scripts orange [process] Done by the Azul team

Comments

@hannes-ucsc
Copy link
Member

No description provided.

@github-actions github-actions bot added the orange [process] Done by the Azul team label Apr 2, 2022
@theathorn theathorn added enh [type] New feature or request infra [subject] Project infrastructure like CI/CD, build and deployment scripts compliance [subject] Information and software security labels Apr 4, 2022
@hannes-ucsc hannes-ucsc changed the title Switch build to using ECR only Switch build to using ECR private registry and GitLab registry only May 13, 2022
@hannes-ucsc hannes-ucsc removed the urgent label Dec 8, 2022
@hannes-ucsc hannes-ucsc added the + [priority] High label Feb 24, 2023
@hannes-ucsc hannes-ucsc changed the title Switch build to using ECR private registry and GitLab registry only Switch build to using private registries (ECR and GitLab) only Feb 28, 2023
@hannes-ucsc hannes-ucsc changed the title Switch build to using private registries (ECR and GitLab) only Switch build to using private registries (ECR & GitLab) only Feb 28, 2023
@hannes-ucsc
Copy link
Member Author

hannes-ucsc commented Feb 28, 2023

There are too many unknowns at this point. As we implement blocker #4031 we will able to spec this out more fully. Estimate is low confidence for that reason.

@hannes-ucsc hannes-ucsc self-assigned this May 8, 2023
@hannes-ucsc
Copy link
Member Author

For demo, show azul_docker_registry. Show evidence that it is being used on GitLab and locally.

@hannes-ucsc hannes-ucsc added demo [process] To be demonstrated at the end of the sprint demoed [process] Successfully demonstrated to team labels Jun 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
+ [priority] High compliance [subject] Information and software security demo [process] To be demonstrated at the end of the sprint demoed [process] Successfully demonstrated to team enh [type] New feature or request infra [subject] Project infrastructure like CI/CD, build and deployment scripts orange [process] Done by the Azul team
Projects
None yet
Development

No branches or pull requests

2 participants