Update git URLs
git.osmocom.org has been deprecated, use gerrit or gitea urls instead. Related: https://osmocom.org/projects/cellular-infrastructure/wiki/Git_infrastructure Related: OS#6251 Change-Id: I03a06d23e87a75257eb731a97facd7a67c40a2c6
This commit is contained in:
parent
e8b16f4e90
commit
f3930bbecc
|
@ -16,11 +16,12 @@ under _sysmocom/_ as a reference for others.
|
|||
|
||||
Ansible scripts to set up hosts to be used as Osmo-GSM-Tester Main Units or/and
|
||||
Slave Units on the above mentioned setup can be found at
|
||||
https://git.osmocom.org/osmo-ci/tree/ansible, which actually install sample
|
||||
system configuration files from _utils/_ directory in this same repository.
|
||||
https://gitea.osmocom.org/osmocom/osmo-ci/src/branch/master/ansible, which
|
||||
actually install sample system configuration files from _utils/_ directory in
|
||||
this same repository.
|
||||
|
||||
A sample Docker setup is also maintained publicly at
|
||||
https://git.osmocom.org/docker-playground/tree/osmo-gsm-tester.
|
||||
https://gitea.osmocom.org/osmocom/docker-playground/src/branch/master/osmo-gsm-tester.
|
||||
|
||||
For the complete documentation, please refer to Osmo-GSM-Tester User manual,
|
||||
available in sources under _doc/manuals/_ under this same repository, and
|
||||
|
|
|
@ -42,7 +42,7 @@ if [ -z "$name" -o -z "$base" ]; then
|
|||
exit 1
|
||||
fi
|
||||
|
||||
git_url="${git_url:-https://git.osmocom.org}"
|
||||
git_url="${git_url:-https://gerrit.osmocom.org}"
|
||||
prefix="${prefix:-$base/inst-$name}"
|
||||
# prefix_real is usually identical with prefix, except when installing to a
|
||||
# different $DESTDIR than /, which is the case for example when building
|
||||
|
|
|
@ -15,7 +15,7 @@ fi
|
|||
if [ -d "$OSMO_GSM_MANUALS_DIR" ]; then
|
||||
git -C "$OSMO_GSM_MANUALS_DIR" pull
|
||||
else
|
||||
git clone "https://git.osmocom.org/osmo-gsm-manuals" "$OSMO_GSM_MANUALS_DIR"
|
||||
git clone "https://gerrit.osmocom.org/osmo-gsm-manuals" "$OSMO_GSM_MANUALS_DIR"
|
||||
fi
|
||||
git -C "$OSMO_GSM_MANUALS_DIR" checkout -f HEAD
|
||||
|
||||
|
|
|
@ -4,7 +4,8 @@ base="$PWD"
|
|||
name="osmo-bts"
|
||||
. "$(dirname "$0")/jenkins-build-common.sh"
|
||||
|
||||
have_repo octphy-2g-headers
|
||||
(git_url=https://gitea.osmocom.org/cellular-infrastructure
|
||||
have_repo octphy-2g-headers)
|
||||
|
||||
build_repo libosmocore ${SANITIZE_FLAGS} --disable-doxygen --disable-uring
|
||||
build_repo libosmo-abis ${SANITIZE_FLAGS} --disable-dahdi
|
||||
|
|
|
@ -5,8 +5,8 @@ Since the set of steps to set up a full {app-name} environment can be quite long
|
|||
and tedious, nowadays the Osmocom RnD and Production {app-name} setups are
|
||||
installed and maintained using Ansible scripts. The set of ansible scripts is
|
||||
available in Osmocom's git repository
|
||||
link:https://git.osmocom.org/osmo-ci/[osmo-ci.git] under 'ansible' subdirectory,
|
||||
with the rest of ansible scripts to set jenkins slaves, etc.
|
||||
link:https://gitea.osmocom.org/osmocom/osmo-ci/[osmo-ci.git] under 'ansible'
|
||||
subdirectory, with the rest of ansible scripts to set jenkins slaves, etc.
|
||||
|
||||
Since these set of scripts is mainly aimed at Osmocom's own setup, and debian is
|
||||
used there, so far only debian hosts are supported officially, though patches to
|
||||
|
|
|
@ -3,8 +3,8 @@
|
|||
|
||||
A sample {app-name} setup based on docker containers and maintained by the
|
||||
Osmocom community is available in Osmocom's git repository
|
||||
link:https://git.osmocom.org/docker-playground/[docker-playground.git], under
|
||||
'osmo-gsm-tester' subdirectory. In there, one can find:
|
||||
link:https://gitea.osmocom.org/osmocom/docker-playground/[docker-playground.git],
|
||||
under 'osmo-gsm-tester' subdirectory. In there, one can find:
|
||||
|
||||
- A 'Dockerfile' file can be found which builds a docker image which can
|
||||
be used both to run as an osmo-gsm-tester <<install_main_unit,Main Unit>> or as
|
||||
|
|
|
@ -51,8 +51,8 @@
|
|||
</para>
|
||||
<para>
|
||||
The Asciidoc source code of this manual can be found at
|
||||
<ulink url="http://git.osmocom.org/osmo-gsm-manuals/">
|
||||
http://git.osmocom.org/osmo-gsm-manuals/
|
||||
<ulink url="https://gitea.osmocom.org/cellular-infrastructure/osmo-gsm-manuals">
|
||||
https://gitea.osmocom.org/cellular-infrastructure/osmo-gsm-manuals
|
||||
</ulink>
|
||||
</para>
|
||||
</legalnotice>
|
||||
|
|
|
@ -80,7 +80,7 @@ class OsmoVty(log.Origin):
|
|||
|
||||
def _command(self, command_str, timeout=10, strict=True):
|
||||
'''Send a command and return the response.'''
|
||||
# (copied from https://git.osmocom.org/python/osmo-python-tests/tree/osmopy/osmo_interact/vty.py)
|
||||
# (copied from osmo-python-tests/osmopy/osmo_interact/vty.py)
|
||||
self.dbg('Sending', command_str=command_str)
|
||||
self.sck.send(command_str.encode())
|
||||
|
||||
|
@ -159,7 +159,7 @@ class OsmoVty(log.Origin):
|
|||
self.sck.setblocking(1)
|
||||
|
||||
# read first prompt
|
||||
# (copied from https://git.osmocom.org/python/osmo-python-tests/tree/osmopy/osmo_interact/vty.py)
|
||||
# (copied from osmo-python-tests/osmopy/osmo_interact/vty.py)
|
||||
self.this_node = None
|
||||
self.this_prompt_char = '>' # slight cheat for initial prompt char
|
||||
self.last_node = None
|
||||
|
@ -209,7 +209,7 @@ class OsmoVty(log.Origin):
|
|||
with self:
|
||||
return self.cmd(command_str, timeout, strict)
|
||||
|
||||
# (copied from https://git.osmocom.org/python/osmo-python-tests/tree/osmopy/osmo_interact/vty.py)
|
||||
# (copied from osmo-python-tests/osmopy/osmo_interact/vty.py)
|
||||
command_str = command_str or '\r'
|
||||
if command_str[-1] not in '?\r\t':
|
||||
command_str = command_str + '\r'
|
||||
|
|
|
@ -1,5 +1,6 @@
|
|||
This directory contains a set of scripts and osmo-gsm-tester testsuites to run
|
||||
osmo-ttcn3-hacks.git BTS_tests.ttcn (https://git.osmocom.org/osmo-ttcn3-hacks/tree/bts).
|
||||
osmo-ttcn3-hacks.git BTS_tests.ttcn
|
||||
(https://gitea.osmocom.org/ttcn3/osmo-ttcn3-hacks/src/branch/master/bts).
|
||||
|
||||
The idea is to set up automatically the following components:
|
||||
TTCN3 <-> osmocon (osmocom-bb) <-> motorola C123 <-> RF network <-> BTS_TO_TEST <-> TTCN3 + osmo-bsc
|
||||
|
|
Loading…
Reference in New Issue