Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
T
tests_api
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Deploy
Releases
Container Registry
Model registry
Operate
Environments
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
hive
tests_api
Commits
03f1bcc4
Commit
03f1bcc4
authored
2 years ago
by
Krzysztof Mochocki
Browse files
Options
Downloads
Patches
Plain Diff
Add first implementation of .gitlab-ci.yaml
parent
9834a6e1
No related branches found
No related tags found
1 merge request
!252
Fixes in benchmarking script and add benchmark CI request
Changes
1
Pipelines
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
.gitlab-ci.yaml
+36
-0
36 additions, 0 deletions
.gitlab-ci.yaml
with
36 additions
and
0 deletions
.gitlab-ci.yaml
0 → 100644
+
36
−
0
View file @
03f1bcc4
stages
:
-
benchmark
variables
:
CI_DEBUG_SERVICES
:
"
true"
BENCHMARK_ADDRESS
:
"
"
BENCHMARK_PORT
:
"
"
Trigger any benchmark
:
stage
:
benchmark
image
:
alpine:3.7
rules
:
-
when
:
manual
services
:
-
name
:
registry.gitlab.syncad.com/hive/tests_api/benchmark_aio:latest
alias
:
benchmark
variables
:
# const:
eROOT_DIR
:
"
/builds/hive/tests_api"
# required:
eADDRESS
:
$BENCHMARK_ADDRESS
ePORT
:
$BENCHMARK_PORT
# optional:
eJOBS
:
1
eLOOPS
:
1
# eAPI: account_history_api
# eCSV: perf_60M_heavy.csv
# eJOBS: 10
# eLOOPS: 500
# eCALL_STYLE: old-style
# ePOSTGRES_URL: postgresql:///haf_block_log
# ePOSTGRES_SCHEMA: hive
# eSERVE_PORT: ""
script
:
-
ls -la /
-
find /builds -type d -maxdepth
4
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