summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* Merge branch 'master' into releaser1.9.1Florian Zschocke2020-04-0517-80/+254
|\
| * 📖docs: Add update of service scripts in upgrade GO documentationFlorian Zschocke2020-04-052-4/+49
| | | | | | | | Also: release notes.
| * 🏃 run: Fix Linux service scripts to use classpath and classFlorian Zschocke2020-04-053-9/+9
| | | | | | | | | | | | | | Update the service scripts to use `-cp` and specify the GitBlitServer class, instead of the `-jar` parameter. Fixes #1333
| * 🏃run: Use quotes around class path in scriptsFlorian Zschocke2020-04-055-5/+5
| | | | | | | | | | | | | | | | | | While most systems will not need the class path passed to the JVM with the `-cp` parameter to be in quotes, apparently some exist where that will not work without the quotes, e.g. FreeBSD. So always use quotes for the class path in all scripts. Issue #1333
| * Change tests in shell scripts to be more compatible with Bourne shellFlorian Zschocke2020-04-052-2/+2
| | | | | | | | | | This is needed for the scripts to work in Alpine Linux, which comes with a Bourne shell.
| * Delete password from memory in AuthenticationManagerFlorian Zschocke2020-04-054-31/+125
| | | | | | | | | | | | Zero out the password to remove it from memory after use. This is only a first step, implementing it for one method: `AuthenticationManager.authenticate(String, char[], String)`.
| * 🦟 fix: Password hash upgrade kills existing passwordsFlorian Zschocke2020-04-052-21/+38
| | | | | | | | | | | | | | | | | | | | The upgrade of a MD5 stored password hash to a PBKDF password hash destroys the stored password. The has check zeroes out the password that is tested, so that the new hash is built over the zeroed out value. This fix prevents that an also adds a check to the test. Fixes #1335
| * docu: Fix typoFlorian Zschocke2020-04-041-1/+1
| |
| * Switch Eclipse repositories to HTTPS.Florian Zschocke2020-04-011-2/+2
| | | | | | | | | | | | | | | | | | | | | | The Eclipse maven repositories changed to only allow HTTPS and not serve HTTP anymore. HTTP will redirect to HTTPS, which moxie does not handle well and fails. So the registered Eclipse repositories are changed to 'https://' transport. Fixes #1334
| * Fix download link in README file.Florian Zschocke2020-02-021-1/+1
| |
| * Reset build identifiers for next point release cyclefzs2020-02-012-2/+20
| |
| * Prepare 1.9.0 releasev1.9.0fzs2020-02-012-10/+10
| |
* | ci: Set GitHub org to `gitblit` for release.r1.9.0Florian Zschocke2020-02-011-1/+1
| |
* | Only run the release workflow in my repo fzs/gitblitFlorian Zschocke2020-02-011-0/+1
| |
* | ci: Remove incorrect changes from the Maven artifacts.json fileFlorian Zschocke2020-02-011-1/+3
| | | | | | | | | | | | | | | | | | | | | | | | Moxie's deploy task updates the `artifacts.json` file in the Maven repository. But it does rewrite the whole file, not just add the newly deployed artifacts. Which causes the "last updated" dates for all artifacts in the repository to be rewritten. In our case, where the repository is a Git repo, if the Git repo is a fresh checkout, that resets all the dates to the checkout date. Therefore we adjust the `artifacts.json` file to only keep the update for the newly deployed artifacts, removing the other updates for the dates with some awk magic.
* | Add workflow to run a release against gitblit/gitblitFlorian Zschocke2020-01-311-0/+194
| |
* | Build: create macro for creating the release process scriptFlorian Zschocke2020-01-311-27/+60
|/ | | | | | | | | Refactor the creation of the release process script, from `release.template` into a `macrodef`. Add a new target `releaseScript`, so that the release script can be created after the `tagRelease` target was run. This is helpful if the `tagRelease` target is run by a different, earlier process than the actual release creation process.
* ci: Ignore all branches starting with `release`.Florian Zschocke2020-01-311-2/+1
| | | | Set the ignored branches pattern to `release*` for the normal ci workflow.
* Build: Set GitHub org to `gitblit` for release.Florian Zschocke2020-01-311-2/+2
|
* Merge branch 'release-github' into masterFlorian Zschocke2020-01-309-53/+2903
|\
| * Build: Store release version information in file.Florian Zschocke2020-01-301-2/+16
| | | | | | | | | | | | If requested, by setting a file name in the `versionInfo` property, store release version and tag in a file, for other scripts and programs to pick up.
| * Doc: Fix change log in built-in docsFlorian Zschocke2020-01-281-2/+8
| | | | | | | | | | Use the same templates as in `buildSite` to generate the change log in the built-in documentation.
| * Build: Fix output printsFlorian Zschocke2020-01-281-2/+2
| |
| * Add Maven Central to registeredRepositoriesFlorian Zschocke2020-01-281-0/+2
| | | | | | | | | | | | | | | | Moxie does have these defined by default, but with transport HTTP. Since January 2020, Maven Central only accepts HTTPS, no HTTP anymore. So we add them here explicitly, with `https://`. We add it to the `build.moxie` file, instead of keeping it in a local `settings.moxie`, so that a CI server can immediately use it.
| * Doc: Change download button on Readme to point to GitHubFlorian Zschocke2020-01-281-1/+1
| |
| * Doc: Remove Google+ from ReadmeFlorian Zschocke2020-01-281-1/+0
| | | | | | Since Google Plus doesn't exist any more...
| * Doc: Update built-in docs with missing pages and linksFlorian Zschocke2020-01-271-3/+8
| | | | | | | | | | | | | | | | Add pages for `fail2ban` and GFS to the `generateDocs` target, so that they also show up in the documentation on GO etc. Also adjust the links to issues and commits. Add the replacement of the download base URL.
| * Use GitHub org property in octokit callsFlorian Zschocke2020-01-271-6/+6
| |
| * Add Twitter link to site overview and built-in docs.Florian Zschocke2020-01-272-0/+2
| |
| * Site: Remove link to Bintray update notificationsFlorian Zschocke2020-01-271-2/+1
| |
| * Site: Change the download URL to GitHubFlorian Zschocke2020-01-271-9/+13
| |
| * Site: Remove Google Plus idFlorian Zschocke2020-01-271-2/+2
| | | | | | | | Google Plus is gone, so linking to it makes no sense anymore.
| * Add project property `release.tag` as a global `project.tag`Florian Zschocke2020-01-271-5/+6
| | | | | | | | | | | | | | | | | | | | | | Add property `release.tag` to keep a generally available property. The `project.tag` was getting used in many places, so I need a global definition for it. The property `project.tag`, defined in the target `tagRelease` could not be reused, since when that target runs, the version is still a SNAPSHOT version. (And properties don't get re-assigned.) So instead a new property `release.tag` is defined, just like `release.name`, which can be only used sensible in a release stage, i.e. after `tagRelease` ran.
| * Update the gh-pages branchFlorian Zschocke2020-01-272-0/+18
| | | | | | | | | | | | The site was generated, but updating the gh-pages branch was included in the `publishSite` target. So a new target is added and called, `updateSite`.
| * Adjust `release.template` for publishing releases on GitHubFlorian Zschocke2020-01-271-20/+44
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The major change is switching from `publishBinaries`, which still exists and uploads to Bintray, to `releaseBinaries`, which creates a draft release on GitHub and uploads the binaries. Another change is some reordering. Now first the binaries are uploaded, the maven artifacts pubished and the tag and site pages pushed. Then the GitHub release is made public. Only after that is the minor version bumped and pushed. The whole script could use some error checking and stoping when things go wrong, instead of blindly continuing. A minor change, and temporary, is that we need and check for Ant 1.9, as we still build with Java 7.
| * Add deployment of a release to GitHubFlorian Zschocke2020-01-273-9/+2785
| | | | | | | | | | | | | | | | | | | | | | | | Add Ant tasks and macros to deploy binaries to GitHub, using GitHub's releases. Adds an Awk script to extract GH flavoured markdown release notes from the release.moxie file. Adds `ok.sh` to the repository so that it is readily available. This is a Bourne shell GitHub API client, used to create a release on GitHub and upload the binaries.
| * Change single quotes to back ticks for formattingFlorian Zschocke2020-01-261-2/+2
| |
| * Run build and tests on Java 7.Florian Zschocke2020-01-111-1/+1
|/
* Merge branch 'ci' into masterFlorian Zschocke2020-01-111-0/+65
|\ | | | | | | | | | | Now we can also build on GitHub ci ignore
| * ci: Ignore release and gh-pages branches for CI build on pushFlorian Zschocke2020-01-111-1/+6
| |
| * ci: Add build with Java 7 on LinuxFlorian Zschocke2020-01-101-0/+29
| | | | | | | | | | | | | | Add a job to run a build with Java 7. The job currently only runs on Linux. In order to run on Java 7, an old Ant version is downloaded and installed. We use moxie+ant for this, so we build with moxie.
| * Build on matrix of latest Ubunutu and latest Windows.Florian Zschocke2020-01-051-1/+2
| | | | | | | | | | Currently that is Ubuntu 18.04 and Windows Server 2019. https://help.github.com/en/actions/automating-your-workflow-with-github-actions/virtual-environments-for-github-hosted-runners
| * Build as matrix of Java 8 and 11, only.Florian Zschocke2020-01-051-1/+1
| | | | | | | | | | We cannot build with Ant on GitHub since the provided Ant version does not run on Java 7.
| * Build with matrix of Java 7, 8 and 11.Florian Zschocke2020-01-051-5/+10
| |
| * Add ci workflow to build on every push.Florian Zschocke2020-01-051-0/+25
|/
* Update JGit to versoin 4.5.7.201904151645-rFlorian Zschocke2019-11-204-21/+10
|
* Correct issue in FAQ page to link to GitHub issue.Florian Zschocke2019-11-182-2/+2
|
* Add dependency javax.activation to WAR, manager and fedclient, too.Florian Zschocke2019-11-181-1/+1
| | | | | I actually don't know if it is needed for the manager and fedclient, but right now I'm going with better safe than sorry.
* Add pattern to create links to GitHub commits from release notes etc.Florian Zschocke2019-11-171-1/+2
|
* Change issue links in release history to point to correct GitHub issuesFlorian Zschocke2019-11-172-266/+266
|
generated by cgit v1.2.3 (git 2.39.1) at 2025-01-11 13:22:52 +0000