Yep, a branch in the repo is currently needed to test a specific change. We could update the job to allow alternative repos, but my read of recent rumblings from the ASF infra team is that we'd have to lock it down to some particular set of vetted people (i.e. committers on the project or a whitelist the PMC maintains).
On Sat, Aug 31, 2019 at 11:02 AM Nick Dimiduk <ndimi...@gmail.com> wrote: > > Hi Sakthi, > > I apologize for the delay of reply. I’m not familiar with the details of > this job, nor am I a recent participant in the community, so I was hoping > someone with more recent experience would answer these questions. > > To the best of my knowledge, we have no objection to creating jira-specific > branches in the repo, there are plenty of examples of this in our past. > Usually they’re done as a means of multi-developer collaboration, but > that’s not by policy. I think what you propose is a fine use-case for > pushing a branch. Please observe good hygiene in the shared space and clean > up after yourself when finished. > > Thanks, > Nick > > On Thu, Aug 22, 2019 at 14:23 Sakthi <sak...@apache.org> wrote: > > > Hello, > > > > I would like to test the fix to one of the flakies (HBASE-22895). For that, > > I want to utilize our HBase-adhoc-run-tests job to run the test repeatedly > > (~50 times) with the fix and see if it helps before pushing in the fix. I > > see that currently we only allow any of the branches from the hbase repo to > > be used for the testing in the job. > > > > Does that mean that I can create a branch(HBASE-22895) in the repo, push > > the fix there, run the job & when the issue is rectified, push the fix & > > delete the branch? Or is creation of new ad_hoc branches in the repo not > > really necessary or isn't the right way? > > > > Would appreciate your suggestions. > > > > -Sakthi > >
