You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

Michael Prokop c9b62658a1 MT#15973 Report in 'status' action when build/apply run is needed ... In a previous implementation using timestamps we ran into timing problems on slower systems. So instead lets record the git commit ID of the latest ngcpcfg commit and check whether we have a match between this commit and an according ngcpcfg build. If the "ngcpcfg build" was executed without an "ngcpcfg commit" before then we mark it as dirty since we don't have an according git commit available for testing against. Since that's a common workflow we don't report it as a real problem though, instead we inform the user using: | OK: nothing to build (latest build newer than latest commit) As we commit AFTER the build in the apply action we can use a workaround for this situation, so build and commit state match with each other in that case then. Change-Id: I48e32db6f42b53fe97a0b88805e7ddbee8576133		10 years ago
..
main	MT#15973 Report in 'status' action when build/apply run is needed	10 years ago