This repository has been archived by the owner on Mar 18, 2024. It is now read-only.
Refactor Artifact Structure across the package creation tasks #131
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
azlam-abdulsalam
force-pushed
the
feature/unlocked_package_artifact
branch
from
fdcae03 to
df0aa02
Compare
aly76
reviewed
Aug 24, 2020
added 21 commits
August 24, 2020 16:49
- Introduce async retry for Org Check - Fix Delta Package Issues - Remove Project directory flags, Fix issues with CLI - Add Profile check, futher refactoring to ManifestHelpers
added 11 commits
August 30, 2020 15:09
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
sfpowerscripts feature artifact as the central idea for connecting build and release. Till Milestone 16, the artifacts were only metadata and it need to be checked out from version control, in the case of source package. Delta package did generate the artifacts, but the package format was not fully thought out.
Also to satisfy, skipping of artifacts, if installed not only in unlocked package, also in source package, it is much simpler if we have the artifact carried as part of the build process. This was already done as part of #101, however we have decided to make it uniform across the entire packages.
Every artifact will be named <package_name>_sfpowerscripts_aritfact or spowerscripts_artifact (only in the case of delta package, generated across all the repositories)
Each artifact will contain an aritfact_metadata.json (which has all the information regaring the artifact). as well as a folder called source (which is the metadata that will be deployed).
Backward compatibility is not supported, The Install Source Package or Deploy Task will only work with the newer versions of associated artifact producer tasks
Fixes #56
Fixes #101