Small precision: better using "git checkout -B ${BRANCH_NAME}" in case the
workspace is not discarded
On Saturday, 18 February 2017 19:26:58 UTC+1, Damien Coraboeuf wrote:
>
> Using "git checkout -b ${BRANCH_NAME}" as a first shell step before the
> actual build is a very elegant trick.
>
> Than
Using "git checkout -b ${BRANCH_NAME}" as a first shell step before the
actual build is a very elegant trick.
Thanks Mark!
Best regards,
Damien.
On Saturday, 18 February 2017 19:14:12 UTC+1, Mark Waite wrote:
>
> The git plugin defaults to performing a checkout with a detached head at
> the SHA
The git plugin defaults to performing a checkout with a detached head at
the SHA1 hash to be built. There is a plugin option "LocalBranch" which
can assign the name of the local branch to be created at that SHA1. If
that's not available from the declarative pipeline, you may be able to
perform a
Hi Mark,
I'm also using the Pipeline Model Definition plug-in, and I think this is
the culprit in this story. Using the model definition, I do not see any way
to specify the "checkout scm" (as I would do in a "regular" pipeline
definition).
I'm using a versioning Gradle plugin and its output show
What are you observing that makes you think that shallow clone is always
enabled?
The git plugin and all my work with GitHub Organization Folders indicates
that shallow clone is disabled by default for all git plugin usage,
including GitHub Organization Folders.
I run a GitHub Organization Folder
Hi,
In order to compute versions correctly
(using https://github.com/nemerosa/versioning), I need my projects not to
be checked out using a shallow clone option.
The Organization plug-in
(https://wiki.jenkins-ci.org/display/JENKINS/GitHub+Organization+Folder+Plugin)
does not seem to allow to
