Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
monitoring
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
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
Community forum
Contribute to GitLab
Provide feedback
Terms and privacy
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
postmarketOS
monitoring
Commits
0ad01b51
Unverified
Commit
0ad01b51
authored
1 year ago
by
Oliver Smith
Browse files
Options
Downloads
Patches
Plain Diff
Add v23.12
parent
b49b70c9
Branches
Branches containing commit
Tags
Tags containing commit
1 merge request
!12
Add v23.12
Pipeline
#177008
failed
1 year ago
Stage: check
Stage: badge
Changes
2
Pipelines
121
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
.ci/generate_page.sh
+1
-0
1 addition, 0 deletions
.ci/generate_page.sh
.gitlab-ci.yml
+12
-0
12 additions, 0 deletions
.gitlab-ci.yml
with
13 additions
and
0 deletions
.ci/generate_page.sh
+
1
−
0
View file @
0ad01b51
...
...
@@ -3,6 +3,7 @@
export
BRANCHES
=
"
master
v23.06
v23.12
"
mkdir
-p
public
...
...
This diff is collapsed.
Click to expand it.
.gitlab-ci.yml
+
12
−
0
View file @
0ad01b51
...
...
@@ -58,6 +58,18 @@ upstream-compat-v23.06:
-
"
*.check-passed"
expire_in
:
1 week
upstream-compat-v23.12
:
stage
:
check
<<
:
*only-default
allow_failure
:
true
script
:
-
./test_upstream_compat_setup.sh "v23.12"
artifacts
:
when
:
always
paths
:
-
"
*.check-passed"
expire_in
:
1 week
pages
:
stage
:
badge
<<
:
*only-default
...
...
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