Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
Maven
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
Model registry
Operate
Environments
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
SmartDataLab
public
CI-CD components
Maven
Commits
bc128a98
Commit
bc128a98
authored
Nov 25, 2022
by
Pierre Smeyers
Browse files
Options
Downloads
Plain Diff
Merge branch 'docs/acces-token' into 'master'
docs: fix access token description See merge request to-be-continuous/maven!44
parents
ba1d66e0
396cdf26
Branches
Branches containing commit
No related tags found
No related merge requests found
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
README.md
+1
-1
1 addition, 1 deletion
README.md
with
1 addition
and
1 deletion
README.md
+
1
−
1
View file @
bc128a98
...
@@ -324,7 +324,7 @@ The template handles both classic variable and file variable.
...
@@ -324,7 +324,7 @@ The template handles both classic variable and file variable.
Simply specify :lock:
`$GIT_USERNAME`
and :lock:
`$GIT_PASSWORD`
as protected project variables and they will be dynamically
Simply specify :lock:
`$GIT_USERNAME`
and :lock:
`$GIT_PASSWORD`
as protected project variables and they will be dynamically
evaluated and appended to the Maven release arguments.
evaluated and appended to the Maven release arguments.
Note that the password should be an access token with
`read_repository`
and
`write_repository`
scope
s
.
Note that the password should be an access token with
`write_repository`
scope
and
`Maintainer`
role
.
:warning: The
`scm`
connections in your
`pom.xml`
should use the
`https`
protocol
:warning: The
`scm`
connections in your
`pom.xml`
should use the
`https`
protocol
...
...
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
sign in
to comment