sul-dlss-deprecated / wasmetadataextractor Goto Github PK

if this is upstream code, fix the coverage config.

Would it be possible and/or make sense if we deploying this code to the was-robots VMs via capistrano? And then the robot code either looked for the jar at execution time, or there was a way to copy or symlink the jar into the robot code during a robot deploy and/or a was-md-extractor deploy?

devops operations concerns and checklist:

• indicate not deployed by puppet (why is it in jenkins if there is no puppet tie in? It creates deployed artifacts ... are they really not used?)

• indicate NOT deployed by was_robot_suite

• checklist should at least have TODO

  • to turn jenkins build into travis build
  • use coveralls for test coverage
  • add these badges to readme
  • add badge for github release

update ops concerns, esp ops escalation path and links to robot suite stuff that is relevant (e.g. restart via restarting robots??? redeploying robots???)

must haves:

• operations checklist written
• mailing list (indicate in checklist and ops concerns?)

at least add TODOs for to prod checklist for

• badges on README for release, and the below,
• travis build that runs tests (if not deploying from jenkins, remove from jenkins)
• coveralls for tests (see dlss-wowza for how to use coveralls w java)

see also #5