Differences

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

--- wiki:development:build-server [2013/12/28 23:24]
sunweaver
+++ wiki:development:build-server [2016/11/10 10:33] (current)
gratuxri New versions from buildscripts
@@ Line 6: / Line 6: @@
 However, the Ubuntu packages we provide are built on [[http://launchpad.net/~x2go|Launchpad]].
 ===== Manual Package Builds =====
-==== Build X2Go Packages for Debian ====
+==== Build Server Logon ====
 X2Go developers can logon to...
 <code>
-$ ssh -lx2go-admin -p64064 japsand.x2go.org
+$ ssh -lx2go-admin -p9175 japsand.x2go.org
 </code>
+==== Build X2Go Packages for Debian ====
 === Run a ,,normal" build job ===
@@ Line 23: / Line 24: @@
 <code>
-$ x2go-build+upload-package <package-name> {heuler,main}[/{squeeze,wheezy,sid}]
+$ x2go-build+upload-deb-package <package-name> {heuler,main}[/{squeeze,wheezy,jessie,stretch,sid}]
 </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 ===
@@ Line 33: / Line 34: @@
 <code>
-$ x2go-build-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-packages [{heuler|main}|<leave-empty>]
 </code>
@@ Line 49: / Line 42: @@
 <code>
-$ EXTRA_ARCHS=armel EXTRA_ARCHS_ONLY=yes x2go-build+upload-package <package-name> {heuler,main}[/{squeeze,wheezy,sid}]
+$ EXTRA_ARCHS=armel EXTRA_ARCHS_ONLY=yes x2go-build+upload-deb-package <package-name> {heuler,main}[/{squeeze,wheezy,sid}]
 </code>
@@ Line 56: / Line 49: @@
 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):
 <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>
@@ Line 71: / Line 63: @@
 Ubuntu packages of X2Go (amd64, i386) are built fully automatically via Launchpad: http://launchpad.net/~x2go
+==== Build X2Go Packages for Fedora/EPEL ====
+=== Run a ,,normal" build job ===
+... and launch a package build process:
+<code>
+$ RPM_BUILD_FOR="fedora:18,19 epel:6" x2go-build+upload-rpm-package <package-name> {heuler,main}
+</code>
+The build scripts use mock. The packages are built in clean chroot environments of the corresponding distro version. Packages are built for amd64 and i386 archictectures.
+=== 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 .rpm repository...
+<code>
+$ x2go-build-rpm-package <package-name> heuler/rawhide
+</code>

X2Go - everywhere@home

User Tools

Site Tools

Differences

Page Tools