-
Bug
-
Resolution: Fixed
-
Blocker
-
Jenkins ver. 2.190.2
bitbucket-branch-source-plugin: 2.6.0
Unfortunately with bitbucket-branch-source-plugin: 2.6.0 I can not make use of "traits" with job-dsl + configuration-as-code.
I used to be able to do the following:
organizationFolder('foo') { displayName('Foobar') organizations { bitbucket { serverUrl('https://stash.foobar.com') repoOwner('foo') credentialsId('stash-token') traits { sourceWildcardFilter { includes('sample-project') excludes('') } } } }
But now its not supported anymore. Also clearly visible via the api-viewer that that option is now missing.
Downgrading bitbucket-branch-source-plugin to 2.5.0 fixes the issue. So definitely a regression happening.
- is blocked by
-
-
- Open
-
- relates to
-
-
- Open
-
- links to
[JENKINS-60155] "traits" stopped working in 2.6.0
why do you consider configuration-as-code plugin to be one of the components involved with that? I can't see it, I may be wrong though - please explain or remove configuration-as-code - I'm afraid I can't help much so this has to be assigned to someone involved with bitbucket-branch-source I'm guessing
qalinn downgrading bitbucket-branch-source-plugin to 2.5.0 resolves the issue for me now.
ewel: this problem only occurs when using configuration-as-code + job-dsl in conjunction with Bitbucket org folder. I could not find anything in the changelog of the Bitbucket plugin that would indicate that the feature was removed deliberate. So I am assuming there is some incompatibility between the three involved plugins?
Updated the involved plugins as per https://github.com/jenkinsci/bitbucket-branch-source-plugin/issues/258#issuecomment-553405822
Hi, I managed to fix it in v2.7.0 so sorry for the long wait.
If you want faster fixes I suggest contributing to the plugin as a maintainer that does not use Bitbucket at all I have very little time to debug and fix the plugin.
I basically rely on the community to drive the plugin development.
I have the same issue.
Do you have any workaround?