Nest: Use CircleCI as replacement of TravisCI

[BrunnerLivio]

Feature Request

What is the motivation / use case for changing the behavior?

TravisCI is great for smaller projects and easy to get started with. In my opinion NestJS has grown out of this.

Some features why choose CircleCI over TravisCI:

• YAML Anchors: Allows to define "mixin" jobs. It allows to reduce redundancy. Useful for e.g. setup the environment and saving / restoring cache.
• Displays each job on GitHub:
  
• Better measuring:
  
• Better workflow integration:
  

Teachability, Documentation, Adoption, Migration Strategy

Migrate nestjs/nest to CircleCI. Migrate integrations only if needed.

[kamilmysliwiec]

I wanted to migrate over CircleCI for months! :) Let's do it as soon as possible. Feel free to move forward with this migration if you have some spare time.

[marcus-sa]

Let me know if you need any help, since this will affect https://github.com/nestjs/nest/pull/2743 aswell 🥳

[kamilmysliwiec]

I started the migration towards CircleCI. Feel free to contribute:)

[BrunnerLivio]

@kamilmysliwiec looking really nice - exactly how I had imagined it to be (with the mixins / aliases, etc. so awesome) :)

The checks are so useful for a contributor:

and the config is way cleaner and maintainable.

[marcus-sa]

Any reason for why you're not using yarn?

[BrunnerLivio]

@marcus-sa we challenged that idea some time ago in #1060, but in the end went for #1176. It would have been a huge change to the existing codebase, so #1176 made more sense at the time.

Maybe we can re-discuss this topic since we are anyway currently expanding our build system, but this should be handled in a separate issue / PR.

[kamilmysliwiec]

Just finished the migration of the main repo. I'll do the same for the rest of them too. If anyone wants to contribute, PRs are welcome!

PS. @BrunnerLivio I think that @marcus-sa asked about NPM vs Yarn, not Yarn workspaces. I'm personally using NPM recently, but I don't have any preference here. Both aren't perfect, neither one convinced me, so I'm just using this one which is more popular now:)

[lock[bot]]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.