Manifest and build-tools repo do not have merge jobs as they do not produce any artifacts i.e RPMs etc. Hence there is nothing to package and upload with a merge job.

Taking the case of manifest repository, any change in it can result in a completely different image build (e.g. different base packages, newly added packages).

This repository contains mainly:

• A list of packages to be installed
• A list of RPM repositories to be used

Both of these contribute heavily on the ISO image output and a single line change in build_config.ini may result in a huge change over the product ISO.

Also is a case in the build-tools repository where any change may result in changes in the ISO image.

Hence it is required to add two static triggers to the "akraino-project-release-ta-build" template. One for manifest and another for build tools.