[JIRA] (JENKINS-61312) Unable to seed a pipeline job which has the BbS SCM step

12 views
Skip to first unread message

parameshj.sudhan@gmail.com (JIRA)

unread,
Mar 3, 2020, 12:26:03 PM3/3/20
to jenkinsc...@googlegroups.com
PJ updated an issue
 
Jenkins / Bug JENKINS-61312
Unable to seed a pipeline job which has the BbS SCM step
Change By: PJ
Attachment: groovy-bbs-scm.txt
Add Comment Add Comment
 
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
Atlassian logo

parameshj.sudhan@gmail.com (JIRA)

unread,
Mar 3, 2020, 12:26:04 PM3/3/20
to jenkinsc...@googlegroups.com
PJ created an issue
Issue Type: Bug Bug
Assignee: Kristy Hughes
Attachments: groovy-bbs-scm.txt
Components: atlassian-bitbucket-server-integration-plugin, job-dsl-plugin
Created: 2020-03-03 17:25
Environment: Jenkins- 2.204.2
BitBucket-Server-Integration Plugin: 1.1.0
job-dsl-plugin: 1.76
Priority: Blocker Blocker
Reporter: PJ

Unable to Seed a pipeline job when replacing the following in the groovy for the scm definition step and receive the following error 

When editing the job using the Jenkins UI and updating the all the appropriat fields, everything works perfectly. Just that the seed-job fails to read the groovy file to create a job. 

Attached is my groovy code for the SCM step.

Could you please advice if this is an issue with the dsl-plugin or with the Bitbucket-Server-Integration Plugin ?

Build Error: [hudson.AbortException: (job.groovy, line 50) No signature of method: javaposse.jobdsl.dsl.helpers.ScmContext.Bbs() is applicable for argument types: (<git-folder>$_run_closure1$_closure4$_closure6$_closure7$_closure8) values: [<git-folder>$_run_closure1$_closure4$_closure6$_closure7$_closure8@71df7e4c] Possible solutions: is(java.lang.Object), any(), git(groovy.lang.Closure), git(java.lang.String), hg(java.lang.String), rtc(groovy.lang.Closure)]

parameshj.sudhan@gmail.com (JIRA)

unread,
Mar 4, 2020, 4:54:02 PM3/4/20
to jenkinsc...@googlegroups.com
PJ updated an issue
Change By: PJ
Unable to Seed a pipeline job when replacing the following in the groovy for the git scm definition step with Bbs (as attached) and receive the following error 


When editing the job using the Jenkins UI and updating the all the appropriat fields, everything works perfectly. Just that the seed-job fails to read the groovy file to create a job. 


Attached is my groovy code for the SCM step.

Could you please advice if this is an issue with the dsl-plugin or with the Bitbucket-Server-Integration Plugin ?



{code:java}

Build Error: [hudson.AbortException: (job.groovy, line 50) No signature of method: javaposse.jobdsl.dsl.helpers.ScmContext.Bbs() is applicable for argument types: (<git-folder>$_run_closure1$_closure4$_closure6$_closure7$_closure8) values: [<git-folder>$_run_closure1$_closure4$_closure6$_closure7$_closure8@71df7e4c] Possible solutions: is(java.lang.Object), any(), git(groovy.lang.Closure), git(java.lang.String), hg(java.lang.String), rtc(groovy.lang.Closure)]

{code}

dkjellin@atlassian.com (JIRA)

unread,
Mar 15, 2020, 7:54:04 PM3/15/20
to jenkinsc...@googlegroups.com
Daniel Kjellin assigned an issue to Unassigned
Change By: Daniel Kjellin
Assignee: Kristy Hughes

mail@daniel-spilker.com (JIRA)

unread,
Mar 16, 2020, 4:01:02 PM3/16/20
to jenkinsc...@googlegroups.com

mail@daniel-spilker.com (JIRA)

unread,
Mar 16, 2020, 4:54:36 PM3/16/20
to jenkinsc...@googlegroups.com
Daniel Spilker updated Bug JENKINS-61312
 

Unfortunately the BitBucket Server plugin maintainers made a rather poor choice when picking the name, it BbS, not Bbs. The DSL is case sensitive.

pipelineJob('example') {
  definition {
    cpsScm {
      scm {
        BbS {
          id('id')
          branches {
            branchSpec {
              name('test')
            }
          }
          credentialsId('user')
          gitTool(null)
          mirrorName('')
          projectName('Proj')
          repositoryName('Repo')
          serverId('12345')
        }
      }
    }	
  }
}
Change By: Daniel Spilker
Status: Open Fixed but Unreleased
Resolution: Not A Defect
Reply all
Reply to author
Forward
0 new messages