Jenkins [skip ci] implementation for multi-branch declarative pipeline

Jenkinsfile

// change 'agent' lines as appropriate

pipeline {
  agent none

  stages {
    
    stage('Run CI?') {
      agent any
      steps {
        script {
          if (sh(script: "git log -1 --pretty=%B | fgrep -ie '[skip ci]' -e '[ci skip]'", returnStatus: true) == 0) {
            currentBuild.result = 'NOT_BUILT'
            error 'Aborting because commit message contains [skip ci]'
          }
        }
      }
    }

    stage('next stage') {
      agent { dockerfile true }
      steps {
        echo 'next stage here...'
      }
    }

  }
}

You're a hero 🦸

@tylerlwsmith 😄 IIRC this has difficulty with squashed commits and/or pushing several commits at once, some of which have [skip ci]. So watch out for that!

Good to know, thank you 😁

I just stumbled across this, and if anyone's wondering about addressing multiple pushed commits, this SO answer is a fantastic resource for traversing all commit messages instead of just the first:
https://stackoverflow.com/a/60390768/3405140

def getChangesSinceLastSuccessfulBuild() {
    def changes = []
    def build = currentBuild

    while (build != null && build.result != 'SUCCESS') {
        changes += (build.changeSets.collect { changeSet ->
            (changeSet.items.collect { item ->
                (item.affectedFiles.collect { affectedFile ->
                    affectedFile.path
                }).flatten()
            }).flatten()
        }).flatten()

        build = build.previousBuild
    }

    return changes.unique()
}

Thank you for that @moertel!