-
-
Notifications
You must be signed in to change notification settings - Fork 74
Integration of docker update into CSGO CI/CD pipeline #17
Comments
Hey @sasanmcp, the images used to hold the entirety of the CS:GO dedicated server a couple of months ago (about 17-20GB) which made the entire image unpractical to pull, because you would need to spend 15 minutes extracting it (and then having to update to the latest version). The current version of the image is only steamcmd with the entry script, building it periodically to keep it up to date is not going to change much, the only difference will probably be the initial steamcmd update which is negligible. Even if you hook it to the CSGO update cycle via the steam webapi or steamdb it's still going to remain in the same state after it was rebuild (only steamcmd will be updated). So I don't really see a reason why it should be done. |
You're right. After 2nd thought it makes sense the way it is. However, I should find a way to make it persistent. I am trying to get it running in Azure Container Instances and each time I stop/start or restart it I have to wait 20 mins to bring it up to speed.
Get Outlook for Android<https://aka.ms/ghei36>
…________________________________
From: Walentin L. <notifications@github.com>
Sent: Wednesday, May 6, 2020 12:21:44 PM
To: CM2Walki/CSGO <CSGO@noreply.github.com>
Cc: Sassan Hajrasooliha <Sasan_hj@hotmail.com>; Mention <mention@noreply.github.com>
Subject: Re: [CM2Walki/CSGO] Integration of docker update into CSGO CI/CD pipeline (#17)
Hey @sasanmcp<https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fsasanmcp&data=02%7C01%7C%7C1f7397a8b6bd4cba0b1308d7f1f2b75d%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637243897063142571&sdata=D0owxFZ2tm8RgaZ4kFvnm1dt9qas27OkFSUNST7pU%2FU%3D&reserved=0>,
the images used to hold the entirety of the CS:GO dedicated server a couple of months ago (about 17-20GB) which made the entire image unpractical to pull, because you would need to spend 15 minutes extracting it (and then having to update to the latest version).
The current version of the image is only steamcmd with the entry script, building it periodically to keep it up to date is not going to change much, the only difference will probably be the initial steamcmd update which is negligible.
Even if you hook it to the CSGO update cycle via the steam webapi or steamdb it's still going to remain in the same state after it was rebuild (only steamcmd will be updated).
So I don't really see a reason why it should be done.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FCM2Walki%2FCSGO%2Fissues%2F17%23issuecomment-624840863&data=02%7C01%7C%7C1f7397a8b6bd4cba0b1308d7f1f2b75d%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637243897063152571&sdata=7wWqZF7x8oR5R2JnhoSs5l00PLxUAC8%2BOr8AAKWUa3g%3D&reserved=0>, or unsubscribe<https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAJXJYF76CUYZTPVUMYE27F3RQG2ERANCNFSM4M2BTX6Q&data=02%7C01%7C%7C1f7397a8b6bd4cba0b1308d7f1f2b75d%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637243897063162567&sdata=fk%2BBy%2F25DJKkyZUAbXWSPo%2BWoFGiI8W3LbsGX3UI2HU%3D&reserved=0>.
|
I could think of a way. Use a local network private registry that has compression disabled (so you don't have to extract the image again for 15 minutes). Commit your fully built docker images there (using docker commit / build & docker push). Then just run from that registry, this approach is obviously quiet bandwidth heavy but it should cut your deployment time. |
guys;
right now when I run the docker image, it takes quite a while for entry.sh to update the container with new binaries before the server is actually up and running.
I am thinking maybe it is a better idea to add a routine to the actual CSGO CI/CD pipelines so that whenever they release a new binary for it, this docker image is also updated along with that and tagged with "latest".
to be transparent, I just fetch "cm2network/csgo" image and not "cm2network/csgo:latest" but I don't think that would make any change in my experience.
The text was updated successfully, but these errors were encountered: