-
Dear owners, first of all: I'm super excited about the actions importer! It has the potential to be an absolute game changer on our current journey. We're migrating 1000+ projects from Bitbucket+Jenkins to GitHub. So currently the Jenkins pipelines we need to migrate are all configured to get their code and Jenkinsfiles from Bitbucket. After some first tests I'm running into issues with our Jenkins Multibranch pipelines. I assume the actions importer currently is built for teams who have already been using GitHub as their code repository and now just want to move their CI/CD part to GitHub as well. However I think for many GitHub Enterprise customers it would be a big win to also be able to import Jenkins pipelines with other source types. Maybe I'm wrong with my assumption and I'm just doing something wrong, that would make me very happy :) so any hints welcome! BR Christina |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 2 replies
-
Hello @chrissike Github Actions Importer currently only supports Bitbucket Server when using Bitbucket as a source for Jenkins files. If I understand currently your Jenkins file are currently in Bitbucket (not Server) and that is unfortunately not supported right now. Here are some docs on how to configure a credentials file for authenticating to Bitbucket Server if that ever becomes handy for you. |
Beta Was this translation helpful? Give feedback.
Hello @chrissike
Github Actions Importer currently only supports Bitbucket Server when using Bitbucket as a source for Jenkins files. If I understand currently your Jenkins file are currently in Bitbucket (not Server) and that is unfortunately not supported right now.
Here are some docs on how to configure a credentials file for authenticating to Bitbucket Server if that ever becomes handy for you.