Feature #3840
closed
script + web-page to show latest tags + git hashes of all osmocom CNI projects
Added by laforge about 5 years ago.
Updated about 5 years ago.
Description
We've been asked to provide a way to automatically in one page show the following information for all git repositories of the Osmocom CNI project:
- the latest tag + related git hash
- the current master git hash
So I think the best way to go about this is to have a shell script that peforms the related tasks and generates some human-readable and easily machine (shellscript) parseable text output.
The related script could be in osmo-ci.git and we could then have a jenkins job that runs this script once daily and pushes the resulting ascii file to the osmocom webserver for public consuption.
Script created:
https://gerrit.osmocom.org/#/c/osmo-ci/+/13301/
Current output:
# repository clone URL last tag last tag commit HEAD commit
libosmo-abis.git = https://git.osmocom.org/libosmo-abis 0.5.1 bbb5f99d6cc6ee8ce3765fb9696ef44b83f0eef4 c0a0ec494ff2dfdf2a28f38b382505da72d405d4
libosmocore.git = https://git.osmocom.org/libosmocore 0.1.30 f99b95cc94d7f28d04bd020cf178eaf4e0ac544c 24e67f86dd5da3c36eae4476e50d630689612d87
libosmo-netif.git = https://git.osmocom.org/libosmo-netif 0.0.3 fc9d4e3efc826db4e8853453bb3416c77b46fa24 1ab218d28f684a431cd9de972499b987b63a507a
libosmo-sccp.git = https://git.osmocom.org/libosmo-sccp 0.0.6 fc5f3348f02d7f9d7708a91ece4bc47b758be936 99beede80cc054ac84c80d90a3aa7330cd519076
osmo-bsc.git = https://git.osmocom.org/osmo-bsc 1.2.0 e9e421c671cf74205591f14233b30f79ad170c27 55073613bbd9b6a0f97309bcfb8683f951c4405f
osmo-bts.git = https://git.osmocom.org/osmo-bts 0.1.0 fb6d733299a4f60bf0ed05b7b28ce210aff5a2e3 965b911583dd7bb7e90983f4143b6359213bc98f
osmo-ggsn.git = https://git.osmocom.org/osmo-ggsn 1.0.0 f9c8fda6546f3cc1198c7e729999e734ea70f1b6 3fc9cc97de9f594b32def873ee78301a9ac608b4
osmo-hlr.git = https://git.osmocom.org/osmo-hlr 0.2.1 a85b27e32a6b75f597ba8fdde0879a240b10aa2a c5044cfd80666fc420e7019716613e5c3ab89bb8
osmo-mgw.git = https://git.osmocom.org/osmo-mgw 1.5.0 f174b8215e258f0fcd1c333ff689dcd762002f8f 58128258b03221728329ce9a57ff6557c3236dfe
osmo-msc.git = https://git.osmocom.org/osmo-msc 1.0.1 ec798b89700dcca5c5b28edf1a1cd16ea311f30a 9286114f6f9a8b45e620ccf2014ed713c770c9ed
osmo-pcu.git = https://git.osmocom.org/osmo-pcu 0.2.0 bb2b38124003825eb1646700b335c295b842044c a3ff316c5f2167f3b485a680e3a4b2576a2112de
laforge: ...or we could use jenkins' build artifacts feature, then we don't need to worry about upload permissions. Would that also be acceptable?
On Tue, Mar 19, 2019 at 10:55:49AM +0000, osmith [REDMINE] wrote:
laforge: ...or we could use jenkins' build artifacts feature, then we don't need to worry about upload permissions. Would that also be acceptable?
this actually makes sense for this, as it runs on the public osmocom jenkins.
- Status changed from In Progress to Resolved
- % Done changed from 90 to 100
Also available in: Atom
PDF
