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.

Sign up for GitHub

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

Jump to bottom

Address 1es release warning #6392

Open
3 tasks
scbedd opened this issue Feb 5, 2025 · 0 comments
Open
3 tasks

Address 1es release warning #6392

scbedd opened this issue Feb 5, 2025 · 0 comments
Assignees
@danieljurek
Labels
Central-EngSys This issue is owned by the Engineering System team.

Comments

@scbedd
Copy link
Member

scbedd commented Feb 5, 2025

We want to eliminate this warning that is appearing on ALL go release pipelines.

Reference this PR for a summary of the necessary changes.

Need to:

  • Eliminate any download or checkout usage in the deployment job
  • Ensure that only the release job in the stage is actually a deployment with templateContext setting it to a release job. The rest should be moved to regular job instead of deployments

We need to update

  • archtype-cpp-release
@github-actions github-actions bot added the needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. label Feb 5, 2025
@kurtzeborn kurtzeborn added Central-EngSys This issue is owned by the Engineering System team. and removed needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. labels Feb 13, 2025
@kurtzeborn kurtzeborn moved this from 🤔 Triage to 📋 Backlog in Azure SDK EngSys 🥧📅 Feb 13, 2025
@kurtzeborn kurtzeborn moved this from 📋 Backlog to 🐝 Dev in Azure SDK EngSys 🥧📅 Mar 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@danieljurek danieljurek

Labels
Central-EngSys This issue is owned by the Engineering System team.
Projects
Azure SDK EngSys 🥧📅
Status: 🐝 Dev
Milestone
No milestone
Development

No branches or pull requests
3 participants
@danieljurek @kurtzeborn @scbedd