bytepark/release

A release tool that lets you deploy your web project via multiple methods (rsync, rpm, deb) Written in Bash.

release's Issues

Merge methods "rsync" and "dump"

Methods "rsync" and "dump" are basically the same, both use rsync - the only difference is the direction they transfer files.

This can simply be handled with a config variable.

debian packaging: support for multiple control files missing

When using the release tool for packaging of debian deb files you need to provide a control file.
When you have multiple deb-config targets defined they would all take the same control file at .release/debian/control - there is no way to define the control file to use.

Unit test the dialog view

As the maintainer of the release tool, I want to be sure that the view implementation dialog defines all the declared variables of the interface script and assigns concrete functions to these.

Idea: make use of subshells to encapsulate working directory changes

While using the deb deploy method, it's sometimes not obvious where your are when using the provided hooks. Subshells could help a lot and we can ensure the user is landing in a well defined directory context while using hooks.

E.g.

  # do something in current dir
  (cd /some/other/dir && other-command)
  # continue in original dir

debian packaging fails when bundled files go to same parent dir as application

When bundling additional files in .release/debian/files and they go to the same parent dir as the application itself, the mv command in the debian include method fails.

Example
Bundling additional files in
.release/debian/files/opt/jackrabbit

When the APPROOT is
/opt/example

the mv of the opt/jackrabbit folder fails, as "mv" complains about a non-empty directory.

Check for git mode on wrong target

When one aborts on the first release, afterwards git tries to fetch instead of cloning the project. This fails naturally. Better check if the .git directory existst in the workspace.

Verify the upload to deb repository

Add a check that the package is available in the pool of the debian repository after upload and repository update.

Don't mix variable names

Variable names are mixed with uppercase and lowercase/uppercase variants.
There should only be one way to name variables.

Normally you would use uppercase variable names in shell scripts

Feedback: License (mah)

Hi,

some feedback about adding a license came up (mah).

Just adding this issue here in order to not lose sight of it.

Best,

tommy

Add travis CI tests

A travis.yml needs to be created together with the first functional tests in order to set up a working build pipeline for the tool

Unit test the prompt view

As the maintainer of the release tool, I want to be sure that the view implementation prompt defines all the declared variables of the interface and assigns concrete functions to these.