On Thu, Jan 16, 2014 at 02:12:44AM +0300, Kanstantsin Shautsou wrote:
@mls i had all service files in disabled mode, probably that why i end with new md5 for the same sources. Checksum for the same files is random, right?
Every new service run gets a new id, as the result may be different. Dunno if the service code checks if they are all disabled or not. And my idea in getting reproducible hashes if files not changed. For example: file1 hash1 file2 hash2
On Jan 16, 2014, at 17:07 , Michael Schroeder <mls@suse.de> wrote: then final hash = hash(hash1, hash2). File name should be also part of hash i suppose.
I want rework it and do repository copy in one call and without copies to job dirs and without stopping scheduler. How better implement this? I think then "obs_admin --clone-repository" can switch to this functionality then.
Conceptually the scheduler "owns" the build tree, i.e. it is assumed that only the scheduler does any changes. That way we don't need any locking, as just one process does the modifications.
That's also why things like binary uploads go through putting the files into a job dir and letting the scheduler do the integration part.
So the repo copy would IMHO need to be similar: stage the copy into some tmp job dir and let the scheduler do the final renaming.
Thanks, and what files can i link()? Hard link is used for build->jobdir and then for jobdir->newprj_builddir. New project files will be hard linked with src project and this potentially can effect if some daemon do open() for files. Also BSUtil:cp do open for src and dst that will cause in content changes for all hard linked files -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org