​Thanks Mark. Will try it. *Kind Regards, * *Sairam * 9884699987 | Skype - vjsairam
On Wed, Jul 16, 2014 at 6:19 PM, Mark Waite <[email protected]> wrote: > You could add a build step to the job which copies the file before the > step which performs the build. > > > On Wed, Jul 16, 2014 at 6:38 AM, sai ram <[email protected]> wrote: > >> We do not have privileges to change the source code of the testng file >> creation and it. >> >> The file is created to the workspace directory on the run time by taking >> the string parameters from Jenkins. >> >> is there any workaround for this ? >> >> *Kind Regards, * >> *Sairam * >> 9884699987 | Skype - vjsairam >> >> >> On Wed, Jul 16, 2014 at 6:02 PM, Mark Waite <[email protected]> >> wrote: >> >>> If you create the file yourself, then why not create the file in the >>> directory where you want it? >>> >>> Alternately, why not copy it into the place where you want it with the >>> same program or build step which created the file? >>> >>> >>> On Wed, Jul 16, 2014 at 6:18 AM, sai ram <[email protected]> wrote: >>> >>>> The dynamic file is not associated with the repo. We create a dynamic >>>> testng file and refer the test class in that. so the testng file should >>>> reside inside the repo. >>>> >>>> *Kind Regards, * >>>> *Sairam * >>>> 9884699987 | Skype - vjsairam >>>> >>>> >>>> On Wed, Jul 16, 2014 at 5:08 PM, Mark Waite <[email protected]> >>>> wrote: >>>> >>>>> I don't understand what you mean by dynamic file. >>>>> >>>>> Git does not have a concept of a file kept in one location in the >>>>> repository and moved to another during checkout, at least not as far as I >>>>> know. >>>>> >>>>> I guess you could copy the file as part of your build script, but >>>>> there is no way to make that part of the checkout. >>>>> >>>>> Mark Waite >>>>> >>>>> >>>>> On Tue, Jul 15, 2014 at 11:06 PM, sai ram <[email protected]> wrote: >>>>> >>>>>> When I do a sparse checkout, then in the Jenkins workspace I see, >>>>>> >>>>>> ProjectA/ProjectB >>>>>> >>>>>> but I want to create a dynamic file that has be moved inside the >>>>>> ProjectB and currently its located under, >>>>>> >>>>>> ProjectA/ProjectB >>>>>> abc.xml >>>>>> >>>>>> Please let me know how to do sparse checkout for this. >>>>>> >>>>>> Thanks, >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> On Mon, Jul 14, 2014 at 7:05 PM, Mark Waite < >>>>>> [email protected]> wrote: >>>>>> >>>>>>> If directoryA is a parent of directoryB and you only want >>>>>>> directoryB, then you would list directoryA/directoryB in the sparse >>>>>>> checkouts field. >>>>>>> >>>>>>> >>>>>>> On Mon, Jul 14, 2014 at 7:20 AM, sai ram <[email protected]> >>>>>>> wrote: >>>>>>> >>>>>>>> Thanks Mark. Will give a try. Could you please let me know what >>>>>>>> path should I give in the sparse checkout if my project setup is as >>>>>>>> below, >>>>>>>> >>>>>>>> Root >>>>>>>> --- Project A >>>>>>>> ---- Project B >>>>>>>> >>>>>>>> I want to sparse checkout Project B >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> *Kind Regards, * >>>>>>>> *Sairam * >>>>>>>> 9884699987 | Skype - vjsairam >>>>>>>> >>>>>>>> >>>>>>>> On Mon, Jul 14, 2014 at 6:40 PM, Mark Waite < >>>>>>>> [email protected]> wrote: >>>>>>>> >>>>>>>>> Check that your git repository actually contains a commit with >>>>>>>>> SHA1 faaf2c4ff254904ca0692a69270b9d342cd8a637 . >>>>>>>>> >>>>>>>>> If it does, then check that the repository which Jenkins is using >>>>>>>>> actually contains a commit with SHA1 >>>>>>>>> faaf2c4ff254904ca0692a69270b9d342cd8a637. >>>>>>>>> >>>>>>>>> Assure that you are not using "shallow clone" in the Jenkins >>>>>>>>> repository, since a shallow clone may not include the SHA1 you're >>>>>>>>> trying to >>>>>>>>> use. >>>>>>>>> >>>>>>>>> >>>>>>>>> On Mon, Jul 14, 2014 at 7:01 AM, sai ram <[email protected]> >>>>>>>>> wrote: >>>>>>>>> >>>>>>>>>> Please help me out with this error, >>>>>>>>>> >>>>>>>>>> Command "git read-tree -mu HEAD" returned status code 128: >>>>>>>>>> stdout: >>>>>>>>>> stderr: fatal: Not a valid object name HEAD >>>>>>>>>> >>>>>>>>>> . >>>>>>>>>> . >>>>>>>>>> FATAL: Could not checkout null with start point >>>>>>>>>> faaf2c4ff254904ca0692a69270b9d342cd8a637hudson.plugins.git.GitException >>>>>>>>>> >>>>>>>>>> <http://stacktrace.jenkins-ci.org/search?query=hudson.plugins.git.GitException>: >>>>>>>>>> Could not checkout null with start point >>>>>>>>>> faaf2c4ff254904ca0692a69270b9d342cd8a637 >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> . >>>>>>>>>> . >>>>>>>>>> Caused by: hudson.plugins.git.GitException >>>>>>>>>> <http://stacktrace.jenkins-ci.org/search?query=hudson.plugins.git.GitException>: >>>>>>>>>> Command "git checkout -f faaf2c4ff254904ca0692a69270b9d342cd8a637" >>>>>>>>>> returned status code 128: >>>>>>>>>> stdout: >>>>>>>>>> stderr: error: Sparse checkout leaves no entry on working directory >>>>>>>>>> >>>>>>>>>> . >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> *Kind Regards, * >>>>>>>>>> *Sairam * >>>>>>>>>> 9884699987 | Skype - vjsairam >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> On Mon, Jul 14, 2014 at 6:28 PM, Mark Waite < >>>>>>>>>> [email protected]> wrote: >>>>>>>>>> >>>>>>>>>>> Yes, it is. You'll need a git version which supports sparse >>>>>>>>>>> checkout, and a recent version of git-client-plugin and a recent >>>>>>>>>>> version of >>>>>>>>>>> git-plugin. >>>>>>>>>>> >>>>>>>>>>> Once you have those pre-requisites, then you click the "Add" >>>>>>>>>>> button in "Additional Behaviours" and select "Sparse Checkout >>>>>>>>>>> paths". We >>>>>>>>>>> use it very often. It works well for us. >>>>>>>>>>> >>>>>>>>>>> Mark Waite >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> On Mon, Jul 14, 2014 at 6:49 AM, sai ram <[email protected]> >>>>>>>>>>> wrote: >>>>>>>>>>> >>>>>>>>>>>> Hi, >>>>>>>>>>>> >>>>>>>>>>>> I want to checkout a particular folder from GIT repo. Please >>>>>>>>>>>> let me know if this is possible in the latest GIT version. >>>>>>>>>>>> >>>>>>>>>>>> Thanks, >>>>>>>>>>>> *Sairam * >>>>>>>>>>>> >>>>>>>>>>>> -- >>>>>>>>>>>> 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]. >>>>>>>>>>>> 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]. >>>>>>>>>>> For more options, visit https://groups.google.com/d/optout. >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> -- >>>>>>>>>> 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]. >>>>>>>>>> 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]. >>>>>>>>> For more options, visit https://groups.google.com/d/optout. >>>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> 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]. >>>>>>>> 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]. >>>>>>> For more options, visit https://groups.google.com/d/optout. >>>>>>> >>>>>> >>>>>> -- >>>>>> 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]. >>>>>> 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]. >>>>> For more options, visit https://groups.google.com/d/optout. >>>>> >>>> >>>> -- >>>> 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]. >>>> 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]. >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> -- >> 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]. >> 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]. > For more options, visit https://groups.google.com/d/optout. > -- 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]. For more options, visit https://groups.google.com/d/optout.
