Working on ci-management locally
- Gary Wu
(Copied from https://lists.onap.org/pipermail/onap-discuss/2017-July/002315.html)
In an effort to improve inefficiencies across our managed projects The Linux Foundation Release Engineering (LF RelEng) team has been working on a couple of projects. These projects are global-jjb [0] and lftools [1]. They are mirrored on GitHub at [2] and [3].
I'm making this announcement in part because Jeremy has just completed a migration of the ci-management verify and merge jobs to using our new global versions of them.
What does this mean for you? It means the following, if you do any work on job updates and wish to test locally you will need to now do a submodule init in any local clone of ci-management. The following would be what you do on a clean clone:
--[cut]--
LFID=yourLFID
git clone ssh://${LFID}@gerrit.onap.org:29418/ci-management.git
cd ci-management
git submodule update --init --recursive
--[/cut]--
If you've already got a clone then do the following:
--[cut]--
git checkout master
git pull
git submodule update --init --recursive
--[/cut]--
You will find that we use the GitHub mirror for the submodule, which is intentional as it will allow us to do work on the LF Gerrit system without affecting production systems :)
In the coming weeks we'll be going through and modifying current templates to use some of our global macros instead of local ones as well as seeing where we can transition current jobs in use to templates in our global repo.
-Andy-
[0] https://gerrit.linuxfoundation.org/infra/#/admin/projects/releng/global-jjb [1] https://gerrit.linuxfoundation.org/infra/#/admin/projects/releng/lftools [2] https://github.com/lfit/releng-global-jjb [3] https://github.com/lfit/releng-lftools -- Andrew J Grimberg Lead, IT Release Engineering The Linux Foundation