suzanne.soy/travis-web
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Don't instantiate repo nor job on worker updates

Browse Source 
We can create thos records based on job:started event. Also, links used
on the workers list are created from attributes only anyway.
This commit is contained in:
Piotr Sarnacki 2013-01-23 21:33:08 +01:00
parent 28e40ab0e4
commit ee9f9d934c
1 changed files with 1 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
assets/scripts/app/store.coffee
View File

@ -68,8 +68,6 @@ Travis.Store = DS.Store.extend
{ id: id, clientId: clientId }
receive: (event, data) ->
# return if event == 'worker:added' || event == 'worker:removed'
[name, type] = event.split(':')
mappings = @adapter.get('mappings')
@ -111,14 +109,7 @@ Travis.Store = DS.Store.extend
# things I want to update here:
if type == Travis.Build && (json.repository || json.repo)
@loadIncomplete(Travis.Repo, json.repository || json.repo)
else if type == Travis.Worker && json.worker.payload
if repo = (json.worker.payload.repo || json.worker.payload.repository)
# I use skipIfExists here, cause worker payload is usually outdated
# If there is no info on repo yet, it's worth to add it, but if it already
# exists, we will most likely end up with inconsistent situation
@loadIncomplete(Travis.Repo, repo, skipIfExists: true)
if job = json.worker.payload.job
@loadIncomplete(Travis.Job, job)
@loadIncomplete(type, json[root])
addLoadedData: (type, clientId, hash) ->