Orchestrator Deploy Error TypeError: Cannot read properties of null (reading 'match')

[Schuchie]

Describe the bug
Trying to deploy the dreamhouse-package (as mentioned in your tutorial/trailhead) and also tried to deploy a simpler own package to a scratch org.

To Reproduce
Steps to reproduce the behavior:
Follow your trail ( https://docs.dxatscale.io/challenges/challenges/build-your-package ) and after that try to deploy any package.

Expected behavior
The package gets deployed without an error.

Screenshots
Receiving following error:

sfdx sfpowerscripts:orchestrator:deploy -u test-v9qua1lzbkdk@example.com --loglevel debug
-------------------------------------------------------------------------------------------
sfpowerscripts  -- The DX@Scale CI/CD Orchestrator -Version:10.2.15 -Release:February 22
-------------------------------------------------------------------------------------------
command: deploy
Skip Packages If Already Installed: false
Artifact Directory: artifacts
Target Environment: test-v9qua1lzbkdk@example.com
-------------------------------------------------------------------------------------------
TypeError: Cannot read properties of null (reading 'match')
----------------------------------------------------------------------------------------------------
0 packages deployed in 00:00:00 with {0} errors

Platform Details (please complete the following information):

• OS: macOS BigSur 11.6
• Version: 10.2.15 -Release:February 22
• Salesforce CLI(sfdx cli) Version: 7.139.0
• CI Platform: Console

Additional context
Forked Dreamhouse Repo https://github.com/dxatscale/dxatscale101/

[azlam-abdulsalam]

@Schuchie , Can you confirm whether artifacts are successfully created using the build command? and do you have the artifacts created?

[Schuchie]

Hey @azlam-abdulsalam ,

both apps (dreamhouse and my own) are build successfully:

Dreamhouse:

sfdx sfpowerscripts:orchestrator:build -v dxscale-prod --branch main
-------------------------------------------------------------------------------------------
sfpowerscripts  -- The DX@Scale CI/CD Orchestrator -Version:10.2.15 -Release:February 22
-------------------------------------------------------------------------------------------
command: build
Build Packages Only Changed: false
Config File Path: config/project-scratch-def.json
Artifact Directory: artifacts
-------------------------------------------------------------------------------------------
Packages scheduled for build
┌────────────────┬────────────────────────────────────────┐
│ Package        │ Reason to be built                     │
├────────────────┼────────────────────────────────────────┤
│ dreamhouse-app │ Activated as part of all package build │
└────────────────┴────────────────────────────────────────┘

Packages currently processed:{1}  dreamhouse-app
Awaiting Dependencies to be resolved:{0}  
Package creation initiated for  dreamhouse-app

dreamhouse-app package created in 00:11:02
-- Package Details:--
-- Package Version Number:         0.1.0.2
-- Package Version Id:              04t7Q000000DaUmQAK
-- Package Test Coverage:           98
-- Package Coverage Check Passed:   true
-- Apex In Package:              Yes
-- Profiles In Package:          No
-- Metadata Count:          86

Packages currently processed:{0}  
Awaiting Dependencies to be resolved:{0}  



Generating Artifacts and Tags....
Artifact Generation Completed for dreamhouse-app to /Users/nilsschuch/repository/salesforce/deployment/artifacts/dreamhouse-app_sfpowerscripts_artifact_0.1.0-2.zip
----------------------------------------------------------------------------------------------------
1 packages created in 00:11:02 minutes with {0} errors}
----------------------------------------------------------------------------------------------------

Own:

-------------------------------------------------------------------------------------------
sfpowerscripts  -- The DX@Scale CI/CD Orchestrator -Version:10.2.15 -Release:February 22
-------------------------------------------------------------------------------------------
command: build
Build Packages Only Changed: false
Config File Path: config/project-scratch-def.json
Artifact Directory: artifacts
-------------------------------------------------------------------------------------------
Packages scheduled for build
┌────────────────┬────────────────────────────────────────┐
│ Package        │ Reason to be built                     │
├────────────────┼────────────────────────────────────────┤
│ dreamhouse-app │ Activated as part of all package build │
└────────────────┴────────────────────────────────────────┘

Packages currently processed:{1}  dreamhouse-app
Awaiting Dependencies to be resolved:{0}  
Package creation initiated for  dreamhouse-app

dreamhouse-app package created in 00:09:26
-- Package Details:--
-- Package Version Number:         0.1.0.3
-- Package Version Id:              04t7Q000000DaZ4QAK
-- Package Test Coverage:           98
-- Package Coverage Check Passed:   true
-- Apex In Package:              Yes
-- Profiles In Package:          No
-- Metadata Count:          14

Packages currently processed:{0}  
Awaiting Dependencies to be resolved:{0}  



Generating Artifacts and Tags....
Artifact Generation Completed for dreamhouse-app to /Users/nilsschuch/repository/salesforce/deployment/artifacts/dreamhouse-app_sfpowerscripts_artifact_0.1.0-3.zip
----------------------------------------------------------------------------------------------------
1 packages created in 00:09:26 minutes with {0} errors}
----------------------------------------------------------------------------------------------------

And i also can see the created artifacts in the "artificats"-folder.

[azlam-abdulsalam]

Looks like a bug in the core dependencies, can you upgrade to the latest beta and let me know if it happens

 echo'y' | sfdx plugins:install @dxatscale/sfpowerscripts@beta

[Schuchie]

Tried your beta-version, still receive the same result:

 sfdx plugins:install @dxatscale/sfpowerscripts@beta
This plugin is not digitally signed and its authenticity cannot be verified. Continue installation y/n?: y
Finished digital signature check.
warning "@salesforce/lwc-dev-server > @rollup/plugin-alias@3.1.9" has unmet peer dependency "rollup@^1.20.0||^2.0.0".
warning "@salesforce/lwc-dev-server > request-promise-native@1.0.9" has unmet peer dependency "request@^2.34".
warning "@salesforce/lwc-dev-server > request-promise-native > request-promise-core@1.1.4" has unmet peer dependency "request@^2.34".
warning "dependencies-cli > @salesforce-ux/design-system@2.16.2" has unmet peer dependency "postcss@^8.3.5".
warning "sfdx-hardis > mega-linter-runner > yeoman-environment@3.6.0" has unmet peer dependency "mem-fs@^1.2.0 || ^2.0.0".
warning "sfdx-hardis > mega-linter-runner > yeoman-environment@3.6.0" has unmet peer dependency "mem-fs-editor@^8.1.2 || ^9.0.0".
warning "sfpowerkit > ts-node@9.1.1" has unmet peer dependency "typescript@>=2.7".
Installing plugin @dxatscale/sfpowerscripts... installed v10.3.3
 ~/repository/salesforce/deployment   main ±  sfdx sfpowerscripts:orchestrator:deploy -u test-v9qua1lzbkdk@example.com --loglevel debug
-------------------------------------------------------------------------------------------
sfpowerscripts  -- The DX@Scale CI/CD Orchestrator -Version:10.3.3 -Release:March 22
-------------------------------------------------------------------------------------------
command: deploy
Skip Packages If Already Installed: false
Artifact Directory: artifacts
Target Environment: test-v9qua1lzbkdk@example.com
-------------------------------------------------------------------------------------------
TypeError: Cannot read properties of null (reading 'match')
----------------------------------------------------------------------------------------------------
0 packages deployed in 00:00:00 with {0} errors
----------------------------------------------------------------------------------------------------

Should I rebuild the artifact?

[azlam-abdulsalam]

ah right, got it this was recently raised as well, this happens when you dont have a git remote set in the repository. Can you set the upstream in your git repo and rebuild the packages

We will address this as part of the next release

[Schuchie]

@azlam-abdulsalam thx for the support. You were right, about the missing upstream.