- 1 Download and Upgrade to 15.0+ Series
- 2 New Features of ZenTao 15 Series
- 3 Interface Changes of 15 Series
- 4 Update to the Latest Version
- 5 Quick Start of 15 Series
- 6. Basic Application of Version 15
7. Base On The Roles
- 7.1. Admin
- 7.2. Program Leader
- 7.3. Product Owner
- 7.4. Project Manager
7.5. Development Team
- 7.5.1 Apply for Tasks and Bugs
- 7.5.2 Update Status
- 7.5.3 Complete Tasks and Bugs
- 7.5.4 Submit Codes
- 7.5.5 The General Kanban, Story Kanban, Bug Kanban, and Task Kanban
- 7.6. Test Team
- 8. DevOps Features
- 9 General Kanban
- 10. Backstage Settings of Version 15
11. Privileges Management and Access Control of Version 15
- 11.1 Privileges Management and Access Control for Programs
- 11.2 Privileges Management and Access Control for Products
- 11.3 Privileges Management and Access Control for Projects
- 11.4 Privileges Management and Access Control for Executions
- 11.5 Access Control and Data Relationships for Projects and Executions
Integrate GitLab, Bind Users, Link to Issues and Create a Build
GitLab repositories are integrated into ZenTao 15 series.
- Sync repository code
- Bind Users
- View Codebase directory, View code, Blame, Diff
- Link to Issues
- Create a Build
The following will introduce how to maintain GitLab and integrate GitLab repository.
1. Maintain GitLab server
1.1 Create a GitLab server
In the DevOps module, click the Create GitLab button in the top right corner.
In the Create GitLab page:
GitLab URL and a valid Token with administrator privileges need to be filled in.
For example, the access address of my GitLab is: https://gitlab.abc.com then filled in: https://gitlab.abc.com. Do not fill in the access address of the project in GitLab.
Gitlab server cannot be added through a token without administrator privileges.
It can be viewed on the list if the GitLab servers are added successfully.
1.2 Edit and delete GitLab server
There are Edit and Delete buttons on the right side of the GitLab server list.
Click the Edit button to make changes to the GitLab server name, server address, and token.
Edit GitLab page:
1.3 Bind Users
GitLab users can bind with Zen Tao users.
Click the bind user button in the operation bar on the right side of the GitLab list to enter the bind user page.
When binding a user, the user's real name, user name, and email address will be checked by default. If one of them is the same, it will be bound by default.
In addition to binding users by default, you can bind users by yourself.
However, if GitLab's Token expires or without administrator privilege, the GitLab cannot bind users.
The operation button of the bound user is grayed out, and a prompt will be given when the mouse hovers.
2. About Token in GitLab
Log in to GitLab and follow the prompts on the page in Settings--Access Tokens to generate a Token.
Follow the prompts on the page and fill in the content information as needed.
Click the Create personal access token button after filling in the information.
There will be a prompt on the top of the page.
The list of the tokens created before is displayed at the bottom of the page.
3. Create a GitLab type repository
Now the GitLab server is created successfully, you can create a GitLab type repository and view the historical commit records of it. Features of directory viewing, code viewing, tracing, and diff function are provided.
3.1 Create a GitLab type repository
Click the Create button in the top right corner of the DevOps--Repository page.
Product: Could be one or more products.
Next, you need to fill in the GitLab address and Token.
GitLab Server Address: Select the server addresses we have maintained in GitLab.
GitLab project: After selecting the GitLab server address, all project names in the address will be listed by default.
After selecting an item, the name will be filled in automatically, just click Save.
The code of the project will be automatically synchronized after saving.
3.2 Sync the code of a GitLab project
The code is synchronizing.
You can view it in the Code after the synchronization is completed:
You can also view it it in the repository list.
3.3 Code review, blame, diff
View code directory
Compare the differences (diff)
4. Import Issue
There are operation buttons on the right side of the repository including the Import Issue button.
Click the button, it will jump to the page Import Issue, the default types are Task, Requirement, and Bug.
The Product lists the owning products of the repository, and the Execution lists the executions associated with this owning product.
Click Save to view the associated issue in the execution.
The issue imported from GitLab will be attached with its address in GitLab in the description information in ZenTao system.
For issues that have been imported into ZenTao, the ZenTao tag (form: object_object ID, such as task_1234) will be added to the issue page in GitLab and the URL will be used as the tag value.
The issue linked with Task.
The issue linked with Requirement.
The issue linked with Bug.
There will be a direct prompt if no issues could be linked
5. Create a build task (Compile) for the GitLab engine
Next, we can create a build task for the GitLab engine in the Build.
It will list the GitLab-type codebase and its products in the Codebase.
After the build task is created successfully, you can click to execute the build in the build list.
Execute the build tasks and run pipelines.
Creating a build task for the GitLab engine is based on the properly configured pipeline. The build will be failed if the pipeline is not configured in the GitLab project.
Configure the pipeline: https://docs.gitlab.com/ee/ci/pipelines/
View the build log. You can refresh to view the specific build log.
You can view the status of the build task in the build task list. What's more,View the log, Edit, Execute, Delete, and other operations are provided.
View the build history:
6. Deploy rules
There is the default command configuration for tasks, bugs, and requirements, and you can also modify and adjust them according to your needs.
The code submitted according to the configuration instructions will be reflected in the history of tasks, bugs, and requirements.
Instruction settings page and example:
On the Bug details page, you can click view and diff in the history record to view directly.