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

Quick deployments from bundling stage #292

Merged
merged 2 commits into from
Nov 28, 2023
Merged

Quick deployments from bundling stage #292

merged 2 commits into from
Nov 28, 2023

Conversation

EstebanRomero84
Copy link
Contributor

@EstebanRomero84 EstebanRomero84 commented Nov 28, 2023

What does this PR do?

Update quickPromotion to not send testLevel. This will allow to perform quick promotions from the bundling stage.

What issues does this PR fix or reference?

@W-14338568@

Functionality Before

We send testLevel on quick promotion requests. This makes the transaction to fail due to new validation.

Functionality After

We don't send testLevel on quick promotion requests.

@@ -149,7 +149,6 @@ export default abstract class QuickPromotionCommand<T extends typeof SfCommand>
*/
private buildPromoteOptions(deployId: string): void {
this.deployOptions = {
testLevel: 'Default',
Copy link
Contributor Author

Choose a reason for hiding this comment

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

This is the main change: we don't need to send testLevel on a quick promotion request.

Copy link
Contributor

Choose a reason for hiding this comment

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

The testLevel is optional right ?

Copy link
Contributor

Choose a reason for hiding this comment

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

Nice find

Copy link
Contributor Author

Choose a reason for hiding this comment

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

We don't need to specify a test level on a quick deploy since it only deploy metadata, it does't run the tests. They were run in the previous validate-only deployment.

@@ -5,7 +5,7 @@
* For full license text, see LICENSE.txt file in the repo root or https://opensource.org/licenses/BSD-3-Clause
*/

import { spawnSync } from 'child_process';
import { spawnSync } from 'node:child_process';
Copy link
Contributor Author

Choose a reason for hiding this comment

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

Needed to solve eslint error after dev dependencies update.

@EstebanRomero84 EstebanRomero84 merged commit 8259e36 into main Nov 28, 2023
12 of 16 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants