User Tools

Site Tools


wiki:development:build-server

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
wiki:development:build-server [2013/12/28 23:31]
sunweaver
wiki:development:build-server [2016/11/10 10:33] (current)
gratuxri New versions from buildscripts
Line 14: Line 14:
  
 <code> <code>
-$ ssh -lx2go-admin -p64064 japsand.x2go.org+$ ssh -lx2go-admin -p9175 japsand.x2go.org
 </code> </code>
  
Line 24: Line 24:
  
 <code> <code>
-$ x2go-build+upload-deb-package <package-name> {heuler,main}[/{squeeze,wheezy,sid}]+$ x2go-build+upload-deb-package <package-name> {heuler,main}[/{squeeze,wheezy,jessie,stretch,sid}]
 </code> </code>
  
-The build scripts use qemubuilder. The packages are built in clean chroot environments of the corresponding distro version. Packages are built for amd64 and i386 archictectures.+The build scripts use qemubuilder. The packages are built in clean chroot environments of the corresponding distro version. Packages are regularly built for amd64 and i386 archictectures, some other architectures are supported (see below).
  
 === Run a test build === === Run a test build ===
Line 35: Line 35:
 <code> <code>
 $ x2go-build-deb-package <package-name> heuler/sid $ x2go-build-deb-package <package-name> heuler/sid
-</code> 
- 
-=== Build and Upload all Components === 
- 
-There also is a script that build all X2Go components in one go... 
- 
-<code> 
-$ x2go-build+upload-all-deb-packages [{heuler|main}|<leave-empty>] 
 </code> </code>
  
Line 57: Line 49:
 Currently, only ARM(el) builds (and of course i386, amd64) are supported. Currently, only ARM(el) builds (and of course i386, amd64) are supported.
  
-We normally do only build the stable X2Go code base for ARM(el) and only the client-side of X2Go.+We normally do only build the stable X2Go code base for ARM(el). 
 +=== Upload packages ===
  
-==== Upload X2Go Packages for Debian ==== +After the package build follows the package uploaded. Packages are currently uploaded to ''packages.x2go.org'' (aka ''ymir.das-netzwerkteam.de'').
- +
-After package build comes the package uploaded. Packages are currently uploaded to ''code.x2go.org'' (aka ''ymir.das-netzwerkteam.de'').+
  
 Uploaded packages normally get integrated into the repository by a CRON job. The impatient developer can trigger that command manually with this line at the command line shell of the user ''x2go-admin'' (e.g. for Debian squeeze): Uploaded packages normally get integrated into the repository by a CRON job. The impatient developer can trigger that command manually with this line at the command line shell of the user ''x2go-admin'' (e.g. for Debian squeeze):
 <code> <code>
-ssh -lx2go-admin code.x2go.org -p32032 +ssh -lx2go-admin packages.x2go.org -p32032 
-REPREPRO_BASE_DIR=/srv/sites/x2go.org/packages/debian reprepro processincoming x2go-debian-{squeeze|wheezy|sid}+REPREPRO_BASE_DIR=/srv/sites/x2go.org/packages/debian reprepro processincoming x2go-debian-{squeeze|wheezy|jessie|sid}
 </code> </code>
  
Line 89: Line 80:
 === Run a test build === === Run a test build ===
  
-If you just want to trigger a test build from Git master, do this for Fedora rawhide and do not upload to the .deb repository...+If you just want to trigger a test build from Git master, do this for Fedora rawhide and do not upload to the .rpm repository...
  
 <code> <code>
Line 95: Line 86:
 </code> </code>
  
-=== Build and Upload all Components === 
- 
-There also is a script that build all X2Go components in one go... 
- 
-<code> 
-$ x2go-build+upload-all-rpm-packages [{heuler|main}|<leave-empty>] 
-</code> 
  
  
wiki/development/build-server.1388273460.txt.gz · Last modified: 2013/12/28 23:31 by sunweaver