This repository has been archived by the owner on Mar 18, 2024. It is now read-only.
Issue when publishing artifacts to Azure Artifacts #967
Labels
bug
Something isn't working
Milestone
Comments
|
Hi, this might assist with triage: https://stackoverflow.com/questions/63796633/spawnsync-bin-sh-enobufs |
|
Fixed in May 22 |
aly76
pushed a commit
that referenced
this issue
May 6, 2022
azlam-abdulsalam
added a commit
that referenced
this issue
May 20, 2022
* revert(coverage): Fail Package validation if low coverage (#941) Revert back to normal behaviour, as coverage calculation is stable with retries * chore(publish): update versions and publish to npm - @dxatscale/sfpowerscripts.core@19.0.11 - @dxatscale/sfp-cli@2.0.11 - @dxatscale/sfpowerscripts@13.0.13 * chore(release-title): update release title to May22 * feat(fast-feedback): experimental mode for faster feedback during validate (#945) * feat(fast-feedback): experimental mode for faster feedback during validate experimental feature: Add option which would help validate command to provide validation using - Deploy only changed components of a changed package - Trigger only testclasses for impacted classes - Skip coverage validation - Skip package dependencies installation Utilize a hidden flag 'fastfeedback', this feature may be revoked at any time and should be considered unstable * chore(publish): update versions and publish to npm - @dxatscale/sfpowerscripts.core@19.1.0 - @dxatscale/sfp-cli@2.0.12 - @dxatscale/sfpowerscripts@13.1.0 * fix(validateimpl): fast feed back testing to respect testMode set in package * chore(publish): update versions and publish to npm - @dxatscale/sfpowerscripts@13.1.1 * fix(apex-tests): ensure retry is available for all types of test modes * fix(validate): fix headers being incorrectly displayed when there is no impacted test classes * refactor(validate): use constants declared in core lib instead of hardcoding * chore(publish): update versions and publish to npm - @dxatscale/sfpowerscripts.core@19.1.1 - @dxatscale/sfp-cli@2.0.13 - @dxatscale/sfpowerscripts@13.1.2 * chore(dependencies): update @salesforce/core to 2.36.0 * chore(publish): update versions and publish to npm - @dxatscale/sfpowerscripts.core@19.1.2 - @dxatscale/sfp-cli@2.0.14 - @dxatscale/sfpowerscripts@13.1.3 * fix(impacted-apex): add further conditions to impacted test class - add test classes when it is changed -add all test classes to invalidated, when security model changes * chore(publish): update versions and publish to npm - @dxatscale/sfpowerscripts.core@19.1.3 - @dxatscale/sfp-cli@2.0.15 - @dxatscale/sfpowerscripts@13.1.4 * fix(impacted-apex): use array concat instead of push, as it pushes whole array as a new element * feat(validateimpl): add a env variable to support debugging provide an env variable 'SFPOWERSCRIPTS_DEBUG_PREFETCHED_SCRATCHORG' to support during debugging fetch. This allows to skip a new org from fetched from the pool * fix(install-source): remove warning around selective, as its currently only used during fastfeedback * chore(publish): update versions and publish to npm - @dxatscale/sfpowerscripts.core@19.1.4 - @dxatscale/sfp-cli@2.0.16 - @dxatscale/sfpowerscripts@13.1.5 * refactor(trigger-apex-tests): converge writing junit into write block and remove redundant write * feat(docker): add apex-link to docker image * refactor(apex-tests): refactor to make it readable and fix related bugs Refactor trigger logic to make it readable, fix the following issues as well 1. Handle Tests with multiple results 2. Skip retrieving coverage when not requested \3.Split into smaller functions * chore(publish): update versions and publish to npm - @dxatscale/sfpowerscripts.core@19.1.5 - @dxatscale/sfp-cli@2.0.17 - @dxatscale/sfpowerscripts@13.1.6 * refactor(fast-feedback): move fast feedback from using env variable to a deployment type * feat(fast-feedback): add fast feedback support in ValidateAgainstOrg * chore(publish): update versions and publish to npm - @dxatscale/sfpowerscripts.core@19.2.0 - @dxatscale/sfp-cli@2.0.18 - @dxatscale/sfpowerscripts@13.2.0 * fix(scripts): fix paths to pre and post deployment scripts when executed without repository (#954) scripts paths is always pointed to one in the repository, rather than in the artifacts. This started surfacing as the deploy impl generates a version of source package again from the provided artifact (this is being refactored). * chore(publish): update versions and publish to npm - @dxatscale/sfpowerscripts.core@19.2.1 - @dxatscale/sfp-cli@2.0.19 - @dxatscale/sfpowerscripts@13.2.1 * fix(scripts): fix the incorrect fix to paths to pre and post * chore(publish): update versions and publish to npm - @dxatscale/sfpowerscripts.core@19.2.2 - @dxatscale/sfp-cli@2.0.20 - @dxatscale/sfpowerscripts@13.2.2 * chore(publish): update versions and publish to npm - @dxatscale/sfpowerscripts.core@19.2.3 - @dxatscale/sfp-cli@2.0.21 - @dxatscale/sfpowerscripts@13.2.3 * fix: predeployment script path * chore(publish): update versions and publish to npm - @dxatscale/sfpowerscripts.core@19.2.4 - @dxatscale/sfp-cli@2.0.22 - @dxatscale/sfpowerscripts@13.2.4 * fix: upgrade semver from 7.3.5 to 7.3.6 (#956) Snyk has created this PR to upgrade semver from 7.3.5 to 7.3.6. See this package in npm: https://www.npmjs.com/package/semver See this project in Snyk: https://app.snyk.io/org/azlam-abdulsalam/project/05b6b6d2-ba3e-421a-b920-224a7c9e0896?utm_source=github&utm_medium=referral&page=upgrade-pr * fix: upgrade semver from 7.3.5 to 7.3.6 (#956) Snyk has created this PR to upgrade semver from 7.3.5 to 7.3.6. See this package in npm: https://www.npmjs.com/package/semver See this project in Snyk: https://app.snyk.io/org/azlam-abdulsalam/project/05b6b6d2-ba3e-421a-b920-224a7c9e0896?utm_source=github&utm_medium=referral&page=upgrade-pr * refactor/sfpPackage (#964) * refactor(sfppackage): refactor to use sfppackage * refactor(fast-feedback): migrate fastfeedback to build as opposed to validate building after success * chore(publish): update versions and publish to npm - @dxatscale/sfpowerscripts.core@20.0.0 - @dxatscale/sfp-cli@2.1.0 - @dxatscale/sfpowerscripts@13.3.0 * feat(deploy): add additional log with trace level * chore(publish): update versions and publish to npm - @dxatscale/sfpowerscripts@13.3.1 * fix(artifacts): remove temp directories before packaging artifact * fix(publish): fix issue when publishing artifacts bigger than 5 MB fix #967 * chore(publish): update versions and publish to npm - @dxatscale/sfpowerscripts.core@20.0.1 - @dxatscale/sfp-cli@2.1.1 - @dxatscale/sfpowerscripts@13.3.2 * fix(deploy): fix crash when skipIfInstall is used with deploy * fix(test-options): fix lodash import * chore(publish): update versions and publish to npm - @dxatscale/sfpowerscripts.core@20.0.2 - @dxatscale/sfp-cli@2.1.2 - @dxatscale/sfpowerscripts@13.3.3 * fix(changelog): fix crash in changelog due to incorrect usage of sourceVersionFrom * chore(publish): update versions and publish to npm - @dxatscale/sfpowerscripts.core@20.0.3 - @dxatscale/sfp-cli@2.1.3 - @dxatscale/sfpowerscripts@13.3.4 * fix(package-test-coverage): fix matching of package type * chore(publish): update versions and publish to npm - @dxatscale/sfpowerscripts.core@20.0.4 - @dxatscale/sfp-cli@2.1.4 - @dxatscale/sfpowerscripts@13.3.5 * refactor(packagetype): move to an enum for packageType * chore(publish): update versions and publish to npm - @dxatscale/sfpowerscripts.core@21.0.0 - @dxatscale/sfp-cli@2.2.0 - @dxatscale/sfpowerscripts@13.4.0 * fix(package-type): fix issues with overriding packageType during validate * chore(publish): update versions and publish to npm - @dxatscale/sfpowerscripts.core@21.0.1 - @dxatscale/sfp-cli@2.2.1 - @dxatscale/sfpowerscripts@13.4.1 * fix(deploy): override package type in validate mode * chore(publish): update versions and publish to npm - @dxatscale/sfpowerscripts@13.4.2 * fix(sfpackagebuilder): ignore diff computation on any error * chore(publish): update versions and publish to npm - @dxatscale/sfpowerscripts.core@21.0.2 - @dxatscale/sfp-cli@2.2.2 - @dxatscale/sfpowerscripts@13.4.3 * [CodeFactor] Apply fixes to commit cea880f (#969) Co-authored-by: codefactor-io <support@codefactor.io> * fix(fast-feedback): fix multiple issues with package diff creation * chore(publish): update versions and publish to npm - @dxatscale/sfpowerscripts.core@21.0.3 - @dxatscale/sfp-cli@2.2.3 - @dxatscale/sfpowerscripts@13.4.4 * refactor(sfppackagebuilder): remove usage of ChangeComponent and rather use componentSet directly * chore(publish): update versions and publish to npm - @dxatscale/sfpowerscripts.core@21.0.4 - @dxatscale/sfp-cli@2.2.4 - @dxatscale/sfpowerscripts@13.4.5 * fix(install-source): skip reconcile if no profiles are found in diff package * chore(publish): update versions and publish to npm - @dxatscale/sfpowerscripts.core@21.0.5 - @dxatscale/sfp-cli@2.2.5 - @dxatscale/sfpowerscripts@13.4.6 * fix(changedcomponents): revert to an earlier version,as its no longer used by fast feedback * chore(publish): update versions and publish to npm - @dxatscale/sfpowerscripts.core@21.0.6 - @dxatscale/sfp-cli@2.2.6 - @dxatscale/sfpowerscripts@13.4.7 * chore(dependencies): update @salesforce/core to 2.36.1 * chore(publish): update versions and publish to npm - @dxatscale/sfpowerscripts.core@21.0.7 - @dxatscale/sfp-cli@2.2.7 - @dxatscale/sfpowerscripts@13.4.8 * chore(dependencies): update marked to 4.0.14 * chore(dependencies): update semver to 7.3.6 * chore(dependencies): update @oclif/plugin-help to 5.1.12 * chore(publish): update versions and publish to npm - @dxatscale/sfpowerscripts.core@21.0.8 - @dxatscale/sfp-cli@2.2.8 - @dxatscale/sfpowerscripts@13.4.9 * chore(dependencies): update source-deploy-retrieve to 5.12.13 * chore(publish): update versions and publish to npm - @dxatscale/sfpowerscripts.core@21.0.9 - @dxatscale/sfp-cli@2.2.9 - @dxatscale/sfpowerscripts@13.4.10 * fix(apex-tests): do not replace coverage when coverage is not requested * chore(publish): update versions and publish to npm - @dxatscale/sfpowerscripts.core@21.0.10 - @dxatscale/sfp-cli@2.2.10 - @dxatscale/sfpowerscripts@13.4.11 * feat(validate): do not delete scratch org when there is no package to be built (#972) * feat(validate): do not delete scratch org when there is no package to be built fix #971 * chore(publish): update versions and publish to npm - @dxatscale/sfpowerscripts.core@21.0.11 - @dxatscale/sfp-cli@2.2.11 - @dxatscale/sfpowerscripts@13.4.12 * chore(dependencies): update sfdc-soup to 18.2.1 * chore(publish): update versions and publish to npm - @dxatscale/sfpowerscripts.core@21.0.12 - @dxatscale/sfp-cli@2.2.12 - @dxatscale/sfpowerscripts@13.4.13 * fix(fast-feedback): fix and refactor impacted test class selection * chore(publish): update versions and publish to npm - @dxatscale/sfpowerscripts@13.4.14 * fix(log): fix time displayed as well as packages desplaying undefined keys * chore(publish): update versions and publish to npm - @dxatscale/sfpowerscripts.core@21.0.13 - @dxatscale/sfp-cli@2.2.13 - @dxatscale/sfpowerscripts@13.4.15 * fix(scratchorg-info-assigner): fix incorrect use of async-retry * chore(publish): update versions and publish to npm - @dxatscale/sfpowerscripts.core@21.0.14 - @dxatscale/sfp-cli@2.2.14 - @dxatscale/sfpowerscripts@13.4.16 * fix(get-formatted-time): fix get formatted time to use milliseconds * chore(publish): update versions and publish to npm - @dxatscale/sfpowerscripts.core@21.0.15 - @dxatscale/sfp-cli@2.2.15 - @dxatscale/sfpowerscripts@13.4.17 * fix(pool): fix issues while returning scratch org to pool the code was using incorrect Id of the scratch org.. this fixes to the correct id, However its is still dependent on pre-requisite pool package * chore(publish): update versions and publish to npm - @dxatscale/sfpowerscripts.core@21.0.16 - @dxatscale/sfp-cli@2.2.16 - @dxatscale/sfpowerscripts@13.4.18 * fix(data-pkg): fix vlocity package being incorrectly returned as empty * fix(install-source): packages are committed even when push fails fix issue where packages are committed to the org even when push fails to deploy, as error was incorrectly handled * feat(fast-feedback): fast feedback to skip packages from validation when descriptor changes validate will validate the full package when the descriptor of the package changes. Most often the change is in a version number, and this triggers full deployment and testing, in fast feedback mode, this could be skipped. This has a negative issue when additonal orchestrator parameters are added like assignPermissionSets etc, this could be validated in a thorough mode * feat(fast-feedback): unhide fast-feedback and display info in header * feat(reconcile): enhance how reconcile is handled during fast feedback * docs(dr): add a dr on fast feedback * chore(sfpowerkit): update sfpowerkit to 4.2.7 * fix(alias): fix aliasified packages using username instead of alias Fix aliasified packages t use aliases instead of username. Refactor to utilize sfpOrg as opoosed to passing targetusername * fix(install-package): fix import casing * chore(dockerfile): update sfpowerkit to 4.2.8 * fix(creation-metrics): fix package creation metrics reporting package metrics during creation is not sending the flag whether its used with build or quickbuild, added an additional metric to deprecate package.elapsed.time in the future * chore(dependencies): update @salesforce/core to 2.36.3 * fix(dependencies): update import of core to same version in core * fix(package-lock): sync package lock across * Add chunking to ApexClassFetcher, ApexTriggerFetcher and ACCG Fetcher (#953) * Add chunking to ApexClassFetcher, ApexTriggerFetcher and ACCG Fetcher * Fix return values Co-authored-by: Azlam <43767972+azlam-abdulsalam@users.noreply.github.com> * fix(fast-feedback): fix All tests getting triggered when invalidated test class was not found * Update 002-fast-feedback.md Fixed typos and minor edits to wording for better flow. * fix(publish): create tags when atleast one package is published fix a bug when a tag when the same package would have been published * fix(fast-feedback): add warning message when tests are skipped due to a full package being deployed * fix(install-package): fix logs to show 'default' when aliasifed folder is not found * fix(fast-feedback): add additional logs about selective components utilized in fast feedback * fix(validate): add error to display when validate fails for anyother reason * fix(validate): remove erroneous json stringify on error message * chore(publish): update versions and publish to npm - @dxatscale/sfpowerscripts@13.6.13 * chore(dependencies): update simple-git to 3.7.1 * chore(publish): update versions and publish to npm - @dxatscale/sfpowerscripts.core@21.3.3 - @dxatscale/sfp-cli@2.3.3 - @dxatscale/sfpowerscripts@13.6.14 * fix(git): use command to fetch git remote instead of simple-git * fix(git): fix git related issues on docker - Rollback change made earlier to simple-git - Use pinned version of heroku docker image as this version seems not to have the issue. This will be analyzed in a future release Co-authored-by: Alan Ly <alan.ly@accenture.com> Co-authored-by: Snyk bot <snyk-bot@snyk.io> Co-authored-by: codefactor-io <support@codefactor.io> Co-authored-by: Alan Ly <36793262+aly76@users.noreply.github.com> Co-authored-by: Vu Ha <59901319+vuha-acn@users.noreply.github.com>
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Describe the bug
There is an issue when publishing the artifacts to Azure Artifacts
sfpowerscripts -- The DX@Scale CI/CD Orchestrator -Version:13.3.1 -Release:May 22
command: publish
target: NPM
Publish promoted artifacts only: false
Publishing xxxxx Version 14.0.0-14 with tag develop_h2r6...
spawnSync /bin/sh ENOBUFS
0 artifacts published in 00:00:06 with {1} errors
Packages Failed to Publish xxxxx v14.0.0-14
##[error]Bash exited with code '1'.
To Reproduce$(SCOPE) --npmrcpath .npmrc --npmtag $ (Build.SourceBranchName) --gittag --pushgittag
re-run the pipeline with command
sfdx sfpowerscripts:orchestrator:publish -d artifacts --npm --scope
Expected behavior
Publish successfully
Screenshots
Platform Details (please complete the following information):
The text was updated successfully, but these errors were encountered: