1 .. This work is licensed under a Creative Commons Attribution 4.0 International License.
2 .. http://creativecommons.org/licenses/by/4.0
3 .. (c) 2017 Enea AB and others
8 This repository holds build scripts for MCP Fuel OPNFV installer
14 The standard workflow should look as follows:
16 #. Clone the repository.
18 #. All the sub-projects are registered as submodules. To initialize them, call:
22 $ make submodules-init
24 #. Apply patches from ``patches/<sub-project>/*`` to respective submodules via:
30 This will result in creation of:
32 - a tag called ``${A_OPNFV_TAG}-root`` at submodule remote branch HEAD;
33 - a new branch ``opnfv-armband`` which will hold all the armband work.
35 Then each patch is applied on this new branch with ``git-am``.
37 The new HEAD is tagged with ``${A_OPNFV_TAG}``.
39 #. Modify sub-projects for whatever you need.
41 Commit your changes when you want them taken into account in the build.
43 *NOTE*: If you want to re-export patches, make sure to move the tag
44 ``${A_OPNFV_TAG}`` to the latest commit that should be included.
46 #. Re-create patches and add default copyright header via:
50 $ make patches-export patches-copyright
52 Each commit on ``opnfv-armband`` branch of each subproject will be
53 exported to ``patches/subproject/`` via ``git format-patch``.
55 #. Clean workbench branches and tags with:
59 $ make submodules-clean
64 If you need to add another subproject, you can do it with ``git submodule``.
65 Make sure that you specify branch (with ``-b``), short name (with ``--name``)
66 and point it to ``upstream/*`` directory, i.e.:
70 $ git submodule -b stable/mitaka add --name fuel-web \
71 https://github.com/openstack/fuel-web.git upstream/fuel-web