Neon/Git: Difference between revisions

From KDE Community Wiki
(Created page with "The Neon Git repositories are at http://git.edinburghlinux.co.uk In the future all KDE contributors can commit to these on branches used by Neon and related projects. It wil...")
 
No edit summary
(28 intermediate revisions by 3 users not shown)
Line 1: Line 1:
The Neon Git repositories are at http://git.edinburghlinux.co.uk
The Neon Git repositories are at https://invent.kde.org/neon


In the future all KDE contributors can commit to these on branches used by Neon and related projects.  It will reject commits on other branches.
All KDE contributors can commit to Neon/* branches or any branch for repositories under neon/, forks/, neon-packages/ directories, 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.
They are clones of the repositories used by Debian pkg-kde team https://salsa.debian.org/qt-kde-team/.  Any commits made to a Debian pkg-kde repository will be pulled into Neon Git immediately.


Add this to <code>~/.gitconfig</code>
Add this to <code>~/.gitconfig</code>
{{Input|1=<nowiki>
{{Input|1=<nowiki>
[url "gitolite3@git.edinburghlinux.co.uk:"]
[url "git@invent.kde.org:"]
        insteadof = neon:
    insteadOf = invent:
}}
[url "git@invent.kde.org:"]
    pushInsteadOf = invent:
</nowiki>}}
and clone with:
and clone with:
{{Input|1=<nowiki>git clone invent:neon/kde/khotkeys</nowiki>}}
=== Anonymous Access ===
If you don't have a KDE account you can still clone the repo at
{{Input|1=<nowiki>git clone https://invent.kde.org/neon/kde/khotkeys</nowiki>}}
=== Settings up new repositories ===
This is now done through invent.kde.org which can also be set to clone another git repo
=== The Set Up===
* neon:gitolite-admin has hooks in .gitolite/hooks/common which are symlinks to neon-hooks/ that get added to new repositories
* .gitolite/hooks/update is the normal hook from gitolite that does whatever gitolite needs
* neon-hooks/post-receive pings jenkins to start a new build
* neon-hooks/pre-receive rejects pushes to non-neon branches and sets up remote to Debian if it exists
* neon/website and neon/releases.neon.kde.org have a post-receive hook to update their websites (no longer used for websites at least)
* cron on the gitolite server runs bits to restart the servers and run the check scripts:
{{Input|1=<nowiki>
{{Input|1=<nowiki>
git clone neon:plasma/khotkeys
# Hourly sync of new repositories from salsa.debian.org
}}
@hourly python3 ~/config-sync/gitolite-admin/maintenance/update-gitolite-setup.py
# Daily full sync of all repositories from salsa.debian.org
@daily python3 ~/config-sync/gitolite-admin/maintenance/update-gitolite-setup.py --fetch-all-repositories
</nowiki>}}

Revision as of 21:21, 15 October 2020

The Neon Git repositories are at https://invent.kde.org/neon

All KDE contributors can commit to Neon/* branches or any branch for repositories under neon/, forks/, neon-packages/ directories, it will reject commits to other branches.

They are clones of the repositories used by Debian pkg-kde team https://salsa.debian.org/qt-kde-team/. Any commits made to a Debian pkg-kde repository will be pulled into Neon Git immediately.

Add this to ~/.gitconfig

[url "[email protected]:"]
    insteadOf = invent:
[url "[email protected]:"]
    pushInsteadOf = invent:

and clone with:

git clone invent:neon/kde/khotkeys

Anonymous Access

If you don't have a KDE account you can still clone the repo at

git clone https://invent.kde.org/neon/kde/khotkeys

Settings up new repositories

This is now done through invent.kde.org which can also be set to clone another git repo

The Set Up

  • neon:gitolite-admin has hooks in .gitolite/hooks/common which are symlinks to neon-hooks/ that get added to new repositories
  • .gitolite/hooks/update is the normal hook from gitolite that does whatever gitolite needs
  • neon-hooks/post-receive pings jenkins to start a new build
  • neon-hooks/pre-receive rejects pushes to non-neon branches and sets up remote to Debian if it exists
  • neon/website and neon/releases.neon.kde.org have a post-receive hook to update their websites (no longer used for websites at least)
  • cron on the gitolite server runs bits to restart the servers and run the check scripts:
# Hourly sync of new repositories from salsa.debian.org
@hourly python3 ~/config-sync/gitolite-admin/maintenance/update-gitolite-setup.py
# Daily full sync of all repositories from salsa.debian.org
@daily python3 ~/config-sync/gitolite-admin/maintenance/update-gitolite-setup.py --fetch-all-repositories