TL;DR: Caching the Library folder can significantly speed up your Unity builds in CI/CD environments. Codemagic CI/CD also allows you to cache the Unity version of your project so that you don’t need to re-download it each time. When you work on complex Unity projects and start adding more and more resources, you’ll quickly notice that the build times in your Codemagic workflow grow as well.
The world is facing the highest inflation rate in ages, and Codemagic is reacting to it by… lowering its prices. These are tough times for everybody, and because we’ve benefited from some recent changes, we wanted to pass on these benefits to all developers so that you have one less thing to worry about.
In this era of collaborative development in the cloud, local development makes it easy to iterate and build new features quickly. You can also make different versions of your projects very quickly to test new features in the local machine without affecting the production build.
Since Apple started using SwiftUI in its operating systems, it has been experiencing a noticeable evolution, from redesigns of apps to deep system integrations. The team behind SwiftUI has taken into account the feedback they got on Twitter and other social networking sites, resulting in some fantastic APIs to work and play with this year! Here’s a quote from the session on “What’s new in SwiftUI”: So, let’s dive into everything that SwiftUI 4.0 has to offer you!
We received a lot of questions during our Build Pipelines webinar in July, so in this article, you'll read part 1 of the Q&A about Build Pipelines and rerunning workflows, stages, or pipelines.
TL;DR: It’s critical to deliver the latest builds of your Unity game to testers and stakeholders. You can automate this process by setting up a Codemagic CI/CD pipeline and either using public Codemagic dashboards to access build artifacts or setting up notifications in Discord with links to builds and release notes. Let’s see how we can use automation tools to share our game builds with QA testers and stakeholders!
The pace of the industry today is pressuring software developers to build, test, and release software more frequently than ever. To achieve this pace, teams have built two core processes into their workflow: Continuous Integration and Continuous Deployment. Continuous Integration and Continuous Deployment (CI/CD) is a subset of the DevOps workflow that automates application code management and its safe, predictable shipping. In this article, we’ll take a deep dive into CI/CD.
In this article, we will walk you through steps to run a Jenkins server in docker and deploy the MLRun project using Jenkins pipeline. Before we dive into the actual set up, let’s have a brief background on the MLRun and Jenkins.
Improving your app’s user engagement is key to its success. One way to prevent churn and increase interactions in your Flutter app is by using notifications. Push notifications are pop-up messages that are displayed outside the app’s UI. These messages can appear when the app is closed or in the background. Push notifications are used to get users’ attention and communicate information to them.
