Download the PHP package daltcore/release-tools without Composer
On this page you can find all versions of the php package daltcore/release-tools. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package release-tools
Release tools for Projects
Installation
Via composer:
or
Via executable:
Go to releases and add this executable to your $PATH environment.
Initialize ReleaseTools on current running repo. Creates .release-tools directory and .release-tool file.
Check if ReleaseTools is ready for use
If you want to know more about thestructure behind ReleaseTools
then you can use the -v flag behind every command to see the
verbose info
_If a error occurs then you can add the -vvv parameter to the tool. A stack-trace will be shown.
Usage
Development
In development you should make a new branch for all your features/changes.
Release tools makes use of the current branch name for file naming for the changelog files.
Adding a new changelog file to the repo, this command is interactive.
For testing you can use --dry-run as parameter
Implement git hook to force you to make a changelog entry
Releasing
In development you want to run the prepare command which will create a issue in the repo that is specified in the .release-tools file
For testing you can use --dry-run as parameter
Building changelog file
For testing you can use --dry-run as parameter
List all pending changelogs
Building a stub:
If you need to create a custom stub for release-tool prepare you can
create a file called prepare.stub in the directory .release-tools/stubs
These files are markdown files and the following variables are available:
- :version This represents the version you fill when askes
- :reop This represents the
repovariable from the.release-toolfile
This wil override as the issue template pushed to GitLab when releasing.
Example:
Building playbooks:
If you need to create a custom playbook for release-tool playbook <playbook-name> you can
create a file called <name>.rtp in the directory .release-tools/playbooks
These files are yaml files and the following variables are available:
- :version This represents the version you fill when askes
- :reop This represents the
repovariable from the.release-toolfile
Example:
The example contains all available methods for playbooks.
.release-tools file example
License
All versions of release-tools with dependencies
symfony/finder Version ^3.3
m4tthumphrey/php-gitlab-api Version ^8.0
php-http/guzzle6-adapter Version ^1.1
symfony/filesystem Version ^3.3
symfony/console Version ^3.3
symfony/var-dumper Version ^3.3
symfony/process Version ^3.3
symfony/event-dispatcher Version ^3.3
thibaud-dauce/mattermost-php Version ^1.0