diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml index 15537df..9366fc7 100644 --- a/.gitlab-ci.yml +++ b/.gitlab-ci.yml @@ -1,8 +1,20 @@ -include: - - project: 'continuous_integration/ci_scripts' - ref: master - file: '/gitlab-ci-yml/catkin_pipeline.yml' +image: docker:git +services: + - docker:dind +before_script: + - apk add --update bash coreutils tar + - git clone --quiet --depth 1 https://github.com/ros-industrial/industrial_ci .industrial_ci + +clang-format: + variables: + CLANG_FORMAT_CHECK: "file" + CLANG_FORMAT_VERSION: "6.0" + ROS_DISTRO: "kinetic" + script: .industrial_ci/gitlab.sh + +build_kinetic: + variables: + ROS_DISTRO: "kinetic" + CATKIN_LINT: "true" + script: .industrial_ci/gitlab.sh -variables: - BUILD_INDIGO: "false" - BUILD_MELODIC: "false" diff --git a/.gitlab/issue_templates/default.md b/.gitlab/issue_templates/default.md new file mode 100644 index 0000000..a534953 --- /dev/null +++ b/.gitlab/issue_templates/default.md @@ -0,0 +1,45 @@ +# Summary +*Introduction to the issue* + +# Versions + - ROS Driver version: + - Affected Robot Software Version(s): + - Affected Robot Hardware Version(s): + - Robot Serial Number: + - UR+ product(s) installed: + - URCaps Software version(s): + +# Impact +*What is the impact of the issue. Try to describe it well enough, in order for us to prioritise the issues.* + + +# Issue details +*This part is important in order to clarify the severity of the issue.* + + +## Use Case and Setup +*What does the setup look like and what are the objectives?* + + +## Project status at point of discovered +*When did you first observe the issue?* + - *Before I started?* + - *In first couple of tries?* + - *In normal use?* + - *etc...* + + +## Steps to Reproduce +*Make simple example to reproduce the issue. Try to remove dependencies to other hardware and software components, if it is possible.* + + +## Expected Behavior +*What did you expect and why?* + + +## Actual Behavior +*What did you observe? If possible please attach relevant information.* + + +## Workaround Suggestion +*If a workaround has been found, you are welcome to share.*