Regarding a CI setup, do I need to provide an OFBiz personality to the Yetus repo, or can I have one in the appropriate OFBiz repo?
Met vriendelijke groet, Pierre Smits *Proud* *contributor* (but without privileges)* of* Apache OFBiz <https://ofbiz.apache.org/>, since 2008 *Apache Trafodion <https://trafodion.apache.org>, Vice President* *Apache Directory <https://directory.apache.org>, PMC Member* Apache Incubator <https://incubator.apache.org>, committer Apache Steve <https://steve.apache.org>, committer On Mon, Feb 17, 2020 at 7:41 PM Pierre Smits <pierresm...@apache.org> wrote: > Hi Allen, all, > > Thank you for the additional hints. I will work with that in my local > setup. And I am confident your hints and suggestions will deliver on my > intermediate goals. :) > > However, next step is setting up a CI and writing a PoC doc for the OFBiz > project. > > Met vriendelijke groet, > > Pierre Smits > *Proud* *contributor* (but without privileges)* of* Apache OFBiz > <https://ofbiz.apache.org/>, since 2008 > > *Apache Trafodion <https://trafodion.apache.org>, Vice President* > *Apache Directory <https://directory.apache.org>, PMC Member* > Apache Incubator <https://incubator.apache.org>, committer > Apache Steve <https://steve.apache.org>, committer > > > On Mon, Feb 17, 2020 at 6:45 PM Allen Wittenauer > <a...@effectivemachines.com.invalid> wrote: > >> >> >> > On Feb 17, 2020, at 5:04 AM, Pierre Smits <pierresm...@apache.org> >> wrote: >> > It seems to me that when credentials are provided, the script does a >> > authentication first before test are executed, and then something >> starts to >> > go wrong. >> > >> > Or am I doing something wrong? >> >> >> A troubleshooting tip is to look at the patch-dryrun.log in the >> --patch-dir. That will give you some hints as to why the patch couldn't be >> applied. >> >> That said, given your previous command lines, I have a suspicion >> that the repo isn't clean. --dirty-workspace, in particular, will force >> test-patch not to try and remove remnants of things. So the patch has >> already been applied and therefore can't be applied again/leads to general >> confusion as test-patch will pick up other things that have changed outside >> of the patch (since a lot of the work has to be done post-compilation). >> >> In general, I personally recommend that when using test-patch >> with PRs, create a fresh repo outside of your normal development repo, set >> --basedir to your new testing repo, and add the --resetrepo flag to >> test-patch. That last flag will make sure that test-patch has a fresh >> working slate to apply things by forcibly cleaning it out, doing pulls, >> setting the branch to trunk/master/whatever, etc. >> >>
