Launch libraries pipelines #274
Description
When we push to framework any changes, it might happen that something gets broken at a particular library pipeline. However, when changes are pushed or merged to master, the libraries pipelines are not validated. I have seen that the library launches the validation of the framework, but it does not happen the otherway around.
I believe the pipeline failing at rawlib: rest-for-physics/rawlib#73 is because a change in the framework and not in the rawlib.
Would be easy that both, framework and libraries ask for validation?
I thought there might be a kind of recursivity problem because calling a validation file that calls again my validation.yml file, probably something nasty may happen.