Gitea is offering Git Repositories as well as Artifact Repositories. Therefore, its services are comparable to Bitbucket,  Gitlab, but also to Nexus OSS.

If you like GitHub, you will love Gitea.

See Using Maven Artifact Repositories in Jenkins on how to push maven artifacts to Gitea.

For other package types, check out the sub pages listed on the left side in the navigation area.

• Activate Gitea
• Enter Gitea
• Projects in Gitea
  • Owners
  • ADMIN
  • MASTER
  • DEVELOPER
  • VIEWER

Activate Gitea

First, make sure that Gitea is enabled for your project. As a Portal Admin you can edit the Project, check Gitea and Save it.

See the following screenshot for an example.

Second, make sure that all users which are supposed to work with Gitea have been granted access to the tool. As a Portal admin you can edit affected Users, simply check Gitea and Save.

See the following screenshot for an example.

Enter Gitea

Go to the Projects page on the DevOps Portal. Tools which are activated for a project are listed in the Tools column. Like the other tools, Gitea is clickable if your user has Gitea enabled, and you have a role in the project.

See the following screenshot for an example.

Now click Gitea. A new tab will open the Project on Gitea for you.

To login with your personal user account, click Sign in with DevOps Portal. The username / password login method is intended for technical user logins only and should not be used with your personal account.

Projects in Gitea

Gitea uses its own hostname. The URL is https://gitea-CUSTOMER.devops.t-systems.net/ where CUSTOMER refers to the name of your DevOps-as-a-Service instance.

Please note, that some terms used in DevOps-as-a-Service have different names in Gitea. Please check the following table to avoid any confusion.

The following screenshot shows an empty Gitea project in its initial state with just one portal user assigned as ADMIN.

To explore the permissions of the different roles and see the currently assigned members, click on the team names.

Owners

The only member of the Owners Team is sdcloud-admin. This is a technical user used by the DevOps Portal for auto-provisioning.

ADMIN

Project Admins are put into the ADMIN Team. The example shows the user used for taking the screenshot as a member.

MASTER

Project Masters are put into the MASTER Team. In the example, no user has been assigned to the MASTER role yet.

DEVELOPER

Project Developers are put into the DEVELOPER Team. In addition, the DevOps Portal creates a technical user named pkey-jenkins-push-gitea whose credentials are automatically put into the Project Credentials in Jenkins. Therefore, this user can be easily used to push (write) code or packages. pkey refers to the project key as defined in the DevOps Portal. See Automatically provided Credentials for more details.

VIEWER

Project Viewers are put into the VIEWER Team. In addition, the DevOps Portal creates a technical user named pkey-jenkins-pull-gitea whose credentials are automatically put into the Project Credentials in Jenkins. Therefore, this user can be easily used to pull (read) code or packages. pkey refers to the project key as defined in the DevOps Portal. See Automatically provided Credentials for more details.