381
edits
Changes
Jump to navigation
Jump to search
Line 76:
Line 76: − + − + − + − + − + + Line 104:
Line 105: − + + + + Line 137:
Line 141: − + + +
SMEServer as a Build Server (view source)
Revision as of 03:15, 21 August 2023
, 03:15, 21 August 2023→CVS shell.koozali.org access
</syntaxhighlight>
</syntaxhighlight>
==== CVS shell.koozali.org access ====
==== Developer access====
You don't need to have developer access to copy out source, local compiles, etc., but you do need it if you are going to want to save changes back into cvs or git.
* SME Server code is stored in the CVS on [[/shell.koozali.org/|http://shell.koozali.org]]. To be able to work on your code in the SME Server CVS repository you need an account on Koozali.org. With this account the development team can give you access to the CVS repository.
*SME Server code is stored in the CVS on [[/shell.koozali.org/|http://shell.koozali.org]] and in the future in git on https://src.koozali.org. To be able to work on your code in the SME Server CVS repository you need an account on Koozali.org. With this account the development team can give you access to the CVS repository.
* After your Koozali.org account has been created you can ask the development team to give you developer access to smecontribs. Create a bug in the Bug Tracker as usual.
* After your Koozali.org account has been created you can ask the development team to give you developer access to smecontribs. Create a bug in the Bug Tracker as usual.
* You will be sent your shell keys (store in ~/.ssh/) and plague keys (store in ~/.buildsys/)
*You will be sent your shell keys (store in ~/.ssh/) and plague keys (store in ~/.buildsys/)
When they have koozali shell and buildsys access, you'll need to set up their configs
When they have koozali shell and buildsys access, you'll need to set up their configs
For shell.koozali.org<syntaxhighlight lang="bash">
=====For shell.koozali.org =====
<syntaxhighlight lang="bash">
nano ~/.ssh/config
nano ~/.ssh/config
</syntaxhighlight>If you didn't have an existing ~/.ssh/config file you may need to change the permissions<syntaxhighlight lang="bash">
</syntaxhighlight>If you didn't have an existing ~/.ssh/config file you may need to change the permissions<syntaxhighlight lang="bash">
chmod 0600 ~/.ssh/config
chmod 0600 ~/.ssh/config
</syntaxhighlight>For buildsys<syntaxhighlight lang="bash">
</syntaxhighlight>
=====For buildsys=====
<syntaxhighlight lang="bash">
nano ~/.plague-client.cfg
nano ~/.plague-client.cfg
build32-1.contribs.org i386 i486 i586 i686 athlon noarch available
build32-1.contribs.org i386 i486 i586 i686 athlon noarch available
===== For git=====
[[Category:Developer]]
[[Category:Developer]]