Skip to content
Training sources for the Scrum for Developers training
Java HTML TSQL Other
Branch: master
Clone or download
Pull request Compare This branch is 1 commit ahead of scrum-for-developers:master.
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
src
worblehat-acceptancetests
worblehat-domain
worblehat-web
.gitignore
.travis.yml
Jenkinsfile
README.md
pom.xml

README.md

Worblehat

Build Status

Worblehat is a training application for the Scrum for Developers training held by codecentric AG.

Requirements

Running the application

  1. Build the project: For example by running mvn clean install in the root directory
  2. Start the database. The easiest way is to fire up a docker container:
#!/bin/bash

docker run --detach \
  --name worblehat-db \
  --env MYSQL_ROOT_PASSWORD=root \
  --env MYSQL_USER=worblehat \
  --env MYSQL_PASSWORD=worblehat \
  --env MYSQL_DATABASE=worblehat_test \
  --publish 3306:3306 \
  mysql:5.6.25
  1. Build the Docker image to run the application
  • mvn cleain install
  • mvn docker:build -f worblehat-web
  • docker run --name worblehat -d -p 8080:8080 --link worblehat-db worblehat/web
  1. Access the application at http://localhost:8080/

Running acceptance tests

  1. The acceptance tests have a dependency on the domain module, so the first step is to ensure that the most recent snapshot is installed in the local maven repository

    root> mvn clean install
    
  2. Then, we need the application running, that should be tested

    root> mvn -f worblehat-web spring-boot:run
    
  3. Run acceptance tests. It currently requires Chrome to be installed.

    root> cd worblehat-acceptancetests
    worblehat-acceptancetests> mvn clean verify
    

    To run the tests headless, use the headless profile > mvn -Pheadless clean verify

  4. The report can be found in target/jbehave/view/reports.html

Howto Release

To release for example version 1.2 follow these steps:

  1. Set next development version: mvn -Pinclude-acceptancetests versions:set -DnewVersion=1.2 -DgenerateBackupPoms=false
  2. Create a tag and push the tag back to the team repository
  3. Let jenkins build the release and deploy it to the test and production environments
  4. Bump the version for the next development iteration: mvn -Pinclude-acceptancetests versions:set -DnewVersion=1.3-SNAPSHOT -DgenerateBackupPoms=false
You can’t perform that action at this time.