Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
C
csp-lmc-subelement-old
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package registry
Container registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
GitLab community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
This is an archived project. Repository and other project resources are read-only.
Show more breadcrumbs
Gianluca Marotta
csp-lmc-subelement-old
Commits
febf6d4c
Commit
febf6d4c
authored
5 years ago
by
Elisabetta Giani
Browse files
Options
Downloads
Patches
Plain Diff
AT5-370: project Makefile is in docker folder.
parent
e686be40
Branches
Branches containing commit
Tags
Tags containing commit
1 merge request
!5
Request to merge AT5-370 branch with master
Pipeline
#11344
failed
5 years ago
Stage: test
Stage: linting
Stage: deploy
Stage: .post
Changes
1
Pipelines
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
Makefile
+0
-27
0 additions, 27 deletions
Makefile
with
0 additions
and
27 deletions
Makefile
deleted
100644 → 0
+
0
−
27
View file @
e686be40
# Use bash shell with pipefail option enabled so that the return status of a
# piped command is the value of the last (rightmost) commnand to exit with a
# non-zero status. This lets us pipe output into tee but still exit on test
# failures.
SHELL
=
/bin/bash
.SHELLFLAGS
=
-o
pipefail
-c
all
:
test lint
# The following steps copy across useful output to this volume which can
# then be extracted to form the CI summary for the test procedure.
test
:
python
setup.py
test
|
tee
./build/setup_py_test.stdout;
\
mv
coverage.xml
./build/reports/code-coverage.xml;
# The following steps copy across useful output to this volume which can
# then be extracted to form the CI summary for the test procedure.
lint
:
# FIXME pylint needs to run twice since there is no way go gather the text and junit xml output at the same time
pip3
install
pylint2junit;
\
pylint
--output-format
=
parseable ska_python_skeleton |
tee
./build/code_analysis.stdout
;
\
pylint
--output-format
=
pylint2junit.JunitReporter ska_python_skeleton
>
./build/reports/linting.xml
;
.PHONY
:
all test lint
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment