You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is this feature request related to a problem? If so, please describe it.
Sometimes we need to build a package and then another package; or otherwise wish to serialize the build of large packages. We can do this in two ways:
add a --wait-for argument which waits until that build completes (Successfully), before running the next build.
Permit multiple packages to be specified when running peridot build package, and have an argument for the max parallelism of the builds, if multiple packages are specified. By default, it would build all the packages in parallel, but would otherwise build them in the order they were supplied, using up to N parallel builds, where N is some integer between 1 and (some maximum)
Describe the solution you'd like to see
Solutions one and/or two would be good.
In the first solution, we would need to decide whether to implement this client side or server side. I'm tempted to say it should be server side, but that may mean it has to wait for peridotv2 (soon!)
Have you considered alternative solutions/features? If so, please describe them.
No response
Version and Build Information
n/a
Additional Context
No response
The text was updated successfully, but these errors were encountered:
Is this feature request related to a problem? If so, please describe it.
Sometimes we need to build a package and then another package; or otherwise wish to serialize the build of large packages. We can do this in two ways:
peridot build package
, and have an argument for the max parallelism of the builds, if multiple packages are specified. By default, it would build all the packages in parallel, but would otherwise build them in the order they were supplied, using up to N parallel builds, where N is some integer between 1 and (some maximum)Describe the solution you'd like to see
Solutions one and/or two would be good.
In the first solution, we would need to decide whether to implement this client side or server side. I'm tempted to say it should be server side, but that may mean it has to wait for peridotv2 (soon!)
Have you considered alternative solutions/features? If so, please describe them.
No response
Version and Build Information
n/a
Additional Context
No response
The text was updated successfully, but these errors were encountered: