openbsc.git branch osmocom/jenkins-test updated. 0.15.0-332-g3a2c2bb

This is merely a historical archive of years 2008-2021, before the migration to mailman3.

A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/osmocom-commitlog@lists.osmocom.org/.

gitosis at osmocom.org gitosis at osmocom.org
Mon Jul 11 18:16:23 UTC 2016


This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "The OpenBSC GSM Base Station Controller (+MSC/HLR/SGSN)".

The branch, osmocom/jenkins-test has been updated
  discards  66363c3a50ec355e44ff79b8d957fb4bd35ba4f1 (commit)
       via  3a2c2bb781fc6cf44ba3e0da3475a7a7a503012d (commit)

This update added new revisions after undoing existing revisions.  That is
to say, the old revision is not a strict subset of the new revision.  This
situation occurs when you --force push a change and generate a repository
containing something like this:

 * -- * -- B -- O -- O -- O (66363c3a50ec355e44ff79b8d957fb4bd35ba4f1)
            \
             N -- N -- N (3a2c2bb781fc6cf44ba3e0da3475a7a7a503012d)

When this happens we assume that you've already had alert emails for all
of the O revisions, and so we here report only the revisions in the N
branch from the common base, B.

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
http://cgit.osmocom.org/openbsc/commit/?id=3a2c2bb781fc6cf44ba3e0da3475a7a7a503012d

commit 3a2c2bb781fc6cf44ba3e0da3475a7a7a503012d
Author: Neels Hofmeyr <neels at hofmeyr.de>
Date:   Mon Jul 11 19:39:51 2016 +0200

    jenkins.sh: remove code dup
    
    Have a bash function to build each dependency with the same commands.  There is
    a tradeoff: having each dependency build with the same function means you can't
    easily tweak one of the dependencies. OTOH having a unified function means a)
    more readable script, b) that we're sure not to forget some steps and c) no
    need to do the same edit n times.
    
    Set the PKG_CONFIG_PATH globally. Also a tradeoff: if a future addition
    wouldn't need the same PKG_CONFIG_PATH, this would make things ugly. But that
    is actually quite unlikely, and the readability improvement is substantial.
    
    Use env variables to remember local paths. That means we always are sure to cd
    to the same absolute base path, which a 'cd ..' can't guarantee; also, we avoid
    possible typos for e.g. "$deps/install".

-----------------------------------------------------------------------

Summary of changes:
 contrib/jenkins.sh | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)


hooks/post-receive
-- 
The OpenBSC GSM Base Station Controller (+MSC/HLR/SGSN)



More information about the osmocom-commitlog mailing list