Release version 0.3.0

CHANGELOG.md

@@ -1,3 +1,25 @@
+<a name="v0.3.0"></a>
+### v0.3.0 (2018-02-16)
+
+#### Features
+
+* Pipelines are now created when a pull request from a fork is submitted.
+  This feature requires the newly released [AlloyCI Runner](https://github.com/AlloyCI/alloy-runner) (GitLab Runner fork),
+  so it is incompatible with all previous and future GitLab Runner versions. (#29)
+* Added support for `only` and `except` keywords for build jobs. This gives
+  you better control over which jobs run when. (#14)
+* Regular users can now manage project specific runners for projects to which
+  they have access. (#33)
+* Projects now support the use of secret variables. They can be used to pass
+  sensitive information to the runner without committing it to the repository. (#23)
+
+#### Bug Fixes
+
+* Redirect to the main projects' view when all auth options have already 
+  been created. (#30)
+* Better processing of pipelines when the worker is called (5a9ca8f)
+* Fix notification bug, that would send one on every failed build. (63dc787)
+
 <a name="v0.2.0"></a>
 ### v0.2.0 (2017-10-16)
 

README.md

@@ -50,7 +50,7 @@ branches, so you can always know their status, just like any other CI service.
   - [x] Can build and test from pull requests coming from a fork
   - [x] Can distinguish between tags and branches
   - [x] Can make use of `only` and `except` tags for jobs
-  - [ ] Can make use of secret variables stored on a per project basis
+  - [x] Can make use of secret variables stored on a per project basis
   - [ ] Can receive uploaded artifacts from runners
   - [ ] Can pass artifacts between build jobs
 - [ ] Deployment functionality

doc/json/README.md

@@ -1,7 +1,7 @@
 # Configuration of your jobs with .alloy-ci.json
 
 This document describes the usage of `.alloy-ci.json`, the file that is used to
-tell GitLab Runner how to manage your project's jobs.
+tell AlloyCI Runner how to manage your project's jobs.
 
 If you want a quick introduction to AlloyCI, follow our
 [quick start guide](../quick_start/README.md).
@@ -12,6 +12,9 @@ AlloyCI uses a [JSON](https://en.wikipedia.org/wiki/JSON)
 file (`.alloy-ci.json`) for the project configuration. It is placed in the root
 of your repository and contains definitions of how your project should be built.
 
+If you have an existing `.gitlab-ci.yml` file, you can use the online [YAML to JSON](https://www.json2yaml.com/convert-yaml-to-json)
+converter to turn your file into an AlloyCI compatible JSON file.
+
 The JSON file defines a set of jobs with constraints stating when they should
 be run. The jobs are defined as top-level elements with a name and always have
 to contain at least the `script` clause:
@@ -159,8 +162,6 @@ the branch or tag name for which project is built.
 
 ### cache
 
-> Introduced in GitLab Runner v0.7.0.
-
 `cache` is used to specify a list of files and directories which should be
 cached between jobs. You can only use paths that are within the project
 workspace.
@@ -236,7 +237,7 @@ job will cache only `binaries/`:
 Note that since cache is shared between jobs cache content can be overwritten.
 
 The cache is provided on a best-effort basis, so don't expect that the cache
-will be always present. For implementation details, please check GitLab Runner.
+will be always present. For implementation details, please check AlloyCI Runner.
 
 ## Jobs
 
@@ -549,7 +550,7 @@ It's possible to overwrite the globally defined `before_script` and `after_scrip
 
 ## Git Submodule Strategy
 
-> Requires GitLab Runner v1.10+.
+> Requires AlloyCI Runner v1.10+.
 
 The `GIT_SUBMODULE_STRATEGY` variable is used to control if / how Git
 submodules are included when fetching the code before a build. Like
@@ -591,7 +592,7 @@ Note that for this feature to work correctly, the submodules must be configured
 
 ## Job stages attempts
 
-> Requires GitLab Runner v1.9+.
+> Requires AlloyCI Runner v1.9+.
 
 You can set the number for attempts the running job will try to execute each
 of the following stages:

lib/alloy_ci/protocols/html_safe.ex

@@ -1,5 +1,5 @@
 defimpl Phoenix.HTML.Safe, for: Map do
   def to_iodata(data) do
-    Poison.encode!(data)
+    Poison.encode!(data, pretty: true)
   end
 end

lib/version.ex

@@ -4,7 +4,7 @@ defmodule AlloyCi.Version do
   To update the version, changes to this file and mix.exs are required.
   """
 
-  @version "0.2.0"
+  @version "0.3.0"
 
   def version do
     @version

mix.exs

@@ -3,7 +3,7 @@ defmodule AlloyCi.Mixfile do
   """
   use Mix.Project
 
-  @version "0.2.0"
+  @version "0.3.0"
 
   def project do
     [