Details
-
Bug
-
Status: Closed (View Workflow)
-
Minor
-
Resolution: Duplicate
-
Jenkins: 2.60.2
workflow-multibranch-plugin: 1.16
git-plugin: 3.4.1
job-dsl-plugin: 1.64
Description
In the past I used `gitSCMSource` to specify my git configuration with extensions in my Job DSL.
Template I used:
multibranchPipelineJob('${JOB_NAME}') { displayName('${JOB_NAME}') description('${JOB_DESCRIPTION}') orphanedItemStrategy { discardOldItems { numToKeep(7) } } branchSources { branchSource { source { gitSCMSource { id('') remoteName('origin') rawRefSpecs('') ignoreOnPushNotifications(false) remote('${JOB_GIT_URL}') credentialsId('${GIT_CREDENTIALS_ID}') includes('*') excludes('') extensions { wipeWorkspace() preBuildMerge { options { mergeRemote('origin') mergeTarget('${GIT_BRANCH}') mergeStrategy('default') fastForwardMode('FF') } } } } } } } }
Now after updating to latest Jenkins/Plugins this no longer works. I looked at using the `git` source instead of `gitSCMSource` but it does not provide a way to set the extensions.
In the new git-plugin 3.4.0 extensions are deprecated and are now traits. Not sure if this has anything to do with the issue.
Attachments
Issue Links
- duplicates
-
JENKINS-45504 Add @Symbol annotations to traits
-
- Closed
-
- is related to
-
-
- Closed
-
Activity
Sam Gleske
added a comment - Added git-plugin since the git-plugin should define "@Symbol" for its classes to help with the DSL generation to be unique.
Sam Gleske
added a comment - Added git-plugin since the git-plugin should define "@Symbol" for its classes to help with the DSL generation to be unique. Sam Gleske
added a comment - https://github.com/jenkinsci/git-plugin/pull/595 
Steffen Gebert
added a comment - sag47 , thanks for bringing this forward! Sam Gleske
added a comment - You're welcome. 
Sure, I can put my frustration in check. My intent wasn't to be hostile nor to imply it was done on purpose (it would be odd to assume that it's on purpose).