Aha! Thanks so much! I will have to get busy on this. I was looking at it
totally wrong.
On Tue, Aug 7, 2018, 9:10 PM Mark Waite wrote:
> The git plugin has no facility to support creating a branch or pushing a
> branch from a Pipeline step.
>
> However, Pipeline can do it with an "sh" or "bat"
Hi Mark!
Yeah, I'm not using a multibranch job in this case. Is that the idiomatic
Jenkins way to do things?
Thanks!
Jack
On Tue, Aug 8, 2017 at 3:37 PM, Mark Waite
wrote:
> BRANCH_NAME should have the value of the branch name in your pipeline
> context.
>
> See https://stackoverflow.com/quest
an
> implementation yet.
>
> There is always the alternative of calling the "sh" command to read the
> git repository and report the branch name to stdout, then assign that
> stdout value to a var.
>
> Mark Waite
>
> On Tue, Aug 8, 2017 at 1:42 PM Jack Brooks
Hi Indra,
To be clear, when you say, "Have you added the SSH public key of the user
used for cloning the github repo on Jenkins node/agent using git plugin?"
do you mean adding the public key of the github user to ~/.ssh on the agent
as a discrete file, or in authorized_users? Sorry, I'm not certa
Aha! I must have gotten something wrong in the rest of the steps, because
using a fresh new key I was able to get this working. Sorry for the dumb
user error, and thanks for the help!
Jack
On Wed, Dec 21, 2016 at 4:34 PM, Jack Brooks wrote:
> Hi Indra,
>
> To be clear, when you say,
