Github actions importer failing with Unable to locate credentials

[ppothakamuri]

Select Topic Area

Question

Body

I'm trying to migrate my Jenkins pipelines sitting in a gitlab repo using github actions importer, but the dry run command is failing with below error
[root@ip-10-xxx-7-xxx bin]# gh actions-importer dry-run jenkins --source-url https://jenkins.XXXX.com/customer_deploy/job/Scale_down_dev_instances/ --output-dir tmp/dry-run --no-ssl-verify
[2023-05-19 13:49:00] Logs: 'tmp/dry-run/log/valet-20230519-134900.log'
[2023-05-19 13:49:02] Unable to parse Jenkins pipeline (Scale_down_dev_instances)
Pipeline type: flow-definition
Message: Unable to locate credentials for 'http://xxxxxxx/awsdev-patching/customer_deploy.git'

please help me understand how github actions importer authenticates with other SCM's in order to migrate from Jenkins to Github workflows, in this case Jenkins pipelines residing in Gitlab repo.

[ashannon202]

Did you ever find a solution for this? I am facing the same issue

[mojeico]

You have to run - gh actions-importer configure to connect importer with Github and you current git server (in my case it was Gitlab)

[sxm-isolis]

@mojeico, the gh actions-importer configure accepts tokens for GitHub and Jenkins not for the SC/VCS that Jenkins is currently using. @ppothakamuri said their Jenkins pipelines clone code from GitLab. Mines from Bitbucket server.

I already tried saving credentials in ~/.git-credentials and in ~/.netrc. Git commands work fine, but I keep getting "Message: Unable to locate credentials for 'https://[REDACTED: BITBUCKET SERVER]:8443/scm/[REDACTED: PROJECT KEY]/[REDACTED: REPOSITORY NAME].git'"

Does anyone know how can we still use the gh actions-importer to convert our Jenkins pipelines?

[bisonlou]

when running gh actions-importer configure make sure to change the default GitHub instance URLs.
The default is https://github.com

change it by adding your account name

https://github.com/<account_name>

[tyrken]

In may vaguely similar issue github/gh-actions-importer#294 I managed to supply credentials using the --credentials-file argument, see https://docs.github.com/en/actions/migrating-to-github-actions/automated-migrations/supplemental-arguments-and-settings#using-a-credentials-file-for-authentication for the format