initial commit

# to-be-continuous template skeleton project

This project allows creating a new to-be-continuous template repository from scratch in seconds using [cookiecutter](https://cookiecutter.readthedocs.io/).

## Usage

1. Install `cookiecutter` globally (requires Python installed):

    ```bash

    pip install cookiecutter

    ```

    :information_source: for other installation options, please have a look at the [official doc](https://cookiecutter.readthedocs.io/en/stable/installation.html).

2. Run cookiecutter to create a new to-be-continuous template project:

    ```bash

    cookiecutter https://gitlab.com/to-be-continuous/tools/template-skeleton-2

    ```

    then answer the CLI questions

3. init the Git repo and share

    ```bash

    cd name-of-template

    git init .

    git remove add origin https://gitlab.com/to-be-continuous/name-of-template.git

    git add .

    git commit -m 'initial commit'

    git push

    ```

{

  "template_name": "Acme Tech",

  "template_type": ["build", "deploy", "acceptance"],

  "project_slug": "{{ cookiecutter.template_name.lower().replace(' ', '-').replace('_', '-') }}",

  "refdoc_url": "https://doc.acme-tech.com",

  "template_prefix": "{{ cookiecutter.project_slug.lower()[0:3] }}",

  "template_PREFIX": "{{ cookiecutter.template_prefix.upper() }}",

  "cli_tool": "{{ cookiecutter.project_slug }}",

  "__prompts__": {

    "template_name": "Name of the template",

    "project_slug": "Project slug (will be used as repository name)",

    "refdoc_url": "Main reference doc url",

    "template_prefix": "Template lowercase short prefix (will be used as job names prefix)",

    "template_PREFIX": "Template uppercase short PREFIX (will be used as config var names prefix)",

    "cli_tool": "(main) CLI tool",

    "template_type": {

      "__prompt__": "Kind of template",

      "build": "Build & Test",

      "deploy": "Deploy & Run",

      "acceptance": "Acceptance"

    }

  }

}

### STS ###

.apt_generated

.classpath

.factorypath

.project

.settings

.springBeans

.sts4-cache

### IntelliJ IDEA ###

.idea

*.iws

*.iml

*.ipr

### NetBeans ###

/nbproject/private/

/build/

/nbbuild/

/dist/

/nbdist/

/.nb-gradle/

.DS_Store

include:

  - project: 'to-be-continuous/tools/gitlab-ci'

    ref: 'master'

    file: '/templates/extract.yml'

  - project: 'to-be-continuous/tools/gitlab-ci'

    ref: 'master'

    file: '/templates/validation.yml'

  - project: 'to-be-continuous/kicker'

    ref: 'master'

    file: '/templates/validation.yml'

  - project: 'to-be-continuous/bash'

    ref: '2.0.0'

    file: 'templates/gitlab-ci-bash.yml'

  - project: 'to-be-continuous/semantic-release'

    ref: '2.0.2'

    file: '/templates/gitlab-ci-semrel.yml'    

stages:

  - build

  - publish

variables:

  GITLAB_CI_FILES: "templates/gitlab-ci-{{cookiecutter.project_slug}}.yml"

  BASH_SHELLCHECK_FILES: "*.sh"

semantic-release:

  rules:

    # on production branch(es): auto if SEMREL_AUTO_RELEASE_ENABLED

    - if: '$TMPL_RELEASE_ENABLED == "true" && $CI_COMMIT_REF_NAME =~ $PROD_REF'

 No newline at end of file

## Describe the bug

(Describe the problem clearly and concisely.)

## Expected behavior

(Describe the expected behavior clearly and concisely.)

## Actual behavior

(Describe the actual behavior clearly and concisely.)

## Logs and/or screenshots

(Join any relevant logs and/or screenshot. Please use code blocks (```) to format console output, logs, and code.)

## Context & Configuration

Link to a project, pipeline or job facing the bug: (please provide one if possible)

The issue was reproduced using:

* Version of the template: (type in the version)

* GitLab server(s): (Was it gitlab.com? A self-managed server? Which version? CE / EE? Which license?)

* GitLab runner(s): (type in any relevant information about the GitLab runner(s) you used)

Here is the `.gitlab-ci.yml` file:

```yaml

# Add your .gitlab-ci.yml here, if applicable and useful.

```

(If useful, list configured GitLab CI project and/or group variables.)

Configured GitLab CI project or group variables:

* `VARIABLE_1`

* `VARIABLE_2`

* ...

(Finally add any possible additional useful context info here.)

/label ~"kind/bug" ~"status/needs-investigation"