Closed ndushay closed 7 years ago
WASMetadataExtractor.jar does have a jenkins build, but it isn't deployed via puppet -- as far as I can see, it just lives in was_robot_suite/jar
and is updated via git commit. Will try to get clearer today on the status of that jar and the things on the mount, especially how they ought to be installed.
Had a chat with @nullhandle: hrwa_manager
is not robots related, nor is anything else in the same directory. hrwa_manager
instead is a was-downloader
concern.
ok, Not sure we have to undertake lots of puppet work for was-downloader
and hrwa-manager
at this time, but we should make sure they won't disappear when we stop using their mount points on sul-robots3-prod
this repo no longer works and we've stopped using it altogether.
maybe via jenkins build?
it's currently on
sul-robots3-prod
, probably manaually installed.how shall it be installed on new VMs?
use WASMetadataExtractor.jar deployment as a model? (I believe it's a jar with a jenkins build, and a puppet script to get a deploy artifact from jenkins???)
also, are there other was-robot specific things mounted for sul-robots3-prod that need to come to new was-robot-vms? cdl-manager? lockss mount? @tallenaz will discuss with @nullhandle