We’re learning how to move faster with Drupal, moving changes from a dev’s laptop to production quickly while maintaining (if not increasing) quality. In part 1 of this Continuous Drupal series, we covered how to get up and running with Drupal using a modern toolset. In this post we’re going to continue where part 1 left off and bring our Drupal website into CircleCI. We’ll run QA tests on the site to make sure everything is running as expected, and optionally PHPUnit test for custom modules or themes we may have. Let’s dive in.
I started at CircleCI HQ in San Francisco as a Solutions Engineer this past August. With a job history of working at much larger companies such as eBay and PayPal, being at a start-up was a big change for me.
And so I found myself grappling with a new problem: how to onboard. I was more accustomed to super structured week-long (or even longer) onboarding formats, which I had found to be dry and data-heavy.
At CircleCI, the culture is very remote friendly. My manager Kevin lives in Seattle and works remotely from there. I have co-workers on my team based out of New York and Colorado. For my first week, Kevin traveled down to the San Francisco office to welcome me and to kick off the onboarding process. It was really helpful to have some 1:1 training time and to get some suggestions on what areas to continue focusing my time on. Solutions Engineers lead the technical implementation and day-to-day management of CircleCI Trials, ensuring early customer success and a long-term business relationship. New hires in this role often start with a week on support duty to help learn the product.
After the newness and excitement of my first week, I felt a little unsure of the best way to soak up more CircleCI tribal know-how. There were plenty of people who could answer any technical questions I might have, but during those beginning days and weeks I didn’t always know quite what (or whom) to ask.
Starting today, CircleCI 2.0 is available for customers building applications for iOS, macOS, tvOS, or watchOS. Teams building for Apple devices can now access Workflows to customize their app delivery pipeline, build for Apple platforms, Android, and Linux using a single configuration file, and have complete control over their Xcode versions.
Developers can now also schedule jobs, making tasks like simultaneously updating apps across all operating systems in the App Store and Google Play Store easy.
We’ve recently been exploring signals around engineering productivity in order to share metrics teams can look at to know if they are on the right track (the results of our research here). We were surprised and deighted when our research revealed that Code For America was leading the pack in measures of engineering velocity. We spoke to two members of their team, John O’Duinn and Ben Sheldon, to learn more about how a non-profit focused on delivering services for the public sector is able to maintain incredible speed and engineering productivity.
The Python Package Index commonly known as PyPI is a repository of software for the Python programming langauge. Every time you run
pip install $PACKAGEyou are using PyPI. In this post, you will learn how to continuously deploy your own Python packages to PyPI using git tags and CircleCI.
Over the last few weeks, I have been working on a Python wrapper for the CircleCI API. This project uses the same approach that we are going to be discussing here.
Many moons ago, I use to host a Drupal website on GoDaddy Shared Hosting, managing files with FTP and duplicating the MySQL database every once in awhile as “backups”. How many things wrong can you find in that sentence? In 2017, there are many tools and best practices that allow us to maintain a Drupal site efficiently and scale across team members as well as infrastructure. Starting a Drupal website today using these tools and practices allows developing with Drupal to happen with increased velocity. Furthermore, if you decide to implement CI into your Drupal site later on, having your site set up with this stack will make that possible.
In this first post of a three-part series, we’re going to cover how we can use Docker, Git, Composer, and Drush to maintain a Drupal 8 website intelligently and efficiently.
In CircleCI 2.0, teams now have more flexibility than ever in how they choose to run Workflows. Your jobs can be complex (or as simple as you’d like) and jobs don’t necessarily run sequentially.
When we delivered Workflows, we wanted to offer you a way to break up your jobs and choose when and how you’d like to orchestrate your configurations. BUT you were still stuck– it was still up to you to figure out a way to run your jobs in a way that doesn’t break anything, or that you’re not wasting time waiting for them to run. You were forced to make many separate decisions about how and when to run jobs, even jobs you ran daily.
Google Chrome is the most-used browser on the Internet. And people are creating Chrome Extensions for all kinds of use-cases. Within 24 hours of Twitter announcing their 280 character tweets test, a new Chrome Extension collapsing tweets back to 140 characters was born. Within days of the hurricane in Puerto Rico, a $0.99 extension called Donate to Puerto Rico was created, showcasing beautiful images of the island, with all proceeds going towards charities helping rehabilitate the island.
In a space that moves this quickly, we can automate the delivery of features, bug fixes, and security patches with Continuous Deployment. Google’s Chrome Developer Docs has a lot of information but doesn’t include anything on Continuous Integration or provide examples for automated deployment. We’ll cover one example in this post along with how we can tackle development environment challenges and versioning.
What follows is a letter to potential CircleCI employees, from our Head of Human Resources, David Mann.
Dear CircleCI Candidates,
I wanted to share our philosophy and standards around the hiring process to give you more clarity about what you should expect from us, and what we’ll look for from you.
Overall, know this: we respect you. And we’re honored you’re interested in joining our team.
To make the interview flow go smoothly, we have some standards we live by. We’re not perfect, but we do our best to make the getting-to-know-each-other process as enjoyable as possible. And as you consider joining our team, I want to share with you the thinking behind our methodology.