1 |
On 01:34 Sun 16 Nov , Alec Warner wrote: |
2 |
> Change the workflow[1]. |
3 |
> |
4 |
> Right now you pay the cost of running tree-wide tests every time you |
5 |
> commit. This incentivizes developers to commit less often (to avoid |
6 |
> paying the tax of tree-wide tests). |
7 |
> |
8 |
> In CVS commiting less is a problem: |
9 |
> |
10 |
> 1. Make Changes to a number of files. |
11 |
> 2. Script your commits. |
12 |
> 3. Run Script |
13 |
> 4....N: Script commits one file at a time. |
14 |
> 4.5: A race condition between changes you have commited to CVS versus |
15 |
> uncommited changes occurs when CVS is synced to Osprey. This race |
16 |
> condition can often cause tree oddness. |
17 |
> 5. All Changes commited. |
18 |
> 5.5: All changes synced to Osprey. |
19 |
> |
20 |
> I am unsure if repoman category and repoman tree-wide commits avoid |
21 |
> this race condition. |
22 |
> |
23 |
> A new scheme would be: |
24 |
> |
25 |
> 1. Make Changes to a number of files. |
26 |
> 2. Category or Treewide Repoman commit. |
27 |
> 3. Run taxing tree-wide tests. |
28 |
> 4. git commit -a (?) |
29 |
> 5. Done! |
30 |
> |
31 |
> Tell me if I'm horribly wrong or missing something, it is late here. |
32 |
|
33 |
Are you saying we could use the index here? Another option (that you may |
34 |
or may not be suggesting) could be to make a new 'repoman push' |
35 |
operation that actually does the hard checks, and make 'repoman commit' |
36 |
just do a local commit and only very quick checks. |
37 |
|
38 |
-- |
39 |
Thanks, |
40 |
Donnie |
41 |
|
42 |
Donnie Berkholz |
43 |
Developer, Gentoo Linux |
44 |
Blog: http://dberkholz.wordpress.com |