summaryrefslogtreecommitdiffstats
path: root/src/main/java/com/gitblit/manager
Commit message (Collapse)AuthorAgeFilesLines
...
* Simplify current plugin release detection, ignore currentRelease registry fieldJames Moger2014-04-231-1/+1
|
* Filter the current plugin release by the system versionJames Moger2014-04-171-1/+1
|
* [findbugs] Fix potential NPE on determining hasOrigin on loading a modelJames Moger2014-04-171-1/+2
|
* [findbugs] Clarify class used for resource loadingJames Moger2014-04-171-2/+2
|
* Update javadocJames Moger2014-04-1710-2/+139
|
* Add plugin (un)install lifecycle methodsJames Moger2014-04-173-5/+31
|
* Enforce plugin-requires attributeJames Moger2014-04-153-3/+32
|
* Upgrade plugin commandJames Moger2014-04-133-0/+40
|
* Eliminate plugin name, stick with id and descriptionJames Moger2014-04-122-8/+8
|
* Allow user to disable checksum verification on plugin registry refreshJames Moger2014-04-112-3/+5
|
* Ensure plugins dir is created before pf4j is instantiatedJames Moger2014-04-111-3/+4
|
* Improve plugin manager based on upstreamed contributions to pf4jJames Moger2014-04-103-120/+388
|
* Rename SSH key store on user renameJames Moger2014-04-101-0/+3
|
* Fix ${baseFolder}/plugins mkdir bugJames Moger2014-04-101-0/+1
|
* Implement simple JSON-based plugin registry and install commandJames Moger2014-04-103-7/+327
|
* Split administration commands into a plugin, enhance plugin managerJames Moger2014-04-103-17/+90
|
* Handle ssh keys as objects, not strings, and improve the ls and rm key commandsJames Moger2014-04-103-12/+11
| | | | "gitblit keys ls" now defaults to showing an indexed list of fingerprints which almost matches the output of "sshadd -l". The indexes are useful specifying key(s) to remove using "gitblit keys rm <index>". This is an important improvement for key management.
* Improve isServingRepositories checkJames Moger2014-04-102-1/+9
|
* Exclude SSH repository urls from anonymous usersJames Moger2014-04-101-0/+4
|
* Style: changed manager order to reflect dependency chainJames Moger2014-04-102-7/+7
| | | | Managers are mostly declared in dependency order. Managers with fewer dependencies are first. They are likely to be components of other managers. Also eliminated import artifacts from the cherry-pick.
* Add plugins/extension infrastructureDavid Ostrovsky2014-04-104-2/+114
| | | | | | | | | | | | | | | | | | | | | | | | | Plugins are stored in `${baseFolder}/plugins` and are loaded during startup by the PluginManager. A plugin defines it's metadata in META-INF/MANIFEST.MF: Plugin-Class: com.gitblit.plugins.cookbook.CookbookPlugin Plugin-Dependencies: foo, bar Plugin-Id: gitblit-plugin Plugin-Provider: John Doe Plugin-Version: 1.0 Plugins can define extension points that can be implemented by other plugins and they can depend on other plugins: Plugin-Dependencies: foo, bar During the load phase, a directed acyclic graph is built and the loading order of the dependency chain is reversed using a topological sort; parent followed by children. The parent plugin classloader is the combined classloader of all parent plugins. Change-Id: I738821fa2bff02a5dbe339a944cc7e3c4dd8e299
* Elevate the public key manager to a top-level managerJames Moger2014-04-102-0/+18
|
* Revise SSH public key integration with AuthenticationManagerJames Moger2014-04-103-18/+29
|
* Fix incorrect displayed SSH transport permissionJames Moger2014-04-101-20/+2
|
* Display ssh clone urls in the repository url panelJames Moger2014-04-101-2/+61
|
* Establish ssh keys folder, support multiple keys, revise key authenticatorJames Moger2014-04-101-1/+1
|
* Move Git daemon into different packageJames Moger2014-04-101-1/+1
|
* SSHD: Add support for git pack commandsDavid Ostrovsky2014-04-104-1/+39
| | | | | | | | | | | Add git-upload-pack and git-receive-pack commands. Conflicts: src/main/java/com/gitblit/manager/ServicesManager.java src/main/java/com/gitblit/transport/ssh/CommandDispatcher.java src/main/java/com/gitblit/transport/ssh/SshCommandFactory.java Change-Id: I8c057b41f1dfad6d004e6aa91f96c8c673be9be2
* Eliminate use of Dagger and do not create inner classesJames Moger2014-04-101-53/+4
| | | | | | | | | | | This change outlines somethings I'd like to see in your latest code. 1. Elimination of Dagger 2. Less noise from inner class instantiation 3. Formalizing filesystem location for keys instead of Unix-y /tmp/ 4. Password authentication as alternative to Key authentication Change-Id: I7a76e1811ad7cd545444fd8b59bbe8c4f45ccfec
* Factor out methods from SshCommandServer to SshDaemonDavid Ostrovsky2014-04-101-1/+54
| | | | Change-Id: I02d545a8ab68b06d733ad8e7ed476767a34aa244
* Support serving repositories over the SSH transportEric Myhre2014-04-101-0/+18
| | | | | | | Gitblit would greatly benefit from an integrated SSH server. This would complete the transport trifecta. Change-Id: I6fb95abe65655fa74d47ea71522d8d9a1541450c
* Ensure repositories folder is created before executing a write testJames Moger2014-04-071-0/+3
|
* Fix missing subject in html mailingsJames Moger2014-03-211-0/+1
|
* Fix authentication security hole with external providersJames Moger2014-03-181-29/+44
|
* Exclude ticket branches when forking a canonical repositoryJames Moger2014-03-111-2/+32
|
* Allow configuring the default integration branch for a repositoryJames Moger2014-03-081-0/+7
|
* Implement user "disabled" flag as an alternative to deleting the accountJames Moger2014-03-041-8/+29
|
* Ticket tracker with patchset contributionsJames Moger2014-03-033-0/+30
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | A basic issue tracker styled as a hybrid of GitHub and BitBucket issues. You may attach commits to an existing ticket or you can push a single commit to create a *proposal* ticket. Tickets keep track of patchsets (one or more commits) and allow patchset rewriting (rebase, amend, squash) by detecing the non-fast-forward update and assigning a new patchset number to the new commits. Ticket tracker -------------- The ticket tracker stores tickets as an append-only journal of changes. The journals are deserialized and a ticket is built by applying the journal entries. Tickets are indexed using Apache Lucene and all queries and searches are executed against this Lucene index. There is one trade-off to this persistence design: user attributions are non-relational. What does that mean? Each journal entry stores the username of the author. If the username changes in the user service, the journal entry will not reflect that change because the values are hard-coded. Here are a few reasons/justifications for this design choice: 1. commit identifications (author, committer, tagger) are non-relational 2. maintains the KISS principle 3. your favorite text editor can still be your administration tool Persistence Choices ------------------- **FileTicketService**: stores journals on the filesystem **BranchTicketService**: stores journals on an orphan branch **RedisTicketService**: stores journals in a Redis key-value datastore It should be relatively straight-forward to develop other backends (MongoDB, etc) as long as the journal design is preserved. Pushing Commits --------------- Each push to a ticket is identified as a patchset revision. A patchset revision may add commits to the patchset (fast-forward) OR a patchset revision may rewrite history (rebase, squash, rebase+squash, or amend). Patchset authors should not be afraid to polish, revise, and rewrite their code before merging into the proposed branch. Gitblit will create one ref for each patchset. These refs are updated for fast-forward pushes or created for rewrites. They are formatted as `refs/tickets/{shard}/{id}/{patchset}`. The *shard* is the last two digits of the id. If the id < 10, prefix a 0. The *shard* is always two digits long. The shard's purpose is to ensure Gitblit doesn't exceed any filesystem directory limits for file creation. **Creating a Proposal Ticket** You may create a new change proposal ticket just by pushing a **single commit** to `refs/for/{branch}` where branch is the proposed integration branch OR `refs/for/new` or `refs/for/default` which both will use the default repository branch. git push origin HEAD:refs/for/new **Updating a Patchset** The safe way to update an existing patchset is to push to the patchset ref. git push origin HEAD:refs/heads/ticket/{id} This ensures you do not accidentally create a new patchset in the event that the patchset was updated after you last pulled. The not-so-safe way to update an existing patchset is to push using the magic ref. git push origin HEAD:refs/for/{id} This push ref will update an exisitng patchset OR create a new patchset if the update is non-fast-forward. **Rebasing, Squashing, Amending** Gitblit makes rebasing, squashing, and amending patchsets easy. Normally, pushing a non-fast-forward update would require rewind (RW+) repository permissions. Gitblit provides a magic ref which will allow ticket participants to rewrite a ticket patchset as long as the ticket is open. git push origin HEAD:refs/for/{id} Pushing changes to this ref allows the patchset authors to rebase, squash, or amend the patchset commits without requiring client-side use of the *--force* flag on push AND without requiring RW+ permission to the repository. Since each patchset is tracked with a ref it is easy to recover from accidental non-fast-forward updates. Features -------- - Ticket tracker with status changes and responsible assignments - Patchset revision scoring mechanism - Update/Rewrite patchset handling - Close-on-push detection - Server-side Merge button for simple merges - Comments with Markdown syntax support - Rich mail notifications - Voting - Mentions - Watch lists - Querying - Searches - Partial miletones support - Multiple backend options
* Move GarbageCollector repository methods to the RepositoryManagerJames Moger2014-02-283-4/+76
|
* Improve notification api by introducing the Mailing modelJames Moger2014-02-283-147/+34
|
* Do not grant fork CLONE permissions to users/teams with implied regexJames Moger2014-02-261-5/+6
| | | CLONE permissions (issue-320)
* Reset the commit cache on repository deletionJames Moger2014-02-211-0/+2
|
* API adjustments and elimination of duplicate config optionsJames Moger2014-02-191-0/+7
|
* issue-361: Reset user cookie after administrative password changeJames Moger2014-01-283-26/+48
| | | | | | | Cookies were not reset on administrative password change of a user account. This allowed accounts with changed passwords to continue authenticating. Cookies are now reset on password changes, they are validated on each page request, AND they will now expire 7 days after generation.
* New canonical base url setting for repository urls and notificationsJames Moger2013-12-301-1/+5
| | | | Change-Id: I86a1eb61c2351d1cf3f6b3becf00f2a36d5c8ed6
* Support customizing the "from" display name for generated emailsJames Moger2013-12-303-3/+59
| | | | Change-Id: Ibad9e2b1c12a24ad9c671a0d96aafb3365daa529
* Fix NPE in getting a user's fork if repository caching is disabledJames Moger2013-12-111-1/+1
| | | | Change-Id: I10e90f54964daa32d954b47a8a6d54267b215222
* Fix external authentication failureJames Moger2013-12-111-2/+3
| | | | Change-Id: I0f415941a4bfd5e63d85c60613cea0c7d10cbb49
* Added filesystem write permission check (issue-345)James Moger2013-11-293-4/+22
| | | | Change-Id: I0a3aced3b8e9887347888c85e469b74fc70931ad
* Invalidate all cached repository data on "clear cache" (issue-346)James Moger2013-11-291-0/+2
| | | | Change-Id: I14404e38bbc6f5827c430849baf3c13f4df2c6ef
generated by cgit v1.2.3 (git 2.39.1) at 2025-07-28 09:28:10 +0000