Request for Information

[mrpepik]

Greetings,

I am working on implementing your solution in my environment, but I do not see an example or notes in the Readme to reference what you mean by this code:

lines 53 to 57 Run.swift

`@Argument(help: "The path to the script that GitLab Runner creates for the executor to run.")
var scriptFile: Path`

`@Argument(help: "The name of the sub-stage provided to the executor by the GitLab Runner.")
var subStage: String`

Can you give some more explanation on this section? Is it just expecting the gitlab-ci.yml file name and the custom runner 'build_script' stage?

Thanks in advance for any info you can help me with.

[RLovelett]

The Run.swift is the code that backs the run subcommand meant to be used by the GitLab Runner's run_exec stage. The location relevant to this is in the README.md in the run section.

The .gitlab-ci.yml file is used to configure jobs and not runners; likewise the same is true for the build_script stage in said file. The configuration of a custom executor is meant to happen at the GitLab Runner config.toml level. I suggest you read GitLab's documentation on the custom executor.

Also, an excerpt from an example config.toml is provided at the very end of the README.md for this project.

[mrpepik]

Hey Ryan,

Thank you for the reply, I got the error about needing the script  and sub job while trying to run gitlab-fusion run manually.  After getting your reply and thinking about it, I realized that I was not taking into account that the gitlab custom runner, adds the script and sub job as variable $1 and $2 when it calls the run script specified in the run_exec cmd.

Once I get the rest of my environment up and running, I will let gitlab call the entire process via the runner job natively and just make sure things work like I want them too.

Thanks again for the reply.

Joe