Geek Answers Handbook

Exact use of the "Forbidden Path to File" Jenkins Gerrit Trigger plugin

Jenkins Gerrit Trigger Plugin has a button "Add path to the forbidden file", but in fact there is not much documentation for it. So what is its exact behavior?

  • Does this trigger block if one of the modified files matches?
  • Or does it block the trigger if all modified files match ?
    (in other words: only matching files changed)
  • I believe this "overrides" the "Add File Path" correspondence, right?
  • Do only directory names or file names work?

This leads to the question if:
"Path to file" = ^((?!_abc)(?!_def).)*$
behaves equal to:
"Forbidden path to file" = ^.*_abc$|^.*_def$?

+4
source share
2 answers

According to the documents, my needs should be addressed to the V2.16.0 plug-in (see JENKINS-30620 ) - a new option " Disable strict forbidden file scanning ". The certificate says:

  • Enabling this option will allow the event to initiate assembly if the event contains BOTH one or more desired file paths And one or more applications forbidden file paths.
  • , , , .

, , .

" ", , JENKINS-19891:

, commit COMMIT_MSG, .

, , .

: ^((?!\/COMMIT_MSG|cunit|_abc|_def[\/\.]).)*$
... , ( ), "cunit", "_abc", "_def". "_def/"

+1

, ? , ? ( : )

commit message , - .

, - .

, "" " ", ?

. Add Forbidden file path , Add File path.

...

?

. .

, :

" " = ^ ((?! _ abc) (?! _ def).) * $

:

" " = ^._ abc $| ^._ def $?

, : ^((?!_abc)(?!_def).)*$ ^.*(?!_abc)(?!_def)$. (^), (*) , ..

.

  • Add File path , . Add Forbidden file path , - .
  • Add File path **, , Add Forbidden file path. Add Forbidden file path , Add File path .
+2

More articles:


All Articles