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
Actually, evaluating the product, and I cannot find an easy way to know what was built in order to determine what apps or artefacts that have to be deployed or pusblished. Parsing the outout produced by the command tubo build is a way but this output has many noise. Moreover, this kind of ouput will change over the time... isn't it ?. Then not reliable enough.
Then it will be nice to have an option like turbo build --json or turbo build --json output= ./.turbo/built.json, a parseable format that tell us which artefacts have been really built. Then we can read this file in bitbucket pipeline in the step deploy or else.
Or give a better integration with pipeline. As Turborepo has all information to produce a such file, I was suprised to not have it from the beginning. I'm sad for you.
Thank you Team,
Non-goals
Background
Turbo repo, integration with a pipeline. Ex.: Bitbucket. Need a reliable way to know what artefacts have been really built in order to pass the list to the next steps like deploy, publised or whatever.
Proposal
Produce an option to produce a parseable output for built artefact:
turbo build --json or turbo build --json output= ./.turbo/built.json,
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Goals
Actually, evaluating the product, and I cannot find an easy way to know what was built in order to determine what apps or artefacts that have to be deployed or pusblished. Parsing the outout produced by the command
tubo buildis a way but this output has many noise. Moreover, this kind of ouput will change over the time... isn't it ?. Then not reliable enough.Then it will be nice to have an option like
turbo build --jsonorturbo build --json output= ./.turbo/built.json, a parseable format that tell us which artefacts have been really built. Then we can read this file in bitbucket pipeline in the step deploy or else.Or give a better integration with pipeline. As Turborepo has all information to produce a such file, I was suprised to not have it from the beginning. I'm sad for you.
Thank you Team,
Non-goals
Background
Turbo repo, integration with a pipeline. Ex.: Bitbucket. Need a reliable way to know what artefacts have been really built in order to pass the list to the next steps like deploy, publised or whatever.
Proposal
Produce an option to produce a parseable output for built artefact:
turbo build --jsonorturbo build --json output= ./.turbo/built.json,Beta Was this translation helpful? Give feedback.
All reactions