Sitaram Chamarty
5d1adc63c2
(mkdoc) make it do a little more post-mkdoc work
2012-03-26 05:37:45 +05:30
Sitaram Chamarty
cf10f7933c
(minor) use 'sts' as the url for the ssh-troubleshooting page
...
when g3 becomes "master", the URL in the git info bot won't have to
change
2012-03-26 05:37:45 +05:30
Sitaram Chamarty
2845de74ea
Easy.pm learns config(), acquires a test script
2012-03-25 19:31:01 +05:30
Sitaram Chamarty
2139099706
arguments in rc for triggered programs...
...
...using 'renice' as example and first user
(also had to re-arrange rc file to a more sensible order)
2012-03-25 12:17:37 +05:30
Sitaram Chamarty
cb9794d55b
warn about test suite clobbering lots of stuff
...
(not just ~/.ssh!)
2012-03-25 11:07:11 +05:30
Sitaram Chamarty
8de959476f
fixup: new check-g2-compat, lots of migration related changes
2012-03-25 11:07:11 +05:30
Sitaram Chamarty
3ed923f503
new check-g2-compat, lots of migration related changes
...
- rc differences moved to their own file
- main g2migr now helps interpret output of check-g2-compat
- Gitolite::Compat gone; no point...
2012-03-25 09:43:23 +05:30
Sitaram Chamarty
c14e01d6c0
new 'gitolite print-default-rc' command
2012-03-25 09:19:38 +05:30
Sitaram Chamarty
863a732080
minor fixup to mkdoc; also pulled in Markdown.pl
2012-03-25 05:12:30 +05:30
Sitaram Chamarty
4f7d3d8651
Q: all doc stuff
2012-03-24 18:22:11 +05:30
Sitaram Chamarty
efb29ed135
enhance usage message for 'gitolite setup'
2012-03-24 10:30:46 +05:30
Sitaram Chamarty
8bffbfa02a
3 old VREFs moved in,
...
untested but they're just update hooks anyway so they should work fine
2012-03-24 10:30:46 +05:30
Sitaram Chamarty
eeed52ba2e
list-users acquires an optional repo name patten to speed things up
...
but see warnings in usage text.
2012-03-24 10:30:46 +05:30
Sitaram Chamarty
35ec0cf927
renamed ssh tests to prevent accidents to ~/.ssh
2012-03-24 10:30:46 +05:30
Sitaram Chamarty
329d757167
partial-copy: manually spot-tested (i.e., no test in suite). PW.
2012-03-24 10:30:46 +05:30
Sitaram Chamarty
0748b1225b
external programs can get settings from rc; see below
...
non-core programs can get their settings from the rc file also.
cpu-time is a perl example and desc is a shell example.
(info is not a good example because it does not use "Gitolite::Easy")
2012-03-24 10:30:46 +05:30
Sitaram Chamarty
0b8b144630
trigger prefixes an extra first argument -- the trigger name
2012-03-24 10:30:46 +05:30
Sitaram Chamarty
b39100053d
POST_GIT triggers get 4 more arguments
2012-03-24 10:30:45 +05:30
Sitaram Chamarty
14e1354433
query-rc learns '-q' option
2012-03-24 10:30:45 +05:30
Sitaram Chamarty
e9ea674be9
(minor) fixup various TODOs and such
...
some got junked, some were already done or got done, and some were
converted into actual todo items in the 'todo' file.
2012-03-24 10:30:45 +05:30
Sitaram Chamarty
446a611327
enhance the projects.list updater to look at 'gitweb.*' config settings also
...
(not just 'R = gitweb')
Can you tell I really, really, don't want anything to do with gitweb and
daemon to be part of gitolite *core*? :-)
2012-03-24 10:30:45 +05:30
Sitaram Chamarty
1c590e633f
run compat checks when old rc found
...
(also removed legacy-delegation sugar script)
2012-03-24 10:30:45 +05:30
Sitaram Chamarty
8dc43affdb
minor changes to testing setup
2012-03-24 10:30:45 +05:30
Sitaram Chamarty
938acc589f
test daemon/gitweb updates by setting perms
2012-03-24 10:30:45 +05:30
Sitaram Chamarty
320356d66c
cleaned up logging quite a bit; details:
...
- a remote "id" (usually the IP) is generated and logged on the first
log message in a "transaction"
- speaking of which, a new "transaction ID" is logged that stays the
same for each input command/invocation, tying together all the
spawned commands
- so now time stamps can be generated each time they are needed,
rather than re-use the one at the beginning
- log messages have a keyword at the start now
remote, (create), check1 -- from gitolite-shell
update, check2 -- from update
post-up -- from post-update
command -- from gitolite
die, system -- from anywhere
2012-03-24 10:30:45 +05:30
Sitaram Chamarty
bb9f045ec3
trigger POST_CREATE from user actions
...
- uncomment the POST_CREATE section in rc by default now
- have perms call 'gitolite trigger POST_CREATE'
2012-03-24 10:30:45 +05:30
Sitaram Chamarty
5e2e13aac2
review all user input, system(), and ``
2012-03-24 10:30:45 +05:30
Sitaram Chamarty
98a6b08ff4
'desc' command added (manually smoke tested only; no test script)
2012-03-24 10:30:45 +05:30
Sitaram Chamarty
878bb3009a
last check in the "dammit, don't call creator() on a missing repo" series :)
2012-03-24 10:30:45 +05:30
Sitaram Chamarty
80a234c0f6
upgraded the basic test a bit for quicker turnaround on some experiments
2012-03-24 10:30:45 +05:30
Sitaram Chamarty
661fefbd0e
added more personal branch tests
2012-03-24 10:30:45 +05:30
Sitaram Chamarty
139c08d3a1
abort on suspicious ref names
...
(and the other Dan Carpenter finding too, while we're about it!)
Note that neither of these is an actual issue, (and even less likely now
that gitolite is pure perl and no shell metas used) but it's just
playing safe.
2012-03-24 10:30:45 +05:30
Sitaram Chamarty
999f9cd39d
make site-local scripts easier to write
...
- new Gitolite::Easy module hides all the other stuff
- (put GL_ADMIN_BASE and GL_REPO_BASE into %ENV)
- new 'gitolite creator' shell command
- 'writes' command modified to use Gitolite::Easy. It is also the
only dual mode command -- it can be invoked remotely as well as
locally. I deem that the required trick to make other remote-only
commands work locally is too much trouble for what is probably a
rarely used command.
2012-03-24 10:30:45 +05:30
Sitaram Chamarty
5deafb6823
fix some "this specific user" dependencies for testing
2012-03-24 10:30:45 +05:30
Sitaram Chamarty
43f95f9b22
(minor) help command usage message changed
2012-03-24 10:30:45 +05:30
Sitaram Chamarty
f0355d749b
'gitolite writes off/on...' done
2012-03-24 10:30:45 +05:30
Sitaram Chamarty
1ec8be663e
(test infrastructure) CLONE/PUSH macros redefined
2012-03-24 10:30:45 +05:30
Sitaram Chamarty
bc2bd7a78c
oops; the $repo argument to PRE_ and POST_GIT triggers was wrong!
2012-03-24 10:30:45 +05:30
Sitaram Chamarty
1de773ab8e
perm-roles.t
2012-03-24 10:30:44 +05:30
Sitaram Chamarty
34cfdb4355
add some checks to perms
...
- check user auth
- check role names in legacy mode
2012-03-24 10:30:44 +05:30
Sitaram Chamarty
a6d8184a56
rule sequences test
2012-03-24 10:30:44 +05:30
Sitaram Chamarty
ed47d1aef8
two significant fixes to load:
...
- don't look for user-roles if the repo is missing (doesn't make sense
and because we roll in the <perm> = CREATOR function into that, it
causes bugs like [1] below)
- allow ^CREATOR/ in repo names (i.e., don't insist it has to be
/CREATOR/)
----
[1] here's the bug
repo foo/..*
C = u1
RW+ = CREATOR # <--- this line
R = READERS
RW = WRITERS
causes
GL_USER=u2 gitolite info
to print
hello u2, this is gitolite3 (unknown) on git 1.7.7.6
R W foo/..*
R W testing
when in reality it should not be looking at CREATOR at all.
2012-03-24 10:30:44 +05:30
Sitaram Chamarty
545c00aa26
perms with groups test
2012-03-24 10:30:44 +05:30
Sitaram Chamarty
741512482b
'info' learned not to show ^C column when used with '-p'
2012-03-24 10:30:44 +05:30
Sitaram Chamarty
2e1f840f13
'info' learns '-lc' option (and load.pm exports creator())
2012-03-24 10:30:44 +05:30
Sitaram Chamarty
9f1e360ef3
deny-create test (the RWC stuff)
2012-03-24 10:30:44 +05:30
Sitaram Chamarty
0614655252
(minor) sequence.t
2012-03-24 10:30:44 +05:30
Sitaram Chamarty
3f7edfea67
usage() needed some minor fixes...
2012-03-24 10:30:44 +05:30
Sitaram Chamarty
32494cfa0c
info learned '-p' and pattern limiting.
...
'-p' is what gives you 'expand' now
2012-03-24 10:30:44 +05:30
Sitaram Chamarty
5b5c02f226
merge-check test
2012-03-24 10:30:44 +05:30