Answers: <p>Gitlab Subgroups are essentially only additional path identifiers on the Gitlab server.</p>
  
  <p>For example if you have:  </p>
  
  <ul>
  <li>Gitlab server on <code>localhost</code>   </li>
  <li>Group: <code>test</code></li>
  <li>Subgroup <code>subgroup1</code>  </li>
  <li>Repository <code>myawesomerepo</code></li>
  </ul>
  
  <p>Then the path to your repository will be:</p>
  
  <pre><code>http://localhost/test/subgroup1/myawesomerepo
  </code></pre>
  
  <p>And cloning the repo will be</p>
  
  <pre><code>git clone git@localhost/test/subgroup1/myawesomerepo.git
  </code></pre>
  
  <p>So when you connect any Jenkins pipelines to the repo you will need to connect them to that full path.  </p>
  
  <p>Any changes being done or API's added to the Git repository itself can easily be monitored automatically to do some action via Jenkins.  </p>
  
  <p>However, since a Gitlab Subgroup is not a Git feature rather a Gitlab feature, you need to try and write you own logic to query on the full URL and to see if there were any new Subgroups/ API endpoints added.</p>
  
Answers: CC BY-SA 4.0
Answers: 2020-01-30T13:34:55.860Z
Answers: 2020-01-30T13:34:55.860Z
Answers: J00MZ
Body: <p>I am new to DevOps world and desperately looking for your help.
  We have multiple API depositors in GitLab subgroup, I am trying to establish a CI/CD pipeline, which will connect to GitLab subgroup,</p>
  <ol>
  <li>Any new API added into the subgroup, the pipeline will be triggered.</li>
  <li>If existing API code is updated into any branch pipeline should be triggered.</li>
  </ol>
  <p>In GIT repository, I have to provide the API URL, should I write #of pipelines as number API?</p>
  
Comments: CC BY-SA 4.0
Comments: 2019-12-25T08:33:16.080Z
Comments: Can you specify what the API added into subgroup specifies?
Comments: Manish_
Comments: CC BY-SA 4.0
Comments: 2020-12-24T14:49:51.933Z
Comments: @Biswa, if my answer helped you, can you mark it as accepted answer?
Comments: J00MZ
Tags: <continuous-integration><jenkins-pipeline><gitlab>
Title: Building Jenkins pipeline with GitLab info
UserDisplayName: Biswa Ranjan
ThreadText: # Building Jenkins pipeline with GitLab info
  
  (Asked by: username_0 on 2019-12-24)
  
  I am new to DevOps world and desperately looking for your help.
  We have multiple API depositors in GitLab subgroup, I am trying to establish a CI/CD pipeline, which will connect to GitLab subgroup,
  
  1. Any new API added into the subgroup, the pipeline will be triggered.
  2. If existing API code is updated into any branch pipeline should be triggered.
  
  In GIT repository, I have to provide the API URL, should I write #of pipelines as number API?
  
  **Tags:** continuous-integration, jenkins-pipeline, gitlab
  
  > **Comments:**
  > **username_1**: Can you specify what the API added into subgroup specifies?  
  > **username_2**: @username_0, if my answer helped you, can you mark it as accepted answer?  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_2 on 2020-01-30. Score: 1
  
  Gitlab Subgroups are essentially only additional path identifiers on the Gitlab server.
  
  For example if you have:
  
  * Gitlab server on `localhost`
  * Group: `test`
  * Subgroup `subgroup1`
  * Repository `myawesomerepo`
  
  Then the path to your repository will be:
  
  ```
  http://localhost/test/subgroup1/myawesomerepo
  
  ```
  
  And cloning the repo will be
  
  ```
  git clone git@localhost/test/subgroup1/myawesomerepo.git
  
  ```
  
  So when you connect any Jenkins pipelines to the repo you will need to connect them to that full path.
  
  Any changes being done or API's added to the Git repository itself can easily be monitored automatically to do some action via Jenkins.
  
  However, since a Gitlab Subgroup is not a Git feature rather a Gitlab feature, you need to try and write you own logic to query on the full URL and to see if there were any new Subgroups/ API endpoints added.
  
  
  ---
  
  