Git Publisher "target remote name" validation problems, single repo

37,842

Solution 1

If your branch name is experiment and remote name is origin, change your SCM and Git Publisher configuration to:

SCM configuration:

  • Name: "origin"
  • Branch Specifier: "*/experiment"

Git Publisher configuration:

  • Target remote name: "origin"

The important thing, is to set the same name for Name parameter in SCM and Target remote name in Git Publisher.

I know it's a bit too late for answer, but maybe someone will find it useful.

Solution 2

Target remote name: will be "origin"

You can execute shell and generate custom tag and pass the same to git publisher.

Share:
37,842
TreeRex
Author by

TreeRex

I'm a middle-aged nerd with an awesome wife, a crazy terrier, and twin daughters away at college. Currently I mostly program in Clojure developing cognitive systems in the medical point-of-care space. I occasionally jump in Java, JavaScript, Groovy, Bash, Python, and R. Insert cloud buzzwords. In previous lives I worked on development tools (Symantec and Thinking Machines), operating systems (Apple), browsers (Spyglass), linguistic analysis systems (Basis Technology), and search and cognitive systems. I also have stage IV cancer, but it is what it is.

Updated on February 23, 2020

Comments

  • TreeRex
    TreeRex about 4 years

    I am trying to use the Git Publisher plugin to tag a successful build with the $BUILD_TAG, but I cannot figure out a value for the Target remote name that it will accept. If I use the Repository URL in the GIT configuration I'm told, No remote repository configured with the name . I tried naming the configuration and using that as the Target remote name, no luck.

    My SCM configuration (company name elided):

    My Git Publisher configuration:

    There is something about Git that I'm missing here.

    Thank you in advance for your help.