Add ability to associate run with git commit or comment about mlops.net HOT 8 CLOSED

Once #50 is merged assemby you should be able to use something along these lines to get the git hash using something like this:

typeof(MLOps.NET.MLLifeCycleManager).Assembly
    .GetCustomAttribute<AssemblyInformationalVersionAttribute>()
    .InformationalVersion

This returns 0.0.13-alpha+d3d9d32478 on the assembly from one of the packages generated from my testing setting up the git versioning

from mlops.net.

cc: @dcostea @lqdev @AnoojNair - would love your input on this one. Sammy, I can't tag you yet but I'll tag you in the associated issue for your awareness.

from mlops.net.

@AnoojNair I think we would need to store some kind of traceable artifact, since down the line we want to be able to look back from a model to see what data and code that was used. I'm thinking that we in the UI would be able to click a model and be taken straight to the repo and the comimt which contains the code used :)

from mlops.net.

That's super helpful, thanks for the heads-up @ssa3512

from mlops.net.

Would this value (git hash/ build version) be surfaced up in the user program so that they can then log it in the metadata store?

from mlops.net.

Ideally it would be set automatically on the run and they can provide a comment is they like

from mlops.net.

Another way to achieve this would be to use tags. We can tag the repo whenever we get the best run? Then we don't store anything git specific in the dB.

This should be possible from GitHub actions? I am not sure

from mlops.net.

@AnoojNair I think we would need to store some kind of traceable artifact, since down the line we want to be able to look back from a model to see what data and code that was used. I'm thinking that we in the UI would be able to click a model and be taken straight to the repo and the comimt which contains the code used :)

Nice, that would be a good feature

from mlops.net.