- Timestamp:
- Jun 13, 2009, 6:59:08 PM (16 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
trunk/scripts/git-hooks/notes
r2350 r2358 5 5 nothing else? 6 6 7 superrepo heads are dev, prod 7 superrepo heads are dev, prod, and dev-incoming, prod-incoming 8 8 on commit to superrepo: 9 reject commits to dev, prod 10 grab lock or fail 11 spawn build process 12 zephyr 13 14 in build process for foo-incoming: 9 15 for each changed submodule revision: 10 16 (as optimization: if same commit already in dev, just reprepro move) 11 17 try to build submodule 12 18 if fail: 13 abort whole commit19 abort whole build 14 20 clean up any previous packages' built files, maybe keep this one's around 15 21 remember package and version … … 18 24 upload to dev/prod respectively 19 25 clean up built files 20 actually commit 26 commit to foo 27 zephyr? 28 release lock 29 if fail: 30 reset foo-incoming to old revision 31 send mail with log 21 32 zephyr 33 release lock 22 34 23 This makes a long pre-receive process. Is that cool? 24 Probably is the right thing. 25 35 Maybe there could be something sane without the lock? It'd require 36 more thought.
Note: See TracChangeset
for help on using the changeset viewer.