Delayed Jobs API merge requestshttps://gitlab.ebi.ac.uk/chembl/chembl/delayed-jobs/delayed-jobs-api/-/merge_requests2020-04-17T00:53:39Zhttps://gitlab.ebi.ac.uk/chembl/chembl/delayed-jobs/delayed-jobs-api/-/merge_requests/12Do all steps of deployment in master branch automatically2020-04-17T00:53:39ZDavid MendezDo all steps of deployment in master branch automaticallyhttps://gitlab.ebi.ac.uk/chembl/chembl/delayed-jobs/delayed-jobs-api/-/merge_requests/11Job output files: do not include scheme in output files urls2020-04-17T00:25:42ZDavid MendezJob output files: do not include scheme in output files urlsLet the consumer choose. Otherwise it can cause troubles with mixing http and https in browsersLet the consumer choose. Otherwise it can cause troubles with mixing http and https in browsershttps://gitlab.ebi.ac.uk/chembl/chembl/delayed-jobs/delayed-jobs-api/-/merge_requests/10Job Output files: generate output url from server host in request.2020-04-16T23:05:00ZDavid MendezJob Output files: generate output url from server host in request.https://gitlab.ebi.ac.uk/chembl/chembl/delayed-jobs/delayed-jobs-api/-/merge_requests/9Rate Limit: allow to set up rates in config and use memcached.2020-04-16T22:05:05ZDavid MendezRate Limit: allow to set up rates in config and use memcached.https://gitlab.ebi.ac.uk/chembl/chembl/delayed-jobs/delayed-jobs-api/-/merge_requests/8Use PostgreSQL instead of MySQL2020-04-15T14:30:32ZDavid MendezUse PostgreSQL instead of MySQLSo we don't have to wait for ports to be opened. Also we can now live without DB continuous replicas.So we don't have to wait for ports to be opened. Also we can now live without DB continuous replicas.https://gitlab.ebi.ac.uk/chembl/chembl/delayed-jobs/delayed-jobs-api/-/merge_requests/7Start to set up rate limiting2020-04-09T16:59:20ZDavid MendezStart to set up rate limitingThis adds the basics for rate limiting. I will work on another branch because the deployment of this one is being used by othersThis adds the basics for rate limiting. I will work on another branch because the deployment of this one is being used by othershttps://gitlab.ebi.ac.uk/chembl/chembl/delayed-jobs/delayed-jobs-api/-/merge_requests/6Enable functional tests again2020-04-08T21:00:16ZDavid MendezEnable functional tests againAdded a the header "Cache-Control": "no-cache" to the requests to get the status. This way we avoid the issue of the status endpoint being stuck with outdated data. This is a configuration of the traffic manager.Added a the header "Cache-Control": "no-cache" to the requests to get the status. This way we avoid the issue of the status endpoint being stuck with outdated data. This is a configuration of the traffic manager.https://gitlab.ebi.ac.uk/chembl/chembl/delayed-jobs/delayed-jobs-api/-/merge_requests/5Set up structure search job2020-04-07T22:58:02ZDavid MendezSet up structure search jobhttps://gitlab.ebi.ac.uk/chembl/chembl/delayed-jobs/delayed-jobs-api/-/merge_requests/4Change log level to debug for most log messages2020-04-03T15:09:46ZDavid MendezChange log level to debug for most log messageshttps://gitlab.ebi.ac.uk/chembl/chembl/delayed-jobs/delayed-jobs-api/-/merge_requests/3Simplify locking mechanism, use cache instead of DB2020-04-02T18:21:55ZDavid MendezSimplify locking mechanism, use cache instead of DBThis simplifies the locking mechanism used by the status agents. Now it saves the lock in the cache, so the expiration time is handled by the caching. The agent does not have to decide if it respects the lock or not.This simplifies the locking mechanism used by the status agents. Now it saves the lock in the cache, so the expiration time is handled by the caching. The agent does not have to decide if it respects the lock or not.https://gitlab.ebi.ac.uk/chembl/chembl/delayed-jobs/delayed-jobs-api/-/merge_requests/2Do first deployment to prod hx2020-04-01T23:47:38ZDavid MendezDo first deployment to prod hxhttps://gitlab.ebi.ac.uk/chembl/chembl/delayed-jobs/delayed-jobs-api/-/merge_requests/1Run jobs on lsf (First Step)2020-01-31T14:04:19ZDavid MendezRun jobs on lsf (First Step)This prepares the job run directory, input files, and output directory, but it doesn't submit the job yet. The job submission will be implemented by working on the cluster directly.This prepares the job run directory, input files, and output directory, but it doesn't submit the job yet. The job submission will be implemented by working on the cluster directly.