WIP: 0.3.0 developments

.github/CONTRIBUTING.md

@@ -0,0 +1,35 @@
+## Really want to contribute to PSICK?!?
+
+### Supply your own profile
+
+One of the main components of PSICK is the collection of profiles, and the framework to easily switch from one to another.
+
+We encourage the existence of multiple profiles to manage applications ussing different patterns and modules, we think it would be nice to have a good library of profiles to choose from and customise when needed.
+
+So if you have written a good profile, which may adapt to common use cases, both for new or existing applications, you're welcomed to share it:
+
+  * the profile class 
+  * some hiera examples
+  * enventual modules to add to Puppetfile
+  * possibly spec test for the profile
+
+### Submit your bug or feature request
+
+We are not suprised. There are so many combinations of OS, applications and use cases, that it's hard to test them all.
+
+We still welcome bug fix or feature requests, even better relevant PR, we want to make PSICK as good and useful as possible,
+
+### Contribution guideline
+
+  * Open a new GitHub pull request with the patch.
+    1. Fork this project
+    1. Create your feature branch: `git checkout -b my-new-feature`
+    1. Commit your changes: `git commit -am 'Add some feature'`
+    1. Push to the branch: `git push origin my-new-feature`
+    1. Submit a pull request via GitHub's web interface
+  * Ensure the PR description clearly describes the problem and its solution. Include the relevant issue number if applicable.
+
+### Commercial support
+
+If you need an enterprise level support on your Puppet infrastructure and may be interested in using some of all the PSICK features, you can contribute to this project by subscribing to example42 Puppet support services and, possibily, allowing us to share here the shareable work we do with you.
+

.github/ISSUE_TEMPLATE.md

@@ -0,0 +1,19 @@
+## Expected Behavior 
+
+
+## Actual Behavior
+
+
+## Steps to Reproduce the Problem
+
+  1. 
+  1. 
+  1. 
+
+## Specifications
+
+Please add this info:
+
+  1. Output of ```facter -p``` on the failing node (at least the OS related facts)
+  1. Version of Puppet and of the module
+  1. The relevant Puppet code and eventually Hiera data

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,11 @@
+## Before submitting your PR
+
+  1. Open an **issue** and refer to its number in your PR title
+  1. If it's a bug and you have the solution, go on with the PR! 
+  1. If it's a new profile got with the PR (possibly with docs, samples and tests)
+
+## After submitting your PR
+
+  1. Verify Travis checks and fix the errors if needed
+  1. Feel free to ping us if we don't reply promptly 
+

.gitlab-ci.yml

@@ -22,15 +22,14 @@ stages:
 # Run Danger based on Dangerfile rules
 run_danger:
   stage: danger
-  before_pre:
+  before_script:
     - export DANGER_GITLAB_HOST=$CI_SERVER_NAME
     - export DANGER_GITLAB_API_BASE_URL="https://${CI_SERVER_NAME}/api/v4"
   script: danger --verbose
   tags:
     - test_puppet
   allow_failure: true
   except:
-    - testing
     - production
   only:
     - branches
@@ -64,7 +63,6 @@ syntax:
   tags:
     - test_puppet
   except:
-    - testing
     - production
   only:
     - branches
@@ -84,7 +82,6 @@ lint:
   tags:
     - test_puppet
   except:
-    - testing
     - production
   only:
     - branches
@@ -102,8 +99,10 @@ rake_site:
     - vagrant/environments/ci/.vagrant/
   tags:
     - test_puppet
+  except:
+    - production
   only:
-    - development
+    - branches
   allow_failure: true
 
 rake_modules:
@@ -119,37 +118,38 @@ rake_modules:
   tags:
     - test_puppet
   only:
-    - development
+    - integration
   allow_failure: true
+  when: manual
 
 catalog_diff:
   stage: diffs
   before_script:
     - "bin/gitlab_before.sh"
-  script: "bin/gitlab_catalog_diff.sh development"
+  script: "bin/gitlab_catalog_diff.sh integration"
   cache:
     untracked: true
     paths:
     - modules/
   tags:
     - deploy_puppet
   only:
-    - development
+    - integration
   allow_failure: true
 
 catalog_preview:
   stage: diffs
   before_script:
     - "bin/gitlab_before.sh"
-  script: "bin/gitlab_catalog_preview.sh development"
+  script: "bin/gitlab_catalog_preview.sh integration"
   cache:
     untracked: true
     paths:
     - modules/
   tags:
     - deploy_puppet
   only:
-    - development
+    - integration
   allow_failure: true
 
 # Can be duplicated to use different images (using different --image)
@@ -167,103 +167,22 @@ docker_test:
   tags:
     - test_puppet
   only:
-    - development
-
-# Destroy a vagrant machine completely.
-vagrant_destroy:
-  stage: integration
-  before_script:
-    - "bin/gitlab_before.sh"
-  script: "bin/vagrant_node_test.sh centos7.ci ci destroy"
-  cache:
-    untracked: true
-    paths:
-    - modules/
-    - tests/
-  allow_failure: true
-  tags:
-    - test_puppet
-  only:
-    - development
-  when: manual
-
-
-# Do Vagrant run. Start the machine, run the tests, halt the machine.
-# This will use a .vagrant dir under $HOME of the users so that 
-# it will not be deleted accidentally  by gitlab-runner
-vagrant_checks:
-  stage: integration
-  before_script:
-    - "bin/gitlab_before.sh"
-  script:
-    - "bin/vagrant_node_test.sh centos7.ci ci setup"
-    - "bin/vagrant_node_test.sh centos7.ci ci drift"
-  after_script:
-    - "bin/gitlab_after.sh"
-    - "bin/vagrant_node_test.sh centos7.ci ci halt"
-  cache:
-    untracked: true
-    paths:
-    - modules/
-    - tests/
-  allow_failure: true
-  tags:
-    - test_puppet
-  only:
-    - development
-  when: manual
-
-tp_test:
-  stage: integration
-  before_script:
-    - "bin/gitlab_before.sh"
-  script: "bin/gitlab_tp_test.sh development"
-  cache:
-    untracked: true
-    paths:
-    - modules/
-    - tests/
-  tags:
-    - test_puppet
-  only:
-    - development
-  allow_failure: true
-
-# Development to testing merge request creation
-merge_request_testing:
-  stage: merge_request
-  script: "bin/gitlab_create_merge_request.rb development testing"
-  tags:
-    - deploy_puppet
-  only:
-    - development
-
-# Automatic Accept merge request from Development to testing 
-merge_accept_testing:
-  stage: promote
-  script: "bin/gitlab_accept_merge_request.rb development testing"
-  only:
-    - development
-  tags:
-    - deploy_puppet
-  when: on_success
-  allow_failure: true
+    - integration
 
-# On testing branch
-run_puppet_on_testing:
+run_puppet_on_integration:
   stage: live_runs
   before_script:
     # Trigger remote Puppet runs via puppet job
-    - "bin/puppet_job_run.sh testing"
+    - "bin/puppet_job_run.sh integration"
     # Trigger remote Puppet runs via Rundeck
 #    - "bin/rundeck_job_run.sh testing"
   script:
-    - "bin/puppetdb_env_query.sh testing"
+    - "bin/puppetdb_env_query.sh integration"
   tags:
     - deploy_puppet
   when: on_success
   only:
-    - testing
+    - integration
   allow_failure: true
 
 # Allow Merge Request to fail as it can happen that there's
@@ -272,22 +191,22 @@ run_puppet_on_testing:
 merge_request_production:
   stage: merge_request
   script:
-    - "bin/gitlab_create_merge_request.rb testing production"
+    - "bin/gitlab_create_merge_request.rb integration production"
   when: on_success
   tags:
     - deploy_puppet
   only:
-    - testing
+    - integration
   allow_failure: true
 
 merge_accept_production:
   stage: promote
-  script: "bin/gitlab_accept_merge_request.rb testing production"
+  script: "bin/gitlab_accept_merge_request.rb integration production"
   tags:
     - deploy_puppet
   when: manual
   only:
-    - testing
+    - integration
   environment:
     name: production
 
@@ -317,15 +236,6 @@ run_puppet_on_production:
   allow_failure: true # TOREMOVE when fixed
 
 
-test_post_run_on_production:
-  stage: postcheck
-  script: "bin/puppetdb_env_query.sh production"
-  tags:
-    - deploy_puppet
-  only:
-    - production
-  allow_failure: true # TOREMOVE when fixed
-
 pages:
   stage: sitedoc
   before_script: