Embodiments described herein are generally directed to a configuration-driven continuous delivery (CD) pipeline that can be used by multiple development teams and integrated with multiple repositories. According to an example, all commands to be run by a particular executor used by a particular development team are specified by the pipeline. A trigger event is received from an external source specifying a repository in which source code for an application being developed or maintained by the particular development team resides. Responsive to the trigger event, the pipeline is configured with information regarding subdirectories within the repository that are to be processed based on a first set of configuration information stored in the repository. Stages of the pipeline are performed by, for each subdirectory, causing the pipeline to issue a subset of the commands to the particular executor based on a second set of configuration information associated with the subdirectory.