issue with building project
Closed this issue · 4 comments
esshab commented
[azureuser@mgt Viya4]$ docker build github.com/sassoftware/viya4-orders-cli -t viya4-orders-cli
unable to prepare context: unable to 'git clone' to temporary context directory: Error trying to use git: exit status 128 (Cloning into '/tmp/docker-build-git267569601'...
git: 'remote-https' is not a git command. See 'git --help'.
)
sarahcpage commented
Hi, what version of Git are you using? Is git-remote-https.exe present in your Git installation?
esshab commented
[azureuser@mgt ~]$ git --version
git version 2.30.0
also from this instruction where I get the 923456_lts_depassets.tgz?
What should I include the configuration file..the API and Scret?
Can you provide a sample yml configuration file?
Using a configuration file, /c/Users/auser/vocli/.viya4-orders-cli.yaml, to convey your API credentials, get deployment assets for SAS Viya order 923456 at the latest version of the Long Term Support (lts) cadence. Send the contents to file /c/Users/auser/vocli/sasfiles/923456_lts_depassets.tgz:
Regards,
Esmat Shabon
Sr. Solution Advisor
Fraud and Security Intelligence
Phone: ( 571) 499-1755
Esmat.shabon@sas.com<mailto:Esmat.shabon@sas.com>
From: Sarah Page <notifications@github.com>
Sent: Monday, February 08, 2021 11:24 AM
To: sassoftware/viya4-orders-cli <viya4-orders-cli@noreply.github.com>
Cc: Esmat Shabon <Esmat.Shabon@sas.com>; Author <author@noreply.github.com>
Subject: Re: [sassoftware/viya4-orders-cli] issue with building project (#8)
EXTERNAL
Hi, what version of Git are you using? Is git-remote-https.exe present in your Git installation?
-
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub<https://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fsassoftware%2Fviya4-orders-cli%2Fissues%2F8%23issuecomment-775265688&data=04%7C01%7Cesmat.shabon%40sas.com%7Cce7efaf60e744f7c43cb08d8cc4de693%7Cb1c14d5c362545b3a4309552373a0c2f%7C0%7C0%7C637483982247440016%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=c7TgodG76QxRh9BYHEGERvilEF3mSndQgt2itocn1Go%3D&reserved=0>, or unsubscribe<https://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAM42JVOWTKOOYYYBK4ST2BDS6AFY3ANCNFSM4XJH3PNQ&data=04%7C01%7Cesmat.shabon%40sas.com%7Cce7efaf60e744f7c43cb08d8cc4de693%7Cb1c14d5c362545b3a4309552373a0c2f%7C0%7C0%7C637483982247450014%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=W32pwmRCYCdERReQL89Cdg7tMRfm5OPkR%2Fq4wIK977M%3D&reserved=0>.
sarahcpage commented
Is git-remote-https.exe present in your Git installation?
From the README.md on the project homepage in GitHub:
sarahcpage commented
user had bad git installation - closing