Updates in the metadata shouldn't trigger the whole Pipeline #9
Description
Right now the updates in the metadata file are triggering the whole Jenkins Pipeline (including expensive Docker rebuild). (example with new metadata)
I see the point of having the updated metadata file in the Docker image, but I don't think it's worth the waste of computing resources. In deephdc, I remember we did have the condition to avoid running the whole Pipeline if only the metadata was changed. I think we should revert to that again.