summaryrefslogtreecommitdiffstats
path: root/src/main/distrib
Commit message (Collapse)AuthorAgeFilesLines
...
* | Add .bat and .cmd to the pretty print extensionsJames Moger2014-11-241-1/+1
| |
* | Add support for image/svg+xml content type to raw servletJames Moger2014-11-191-1/+1
| |
* | Further diff improvementsTom2014-11-061-0/+26
| | | | | | | | - Add the new settings to gitblit.properties - Highlight trailing whitespace
* | Miscellaneous fixes to the Fedora service installer scriptBerke Viktor2014-10-311-5/+2
| |
* | Adopt chain-loading properties as the default setupJames Moger2014-10-272-1881/+1904
|/
* Treat .ico and .jpeg files as imagesBerke Viktor2014-10-061-1/+1
|
* Remove git.streamFileThreshold settingJames Moger2014-09-301-48/+0
|
* Repository url is now rThanksForAllTheFish2014-09-091-1/+1
| | | | The previous 'triggerUrl' version causes a response similar to 'No git jobs using repository: http://gitblit-host/gitblit/git/repo.git'. The wroking url is 'http://gitblit-host/gitblit/r/repo.git'. I also added brackets to improve readability
* Expose setting to control Lucene repository indexing frequencyJames Moger2014-09-081-0/+6
|
* distrib: Add script to install gitblit on fedoraSoeren Grunewald2014-09-041-0/+36
| | | | | | | | | The script will create a environment file keeping all the major settings and installs a systemd unit file. The script (mainly the unit file part) should also work for other systemd based distributions like ArchLinux. But /etc/sysconfig may not exist there. Signed-off-by: Soeren Grunewald <soeren.grunewald@desy.de>
* distrib: Highlight C/C++ header files by defaultSoeren Grunewald2014-09-041-1933/+1933
| | | | | | | We already highlight C/C++ source files with the default configuration, so we should do this also for header files. Signed-off-by: Soeren Grunewald <soeren.grunewald@desy.de>
* Pretty print perl modulesMichael Legart2014-09-041-1/+1
| | | Since perl scripts (.pl) was already supported, add .pm for perl modules
* Refine web.canonicalUrl documentationKyle Gottfried2014-07-011-2/+12
|
* Add setting to control inclusion of personal repositories in the main listJames Moger2014-06-051-0/+5
|
* Simplified repository creation with a NewRepositoryPageJames Moger2014-06-032-0/+5
|
* Clarify server.threadPoolSize documentationJames Moger2014-05-291-2/+5
|
* Add setting to control thread pool size for default work queueJames Moger2014-05-291-0/+6
|
* Merge branch 'ticket/84' into developJames Moger2014-05-231-1/+1
|\
| * Remove GitBlit static singleton reference from localclone.groovyJames Moger2014-05-231-1/+1
| |
* | Merged #67 "Allow disabling repository deletion"James Moger2014-05-091-0/+5
|\ \
| * | Move delete repository function into the edit pageJames Moger2014-05-091-1/+1
| | |
| * | Added option to disable deleting of non empty repositories through the user ↵peto2682014-05-081-0/+5
| | | | | | | | | | | | interface
* | | Add option to explicitly specify the use of STARTTLSBerke Viktor2014-05-081-0/+5
|/ / | | | | | | Required for servers that use STARTTLS without SMTPS such as Office 365
* | Merge branch 'ticket/63' into developJames Moger2014-05-071-0/+11
|\|
| * Allowed all transports for TortoiseGit and changed the project descriptionpbe2014-05-051-2/+1
| |
| * Added TortoiseGit to the clientappspbe2014-05-051-0/+12
| |
* | Implementation of a ticket mgration toolJames Moger2014-05-023-1/+43
|/
* fix the script so it REALLY works on LinuxMichel Daviot2014-04-271-1/+1
|
* Expose JGit 3.x receive pack settings as Gitblit settingsJames Moger2014-04-171-0/+41
|
* Improve plugin documentationJames Moger2014-04-111-24/+1
|
* DocumentationJames Moger2014-04-101-1/+3
|
* Allow specifying accepted PUSH transportsJames Moger2014-04-101-0/+10
|
* Implement simple JSON-based plugin registry and install commandJames Moger2014-04-101-8/+12
|
* Improve Sparkleshare integration, but leave disabled for nowJames Moger2014-04-101-1/+1
|
* Expose new property: sshCommandStartThreadsDavid Ostrovsky2014-04-101-0/+6
|
* Add plugins/extension infrastructureDavid Ostrovsky2014-04-101-0/+8
| | | | | | | | | | | | | | | | | | | | | | | | | 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-101-5/+0
|
* Add SSH daemon testDavid Ostrovsky2014-04-101-0/+5
|
* Add support for NIO2 IoSessionDavid Ostrovsky2014-04-101-0/+5
| | | | | | | | | | Starting from version 0.9.0 Apache SSHD project added support for NIO2 IoSession. To use the new NIO2 session the `backend` option must be set to `NIO2`. By default, `NIO2`. Change-Id: I06cf92b02e80ecf9e8bfbd9f6d6d623dfe3ccff3
* Extract key manager interface and implement a file-based key managerJames Moger2014-04-101-1/+10
|
* Listen for ssh clients on all interfaces, by defaultJames Moger2014-04-101-1/+1
|
* Establish ssh keys folder, support multiple keys, revise key authenticatorJames Moger2014-04-101-0/+5
|
* Support serving repositories over the SSH transportEric Myhre2014-04-101-0/+17
| | | | | | | Gitblit would greatly benefit from an integrated SSH server. This would complete the transport trifecta. Change-Id: I6fb95abe65655fa74d47ea71522d8d9a1541450c
* Configure Tickets close-on-push commit message regex (issue-404)James Moger2014-03-311-0/+7
|
* Enable the daily log for the Ubuntu and CentOS services (issue-348)James Moger2014-03-282-2/+2
|
* LDAP: Authenticated Searches without a manager passwordj3rem1e2014-03-271-0/+9
| | | | | | Allow to use the LDAP AuthProvider with a LDAP Server prohibiting anonymous searches but without providing a manager password : searches are made on behalf of the authenticated user.
* Listen for git daemon and fanout clients on all intefaces, by defaultJames Moger2014-03-081-2/+2
|
* Improve the GO reindex-tickets shell scriptsJames Moger2014-03-062-4/+22
|
* Add setting to hide the navbar for those embedding GitblitJames Moger2014-03-051-0/+8
|
* Ticket tracker with patchset contributionsJames Moger2014-03-034-0/+110
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
generated by cgit v1.2.3 (git 2.39.1) at 2025-01-28 07:41:41 +0000