fastlane vs Jenkins

Need advice about which tool to choose?Ask the StackShare community!

fastlane

650
433
+ 1
74
Jenkins

57.8K
49.3K
+ 1
2.2K
Add tool

Jenkins vs fastlane: What are the differences?

Differences between Jenkins and fastlane

Jenkins and fastlane are two popular tools used in software development for automating various processes. Here are the key differences between Jenkins and fastlane:

  1. Installation and setup: Jenkins is a Java-based tool, requiring a Java Runtime Environment (JRE) to be installed before it can be used. It can be installed on different operating systems such as Windows, Linux, and macOS. On the other hand, fastlane is a Ruby gem that requires Ruby to be installed, which can make the setup process slightly more complex for developers who are not familiar with Ruby.

  2. Supported platforms: Jenkins is a cross-platform tool, meaning it can be used on various operating systems like Windows, Linux, and macOS. It is highly flexible and can be integrated with different tools and services. Fastlane, on the other hand, is primarily focused on mobile app development and is specifically designed for iOS and Android platforms. It offers a wide range of features and tools specifically tailored for these platforms.

  3. Functionality: Jenkins is a powerful CI/CD (Continuous Integration/Continuous Deployment) tool that provides a wide range of features to automate build, test, and deployment processes. It can handle complex workflows and supports integration with various plugins to enhance its functionalities. Fastlane, on the other hand, is primarily focused on mobile app deployment processes. It provides a streamlined approach for automating common tasks like building, testing, and distributing mobile apps.

  4. Ease of use and learning curve: Jenkins has a steep learning curve, especially for developers who are new to the tool. It requires knowledge of scripting and configuration to set up and manage jobs or pipelines. Fastlane, on the other hand, has a more straightforward and intuitive approach, with a simplified configuration setup using a "Fastfile" that defines the automation tasks. It is relatively easier to learn and use, especially for developers working on mobile app development.

  5. Community support and plugins: Jenkins has a large and active community, with a wide range of plugins available for extending its functionalities. It has been around for many years and has a mature ecosystem supporting it. Fastlane also has a growing community, but it might not have the same level of extensive plugin support as Jenkins. However, fastlane provides a rich set of built-in tools and integrations specifically tailored for mobile app development.

  6. Integration with other tools: Jenkins is known for its flexibility in integrating with other tools and services, allowing developers to create customizable workflows and pipelines. It supports various version control systems, build tools, and issue tracking systems. Fastlane, on the other hand, offers native integrations with popular development tools like Xcode and Android Studio. It focuses on providing a streamlined experience for mobile app developers by integrating with the existing ecosystem of mobile app development tools.

In summary, Jenkins is a flexible CI/CD tool that can be used on multiple platforms and is highly customizable through plugins. On the other hand, fastlane is a specialized tool for mobile app development, providing a streamlined approach for automating common tasks in the iOS and Android app deployment process.

Advice on fastlane and Jenkins
Needs advice
on
Azure PipelinesAzure Pipelines
and
JenkinsJenkins

We are currently using Azure Pipelines for continous integration. Our applications are developed witn .NET framework. But when we look at the online Jenkins is the most widely used tool for continous integration. Can you please give me the advice which one is best to use for my case Azure pipeline or jenkins.

See more
Replies (1)
Recommends
on
GitHubGitHub

If your source code is on GitHub, also take a look at Github actions. https://github.com/features/actions

See more
Mohammad Hossein Amri
Chief Technology Officer at Planally · | 3 upvotes · 504.5K views
Needs advice
on
GoCDGoCD
and
JenkinsJenkins

I'm open to anything. just want something that break less and doesn't need me to pay for it, and can be hosted on Docker. our scripting language is powershell core. so it's better to support it. also we are building dotnet core in our pipeline, so if they have anything related that helps with the CI would be nice.

See more
Replies (1)
Ankit Malik
Software Developer at CloudCover · | 1 upvotes · 487.2K views
Recommends
on
Google Cloud BuildGoogle Cloud Build

Google cloud build can help you. It is hosted on cloud and also provide reasonable free quota.

See more
Needs advice
on
ConcourseConcourse
and
JenkinsJenkins

I'm planning to setup complete CD-CD setup for spark and python application which we are going to deploy in aws lambda and EMR Cluster. Which tool would be best one to choose. Since my company is trying to adopt to concourse i would like to understand what are the lack of capabilities concourse have . Thanks in advance !

See more
Replies (1)
Maxi Krone
Cloud Engineer at fme AG · | 2 upvotes · 406.2K views
Recommends
on
ConcourseConcourse

I would definetly recommend Concourse to you, as it is one of the most advanced modern methods of making CI/CD while Jenkins is an old monolithic dinosaur. Concourse itself is cloudnative and containerbased which helps you to build simple, high-performance and scalable CI/CD pipelines. In my opinion, the only lack of skills you have with Concourse is your own knowledge of how to build pipelines and automate things. Technincally there is no lack, i would even say you can extend it way more easily. But as a Con it is more easy to interact with Jenkins if you are only used to UIs. Concourse needs someone which is capable of using CLIs.

See more
Needs advice
on
JenkinsJenkinsTravis CITravis CI
and
CircleCICircleCI

From a StackShare Community member: "Currently we use Travis CI and have optimized it as much as we can so our builds are fairly quick. Our boss is all about redundancy so we are looking for another solution to fall back on in case Travis goes down and/or jacks prices way up (they were recently acquired). Could someone recommend which CI we should go with and if they have time, an explanation of how they're different?"

See more
Replies (6)
Dustin Falgout
Senior Developer at Elegant Themes · | 13 upvotes · 558.8K views

We use CircleCI because of the better value it provides in its plans. I'm sure we could have used Travis just as easily but we found CircleCI's pricing to be more reasonable. In the two years since we signed up, the service has improved. CircleCI is always innovating and iterating on their platform. We have been very satisfied.

See more
Peter Thomas
Distinguished Engineer at Intuit · | 9 upvotes · 869.8K views
Recommends
on
Travis CITravis CI
at

As the maintainer of the Karate DSL open-source project - I found Travis CI very easy to integrate into the GitHub workflow and it has been steady sailing for more than 2 years now ! It works well for Java / Apache Maven projects and we were able to configure it to use the latest Oracle JDK as per our needs. Thanks to the Travis CI team for this service to the open-source community !

See more
Recommends
on
Google Cloud BuildGoogle Cloud Build

I use Google Cloud Build because it's my first foray into the CICD world(loving it so far), and I wanted to work with something GCP native to avoid giving permissions to other SaaS tools like CircleCI and Travis CI.

I really like it because it's free for the first 120 minutes, and it's one of the few CICD tools that enterprises are open to using since it's contained within GCP.

One of the unique things is that it has the Kaniko cache, which speeds up builds by creating intermediate layers within the docker image vs. pushing the full thing from the start. Helpful when you're installing just a few additional dependencies.

Feel free to checkout an example: Cloudbuild Example

See more
Recommends
on
Travis CITravis CI

I use Travis CI because of various reasons - 1. Cloud based system so no dedicated server required, and you do not need to administrate it. 2. Easy YAML configuration. 3. Supports Major Programming Languages. 4. Support of build matrix 6. Supports AWS, Azure, Docker, Heroku, Google Cloud, Github Pages, PyPi and lot more. 7. Slack Notifications.

See more
Oded Arbel
Recommends
on
GitLab CIGitLab CI

You are probably looking at another hosted solution: Jenkins is a good tool but it way too work intensive to be used as just a backup solution.

I have good experience with Circle-CI, Codeship, Drone.io and Travis (as well as problematic experiences with all of them), but my go-to tool is Gitlab CI: simple, powerful and if you have problems with their limitations or pricing, you can always install runners somewhere and use Gitlab just for scheduling and management. Even if you don't host your git repository at Gitlab, you can have Gitlab pull changes automatically from wherever you repo lives.

See more
Recommends
on
BuildkiteBuildkite

If you are considering Jenkins I would recommend at least checking out Buildkite. The agents are self-hosted (like Jenkins) but the interface is hosted for you. It meshes up some of the things I like about hosted services (pipeline definitions in YAML, managed interface and authentication) with things I like about Jenkins (local customizable agent images, secrets only on own instances, custom agent level scripts, sizing instances to your needs).

See more
Decisions about fastlane and Jenkins

Jenkins is a pretty flexible, complete tool. Especially I love the possibility to configure jobs as a code with Jenkins pipelines.

CircleCI is well suited for small projects where the main task is to run continuous integration as quickly as possible. Travis CI is recommended primarily for open-source projects that need to be tested in different environments.

And for something a bit larger I prefer to use Jenkins because it is possible to make serious system configuration thereby different plugins. In Jenkins, I can change almost anything. But if you want to start the CI chain as soon as possible, Jenkins may not be the right choice.

See more
Get Advice from developers at your company using StackShare Enterprise. Sign up for StackShare Enterprise.
Learn More
Pros of fastlane
Pros of Jenkins
  • 20
    Easy to use
  • 13
    Open Source
  • 13
    Itunes connect deployment
  • 11
    Incredible flexability
  • 9
    Third party integrations
  • 3
    Provisioning profile management
  • 3
    Certificate management
  • 1
    All in one iOS DevOps
  • 1
    Can be used for Android as well
  • 0
    Integrate anything with fastlane
  • 523
    Hosted internally
  • 469
    Free open source
  • 318
    Great to build, deploy or launch anything async
  • 243
    Tons of integrations
  • 211
    Rich set of plugins with good documentation
  • 111
    Has support for build pipelines
  • 68
    Easy setup
  • 66
    It is open-source
  • 53
    Workflow plugin
  • 13
    Configuration as code
  • 12
    Very powerful tool
  • 11
    Many Plugins
  • 10
    Continuous Integration
  • 10
    Great flexibility
  • 9
    Git and Maven integration is better
  • 8
    100% free and open source
  • 7
    Slack Integration (plugin)
  • 7
    Github integration
  • 6
    Self-hosted GitLab Integration (plugin)
  • 6
    Easy customisation
  • 5
    Pipeline API
  • 5
    Docker support
  • 4
    Fast builds
  • 4
    Hosted Externally
  • 4
    Excellent docker integration
  • 4
    Platform idnependency
  • 3
    AWS Integration
  • 3
    JOBDSL
  • 3
    It's Everywhere
  • 3
    Customizable
  • 3
    Can be run as a Docker container
  • 3
    It`w worked
  • 2
    Loose Coupling
  • 2
    NodeJS Support
  • 2
    Build PR Branch Only
  • 2
    Easily extendable with seamless integration
  • 2
    PHP Support
  • 2
    Ruby/Rails Support
  • 2
    Universal controller

Sign up to add or upvote prosMake informed product decisions

Cons of fastlane
Cons of Jenkins
    Be the first to leave a con
    • 13
      Workarounds needed for basic requirements
    • 10
      Groovy with cumbersome syntax
    • 8
      Plugins compatibility issues
    • 7
      Lack of support
    • 7
      Limited abilities with declarative pipelines
    • 5
      No YAML syntax
    • 4
      Too tied to plugins versions

    Sign up to add or upvote consMake informed product decisions

    What is fastlane?

    fastlane lets you define and run your deployment pipelines for different environments. It helps you unify your app’s release process and automate the whole process. fastlane connects all fastlane tools and third party tools, like CocoaPods.

    What is Jenkins?

    In a nutshell Jenkins CI is the leading open-source continuous integration server. Built with Java, it provides over 300 plugins to support building and testing virtually any project.

    Need advice about which tool to choose?Ask the StackShare community!

    What companies use fastlane?
    What companies use Jenkins?
    See which teams inside your own company are using fastlane or Jenkins.
    Sign up for StackShare EnterpriseLearn More

    Sign up to get full access to all the companiesMake informed product decisions

    What tools integrate with fastlane?
    What tools integrate with Jenkins?

    Sign up to get full access to all the tool integrationsMake informed product decisions

    Blog Posts

    Mar 24 2021 at 12:57PM

    Pinterest

    GitJenkinsKafka+7
    3
    2162
    GitJenkinsGroovy+4
    4
    2690
    Dec 4 2019 at 8:01PM

    Pinterest

    KubernetesJenkinsTensorFlow+4
    5
    3290
    GitHubPythonNode.js+47
    55
    72435
    GitGitHubPython+22
    17
    14231
    JavaScriptGitHubPython+42
    53
    21957
    What are some alternatives to fastlane and Jenkins?
    HockeyApp
    HockeyApp is the best way to collect live crash reports, get feedback from your users, distribute your betas, and analyze your test coverage.
    Bitrise
    It is a Continous Integration and Delivery (CI/CD) Platform as a Service (PaaS) with a main focus on mobile app development (iOS, Android). You can automate the testing and deployment of your apps with just a few clicks. When you trigger a build a Virtual Machine is assigned to host your build and your defined Workflow (series of Steps scripts) will be executed, step by step.
    Firebase
    Firebase is a cloud service designed to power real-time, collaborative applications. Simply add the Firebase library to your application to gain access to a shared data structure; any changes you make to that data are automatically synchronized with the Firebase cloud and with other clients within milliseconds.
    CircleCI
    Continuous integration and delivery platform helps software teams rapidly release code with confidence by automating the build, test, and deploy process. Offers a modern software development platform that lets teams ramp.
    TestFlight
    With TestFlight, developers simply upload a build, and the testers can install it directly from their device, over the air.
    See all alternatives