If you’re using something like yarn or npm-shrinkwrap or strictly following semver you should be fine.īack when I made this comment Lerna was super early. It seems to me that looking at each package individually and checking for changes (even in the package.json's dependency) would be good enough to to know what did and didn’t change. On the other hand, if you change the one package and then also update al other 9 to use the newest version of the updated dependency then indeed all 10 packages changed and you would want to test them all. However, when CircleCI pings pulse on a successful. If for example you have 10 packages and you update one that happens to touch every other one but the the other 9 packages still declare a dependency to the old version, then it would be ok to just test the 1. We have a project set up in pulse to use webhooks for the build board in the Boulder office. In there you’ll find various scenarios that you can use depending on your needs. For a more complex workflow configuration, checkout this Chromatic CircleCI Orb made by a customer. circleci/config. Confirm that your configuration file is in the right directory. I think that if you can handle dependencies well and make sure to test interdependent repositories where the dependencies changes then you’ll be fine. See this CircleCI documentation for workflows related to pull requests from forked repositories. Generating a personal API token and configure the CLI by running circleci setup Navigate to a directory with a.circleci/config.yml file Run circleci config validate in your project's root directory Troubleshooting. ![]() There’s a strong argument to be made that a monorepo should be built in totality Ideally I’d like either a) a nice way to break up my single repository into multiple projects or b) better documentation of how I should approach setup for a multiapp repository. But that aside, configuring a monorepo build isn’t the clearest of processes right now.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |