search

sgraf812 / feed-gipeda

Daemon for watching for new commits to multiple git repositories and feeding benchmark runs into gipeda
BSD 3-Clause "New" or "Revised" License
5 stars 1 forks source link

feed-gipeda does not react to a changed gipeda.yaml #12

Closed nomeata closed 8 years ago

nomeata commented 8 years ago

After changing the benchmarkScript in a repository, it seems that feed-gipeda still uses the previous one. Also other settings from gipeda.yaml in the repository are ignored.

Of course this needs some thought. Which gipeda.yaml should be used for checking a specific commit – always master, or always the one from the commit in question. Not easy...

sgraf812 commented 8 years ago

That's strange. I decided to always use the most recent commit's gipeda.yaml. I'll look into it.

I think using the most recent commit is the only viable solution here.

nomeata commented 8 years ago

I think using the most recent commit is the only viable solution here.

A problem could be if the benchmarkSkript refers to a file in the repository, then it may not be present in older versions. But we can leave that complexity to the user for now.

sgraf812 commented 8 years ago

After changing the benchmarkScript in a repository, it seems that feed-gipeda still uses the previous one.

I think I fixed that, but haven't really something to reproduce it anymore.

nomeata commented 8 years ago

Yes, seems to be fixed.