From 58b52a8ef14b93d1b983eb9046b1bba35a5522c0 Mon Sep 17 00:00:00 2001 From: julien Lengrand-Lambert Date: Sun, 14 Aug 2016 17:02:11 +0200 Subject: [PATCH] Adds markup for website --- ...16-08-14-jenkins-clone-git-wrong-branch.md | 21 +++++++++++++++++-- 1 file changed, 19 insertions(+), 2 deletions(-) diff --git a/_posts/2016-08-14-jenkins-clone-git-wrong-branch.md b/_posts/2016-08-14-jenkins-clone-git-wrong-branch.md index 98f6ed7..8f0a676 100644 --- a/_posts/2016-08-14-jenkins-clone-git-wrong-branch.md +++ b/_posts/2016-08-14-jenkins-clone-git-wrong-branch.md @@ -1,5 +1,22 @@ -Cloning a workspace in Jenkins with a Git SVM setup does not checkout the correct branch. - +--- +layout: post +status: publish +published: true +title: Cloning a workspace in Jenkins with a Git SVM setup does not checkout the correct branch. +author: Julien Lengrand-Lambert +author_login: jlengrand +author_email: julien@lengrand.fr +author_url: http://www.lengrand.fr +categories: +- tips +tags: +- jenkins +- git +- gitlab +- clone +- SCM +comments: [] +--- Hi there, This is a strange behaviour I have noticed when using Jenkins lately, that caused us a few headaches before we realize what was happening.