User Tools

Site Tools


gamedev:gameci

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
gamedev:gameci [2022/07/01 16:43] – [Docker] dragonlordgamedev:gameci [2022/07/01 16:55] (current) – [Jenkins] dragonlord
Line 32: Line 32:
  
 ===== Docker ===== ===== Docker =====
 +{{ :gamedev:docker.png?direct |Docker Logo}}
  
 A docker image is ready made to be used: [[https://hub.docker.com/repository/docker/lordofdragons/deigde-ci|Docker Image DEIGDE-CI]]. The ready made docker image contains the most recent stable release. A docker image is ready made to be used: [[https://hub.docker.com/repository/docker/lordofdragons/deigde-ci|Docker Image DEIGDE-CI]]. The ready made docker image contains the most recent stable release.
Line 38: Line 39:
 <code bash>docker run -it --rm --volume=/home/user/deprojects/MyGame:/project lordofdragons/deigde-ci /project/MyGame.degp --project.profile.distribute Release</code> <code bash>docker run -it --rm --volume=/home/user/deprojects/MyGame:/project lordofdragons/deigde-ci /project/MyGame.degp --project.profile.distribute Release</code>
  
-The *.delga file is then located in the path "/home/user/deprojects/MyGame/<path-delga>whereas "<path-delga>is the path set in the profile "Release".+The *.delga file is then located in the path <wrap hi>/home/user/deprojects/MyGame/{path-delga}</wrap> whereas <wrap hi>{path-delga}</wrap> is the path set in the profile <wrap hi>Release</wrap>.
  
 ==== Custom Docker Image ==== ==== Custom Docker Image ====
Line 57: Line 58:
  
 ===== GitHub Actions ===== ===== GitHub Actions =====
 +{{ :gamedev:githubactions.png?direct |Github Actions Logo}}
  
 For GitHub Actions a ready made action is provided: [[https://github.com/marketplace/actions/build-delga|Build DELGA distribution docker action]]. This action allows to run the distribute command. To use the action checkout the game project from your repository then include this code in your build script: For GitHub Actions a ready made action is provided: [[https://github.com/marketplace/actions/build-delga|Build DELGA distribution docker action]]. This action allows to run the distribute command. To use the action checkout the game project from your repository then include this code in your build script:
Line 92: Line 94:
 </code> </code>
  
-The upcoming build scripts can then use the distribution file with the path "distribute/MyGame.delgagiven this is the path stored in the profile "Release".+The upcoming build scripts can then use the distribution file with the path <wrap hi>distribute/MyGame.delga</wrap> given this is the path stored in the profile <wrap hi>Release</wrap>. 
 + 
 +==== Custom Actions Script ====
  
 If you do not want to use the provided action, for example to use commands beyond building the distribution file, you can either use the docker image from the previous section or you can install the IGDE-CI into the running VM instance like this: If you do not want to use the provided action, for example to use commands beyond building the distribution file, you can either use the docker image from the previous section or you can install the IGDE-CI into the running VM instance like this:
Line 108: Line 112:
 </code> </code>
  
-Then you can use "deigdecommand directly.+Then you can use <wrap hi>deigde</wrap> command directly.
  
 ===== Jenkins ===== ===== Jenkins =====
 +{{ :gamedev:jenkins.png?direct |}}
  
 For Jenkins it is recommended to use the docker image mentioned above. You can also install the IGDE-CI directly into your build system as outline in the previous section. It is though easier to use the ready made docker image. For Jenkins it is recommended to use the docker image mentioned above. You can also install the IGDE-CI directly into your build system as outline in the previous section. It is though easier to use the ready made docker image.
  
gamedev/gameci.1656693828.txt.gz · Last modified: 2022/07/01 16:43 by dragonlord