Wiki source code of Gitea Technical Users
Last modified by DevOps-as-a-Service Operator on 2025/02/05 11:33
Show last authors
| author | version | line-number | content |
|---|---|---|---|
| 1 | As mentioned in [[Gitea - Developer>>doc:Gitea.WebHome||anchor="gitea_developer"]] and [[Gitea - Viewer>>doc:Gitea.WebHome||anchor="gitea_viewer"]], the DevOps portal automatically creates technical users which can be immediately used in your Jenkins build pipelines of the same project right away. See [[doc:Jenkins.Automatically provided Credentials.WebHome]] for more details. | ||
| 2 | |||
| 3 | For connecting your project in Gitea with other projects or external services, you can also explicitly create Technical Users in the DevOps Portal. | ||
| 4 | |||
| 5 | As Portal Admin create a new Technical User for the tool Gitea. | ||
| 6 | |||
| 7 | [[image:attach:image-2024-2-11_19-56-4.png||data-xwiki-image-style-border="true" queryparams="effects=drop-shadow" height="400"]] | ||
| 8 | |||
| 9 | Copy the password and store it in a safe place. If required, it can be changed later anytime in the DevOps Portal. | ||
| 10 | |||
| 11 | You cannot use the Project Key of an existing project for the Username of a Technical Gitea User. Gitea doesn't allow this, therefore the DevOps Portal will not accept it, too. For the same reason, you cannot create a new project which uses the username of a Technical Gitea User as its Project Key. | ||
| 12 | |||
| 13 | To login to Gitea with a techical user, go to the DevOps portal and click Gitea. Enter the username and password of the technical user and click **Sign In**. | ||
| 14 | |||
| 15 | [[image:1720550624292-325.png||data-xwiki-image-style-border="true" height="310" width="1000"]] | ||
| 16 | |||
| 17 | (% class="box errormessage" %) | ||
| 18 | ((( | ||
| 19 | Do not use the "Sign in with DevOps Portal" option for technical users, since this will do the login with your personal account. | ||
| 20 | ))) | ||
| 21 | |||
| 22 | (% class="box infomessage" %) | ||
| 23 | ((( | ||
| 24 | Some package formats like NPM require a token instead of a password for package access. To create a token, follow the instructions at [[doc:Gitea.Creating Access Tokens for Pushing Packages to Gitea.WebHome]]. | ||
| 25 | ))) |