Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
S
scheduling-system
Manage
Activity
Members
Labels
Plan
Issues
61
Issue boards
Milestones
Iterations
Wiki
Requirements
External wiki
Code
Merge requests
2
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Locked files
Build
Pipelines
Jobs
Pipeline schedules
Test cases
Artifacts
Deploy
Releases
Container Registry
Model registry
Operate
Environments
Monitor
Incidents
Service Desk
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Code review analytics
Issue analytics
Insights
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
SMASCH
scheduling-system
Commits
30a57b2d
Commit
30a57b2d
authored
1 year ago
by
Carlos Vega
Browse files
Options
Downloads
Patches
Plain Diff
Update .gitlab-ci.yml
parent
97f1439d
Branches
ci/licensing_fix
No related tags found
1 merge request
!442
Update Licensing analysis in CI
Pipeline
#80105
passed with stage
in 8 minutes and 57 seconds
Changes
1
Pipelines
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
.gitlab-ci.yml
+1
-4
1 addition, 4 deletions
.gitlab-ci.yml
with
1 addition
and
4 deletions
.gitlab-ci.yml
+
1
−
4
View file @
30a57b2d
...
...
@@ -7,13 +7,10 @@ variables:
POSTGRES_DB
:
smash
POSTGRES_USER
:
runner
POSTGRES_PASSWORD
:
password
SECURE_LOG_LEVEL
:
debug
gemnasium-python-dependency_scanning
:
before_script
:
-
cat /etc/*release*
-
apt-get update
-
apt-get install -y python-dev-is-python3 libldap2-dev libssl-dev libcurl4-openssl-dev libpq-dev libsasl2-dev gcc
-
apt-get update && apt-get install -y python-dev-is-python3 libldap2-dev libssl-dev libcurl4-openssl-dev libpq-dev libsasl2-dev gcc
.test_template
:
&test_definition
stage
:
test
...
...
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