3 ms·

I've used it in the past, but when they finally killed off the 1.0 builders (?) my company went to an "internally" hosted Jenkins[1] server and I haven't played

by azdle 6y ago

I've used it in the past, but when they finally killed off the 1.0 builders (?) my company went to an "internally" hosted Jenkins[1] server and I haven't played with any of the 2.0 stuff. Have you? How do you find working with it? [1] I did also ask about selfhosted stuff, but I'm not willing to host Jenkins for myself. I've heard nothing but complaints about managing a Jenkins install. It's been fine as a user (if a bit confusing), but I really don't want to admin it.

vosper 6y ago
Not the person you're asking, but we use CircleCI, and it's fine. The YAML config language is okay, it gets the job done and hasn't been horrible to maintain or modify. Though we only have a few steps in each. My current gripe is that there doesn't seem to be any way to declare that one pipeline depends on another, though I may just be missing something in the docs. What I'm trying to do is have my front-end feature branch builds run against the build of matching back-end branch, but there doesn't seem a way to declare "this build should depends on the output artifact of that build". I don't really want to have to wire it up myself using their API.
- driverdan 6y ago
  If they're in the same repo you can do this using workflows. If they're separate repos I don't think you can do this without using their API.
  - vosper 6y ago
    Yeah, it's separate repos. Interesting to know about the monorepo option, though - thanks.
- robertlagrant 6y ago
  Also happy with CircleCI here. Main problem for us is their limited support for efficient builds in monorepos.
driverdan 6y ago
We use circle for a lot of stuff (the latest version). It's pretty easy to learn. You can pick up the basics in <30 min.
rochak 6y ago
I have been GitHub Actions ever since they released, but used to use TravisCI before that. There were one or two projects where I used CircleCI and it seemed more mature that TravisCI.

by azdle 6y ago

vosper 6y ago

Not the person you're asking, but we use CircleCI, and it's fine. The YAML config language is okay, it gets the job done and hasn't been horrible to maintain or modify. Though we only have a few steps in each. My current gripe is that there doesn't seem to be any way to declare that one pipeline depends on another, though I may just be missing something in the docs. What I'm trying to do is have my front-end feature branch builds run against the build of matching back-end branch, but there doesn't seem a way to declare "this build should depends on the output artifact of that build". I don't really want to have to wire it up myself using their API.

driverdan 6y ago
If they're in the same repo you can do this using workflows. If they're separate repos I don't think you can do this without using their API.
- vosper 6y ago
  Yeah, it's separate repos. Interesting to know about the monorepo option, though - thanks.
robertlagrant 6y ago
Also happy with CircleCI here. Main problem for us is their limited support for efficient builds in monorepos.

driverdan 6y ago

We use circle for a lot of stuff (the latest version). It's pretty easy to learn. You can pick up the basics in <30 min.

rochak 6y ago

I have been GitHub Actions ever since they released, but used to use TravisCI before that. There were one or two projects where I used CircleCI and it seemed more mature that TravisCI.