Ability to convert JenkinsFile to GitHub actions offline

[ilyesAj]

why ?
In some environments where the connectivity is limited, we should be able to convert any Jenkinsfile to GitHub actions

what ?
Dry-run command should run without the need to specify --jenkins-instance-url or --source-url . you should not need to authenticate to GitHub actions.

expected:

gh actions-importer dry-run jenkins --source-file-path backend/deployment/Jenkinsfile -o output

-> the result would be to output the converted file

[ethanis]

@ilyesAj a connection to the Jenkins server is required, even when using the --source-file-path option, so that Actions Importer can convert the Jenkinsfile contents to a JSON object that can then be converted to its equivalent workflow using this endpoint.

[OpenByteDev]

that requirement seems very odd to me