Transfer Gitlab Issues to Youtrack - gitlab

We use Youtrack for our developers, and we have GitLab CE with repos. In several projects we allow external users to post issues in GitLab and I need copy of them in YouTrack. At least initial copy on posting.
Can't find any solution on web. So I guess we need to make our own, but with way is better?
YouTrack project workflows requesting some GitLab API url?
Webhooks? I don't see any web hook receiver on YouTrack side. Is there any web
hook Should U make some thing in the middle?

There're no webhooks available in YouTrack indeed, so your options would be either to use some external service that would copy information from GitLab to YouTrack, or create a workflow that would request GitLab for new issues every once in awhile.

Related

Creating Gitlab branch from JIRA

I have recently started using Gitlab and integrated with Jira. Both Gitlab and Jira server are self hosted internally in my corporate environment. 
I have come across a requirement where I want to create a branch in Gitlab for a project/issue directly from the JIRA issue.
Is it possible to do it? If yes then how? Is there any plugin required for that?
I have gone through some documentation but I couldn't find anything similar so if anyone has any idea please let me know.
https://docs.gitlab.com/ee/user/project/integrations/jira.html
This is now supported, with GitLab 14.2 (August 2021), in certain condition (Jira Cloud):
Create a GitLab branch from a Jira issue
Users of the GitLab.com for Jira Cloud application can now create GitLab branches directly from a Jira issue’s development panel.
This enables developers to begin work on issues without having to switch tools and lose context.
See Documentation and Issue.
That's not possible using the embedded Gitlab-Jira integration.
In jira, I suppose you have a workflow with statuses and transition. You need to configure a post function on your transition to call Gitlab API from your jira using groovy script.

REST API for gitlab CI?

I have set up a CI pipeline, and it is working well. However, I still have to go to a web interface and click buttons - is there an API for this functionality, specifically the CI part? I know there is a REST interface to gitlab as such, but I still haven't spotted the parts that handle CI - does it exist?
You can refer to the full API documentation.
You should more specifically be interested on the sections regarding jobs and pipelines

Deploy two VSTS repositories to one Azure web app

Let's say I have an Azure App Service web app at foo.azurewebsites.net. The code for the web app (a simple Node.js server and React frontend) is hosted on VSTS, and a custom deployment script is configured build and deploy the web app every time code is pushed to the repository's master branch. In other words, the standard web app configuration.
Now, all of my API code (just a Node.js server) is in another repository on VSTS. I'd like to be able to do the following:
Have all requests to foo.azurewebsites.net/api be handled by the API server (an implication of this, which I would nonetheless like to state explicitly, is that the server can ask the browser to set cookies that the web app can then read, and vice versa).
Set up similar continuous deployment for the API server, such that it gets redeployed whenever there are code changes in the API repo.
Be able to maintain the web app and API repositories completely separately.
This seems like a fairly standard scenario...is there an accepted solution? I came across this, but it seems like a pretty hacky way to do it, not to mention the fact that I have no idea what the correct URL is for the web hook for VSTS and can't seem to find any information on it. Also, that example doesn't cover how to deal with point (1) above.
EDIT: Additional clarification
Note that the accepted answer on this question is not what I'm looking for. It describes how to pull from a second repository at deployment time, but not how to have that second repository trigger deployments, or how to handle the fact that the the second repository is its own server. Additionally, it introduces a dependency between the two repositories, since the deploy.cmd is presumably under source control in the first repository.
EDIT: Virtual Directories
Thanks to #CtrlDot for pointing out that Virtual Directories are the way to solve (1). Still seeking guidance on (2) and (3).
I think the concept you are referring to is called Virtual Directories
I'm not sure which VSTS task you are using to deploy, but based on the article provided, you should be to configure it to target only the virtual directory you want to deploy to.
EDIT
Sorry for not being more clear. The AzureRmWebAppDeployment task has a parameter for virtual application name. You would simply set that in your deployment pipeline for the API project (/api) and for the main project (leave it blank)

Notify developer , If they are not pushing code to gitlab daily

Currently I am working in a project in which we are using Gitlab for repository management. I am the owner of project so I want to automate the code checkin validation on daily basis . my question is , Is there any option so that, I can configure the daily check(whether developer pushed there code or not) and send the notification to developers?
There is no build in functionality for this.
As this is a reasonable feature you should follow the feature request workflow of Gitlab and open an issue for that. https://gitlab.com/gitlab-org/gitlab-ce
But keep in mind that such feature will be probably only available for the EE version.
As alternative you can use the API of Gitlab to extract the commits of a project. https://docs.gitlab.com/ce/api/commits.html
Then process the date diffs using a e.g. python script and send an email or post on a Mattermost channel using their API. https://api.mattermost.com/

Gitlab - Pivotal Tracker integration

How do you integrate Gitlab and Pivotal Tracker for free?
I looked at the documentation on pivotal website, and cannot find anything related to that.
Integration to Pivotal Tracker has been present since Gitlab 6.2. There are more details in a comment on this page:
You will need to add your user API token under your profile in Pivotal to the Services section on the settings page for a specific project.
Then when you commit you just need to include the story ID in your commit message in the format [#id].
Example Commit:
Fixed a bug [#123].
There’s not much documentation on GitLab. Basically, go to your Project > Settings > Integrations, look for the Project Services header, enable the PivotalTracker integration. You’ll need your token from https://www.pivotaltracker.com/profile; enter that, set it as active, and save changes.
Here are three ways in which you can connect git with Pivotal Tracker:
ProjectLocker
GitTracker
This Script

Resources