summaryrefslogtreecommitdiffstats
path: root/src/test/java/com
Commit message (Collapse)AuthorAgeFilesLines
* Tickets - Priority, Severity optionsPaul Martin2014-10-203-4/+193
| | | | | | | | | + Severity indicated via new character indicator and color of ticket icon on ticket list + Priority indicated via new priority icon and color on ticket list + Indexed as integers to provide sorting and maintain language neutral index + Colours and indicator text controlled through CSS classes priority-<x> & severity-<x> + UITicketTest created to generate tickets of all types to ease debugging
* Merge release-1.6.1James Moger2014-10-201-1/+1
|\
| * Correct unit test assertionJames Moger2014-10-201-1/+1
| |
| * Fix GitBlitTest.testGitblitSettings()James Moger2014-10-131-1/+5
| |
* | Fix GitBlitTest.testGitblitSettings()James Moger2014-10-131-1/+5
| |
* | Merge branch 'ticket/161' into developJames Moger2014-09-081-4/+4
|\|
| * Expose setting to control Lucene repository indexing frequencyJames Moger2014-09-081-4/+4
| |
* | Merge branch 'ticket/164' into developJames Moger2014-09-079-14/+45
|\|
| * Create infrastructure for XSS sanitizationJames Moger2014-09-079-14/+45
| |
* | Extract services manager into a top-level injectable managerJames Moger2014-07-031-20/+0
| |
* | Use Guice-Servlet rather than custom code and expose the InjectorJames Moger2014-07-031-0/+6
|/ | | | | | | | | | | | | | | This is a fairly functional variation of Gitblit with one notable exception: The security filters are not working properly. This is a design flaw in Guice that I have reported upstream [1]. The general idea is that Guice-Servlet filters are not properly wrapping the ServletRequest. This has historically been a problem for Guice-Servlet servlets but Google has fixed most of those issues. Unfortunately, all the same flaws reported against the servlet delegation also exist in Guice-Servlet filter delegation. :( [1]: https://code.google.com/p/google-guice/issues/detail?id=807
* Add repository and user/team lifecycle listener extension pointsJames Moger2014-06-098-21/+21
|
* Add a basic SSH public key management UIJames Moger2014-06-051-0/+15
|
* Change enum name and unit test RSS tag queriesJames Moger2014-05-081-1/+35
|
* Revise, complete, and fully test the FORK rpcJames Moger2014-05-082-17/+63
|
* Implement FORK RPC request typemanisha2014-05-082-0/+17
|
* Implementation of a ticket mgration toolJames Moger2014-05-021-1/+4
|
* Fix inconsistency with owner permissions checkJames Moger2014-05-011-2/+40
|
* Fix forcing default locale to en or LANG_CC for web uiJames Moger2014-04-281-0/+6
|
* Prevent adding empty or invalid SSH public keysJames Moger2014-04-251-0/+14
|
* [findbugs] Reorder asserts to avoid potential NPE in JGitUtilsTestJames Moger2014-04-171-3/+5
|
* Organize importsJames Moger2014-04-171-1/+1
|
* Merge pr-170 'ticket-fix' from https://github.com/lucidd/gitblitJames Moger2014-04-151-0/+4
|\
| * fix NullPointerException in ITicketService and add TestCaseKevin Walter2014-04-151-0/+4
| |
* | Removed obsolete Gravatar profile codeJames Moger2014-04-151-32/+0
|/
* Add ssh command to update the permission for an SSH keyJames Moger2014-04-141-0/+16
|
* Add TicketHook extensionJames Moger2014-04-123-0/+12
|
* Add missing unit test utility classJames Moger2014-04-111-0/+33
|
* Unit tests for ssh daemon and keys dispatcherJames Moger2014-04-105-160/+322
|
* Split administration commands into a plugin, enhance plugin managerJames Moger2014-04-101-1/+1
|
* Handle ssh keys as objects, not strings, and improve the ls and rm key commandsJames Moger2014-04-101-1/+2
| | | | "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.
* Elevate the public key manager to a top-level managerJames Moger2014-04-103-53/+29
|
* Add SSH daemon testDavid Ostrovsky2014-04-104-1/+216
|
* LDAP: Added test for binding without special account (e.g. userbasedJani Averbach2014-03-311-0/+13
| | | bind)
* Implement setting removal for configuration settingsJames Moger2014-03-271-0/+5
|
* Fix authentication security hole with external providersJames Moger2014-03-183-11/+168
|
* Implement user "disabled" flag as an alternative to deleting the accountJames Moger2014-03-042-1/+67
|
* Ticket tracker with patchset contributionsJames Moger2014-03-035-1/+568
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
* Improve notification api by introducing the Mailing modelJames Moger2014-02-281-1/+4
|
* Added LdapSyncServiceTest to GitBlitSuite.Alfred Schmid2014-02-212-2/+3
|
* Fixed and introduced tests for synching ldap users and groups.Alfred Schmid2014-02-212-22/+90
| | | | | | | | Using new settings key realm.ldap.synchronize Switched from key String to Keys class. To avoid letting tests pass with hardcoded keys wich doesn't exist anymore. Now on Key Refactorings the test gets compile error again. Test the isReady behavior from LdapSyncService.
* API adjustments and elimination of duplicate config optionsJames Moger2014-02-191-5/+5
|
* Load empty groups as empty teams from ldap, when ldap userAlfred Schmid2014-02-191-0/+28
| | | | synchronization is enabled.
* Fixed Tests, use local copy of users.conf. Initialize reset ldap beforeAlfred Schmid2014-02-191-12/+31
| | | | every test.
* Basic implementation of feature for ldap user synchronization asAlfred Schmid2014-02-191-3/+40
| | | | | background service. Introduced configuration property to configure the synchronization period.
* Show "Displayname (username)" in palettes for edit team and repository pagesAlfred Schmid2014-02-193-0/+116
|
* Fixed test.Alex Lewis2013-12-231-1/+1
| | | | | | testRevlog was expecting 12 commits but getting 19. Looking at the hello-world repository on github (on which the test executes) the 19 commit count appears to be correct.
* Change IGitblit API to be more distinct from IUserServiceJames Moger2013-11-291-5/+5
| | | | Change-Id: I8fb38fb6a3dae74ad7a12b045b054373b9b02518
* Flattened IGitblitManager, GitblitManager, and GitBlit classesJames Moger2013-11-291-3/+3
| | | | Change-Id: Id6deb27306e0034898673bf5d5d76a4ed012ced6
* Revised committer verification to require email addressJames Moger2013-11-292-22/+10
| | | | Change-Id: I5298c93e03099813f5713a4effd87913429aa3dc
generated by cgit v1.2.3 (git 2.39.1) at 2025-03-20 22:01:03 +0000