Thanks Mark for your reply. I did look at the previous successful job
output and compiled a script with following.
if [ ! -d .git ]; then git init; git status; else git status; fi # This is
to ijnitialize git -> this step not seen in the job output when plugin used.
git rev-parse --is-inside-work-tree
git config remote.origin.url ${URL}
git config --local credential.helper store --file=~/.git-credentials
git fetch --tags --progress ${URL} +refs/heads/*:refs/remotes/origin/*
git config --local --remove-section credential
git rev-parse origin/${BNAME}^{commit}
#git config core.sparsecheckout
git checkout -f ${REVNO}
#git branch -a
#git branch -D ${BNAME}
git checkout -b ${BNAME} ${REVNO}
I had commented out some lines above which were giving some errors, except
that I am able to checkout the contents, but in the git hub site I see
below commands (The clone command does little bit diff from above steps
which creates the parent folder in the workspace) :
git clone https://github.com/<pathToRepo>
git checkout develop
Though I see required files checked out from git, but I am skeptical to use
if it breaks anything. So far I am playing around with test repository,
soon I need to hook this to Development code. Can you please look into it
and verify if those steps are good to go?
Thanks in advance. -Sathya.
On Tuesday, March 31, 2015 at 1:07:58 PM UTC-7, Mark Waite wrote:
>
> When the git plugin is used for a job, the git commands used by the plugin
> are generally listed in the job output. What you listed seems to be even
> prior to job execution, so there is no way for you to see what the git
> plugin is doing.
>
> An argument type mismatch is surprising. There are relatively few hits in
> a google search of Jenkins git IllegalArgumentException. You'll need to
> provide more information before others can help you resolve the issue,
> since I doubt there are many others seeing the issue.
>
> Some of the common information which can help with diagnosis is described
> at https://wiki.jenkins-ci.org/display/JENKINS/How+to+report+an+issue .
> The steps listed there "before you submit a bug report" are good helps for
> diagnosis.
>
> Mark Waite
>
> On Tue, Mar 31, 2015 at 11:48 AM, 'sa_nk' via Jenkins Users <
> [email protected] <javascript:>> wrote:
>
>> Hi Team,
>> This is Sathya, I am new to Jenkins. I am not sure if similar to my
>> question was already posted and answered. If it did please direct me to
>> that answer else please see below my request.
>>
>>
>> I am looking for git command line steps that can be accomplished as
>> alternative to the procedure used in Jenkins UI with Git plugin as below:
>>
>>
>> Under Source Code Management Section of Jenkin Job configure UI:
>> ----------------------------------------------------------------
>>
>>
>> Git Repository: Repository URL (https://github.com/<path>)
>> Credentials (Select credentials from globally defined)
>>
>>
>> Branches to build: Branch Specifier (blank for 'any') (*/Development)
>>
>>
>> Repository broswer: (Auto)
>>
>>
>> Additional Behaviors: Check out to specific local branch - Branch name
>> (Development)
>>
>>
>>
>> In the above all the values are mentioned in the extream right
>> parenthesis. What I am looking for is equivakent git command line steps
>> with options to perform exactly like above so that when ever I experience
>> git plugin issues I can have alternate method of doing it. Couple of times
>> we experienced git plugin issues as below (And end up bouncing the Jenkins
>> and some times even bouncing Jenkins did not resolve):
>>
>>
>> *FATAL: argument type mismatch*
>> *java.lang.IllegalArgumentException: argument type mismatch*
>>
>>
>>
>> Thanks in advance and your help is highly appreciated.
>> -Sathya.
>>
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Jenkins Users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to [email protected] <javascript:>.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jenkinsci-users/8772bb4a-0dd7-4555-8d15-0d982f33ac39%40googlegroups.com
>>
>> <https://groups.google.com/d/msgid/jenkinsci-users/8772bb4a-0dd7-4555-8d15-0d982f33ac39%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> --
> Thanks!
> Mark Waite
>
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/adff96b2-9501-47dc-b861-15b414cf64b7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
