i need java task run on scheduled basis, daily. needs executed on demand, on click of button on web page.
i compile business logic jar, , drop somewhere jenkins server can reach. , configure jenkins job execute main class on schedule. , support execution on demand, can create jenkins job (in php or something) run main class single time.
is horrendous misuse? may seem lazy hack avoid installing tomcat , consuming web services call, allows me make changes schedule modifying jenkins job. , has significant advantage of avoiding unnecessary overhead, complexity, , maintenance, considering don't have tomcat server available.
is horrendous misuse?
frankly .... cares.
the issue whether there important objective downsides taking "expedient" path achieving trying achieve. downsides might relevant are:
your jenkins installation potentially has bigger footprint (cpu usage, memory usage, disk space usage) small web-server.
there may hidden costs people might need take on running systems; e.g. dependency on jenkins installation might otherwise not need maintain.
however, don't underestimate "ewww!" reaction might other people.
Comments
Post a Comment