2,569
edits
Changes
From SME Server
Jump to navigationJump to search
mLine 1:
Line 1: − + + − ====Local developer environment====+ − + Line 19:
Line 20: + + Line 39:
Line 42: − + Line 46:
Line 49: − + Line 140:
Line 143: − − Check updates/status on the build server: http://buildsys.contribs.org
no edit summary
===Set up===
===Set up===
We now use cvs without needing mezzanine, check you have it installed
====Local environment====
* We now use cvs without needing mezzanine, check you have it installed
yum install cvs
yum install cvs
* Setup CVS to use ssh
/etc/profile.d/smebuild.sh
/etc/profile.d/smebuild.sh
# Developer environment
# Developer environment
====Access to build system====
====Access to build system====
Check updates/status on the build server: http://buildsys.contribs.org
Ask admin@contribs.org for certificates, give the email address to use for notifications
Ask admin@contribs.org for certificates, give the email address to use for notifications
yum install --enablerepo=smedev plague-client
yum install --enablerepo=smedev plague-client
====Sourceforge access====
====Sourceforge access====
* SME Server code is stored in the CVS on SourceForge. To be able to work on your code in the SME Server CVS repository you need an account on SourceForge. With this account the development team can give you access to the CVS repository. More information can be found here:
* SME Server code is stored in the CVS on http://SourceForge.net. To be able to work on your code in the SME Server CVS repository you need an account on SourceForge. With this account the development team can give you access to the CVS repository. More information can be found here:
[http://sourceforge.net/docman/display_doc.php?docid=11123&group_id=1 B04: Registering a User Account]
[http://sourceforge.net/docman/display_doc.php?docid=11123&group_id=1 B04: Registering a User Account]
[http://sourceforge.net/docman/display_doc.php?docid=29894&group_id=1 E04: CVS (Version Control for Source Code)]
[http://sourceforge.net/docman/display_doc.php?docid=29894&group_id=1 E04: CVS (Version Control for Source Code)]
* After you have created your SourceForge account you can ask the development team to give you developer access to smecontribs. Create a bug in the Bug Tracker as usual.
* After you have created your SourceForge account you can ask the development team to give you developer access to smecontribs. Create a bug in the Bug Tracker as usual.
* Copy your local SSH key to SourceForge https://sourceforge.net/account/editsshkeys.php
* Copy your local public SSH key to SourceForge https://sourceforge.net/account/editsshkeys.php
* If local username is different to sf.net username
* If local username is different to sf.net username
Once the server successfully builds it will automatically be pulled on the next repo update run
Once the server successfully builds it will automatically be pulled on the next repo update run
(40 past the even hours MDT). The package will either be put into the smedev (new package) or smetest (exist in higher repo) After verification the package is manually moved from smedev/smetest to smecontribs/smeupdates-testing
(40 past the even hours MDT). The package will either be put into the smedev (new package) or smetest (exist in higher repo) After verification the package is manually moved from smedev/smetest to smecontribs/smeupdates-testing
