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

Removing duplicated env:USER in image tag for stress test #2578

Merged
3 commits merged into from
Jan 22, 2022

Conversation

ckairen
Copy link
Member

@ckairen ckairen commented Jan 19, 2022

No description provided.

@ckairen ckairen marked this pull request as ready for review January 19, 2022 18:55
@ckairen ckairen self-assigned this Jan 19, 2022
@ckairen ckairen added the Central-EngSys This issue is owned by the Engineering System team. label Jan 19, 2022
@azure-sdk
Copy link
Collaborator

The following pipelines have been queued for testing:
java - template
java - template - tests
js - template
net - template
net - template - tests
python - template
python - template - tests
You can sign off on the approval gate to test the release stage of each pipeline.
See eng/common workflow

@@ -154,7 +154,10 @@ function DeployStressPackage(
if ($repositoryBase) {
$imageTag += "/$repositoryBase"
}
$imageTag += "/$($pkg.Namespace)/$($pkg.ReleaseName):${deployId}"
if ($pkg.Namespace -ne $repositoryBase) {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it would be better to fix the issue at the root in find-all-stress-packages since that's where the context of how we should set these values lives (i.e. whether to use the username or the chart metadata). Perhaps exposing another property like $pkg.ImageRepository and setting that alongside the other "is local user mode" conditionals could work?

Copy link
Member

@benbp benbp Jan 19, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

One problem I can see with this approach is that we would have a less predictable naming structure for prod environments, e.g. if a user adds a release name X that happens to match the namespace X, I don't think we'd want to end up putting that image in the parent repository X and breaking the organizational structure.

@azure-sdk
Copy link
Collaborator

The following pipelines have been queued for testing:
java - template
java - template - tests
js - template
net - template
net - template - tests
python - template
python - template - tests
You can sign off on the approval gate to test the release stage of each pipeline.
See eng/common workflow

@benbp benbp self-requested a review January 21, 2022 21:53
@ghost
Copy link

ghost commented Jan 22, 2022

Hello @azure-sdk!

Because this pull request has the auto-merge label, I will be glad to assist with helping to merge this pull request once all check-in policies pass.

p.s. you can customize the way I help with merging this pull request, such as holding this pull request until a specific person approves. Simply @mention me (@msftbot) and give me an instruction to get started! Learn more here.

@ghost ghost merged commit 5f33e95 into main Jan 22, 2022
@ghost ghost deleted the albertcheng/tag-cleanup branch January 22, 2022 00:58
This pull request was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Central-EngSys This issue is owned by the Engineering System team. Stress This issue is related to stress testing, part of our reliability pillar.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants