Skip to content
This repository has been archived by the owner on Mar 18, 2024. It is now read-only.

Remove Confusion around source packages by introducing a new task #101

Closed
azlam-abdulsalam opened this issue Jul 21, 2020 · 1 comment · Fixed by #123 or #131
Closed

Remove Confusion around source packages by introducing a new task #101

azlam-abdulsalam opened this issue Jul 21, 2020 · 1 comment · Fixed by #123 or #131
Assignees
Labels
documentation Improvements or additions to documentation enhancement enhancement to existing feature
Milestone

Comments

@azlam-abdulsalam
Copy link
Contributor

Source Packages is an idea to bring artifact based deployment (similar to unlocked packaging) but done off the platform and basically to carry over metadata that is not covered by unlocked packages. It is as simple as having a Json metadata with commit id and a version number, which can then be deployed by metadata api.
However the use of this tasks are not straight forward, one have to remember, to checkout the artifact and then deploy the directory.

It is better to have a single task that handles installation of source packages

As this will take some time, we need to ensure the current documents are clear on how to deploy source packages

@azlam-abdulsalam azlam-abdulsalam added documentation Improvements or additions to documentation enhancement enhancement to existing feature labels Jul 21, 2020
@azlam-abdulsalam
Copy link
Contributor Author

There have been significant changes for this issue. We are introducing an Install Source Package Task(only in azure pipelines to begin with), which will install the source package, Create Source Package is uplifted to bundle source along with the artifact and will support both checkout based model and install source package tasks

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
documentation Improvements or additions to documentation enhancement enhancement to existing feature
Projects
None yet
3 participants