A "self hosted version control system" is one that is used for tracking its own source code.
When a new version control system is developed, initially no version control is used for it, or some existing version control.
Eventually, a major milestone is reached when the version control system is good enough for handling its own source code. At that point, ...
What is self hosted version control system
A version control system hosted in a location you control and administer yourself.
Git is designed as a "distributed version control system", this means that by default every user has a complete copy of the history. It's not strictly necessary to even have a central server at all, though it is generally very ...
An example will be maybe worth a thousand words:
$ sudo apt install git
$ ssh 192.168.0.110
kub@host:~$ git init --bare repo1
Initialized empty Git repository in /home/kub/repo1/
Connection to 192.168.0.110 closed.
Voila, We already posses a self-hosted version control system. Let's use it as an example client:
$ git clone 192.168.0....
Let's take it word by word:
Self: You or your organisation owns this thing. By contrast, a cloud-based offering by GitHub.com, Azure, GitLab.com, etc. (see this list on Wikipedia for a more comprehensive list) is not owned by you, but rather the service provider in question. Do not confuse ownership of the code (dictated by it's license – typically owned by ...
Assume you have your own IT infrastructure, eg a Linux server or a good old mainframe, on which you are running (hosting) your VCS software of choice, e.g GIT or ChangeMan ZMF. In such case you have a self hosted hosted VCS. As compared to GitHub, which is a web-based hosting service for software development projects using Git.
GitHub plugin doesn't pass payload data to any variables available from inside the pipeline.
Both Jenkins tracker and GitHub plugin project have a number of open and cancelled feature requests requesting this, for instance, https://issues.jenkins-ci.org/browse/JENKINS-24291.