Reviews from AWS Marketplace
0 AWS reviews
-
5 star0
-
4 star0
-
3 star0
-
2 star0
-
1 star0
External reviews
External reviews are not included in the AWS star rating for the product.
Circle CI as an pre code review check
What do you like best about the product?
We use CircleCI as a pre-check on commits, before doing the actual code review, integrated to phabricator. As our codebase grows, running lint checkers and tests locally before opening a code review takes a long time, so we usually do not do it locally and leave it to the CI, trading our time in running automatic checks for focusing on other tasks. It also help us locate adjusts to our commits before the actual code review, the CI will indicate and error on the commit and not send it to the next step, peer review.
What do you dislike about the product?
I am not in charge of configuration and maintenance of the CI on my company, but sometimes we have problems where the automation stops working, sometimes it would run the tests we delegated to it but not make a post-test change on the commit status (would not change it to ready to review)
What problems is the product solving and how is that benefiting you?
In my company, we use CI in two moments. First, running tests and linter on code reviews, before making it reviewable to peers and once it hits the master branch, to check if everything is ok even after the rebase.
First use guarantee us that we will be reviewing a commit that already had some checks ran on it, that means if that commit broke something else on the code, and it is covered by test, of course, we will be able to notice it and work on adjusts before an actual peer reviews it.
The second use makes sure that, once the commit is approved and then sent to master, the rebase/merge with master branch did not break anything in the project. It is important to us since we have different teams working on different parts of the product, and sometimes they share components, resources or need to adjust something in the whole product.
First use guarantee us that we will be reviewing a commit that already had some checks ran on it, that means if that commit broke something else on the code, and it is covered by test, of course, we will be able to notice it and work on adjusts before an actual peer reviews it.
The second use makes sure that, once the commit is approved and then sent to master, the rebase/merge with master branch did not break anything in the project. It is important to us since we have different teams working on different parts of the product, and sometimes they share components, resources or need to adjust something in the whole product.
- Leave a Comment |
- Mark review as helpful
Go to tool for CI! :)
What do you like best about the product?
Love almost everything about CircleCI :) Is very robust as a CI tool, and I love the fact that everything is documented really well. Orbs implementations are very useful and just perfect!
What do you dislike about the product?
Nothing much to comment on about CircleCI. I'm not aware if its possible to have a GitHub integration to view the pipelines via GitHub itself but it would be a nice to have :)
What problems is the product solving and how is that benefiting you?
Application releases, running unit tests on each and every PR and branch as well as testing automated builds.
Good experience, faced multiple outages that affected our releases couple of times.
What do you like best about the product?
ssh to the container
re-run from failed
re-run from start
nice UI
re-run from failed
re-run from start
nice UI
What do you dislike about the product?
downtine in 2 cruciel releases (bad luck)
pipeline fails for a strange error and succeeds after re-run which is kind of weird
sometimes the pipeline finishes but the status still shows running unless i refresh the page
our keys were exposed after a security breach!!
pipeline fails for a strange error and succeeds after re-run which is kind of weird
sometimes the pipeline finishes but the status still shows running unless i refresh the page
our keys were exposed after a security breach!!
What problems is the product solving and how is that benefiting you?
making sure that no one pushes a code that doesn't pass our linting standards, integration tests, unit tests, functional tests ....
creating the docker image
creating the docker image
Mobile pipeline deployment solution
What do you like best about the product?
Ability to manage all pipelines for separate projects (mobile, backend and front end) in one account. This helps us to keep a single repository for all our development pipelines
What do you dislike about the product?
Sometimes requires users to refresh midway through a running build to identify if the build pipeline has been completed successfully.
What problems is the product solving and how is that benefiting you?
Not having to worry about environment variables or deployment mixups
Have a lot of interests in CI/CD tools
What do you like best about the product?
It's really convenient to test our codes automatically online. It will not block what I'm doing so I can push my work forward offline while CI running online.
What do you dislike about the product?
It's unstable sometimes. Sometimes it will give us a wrong result. And sometimes it took way too much time to finish all the tests.
What problems is the product solving and how is that benefiting you?
Running tests.
Checking code styles.
Checking resources availability.
Checking code styles.
Checking resources availability.
Solid CI for Apple Platforms
What do you like best about the product?
Good documentation to get us started, everything works as expected, I can trust that issues are mine, not Circle CI's.
What do you dislike about the product?
Not their fault, but having it built signed apps for Apple Platforms is difficult, but at least there is help out there.
What problems is the product solving and how is that benefiting you?
They help us know our apps work and we get a consistent build every time.
Simple, easy, and provides a good balance of centralized management and support for flexibility
What do you like best about the product?
It's been a robust, easy and flexible solution for builds on a bunch of different repos with mostly, but not entirely shared flows.
What do you dislike about the product?
Requires code changes to push updates, orb (module) versioning can be non-obvious.
What problems is the product solving and how is that benefiting you?
Automate builds for a variety of different apps, while reusing common modular components and as much common config as possible.
Easy, convenient and customisable CI/CD platform
What do you like best about the product?
It's a promising CI/CD pipeline for early detection of build errors in code.
Also, it gives failed or error notifications and can be easily configurable and is very user interactive
Also, it gives failed or error notifications and can be easily configurable and is very user interactive
What do you dislike about the product?
Even a small syntax error causes the pipeline to fail.
It will be good to have a tool to verify whether the code for circle ci is syntactically correct.
Also if CircleCI could make the deployment code run faster
It will be good to have a tool to verify whether the code for circle ci is syntactically correct.
Also if CircleCI could make the deployment code run faster
What problems is the product solving and how is that benefiting you?
CircleCI tests our code at all steps and ensures that our company doesn't do ship-breaking changes. It also helps in rectifying and troubleshooting the errors before they are made.
Great features and super easy to setup CI product
What do you like best about the product?
Their UI is great. Setting up the CI pipeline, with all the docker features and different options makes it a great option to have in you CI pipeline. We use it in all of our repositories and help us run all of our test with each commit and PR
What do you dislike about the product?
There's really nothing that comes to mind as something negative about CircleCI. Sometimes the CI setup requires some updating (some old versions stop beign supported, etc), but CircleCI makes it super easy
What problems is the product solving and how is that benefiting you?
CircleCi helps us to run all or our tests before deploying to production. When the test suite fails it makes it super easy to see the "artifacts" of the test run, screenshots, logs, etc, that help a lot to figure out what happened
excellent experience with circleci
What do you like best about the product?
The thing I like the most is the simplicity to connect to the server via ssh, restart failed jobs.
Pipeline creations is also easy, and connection with aws too.
Pipeline creations is also easy, and connection with aws too.
What do you dislike about the product?
Nothing in particular. Maybe the documentation could be improved and some more examples provided (my first attempts to use Circleci were difficult since the documentation was a bit difficult to understand and it was not easy to find examples).
What problems is the product solving and how is that benefiting you?
Implementing CI/CD is pretty easy with Circleci. In addition, the integration for aws are also great
showing 11 - 20