Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
restored release ci and issue templates
- Loading branch information
Showing
2 changed files
with
64 additions
and
7 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -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" |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -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.* |