Why should I create custom script step:

While Bitrise provides hundreds of pre-made workflow steps for the most frequent use cases, we can't cover every possible scenario, so customer scripts may be required from time to time. Bitrise offers the Script Step (the default is Bash), which enables you to write code in the programming language of your choice to complete the task.

Following is the list of custom script example running in Bash, Python, NodeJS, Ruby, Swift, Kotlin:

Bash

Script Content

echo "Hello World!"

Command to Run

/bin/bash

Filename of Script (Not Required)

Running this results in

Python

Script Content

print('Hello, World!')

Command to Run

python

Filename of Script

index.py

Results in the following command running

python index.py

• Where the contents of index.py is print('Hello, World!')

Running this results in

NodeJS

Script Content

console.log("Hello World NodeJS");

Command to Run

node

Filename of Script

index.js

Results in the following command running

node index.js

• Where the contents of index.js is console.log("Hello World NodeJS");

Running this results in

Ruby

Script Content

puts "Hello, World!"

Command to Run

ruby

Filename of Script

index.rb

Results in the following command running

ruby index.rb

• Where the contents of index.rb is puts "Hello, World!"

Running this results in

 

Compiled Languages

Swift

Script Content

cat <<EOT >> hello.swift
  print("Hello World")
EOT

chmod u+x hello.swift

swift hello.swift

Command to Run

/bin/bash

Filename of Script (Not Required)

Running this results in

Kotlin

Script Content

brew install kotlin

cat <<EOT >> main.kt
  fun main() {
    println("Hello, World!")
  }
EOT

chmod 777 main.kt

kotlinc main.kt -include-runtime -d hello.jar

java -jar hello.jar

Command to Run

/bin/bash

Filename of Script (Not Required)

Running this results in

JFrog Announcements

• Initial Announcement 2/3/2021: To streamline the productivity of the JFrog Platform we will be sunsetting Bintray, GoCenter, and ChartCenter services on May 1st, 2021. Bintray helped JFrog support the Java community as the host of the JCenter repository for Java OSS libraries, packages and components.

• UPDATE 4/27/2021: We listened to the community and will keep JCenter as a read-only repository indefinitely. Our customers and the community can continue to rely on JCenter as a reliable mirror for Java packages.

• UPDATE 2/28/2021: To better support the community in this migration, JFrog has extended the JCenter new package versions submission deadline through March 31st 2021.

See: https://jfrog.com/blog/into-the-sunset-bintray-jcenter-gocenter-and-chartcenter/

How to migrate from JCenter

Because the builds that use JCenter will be able to resolve dependencies until February 1, 2022 without changes. After that date, there are no guarantees that you will be able to build your software if you continue to use JCenter.

How to migrate from JCenter to Maven Central CDN

• Remove JCenter from your build.gradle and replace it with Maven Central CDN url

buildscript {
  repositories {
    //jcenter()
    mavenCentral()
    maven {
      url "https://repo1.maven.org/"
    }
    google()
  }
}

allprojects{
  repositories {
    //jcenter()
    mavenCentral()
    maven {
      url "https://repo1.maven.org/"
    }
    google()
  }
}

Verify your changes

• Run your Bitrise build with the new code changes to confirm everything works as expected.

Maven Central vs Maven Central CDN Uptime

Although JCenter is still available, it is unreliable and Maven Central CDN is a far better choice with 100% uptime. Maven Central without CDN can be down from time to time.

Maven Central - 99.98% Uptime

• https://repo.maven.apache.org/maven2/

Maven Central CDN - 100% Uptime

• https://repo1.maven.org/maven2/