Start a new topic
Answered

Spider not running with latest commit.

Hi,


We noticed that recent spider jobs had been run with a prior commit version of the spider.


Notice that the executions on 6/8 and 6/7 were run using commit ca092ed-master.  


image


However we had already deployed a new version but it is still running with the old version.


Notice this next run somehow runs with the older version of the spider, this was triggered via the API.


image



It seems to run the latest when triggered from the dashboard, but an older version when run from the API.  We usually trigger via the 


https://app.scrapinghub.com/api/run.json


API.


I would expect that no matter what, the system would always use the latest version of the spider.  Now I'm concerned that other spiders are running without fixes.




Best Answer

Jobs from the dashboard are triggered via the API.


The jobs 15/77, 15/76, 15/75 and 15/74 ran with version ca092ed-master (which was deployed 25 days ago).

Job 15/78 started at 13:18 UTC with version 2f4ed83-master, this version was deployed 3 days ago (06/08 at 3:53 UTC).

The latest version, cba5f96-master, was deployed 3 days ago 06/08 at 14:19 UTC which was later than when 15/78 ran.


So all jobs ran with the version that was deployed at the time.


1 Comment

Answer

Jobs from the dashboard are triggered via the API.


The jobs 15/77, 15/76, 15/75 and 15/74 ran with version ca092ed-master (which was deployed 25 days ago).

Job 15/78 started at 13:18 UTC with version 2f4ed83-master, this version was deployed 3 days ago (06/08 at 3:53 UTC).

The latest version, cba5f96-master, was deployed 3 days ago 06/08 at 14:19 UTC which was later than when 15/78 ran.


So all jobs ran with the version that was deployed at the time.


Login to post a comment