This repository has been archived by the owner on Mar 18, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 101
Consolidated Task Executor #68
Comments
azlam-abdulsalam
added a commit
that referenced
this issue
Oct 14, 2020
This feature introduces a build command (cli version_, which generates all the packages (unlocked/source) in a repo in parallel. This aligns to the vision of the next iteration of sfpowerscripts as described in #68 The command does the following - Do a topology sort based on depenendencies to figure the initial set of packages - Assign priority to build orders, unlocked packages with depenendencies get the highest priority, with no depenedency coming next and finally source/data packages - As soon as a package is built, it will check any childs (which have their dependency satisfied) to be added into the queue. This eliminates where level 0 packages clogging up the queue. - All jobs are scheduled using bottleneck with a max concurrency set to 10. - Logs are consolidated into . sfpowerscripts/log and only failed logs are displayed
Merged
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Closing this as orchestrator commands are now merged |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
In a monorepo, a project will be operating with multiple packages and new packages being added or removed during the course of development.
This means whenever a new package is added, additional tasks that need to be added including in validation (such as PMD, Metadata Validation, Trigger apex tests etc).Same applies for build and deployment stages.
One approach would be is to have a single task, that reads sfdx-project.json and executes the whole set. This has a downside as the logs of such a task is often hard to comprehend, but could be mitigated with folding ( see grouping in azure pipelines https://docs.microsoft.com/en-us/azure/devops/pipelines/scripts/logging-commands?view=azure-devops&tabs=bash#formatting-commands ).
This could be an optional addition to sfpowerkit where a pipeline could be set up and maintained only by changing the project manifest
The text was updated successfully, but these errors were encountered: