GHPRB Job DSL for pipelines breaks with Job DSL >= 1.70

GHPRB Job DSL for pipelines breaks with Job DSL >= 1.70

If I understand correctly, the GHPRB Job DSL example tracks the GitHub repo specified in the scm, git, remote context - see the example Job DSL below taken from the plugin site.

However, support for the scm{} context (and others) has been dropped for Pipeline Jobs in Job DSL 1.70 (see https://github.com/jenkinsci/job-dsl-plugin/wiki/Migration#migrating-to-170).

If scm{} is deprecated, it would seem that the remote for tracking must be specified some other way.

pipelineJob('example') {
    scm {
        git {
            remote {
                github('test-owner/test-project')
                refspec('+refs/pull/*:refs/remotes/origin/pr/*')
            }
            branch('${sha1}')
        }
    }
    triggers {
        githubPullRequest {
            admin('user_1')
            admins(['user_2', 'user_3'])
            userWhitelist('[e-mail]')
            userWhitelist(['[e-mail]', '[e-mail]'])
            orgWhitelist('my_github_org')
            orgWhitelist(['your_github_org', 'another_org'])
            cron('H/5 * * * *')
            triggerPhrase('OK to test')
            onlyTriggerPhrase()
            useGitHubHooks()
            permitAll()
            autoCloseFailedPullRequests()
            allowMembersOfWhitelistedOrgsAsAdmin()
            extensions {
                commitStatus {
                    context('deploy to staging site')
                    triggeredStatus('starting deployment to staging site...')
                    startedStatus('deploying to staging site...')
                    statusUrl('http://mystatussite.com/prs')
                    completedStatus('SUCCESS', 'All is well')
                    completedStatus('FAILURE', 'Something went wrong. Investigate!')
                    completedStatus('PENDING', 'still in progress...')
                    completedStatus('ERROR', 'Something went really wrong. Investigate!')
                }
            }
        }
    }
}

[jmbowman]

Having just helped diagnose a problem updating a pipeline job to seed correctly with a newer version of the Job DSL plugin, I think what you want is pipelineJob -> definition -> cpsScm -> scm. I’ve only tested it with Job DSL 1.67 so far, but it looks like it should continue working past the deprecation of the top-level scm context you’re worried about; all of those contexts are still present in the 1.70 documentation.

[nocode99]

@danielstoian you still get a deprecation warning