Neon/Git: Difference between revisions
No edit summary |
No edit summary |
||
| Line 6: | Line 6: | ||
Add this to <code>~/.gitconfig</code> | Add this to <code>~/.gitconfig</code> | ||
{{Input|1=<nowiki>[url "[email protected] | {{Input|1=<nowiki>[url "[email protected]:"] | ||
insteadof = neon:</nowiki>}} | insteadof = neon:</nowiki>}} | ||
and clone with: | and clone with: | ||
| Line 14: | Line 14: | ||
If you don't have a KDE account you can still clone the repo at | If you don't have a KDE account you can still clone the repo at | ||
{{Input|1=<nowiki>git clone git://packaging.neon.kde.org | {{Input|1=<nowiki>git clone git://packaging.neon.kde.org/plasma/khotkeys</nowiki>}} | ||
=== Admin === | === Admin === | ||
| Line 31: | Line 31: | ||
Web interface is cgit. | Web interface is cgit. | ||
=== Settings up new repositories === | |||
To set up a new repository it is nice to make it first on the Debian server so the syncing is already set up and Debian/Kubuntu packagers know to use it. | |||
* Ask someone with access (Jonathan etc) to <code>ssh git.debian.org; cd /git/pkg-kde/place-to-put-it; ../setup-git-repository <new-repo></code> | |||
* Then wait 15 minutes while the website for git.debian.org syncs the new repo | |||
* Then run <code>./sync-repos-from-debian.py</code> (just tell Jonathan to run it on his embra server) | |||
* Make a Neon/unstable branch on the neon git repo and get a Jenkins admin to run <code>pangea-tooling jenkins_jobs_update_nci.rb</code> | |||
Revision as of 13:57, 11 March 2016
The Neon Git repositories are at http://packaging.neon.kde.org.uk
All KDE contributors can commit to neon* branches or repositories under neon/ directory, it will reject commits to other branches.
They are clones of the repositories used by Debian pkg-kde team http://anonscm.debian.org/cgit/pkg-kde/. Any commits made to a Debian pkg-kde repository will be pulled into Neon Git immediately.
Add this to ~/.gitconfig
[url "[email protected]:"] insteadof = neon:
and clone with:
git clone neon:plasma/khotkeys
Anonymous Access
If you don't have a KDE account you can still clone the repo at
git clone git://packaging.neon.kde.org/plasma/khotkeys
Admin
The repository neon:gitolite-admin has gitolite setup, hooks and hook server for those with admin rights (kde sysadmin does).
neon-hooks/pre-receive is a hook to check the branch can be committed to
debian-hooks/debian-to-neon-post-receive is a hook for debian pkg-kde git repos to call the neon server on updates
server/neon-fetch-request-server.py is an XML-RPC server run on the neon server which is called by the debian hook and fetches updates
sync-repos-from-debian.py checks for all the repositories on in debian pkg-kde and adds any missing to neon. This gets run nightly on Jonathan's server embra.
It uses gitolite3 on weegie.edinburghlinux.co.uk, a server used by Neon and Kubuntu and administrated by Jonathan Riddell and KDE sysadmin.
Web interface is cgit.
Settings up new repositories
To set up a new repository it is nice to make it first on the Debian server so the syncing is already set up and Debian/Kubuntu packagers know to use it.
- Ask someone with access (Jonathan etc) to
ssh git.debian.org; cd /git/pkg-kde/place-to-put-it; ../setup-git-repository <new-repo> - Then wait 15 minutes while the website for git.debian.org syncs the new repo
- Then run
./sync-repos-from-debian.py(just tell Jonathan to run it on his embra server) - Make a Neon/unstable branch on the neon git repo and get a Jenkins admin to run
pangea-tooling jenkins_jobs_update_nci.rb