blob: 60f8b47dd36f74f685ed96eb0a4b47672a7a52b2 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
|
## Extension Points
Gitblit offers several extension points for enhancing and customizing it's runtime behavior.
Each available extension point has a sample implementation in the [gitblit-cookbook-plugin (Maven project)](https://github.com/gitblit/gitblit-cookbook-plugin).
**NOTE:**
Gitblit does not yet offer a comprehensize dependency injection architecture. This will be addressed in a subsequent release. For now you may access all of Gitblit's core managers through a static singleton app context:
```java
import com.gitblit.extensions.GitblitPlugin;
import com.gitblit.servlet.GitblitContext;
import com.gitblit.manager.IRuntimeManager;
import com.gitblit.manager.IUserManager;
import com.gitblit.manager.IAuthenticationManager;
import com.gitblit.manager.INotificationManager;
import com.gitblit.manager.IRepositoryManager;
import com.gitblit.manager.IProjectManager;
import com.gitblit.manager.IFederationManager;
import com.gitblit.manager.IPluginManager;
import com.gitblit.manager.IGitblit;
import ro.fortsoft.pf4j.Version;
public class ExamplePlugin extends GitblitPlugin {
@Override
public void start() {
IRuntimeManager runtime = GitblitContext.getManager(IRuntimeManager.class);
IUserManager users = GitblitContext.getManager(IUserManager.class);
IAuthenticationManager auth = GitblitContext.getManager(IAuthenticationManager.class);
INotificationManager notifications = GitblitContext.getManager(INotificationManager.class);
IRepositoryManager repos = GitblitContext.getManager(IRepositoryManager.class);
IProjectManager projects = GitblitContext.getManager(IProjectManager.class);
IFederationManager federation = GitblitContext.getManager(IFederationManager.class);
IPluginManager plugins = GitblitContext.getManager(IPluginManager.class);
IGitblit gitblit = GitblitContext.getManager(IGitblit.class);
}
@Override
public void stop() {
}
@Override
public void onInstall() {
}
@Override
public void onUpgrade(Version oldVersion) {
}
@Override
public void onUninstall() {
}
}
```
### SSH Dispatch Command
*SINCE 1.5.0*
You can provide your own custom SSH command hierarchies by subclassing the *DispatchCommand* class.
```java
import ro.fortsoft.pf4j.Extension;
import org.kohsuke.args4j.Option;
import org.slf4j.Logger;
import org.slf4j.LoggerFactory;
import com.gitblit.models.UserModel;
import com.gitblit.transport.ssh.commands.CommandMetaData;
import com.gitblit.transport.ssh.commands.DispatchCommand;
import com.gitblit.transport.ssh.commands.UsageExample;
@Extension
@CommandMetaData(name = "mycommands", description = "Sample SSH dispatcher")
public class MyDispatcher extends DispatchCommand {
@Override
protected void setup() {
// commands in this dispatcher
register(CommandA.class);
register(CommandB.class);
// nested dispatchers
register(SubDispatcher1.class);
register(SubDispatcher2.class);
}
@CommandMetaData(name = "commanda", aliases = { "ca" }, description = "description of command a")
@UsageExample(syntax = "${cmd} --myflag", description = "description of commanda with --myflag")
public static class CommandA extends SshCommand {
protected final Logger log = LoggerFactory.getLogger(getClass());
@Option(name = "--myflag", aliases = { "-m" }, usage = "enable myflag")
boolean myflag;
@Override
public void run() throws Failure {
if (myflag) {
log.info("Run with --myflag");
} else {
log.info("Run without --myflag");
}
}
}
}
```
### Pre- and Post- Receive Hook
*SINCE 1.5.0*
You can provide your own custom pre and/or post receive hooks by subclassing the *ReceiveHook* class.
```java
import com.gitblit.extensions.ReceiveHook;
import java.util.Collection;
import org.eclipse.jgit.transport.ReceiveCommand;
import ro.fortsoft.pf4j.Extension;
@Extension
public class MyReceiveHook extends ReceiveHook {
@Override
public void onPreReceive(GitblitReceivePack receivePack, Collection<ReceiveCommand> commands) {
}
@Override
public void onPostReceive(GitblitReceivePack receivePack, Collection<ReceiveCommand> commands) {
}
}
```
### Patchset Hook
*SINCE 1.5.0*
You can provide your own custom patchset hook by subclassing the *PatchsetHook* class.
```java
import com.gitblit.extensions.PatchsetHook;
import com.gitblit.models.TicketModel;
import ro.fortsoft.pf4j.Extension;
@Extension
public class MyPatchsetHook extends PatchsetHook {
@Override
public void onNewPatchset(TicketModel ticket) {
}
@Override
public void onUpdatePatchset(TicketModel ticket) {
}
@Override
public void onMergePatchset(TicketModel ticket) {
}
}
```
### Ticket Hook
*SINCE 1.5.0*
You can provide your own custom ticket hook by subclassing the *TicketHook* class.
```java
import com.gitblit.extensions.TicketHook;
import com.gitblit.models.TicketModel;
import com.gitblit.models.TicketModel.Change;
import ro.fortsoft.pf4j.Extension;
@Extension
public class MyTicketHook extends TicketHook {
@Override
public void onNewTicket(TicketModel ticket) {
}
@Override
public void onUpdateTicket(TicketModel ticket, Change change) {
}
}
```
|
