Note that if you run a job in one of the old pipelines in GitLab CI/CD, the integration will not process the changes backward. When triggered, the integration processes all changes made in the same branch between the last processed job in GitLab CI/CD and the current one. If a job in GitLab CI/CD doesn't match any integration job in YouTrack, it will not be processed by YouTrack.Īn integration in YouTrack is triggered when a corresponding job in GitLab CI/CD finishes successfully. The job name will be matched with the job name in the GitLab CI/CD configuration file. In the sidebar, scroll down to the GitLab CI/CD section.Īdd a name for the integration job. Select the target GitLab integration from the list of configured integrations. To define a new GitLab CI/CD integration job:Ĭlick the Projects link in the header to open the Projects list.įrom the action menu for your project, select VCS.
You can define integration jobs in the settings of an existing GitLab integration. To start using features of the integration with GitLab CI/CD, define one or several integration jobs in YouTrack.Įach integration job must match an existing job in Gitlab CI/CD by name. You can check the expiration date of the token and generate a new token on the Personal Access Tokens page in GitLab. If you are adding a GitLab CI/CD integration to a GitLab integration set up some time ago, the token may expire in the near future.
#Gitlab youtrack integration update
Pull pipeline IDs from connected projects in GitLab CI/CD and automatically update the values in custom fields that store build numbers for resolved issues.Īpply commands to issues in YouTrack when GitLab CI/CD runs a job that contains the commit referencing the issue.īefore you start, verify that the authentication token that you used for the GitLab integration is valid. The integration between YouTrack and GitLab CI/CD enables useful features in both applications:
#Gitlab youtrack integration how to
To learn how to integrate YouTrack projects with GitLab repositories, see Integrate with GitLab.
The integration with GitLab CI/CD becomes possible when you have established a connection between a YouTrack project and a VCS repository that is hosted on, self-hosted GitLab Community Edition (CE), or self-hosted GitLab Enterprise Edition (EE) server. Could you explain a little more ?įields: “Issues url” and “New issue url” are self explainatory but field : “project url” is unclear for me.Follow the instructions on this page to integrate your YouTrack project with GitLab CI/CD. I don’t understand what kind of events you are thinking about ? From my understanding - such funcionality should only generate specific urls if some commit is referring some issue. “Push Event will be triggered by a push to the repository” There is section “Trigger” and there is information: There is funcionality to configure custom issue tracker ( Is this the right place for doing that ?
Connection between YouTrack => Gitlab is working correctly (commits in gitlab are being pinned to YouTrack issues) and now i want connection Gitlab => Youtrack (so, that if i see commit on gitlab with message pointing to some issue - this issue will be visible as link pointing to YouTrack issue) I want to create link with YouTrack issue tracker. Hello - i have a question regarding “Custom issue trackers” There is no documentation about this specific configuration screen (only dedicated tutorial for Redmine, Jira, Bugzilla available here : )
0 kommentar(er)
