Gitea - XWiki

1

[[Gitea>>url:https://docs.gitea.com/||shape="rect"]] is offering Git Repositories as well as Artifact Repositories. Therefore, its services are comparable to [[doc:Bitbucket.WebHome]], [[ Gitlab, >>doc:GitLab.WebHome]]but also to Nexus OSS.

2

3

If you like [[GitHub>>url:https://github.com/||shape="rect"]], you will love [[Gitea>>url:https://docs.gitea.com/||shape="rect"]].

4

5

See [[Using Maven Artifact Repositories in Jenkins>>Jenkins.Using Maven Artifact Repositories in Jenkins.WebHome]] on how to push maven artifacts to Gitea.

6

7

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

= 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.

14

15

See the following screenshot for an example.

16

17

[[image:attach:image-2024-2-11_17-42-51.png||data-xwiki-image-style-border="true" queryparams="effects=drop-shadow" height="522" width="249"]]

18

19

20

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.

21

22

See the following screenshot for an example.

23

24

[[image:attach:image-2024-2-11_17-46-5.png||data-xwiki-image-style-border="true" queryparams="effects=drop-shadow" height="520" width="403"]]

= 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.

29

30

See the following screenshot for an example.

31

32

[[image:attach:image-2024-2-11_17-53-5.png||data-xwiki-image-style-border="true" queryparams="effects=drop-shadow" height="124" width="1100"]]

33

34

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

35

36

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.

37

38

[[image:1720549846176-572.png||data-xwiki-image-style-border="true" height="341" width="1100"]]

39

40

41

At the moment, it's possible for any user with an ACTIVE account on the DevOps Portal to "Sign in with DevOps Portal". But if Gitea has not been assigned to the user, as explained previously in "Activate Gitea", he or she will see no data in Gitea. Assigning Gitea to the user will fix that.

42

43

44

= Projects in Gitea =

45

46

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

47

48

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.

49

50

(% class="table-bordered" %)

51

(% class="active" %)|=(((

DevOps Portal

)))|=(((

Gitea

)))

|(((

Project

)))|(((

Organization

)))

|(((

Project Role

)))|(((

Team

)))

|(((

Git Repository

)))|(((

Repository

)))

|(((

Artifact Repository

)))|(((

Package

)))

|(((

Issue Tracking

)))|(((

Project (currently disabled)

80

)))

81

82

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

83

84

[[image:attach:image-2024-2-11_18-32-43.png||data-xwiki-image-style-border="true" queryparams="effects=drop-shadow" height="566" width="750"]]

85

86

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 {{code language="none"}}sdcloud-admin{{/code}}. This is a technical user used by the DevOps Portal for auto-provisioning.

91

92

[[image:attach:image-2024-2-11_18-57-28.png||data-xwiki-image-style-border="true" queryparams="effects=drop-shadow" height="286" width="750"]]

== ADMIN ==

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

97

98

[[image:attach:image-2024-2-11_19-1-50.png||data-xwiki-image-style-border="true" queryparams="effects=drop-shadow" height="391" width="750"]]

== MASTER ==

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

103

104

[[image:attach:image-2024-2-11_19-3-15.png||data-xwiki-image-style-border="true" queryparams="effects=drop-shadow" height="366" width="750"]]

105

106

== {{id name="gitea_developer"/}}DEVELOPER ==

107

108

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

109

110

[[image:attach:image-2024-2-11_19-4-11.png||data-xwiki-image-style-border="true" queryparams="effects=drop-shadow" height="478" width="750"]]

111

112

== {{id name="gitea_viewer"/}}VIEWER ==

113

114

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

115

116

[[image:attach:image-2024-2-11_19-8-14.png||data-xwiki-image-style-border="true" queryparams="effects=drop-shadow" height="476" width="750"]]

Wiki source code of Gitea

DevOps-as-a-Service

Navigation