Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
A
asdf
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
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Service Desk
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
Terms and privacy
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Tarn Burton
asdf
Commits
26b24b37
Commit
26b24b37
authored
4 years ago
by
Eric Timmons
Browse files
Options
Downloads
Patches
Plain Diff
Run upgrade tests only if explicitly requested
Need to set RUN_UPGRADE_TESTS
parent
e36c0653
Branches
Branches containing commit
Tags
Tags containing commit
No related merge requests found
Changes
2
Show whitespace changes
Inline
Side-by-side
Showing
2 changed files
README.md
+11
-7
11 additions, 7 deletions
README.md
gitlab-ci.yml
+3
-1
3 additions, 1 deletion
gitlab-ci.yml
with
14 additions
and
8 deletions
README.md
+
11
−
7
View file @
26b24b37
...
...
@@ -158,17 +158,21 @@ request or sending a patch to the asdf-devel mailing list.
If you fork the repository on Gitlab, note that Gitlab CI is enabled to help in
automated testing. While not exhaustive, this can help make sure you don't
inadvertantly break anything with your patch! The tests will be run any time
you submit a merge request or manually trigger a run using Gitlab's UI. In
order for the tests to run properly (namely the ASDF upgrade tests), you must
ensure your fork contains the tags for every released version of ASDF. If your
fork is freshly created, this will happen automatically. However, if there has
been a release since you forked, you need to update your tags. Assuming that
your fork is the
`origin`
remote and upstream is the
`upstream`
remote, you can
do this by running:
you submit a merge request or manually trigger a run using Gitlab's UI.
If you would like to run ASDF's upgrade tests you need to first ensure your
fork contains the tags for every released version of ASDF. If your fork is
freshly created, this will happen automatically. However, if there has been a
release since you forked, you need to update your tags. Assuming that your fork
is the
`origin`
remote and upstream is the
`upstream`
remote, you can do this
by running:
git fetch upstream --tags
git push origin --tags
Then set the varialbe
`RUN_UPGRADE_TESTS`
on a pipeline.
If you would like to enable test jobs that use the Lisp scripting test harness,
set the variable
`ENABLE_ASDF_TOOLS`
on a pipeline.
...
...
This diff is collapsed.
Click to expand it.
gitlab-ci.yml
+
3
−
1
View file @
26b24b37
...
...
@@ -99,6 +99,8 @@ Build asdf-tools:
-
build/results/$l-upgrade.text
needs
:
[]
allow_failure
:
true
rules
:
-
if
:
$RUN_UPGRADE_TESTS
.Scripting regression tests
:
extends
:
.Regression tests
...
...
@@ -116,7 +118,7 @@ Build asdf-tools:
needs
:
-
Build asdf-tools
rules
:
-
if
:
$ENABLE_ASDF_TOOLS
-
if
:
$ENABLE_ASDF_TOOLS
&& $RUN_UPGRADE_TESTS
###############################################################################
# Actual test jobs - Makefile based harness
...
...
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