Nightly Update on Indeni Staging

Currently (Apr 16, 2018) there's a nightly process that copies the latest code from the indeni-knowledge develop branch into the indeni develop server.

How do I know if my commit is on a given server?

Look at the actual IND file you committed

If your changes are in .ind files, you can look for the file under /usr/share/indeni-knowledge/stable/ind/parsers/src. You could, e.g., 'cat' the file and manually look for the changes you made.

Look at 'knowledge-version.properties'

• SSH into the server
• cat /usr/share/indeni-knowledge/stable/ind/meta/knowledge-version.properties
• Look at the "indeni.knowledge.buildDate" value – that gives you a general sense as to whether or not your commit is in the build (i.e., if your commit was committed OR merged to staging after that date, it can't be in the build).
• For a precise answer:
  • Note the branch name which is part of the indeni.knowledge.version. E.g., indeni.knowledge.version=6.1.5.20-master  ← branch name.
  • Copy the git commit has from "indeni.knowledge.revision"; e.g., indeni.knowledge.revision=f5d2da2c2429ecb88eeb10e3d4a7fbacc3db4674  ← commit hash. This is the most recent indeni Knowledge (IND scripts and Scala rules) commit on the server.
  • Find the merge commit hash from your change. E.g., look at the pull request you used to submit your change; at the top, next to the green "merged" sign, there's a truncated commit hash: that's what you want:
    
  • You'll need a git commandline for the next step. Go to wherever you store and work on your "local" indeni-knowledge source – i.e., wherever you actually write code.
  • Checkout the branch you noted above, the one from the indeni.knowledge.version.
  • Update this branch to make sure you have the latest code.

  • From the git commandline, run:
    git log --oneline <most-recent-commit-hash> | grep <your-merge-commit-truncated-hash>
    E.g.:

    git log --oneline 0707b46ebe1274fd528acce86059ba002abf32e5 | grep 85f0944

    
    

• This outputs all of the commits that come before the 'most-recent-commit-hash' and then greps those for 'your-merge-commit-truncated-hash'.
• If you see grep output, then your commit should be on the server. Otherwise, it's not there.