summaryrefslogtreecommitdiffstats
path: root/build.moxie
Commit message (Collapse)AuthorAgeFilesLines
* Add plugins/extension infrastructureDavid Ostrovsky2014-04-101-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | 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
* Bump SSHD version to 0.10.1David Ostrovsky2014-04-101-1/+3
| | | | Change-Id: Ic7e204fb7ee2eb172f4c8424fc3d4b7e6c631ddd
* Support serving repositories over the SSH transportEric Myhre2014-04-101-0/+2
| | | | | | | Gitblit would greatly benefit from an integrated SSH server. This would complete the transport trifecta. Change-Id: I6fb95abe65655fa74d47ea71522d8d9a1541450c
* Remove remaining GoogleCharts code and update documentationJames Moger2014-04-101-1/+0
|
* Update to JGit 3.3.1James Moger2014-03-271-1/+1
|
* Replace JCommander with args4jJames Moger2014-03-271-1/+1
|
* Change build identifier to 1.5.0-SNAPSHOTJames Moger2014-03-271-1/+1
|
* Reset build identifiers for next development cycleJames Moger2014-03-181-1/+1
|
* Prepare 1.4.1 releasev1.4.1James Moger2014-03-181-3/+3
|
* Reset build identifiers for next development cycleJames Moger2014-03-091-1/+1
|
* Prepare 1.4.0 releasev1.4.0James Moger2014-03-091-3/+3
|
* Update to JGit 3.3.0James Moger2014-03-051-3/+3
|
* Ticket tracker with patchset contributionsJames Moger2014-03-031-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
* Update to JGit 3.2.0James Moger2013-12-201-1/+1
| | | | Change-Id: I77475dedfecbdc7ba3c065886a51b7a70b7ece48
* Support Markdown image links relative to the repository root (issue-324)James Moger2013-12-091-1/+1
| | | | Change-Id: I8bad02b26a20636e4fc3d1f0ab0a16f0bacc7bf1
* Add support for per-repository bugtraq configurationJames Moger2013-12-031-0/+3
| | | | | | | | | | | | | | | | | | | Imported the reference implementation contributed by syntevo which is used in their SmartGit product. You may create a bugtraq config section inf your .git/config file OR you may add a .gitbugtraq file to the root of your repository. Example: [bugtraq "issues"] url = http://code.google.com/p/gitblit/issues/detail?id=%BUGID% logRegex = "[Ii]ssue[-#:\\s]{1}\\d+" logRegex1 = "\\d+" [bugtraq "[pullrequests"] url = "https://github.com/gitblit/gitblit/pull/%BUGID%" logRegex = "(?:pull request|pull|pr)\\s*[-#]?([0-9]+)" Change-Id: Iaba305bf4280d08cc4d1abf533c2f1365470a43f
* Bump bouncycastle version to 1.49David Ostrovsky2013-12-021-1/+1
| | | | Change-Id: I0ea81f6c45748af3130721b8f8a7244eac9787fc
* Update to Lucene 4.6.0 (pull request #124)James Moger2013-11-291-1/+3
| | | | Change-Id: I21b0daf0550dcc2f12f1712e7b7cf519358a7a1d
* Refactor managers and authentication for federationJames Moger2013-11-291-2/+2
| | | | Change-Id: I5ff18b2768095fb14e7fbece2e756115829abbde
* Use Dagger to inject managers into all filters and servletsJames Moger2013-11-291-0/+4
| | | | Change-Id: I9bb2cc0cbfac9841b13bed15a474fefb24355cd4
* Update to Moxie 0.9.1James Moger2013-11-291-1/+1
| | | | Change-Id: I8e0479b632af3b5ca809aacf955e4be96822ac2c
* Update to Jetty 8.1.13 for Servlet 3James Moger2013-11-261-1/+1
| | | | Change-Id: If3f30af2ed250968e65cde58bd413213f4d384b1
* Update Moxie to 0.9.0James Moger2013-11-191-1/+1
| | | | Change-Id: Ia4c9536282af6df3d9d462946dec1d8112459242
* Add markup support for confluence, mediawiki, textile, trac, and twikiJames Moger2013-11-121-0/+7
| | | | Change-Id: I82ef161c6b6956c7b83cd4a1c37627beac6ea75b
* Replaced MarkdownPapers with pegdownJames Moger2013-10-181-1/+1
| | | | Change-Id: I11eb50ba1ef0bef8ac47bf6f7b17e0f79ecd3f2d
* Update to JGit 3.1.0James Moger2013-10-161-5/+5
| | | | Change-Id: I94d4f6146c79541bf8a36e4c3dca1842e46cddd5
* Updated to Jetty 7.6.13James Moger2013-10-021-1/+1
|
* Merge branch 'init-shared' of https://github.com/fzs/gitblit into prefixesJames Moger2013-09-171-0/+1
|\
| * Add commons-io to explicit dependencies.Florian Zschocke2013-08-261-0/+1
| | | | | | | | | | | | Add the commons-io library explicitly to the depencencies. It was already present as a transitive dependency but is now used in code. Using the version 2.2 as that got so far already packaged in ext.
* | Revisions and documentation for personal repository prefix changeJames Moger2013-09-171-1/+1
| |
* | Reset build identifiers for next development cycleJames Moger2013-08-221-1/+1
|/
* Prepare 1.3.2 releasev1.3.2James Moger2013-08-221-3/+3
|
* Add an Apache htpasswd user serviceFlorian Zschocke2013-08-121-0/+1
| | | | | | | Add a new class, HtpasswdUserService, which performs authentication against a text file created with the Apache 'htpasswd' program. Added dependency on commons-codec:1.7
* Added maintaining a Maven repository to the build release processJames Moger2013-07-251-0/+1
|
* Reset build identifiers for next development cycleJames Moger2013-07-241-1/+1
|
* Prepare 1.3.1 releasev1.3.1James Moger2013-07-241-3/+3
|
* Added PAMUserService for local Linux/Unix/MacOSX account authenticationJames Moger2013-07-231-0/+1
|
* Reset build identifiers for next development cycleJames Moger2013-07-141-1/+1
|
* Prepare 1.3.0 releasev1.3.0James Moger2013-07-141-4/+3
|
* Updated to JGit 3.0.0.201306101825-rJames Moger2013-06-281-1/+1
|
* Added WindowsUserService using WaffleJames Moger2013-06-201-0/+1
|
* Generate filterable project/repository list with FreeMarkerJames Moger2013-06-191-0/+1
|
* Added support for authenticating against a Salesforce org.William Whittle2013-06-071-0/+1
|
* Update to Moxie 0.7.4 to fix prefix index merging bugJames Moger2013-04-261-1/+1
|
* Update to Moxie 0.7.3James Moger2013-04-261-1/+1
|
* Completed migration to JGit 3.0.0-SNAPSHOTJames Moger2013-04-151-2/+2
|
* Bump JGit version to 3.0.0-SNAPSHOTDavid Ostrovsky2013-04-141-2/+2
|
* Fixed NPE in FedClient and support --baseFolder in FedClient (issue 219)James Moger2013-03-291-1/+1
|
* Restored missing Windows distrib files lost during the refactorJames Moger2013-03-281-3/+0
|
* Reorganized to Apache Standard Directory Layout & integrated MoxieJames Moger2013-03-271-0/+161
This is a massive commit which reorganizes the entire project structure (although it is still monolithic), removes the Build classes, and switches to Moxie, a smarter Ant build tookit based on the original Gitblit Build classes. The Ant build script will likely require additional fine-tuning, but this is big step forward.
generated by cgit v1.2.3 (git 2.39.1) at 2024-12-26 13:53:37 +0000