With code that old, I wouldn't attempt an in-place upgrade until you've performed an upgrade on a separate instance that you configured just for upgrade testing. Two years of evolution in Jenkins has introduced many changes.
On Wed, Apr 1, 2015 at 10:16 AM, 'sa_nk' via Jenkins Users < [email protected]> wrote: > Jenkins upgrade was attempted few months back, during then while > restarting Jenkins it was failing to start and due to criticality of > availability it was backed out. We are going to try upgrade again shortly. > Thanks for looking into it. > > -Sathya. > > > On Tuesday, March 31, 2015 at 10:48:38 AM UTC-7, sa_nk 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]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-users/d6ebe9d1-839e-4386-ab6c-80393f343f6e%40googlegroups.com > <https://groups.google.com/d/msgid/jenkinsci-users/d6ebe9d1-839e-4386-ab6c-80393f343f6e%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/CAO49JtGQqDR5RXuMycAPgqp8oei2SUEir-bHo8T%2BFGRX0HgbZQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
