`bit tag --persist` not working on CI

[elliottye]

Hi,

I was trying to publish my components to our private Artifactory registry via CircleCI jobs. All the other steps in the only build job work fine but it got stuck on bit tag with the following error:

fatal: "components/basics/[email protected]" has a dependency "envs/custom-react-env". this dependency was not included in the tag command.

Here's the folder structures of my workspace:

• components basics header ..
• envs custom-react-env

The local custom React env component is for customizing Jest and other tools, and it's applied to all components under components/** by bit env set "components/**/*" envs/custom-react-env. And it looks fine when running bit env.

But I still can't publish the components with bit tag --persist on my CI after I've done bit tag --soft locally. It's strange that bit tag --persist works just fine on my local machine. Any idea why?

You know I've tried bit tag envs/custom-react-env "components/**/*" --persist --ignore-issues --unmodified, literally all the combinations of options because I thought it might have something to do with the custom React env component. But still to no avail. Please help!

Specifications

• Bit version: 0.0.724
• Workspace type: (harmony/legacy) harmony
• Node version: 14.18.0
• npm / yarn version: NPM 6.14.15
• Platform: MacOS Catalina and CircleCI

[davidfirst]

Can you please re-try with the latest version of Bit? if it's still happening, please post the .bitmap file after you soft-tagged it and the debug.log from the CI. (bit globals shows the location of the debug.log file, or you can run the command with --log flag to print the log to the screen).

[elliottye]

Can you please re-try with the latest version of Bit? if it's still happening, please post the .bitmap file after you soft-tagged it and the debug.log from the CI. (bit globals shows the location of the debug.log file, or you can run the command with --log flag to print the log to the screen).

The latest version Bit has issues with React env so that's why I reverted to 0.0.724. I can't use the latest version to test the above issue because it would fail at bit build or bit tag --soft.

[itaymendel]

when running bit tag, it's recommended not to set specific components, as often you may end up with dep-management problems. i'd recommend moving to latest release of bit, as many of these items were resolved.