runs-on and GithubRunner

[ismailhafid1]

Hello , i need more info about runs-on and GithubRunner,
we want to build our own AzureVM to reduce the generation time for our CI/CD builds , PR build ,next minor and next major , each one of them takes 20 to 25 minutes to get completed , and if a CICD fails , run it again and it will take another 20 minutes which is time consuming and costs a lot , so after some exploration i found that there is a parameter runs-on that will help us use our own AzureVM to run our workflows to reduce the time consomation , but i stumbled upon something that i need to understand , the "githubRunner" parameter and it is used for build/test jobs, which require more memory and a container , however the runs-on is for non build/test jobs which is clear but :

• can 1 AzureVM be used for both jobs ? (test/build (CICD PR) + non test/build(Next Major/Minor))
• does the runs-on ovrride the GithubRunner parameter ? if yes , do i need to have a specific configuration to run both job types ?
  -if i use my own AzureVM how much time can i save from the 20min build run ?

[aholstrup1]

can 1 AzureVM be used for both jobs ? (test/build (CICD PR) + non test/build(Next Major/Minor))

Yes

does the runs-on ovrride the GithubRunner parameter ? if yes , do i need to have a specific configuration to run both job types ?

Not exactly. If you don't specify the GitHubRunner setting then AL-Go will use your runs-on setting. As long as you have the GitHubRunner setting in your AL-Go settings files, it won't be overwritten by the runs-on setting.

Note: If you change the runs-on setting, you need to run "Update AL-Go System Files" before it takes effect.

if i use my own AzureVM how much time can i save from the 20min build run ?

I don't think this is really something we can answer. It likely depends on a number of factors like what hardware you're running on.