How CircleCI Processes 4.5M Builds per Month
stackshare.io
How CircleCI Processes 4.5M Builds per Month
1–10 of 89 posts
Re: How CircleCI Processes 4.5M Builds per Month
#2We are using GitLab CI, and it seems majority of the features of CircleCI are already provided in GitLab CI. Can someone with experience with CircleCI and GitLab CI to talk about some differences?
Re: How CircleCI Processes 4.5M Builds per Month
#3 URGENT LOAN HELP @ 2% INTEREST RATE with Victoriafinancier@outlook.com
I was stuck in a financial situation and i needed to refinance and pay my bills for my son's medication and buy a home. I tried seeking for a loans from various loan firms both private and corporate but never with success, and most banks declined my credit. But as God would have it, i was introduced to VICTORIA LAWSON Trust Loan Firm ( victoriafinancier@outlook.com ) with 2% interest by a friend, and i got a loan amount within 2 weeks because i was not always online to responds to her mails. Today am a business owner and my kids are doing well... so i want to advice any one in need of a loan to quickly contact her via email on victoriafinancier@outlook.com. I own Victoria every day appreciation for all she has done in my life. Her service is strong, big and reliable.
Address:_________
Tell:_________
loan amount:_________
Loan duration:_________
Country:_________
Purpose of loan:_________
Monthly Income:__________
Occupation__________
Next of kin:_________
*Email :_________
Contact Her today { victoriafinancier@outlook.com } for quick and financial assistance
Re: How CircleCI Processes 4.5M Builds per Month
#4This post makes no mention of the macOS part of the CircleCI infrastructure, which is one of the trickiest parts of infrastructure IMHO. Tricky because Apple's EULA prevents virtualizing on anything other than its hardware, never more than 4 VMs per host, and not for commercial purposes...
Re: How CircleCI Processes 4.5M Builds per Month
#5Some of our builds are running on CircleCI but have been trying out drone for a more container focused build. Been enjoying the flexibility and increased speed from custom build images which are trivial to make.
Re: How CircleCI Processes 4.5M Builds per Month
#6Some of our builds are running on CircleCI but have been trying out drone for a more container focused build. Been enjoying the flexibility and increased speed from custom build images which are trivial to make.
I feel like http://concourse.ci/ might be the sweet spot here.
Re: How CircleCI Processes 4.5M Builds per Month
#7This post makes no mention of the macOS part of the CircleCI infrastructure, which is one of the trickiest parts of infrastructure IMHO. Tricky because Apple's EULA prevents virtualizing on anything other than its hardware, never more than 4 VMs per host, and not for commercial purposes...
What's the commercial usage limitation? Is that specifically for virtualization of OSX to prevent offering a "Mac On Demand" by not letting you run the OS itself?
Re: How CircleCI Processes 4.5M Builds per Month
#8CircleCI rocks. Our tests ran almost as fast as they do on a MacBook. And their pricing is great.
Of course, that was after trying to get shippable to work.
Re: How CircleCI Processes 4.5M Builds per Month
#9Some of our builds are running on CircleCI but have been trying out drone for a more container focused build. Been enjoying the flexibility and increased speed from custom build images which are trivial to make.
CircleCi 2.0 left beta last week and is fully docker based
Re: How CircleCI Processes 4.5M Builds per Month
#10This post makes no mention of the macOS part of the CircleCI infrastructure, which is one of the trickiest parts of infrastructure IMHO. Tricky because Apple's EULA prevents virtualizing on anything other than its hardware, never more than 4 VMs per host, and not for commercial purposes...
What's the commercial usage limitation? Is that specifically for virtualization of OSX to prevent offering a "Mac On Demand" by not letting you run the OS itself?
Turns out it's two, not four VMs. From macOS Sierra's EULA[0]:
> (iii) to install, use and run up to two (2) additional copies or instances of the Apple Software within virtual operating system environments on each Mac Computer you own or control that is already running the Apple Software, for purposes of: (a) software development; (b) testing during software development; (c) using macOS Server; or (d) personal, non-commercial use.