CI/CD - base decision to train or not on fingerprint logic of `rasa train` itself about financial-demo HOT 4 OPEN

@b-quachtran ,
What do think about this proposal to improve the logic in the CI/CD pipeline?

from financial-demo.

@ArjaanBuijk I think the above approach makes sense, I know of customer that doing something very similar in their CI pipeline for determining if model training needs to be run.

One thing that I think would work well is to make use of the rasa train --dry-run flag as a conditional check that determines if the train job should run.

from financial-demo.

The return code from rasa train --dry-run determines whether model re-training is needed:

  --dry-run             If enabled, no actual training will be performed.
                        Instead, it will be determined whether a model should
                        be re-trained and this information will be printed as
                        the output. The return code is a 4-bit bitmask that
                        can also be used to determine what exactly needs to be
                        retrained: - 1 means Core needs to be retrained - 2
                        means NLU needs to be retrained - 4 means responses in
                        the domain should be updated - 8 means the training
                        was forced (--force argument is specified) (default:
                        False)

from financial-demo.

I tried it out, but when running the cicd pipeline, downloading the model first, and then issuing rasa train does not work. Rasa is always training it.

For now, leaving the existing logic in place.

from financial-demo.