• Type: New Feature
• Resolution: Won't Do
• Priority: Major
• Component/s: gitlab-hook-plugin
• Labels:

  • automation
  • bug
  • gitlab,
  • plugin
• Environment:

  Jenkins 1.615
  Gitlab hook plugin: 1.4.0

1. 

   hookissue.png

   17 kB

   2015-06-18 17:14

[JENKINS-28973] naming autogenerated project does not postfix with branchname on first creation

Thomas Blitz created issue - 2015-06-18 17:15

Thomas Blitz made changes - 2015-06-18 17:17

Description

Original: According to documentation an autogenerated project should be named by the repo name and then postfixed with the branch, i.e. REPONAME_BRANCH In my testing i have observed that this is not the case the first time a project is created from an unknown repository notification. Then the name of the Jenkins project will match only the gitlab repo name and not prefix the branchname. Setup: Jenkins 1.615 Gitlab hook plugin: 1.4.0 Automatic project creation is ON Template based job creation is used and ONLY base project has a value gitlabhookpluginsetup Scenario: Prerequisite. Reponame FOO Gitlab repo FOO has webhook to jenkins using build_now Jenkins does not have a Project relating to repo FOO Reproduce: # Commit to {code:java} master {code}  branch of repo FOO # Jenkins/plugin recieves notification and creates project named FOO. Expected name should be FOO_master # Commit to master branch of repo FOO again and observe that Jenkins/plugin creates a new project named FOO_master. This is wierd since the Jenkins project FOO relate to the master branch # Commit to develop branch of repo FOO # Jenkins/Plugin recieves notification and creates project named FOO_develop as expected. According to log the project FOO_develop is based on project FOO

New: According to documentation an autogenerated project should be named by the repo name and then postfixed with the branch, i.e. REPONAME_BRANCH In my testing i have observed that this is not the case the first time a project is created from an unknown repository notification. Then the name of the Jenkins project will match only the gitlab repo name and not prefix the branchname. Setup: Jenkins 1.615 Gitlab hook plugin: 1.4.0 Automatic project creation is ON Template based job creation is used and ONLY base project has a value gitlabhookpluginsetup Scenario: Prerequisite. Reponame FOO Gitlab repo FOO has webhook to jenkins using build_now Jenkins does not have a Project relating to repo FOO Reproduce: # Commit to *master*  branch of repo FOO # Jenkins/plugin recieves notification and creates project named *FOO*. Expected name should be *FOO_master* # Commit to master branch of repo FOO again and observe that Jenkins/plugin creates a new project named *FOO_master*. This is wierd since the Jenkins project FOO relate to the master branch # Commit to develop branch of repo FOO # Jenkins/Plugin recieves notification and creates project named *FOO_develop as expected*. According to log the project FOO_develop is based on project FOO

Thomas Blitz made changes - 2015-06-18 17:17

Description

Original: According to documentation an autogenerated project should be named by the repo name and then postfixed with the branch, i.e. REPONAME_BRANCH In my testing i have observed that this is not the case the first time a project is created from an unknown repository notification. Then the name of the Jenkins project will match only the gitlab repo name and not prefix the branchname. Setup: Jenkins 1.615 Gitlab hook plugin: 1.4.0 Automatic project creation is ON Template based job creation is used and ONLY base project has a value gitlabhookpluginsetup Scenario: Prerequisite. Reponame FOO Gitlab repo FOO has webhook to jenkins using build_now Jenkins does not have a Project relating to repo FOO Reproduce: # Commit to *master*  branch of repo FOO # Jenkins/plugin recieves notification and creates project named *FOO*. Expected name should be *FOO_master* # Commit to master branch of repo FOO again and observe that Jenkins/plugin creates a new project named *FOO_master*. This is wierd since the Jenkins project FOO relate to the master branch # Commit to develop branch of repo FOO # Jenkins/Plugin recieves notification and creates project named *FOO_develop as expected*. According to log the project FOO_develop is based on project FOO

New: According to documentation an autogenerated project should be named by the repo name and then postfixed with the branch, i.e. REPONAME_BRANCH In my testing i have observed that this is not the case the first time a project is created from an unknown repository notification. Then the name of the Jenkins project will match only the gitlab repo name and not prefix the branchname. Setup: Jenkins 1.615 Gitlab hook plugin: 1.4.0 Automatic project creation is ON Template based job creation is used and ONLY base project has a value gitlabhookpluginsetup Scenario: Prerequisite. Reponame FOO Gitlab repo FOO has webhook to jenkins using build_now Jenkins does not have a Project relating to repo FOO Reproduce: # Commit to *master*  branch of repo FOO # Jenkins/plugin recieves notification and creates project named *FOO*. Expected name should be *FOO_master* # Commit to master branch of repo FOO again and observe that Jenkins/plugin creates a new project named *FOO_master*. This is wierd since the Jenkins project FOO relate to the master branch # Commit to develop branch of repo FOO # Jenkins/Plugin recieves notification and creates project named *FOO_develop as expected*. According to log the project FOO_develop is based on project FOO nb. The attached image shows the setup of the plugin.

Javier Palacios made changes - 2016-01-10 10:49

Resolution		New: Not A Defect [ 7 ]
Status	Original: Open [ 1 ]	New: Resolved [ 5 ]

Thomas Blitz made changes - 2016-01-10 14:39

Issue Type

Original: Bug [ 1 ]

New: New Feature [ 2 ]

Thomas Blitz made changes - 2016-01-10 14:40

Resolution	Original: Not A Defect [ 7 ]
Status	Original: Resolved [ 5 ]	New: Reopened [ 4 ]

Javier Palacios made changes - 2016-02-01 23:14

Resolution		New: Won't Do [ 10001 ]
Status	Original: Reopened [ 4 ]	New: Resolved [ 5 ]

Javier Palacios made changes - 2016-03-24 11:54

Status

Original: Resolved [ 5 ]

New: Closed [ 6 ]

R. Tyler Croy made changes - 2016-07-26 00:01

Workflow

Original: JNJira [ 163837 ]

New: JNJira + In-Review [ 208893 ]