• Type: Bug
• Resolution: Won't Fix
• Priority: Major
• Component/s: git-plugin
• Labels:

  None
• Environment:

  git-plugin version 3.0.1
  jenkins 2.7.4

1. 

   Снимок экрана 2016-12-12 в 17.49.52.png

   62 kB

   2016-12-12 10:50

2. 

   Снимок экрана 2016-12-12 в 17.50.10.png

   33 kB

   2016-12-12 10:50

3. 

   Снимок экрана 2016-12-12 в 17.51.42.png

   37 kB

   2016-12-12 10:51

[JENKINS-40376] Build must fail, if branch spec is an empty string

Nikolay Ustinov created issue - 2016-12-12 10:52

Nikolay Ustinov made changes - 2016-12-12 10:54

Link

New: This issue is blocked by JENKINS-8656 [ JENKINS-8656 ]

Nikolay Ustinov made changes - 2016-12-12 11:23

Description

Original: Use case: {quote} Create a freestyle build project with the following settings: - This build is parameterized Name = BRANCH_SPECIFIER Default Value = <leave blank> Source Code Management Git - Branch Specifier (blank for default): = $BRANCH_SPECIFIER {quote} Expected: The build must fail with ERROR because of $BRANCH_SPECIFIER was set as empty and *explicit better then implicit*. If you want branch spec as "**", then you should set $BRANCH_SPECIFIER was set as "**". Actually: $BRANCH_SPECIFIER was set as "**" and job will start in an infinite loop. Build for the build. Changes inserted in JENKINS-8656 need to be rolled back because they is non logical and misleading.

New: Use case: {quote} Create a freestyle build project with the following settings: - This build is parameterized Name = BRANCH_SPECIFIER Default Value = <leave blank> Source Code Management Git - Branch Specifier (blank for default): = $BRANCH_SPECIFIER {quote} Expected: The build must fail with ERROR because of $BRANCH_SPECIFIER was set as empty and *explicit better then implicit*. If you want branch spec as "**", then you should set $BRANCH_SPECIFIER was set as "**". Actually: $BRANCH_SPECIFIER was set as "**" and job will start in an infinite loop. Build for the build. Changes inserted in JENKINS-8656 need to be rolled back because they is non logical and misleading. Commit https://github.com/jenkinsci/git-plugin/commit/dc575dce269020afe79bf0224c906b2520c5438d

Collapse comment: Mark Waite added a comment - 2016-12-12 15:05

Mark Waite added a comment - 2016-12-12 15:05

We don't change default behaviors of the git plugin, even if one or more users feel they are

non logical and misleading

Too many users and installations depend on the default behaviors, and too little benefit would be gained by requiring them to change their parameterized jobs or their automation which launches jobs.

Expand comment: Mark Waite added a comment - 2016-12-12 15:05

Mark Waite added a comment - 2016-12-12 15:05 We don't change default behaviors of the git plugin, even if one or more users feel they are non logical and misleading Too many users and installations depend on the default behaviors, and too little benefit would be gained by requiring them to change their parameterized jobs or their automation which launches jobs.

Mark Waite made changes - 2016-12-12 15:05

Resolution		New: Won't Fix [ 2 ]
Status	Original: Open [ 1 ]	New: Resolved [ 5 ]

Mark Waite made changes - 2019-10-23 01:28

Status

Original: Resolved [ 5 ]

New: Closed [ 6 ]