Re: Add permissions to close Pull Requests in ASF projects at GitHub

I always track all PRs in my mind and I then determine the order in which I should take theirs and mine branches. Then the classes and modules do not 'touch' and commits are squashed and successfully rebased. On Sun, Mar 18, 2018 at 9:28 PM, Michael Osipov wrote: > Am 2018-03-18 um 21:26 schrieb

Re: Add permissions to close Pull Requests in ASF projects at GitHub

Am 2018-03-18 um 21:26 schrieb Tibor Digana: I always do it with interactive 'git rebase' in IntelliJ IDEA. If there is a merge conflict, the contributor creates a new PR which has happened maybe only once. The most of the time the repo could be successfully rebased on master HEAD. That's the r

Re: Add permissions to close Pull Requests in ASF projects at GitHub

I always do it with interactive 'git rebase' in IntelliJ IDEA. If there is a merge conflict, the contributor creates a new PR which has happened maybe only once. The most of the time the repo could be successfully rebased on master HEAD. On Sun, Mar 18, 2018 at 8:41 PM, Michael Osipov wrote: > A

Re: Add permissions to close Pull Requests in ASF projects at GitHub

Hi, On 18/03/18 21:01, Hervé BOUTEMY wrote: Le dimanche 18 mars 2018, 20:41:05 CET Michael Osipov a écrit : Am 2018-03-18 um 20:28 schrieb Karl Heinz Marbaise: Hi Tibor, On 18/03/18 19:50, Tibor Digana wrote: Do you have permissions to close pull requests in our ASF Maven projects? Are you

Re: Add permissions to close Pull Requests in ASF projects at GitHub

Tibor, With GitBox, Maven developpers can have the permission: this is one of the key feature we expected from GitBox migration See "Link GitHub and ASF accounts (required to push to GitHub)" link on https://gitbox.apache.org/ You're not yet linked, you should follow the instructions and you'l

Re: Add permissions to close Pull Requests in ASF projects at GitHub

Le dimanche 18 mars 2018, 20:41:05 CET Michael Osipov a écrit : > Am 2018-03-18 um 20:28 schrieb Karl Heinz Marbaise: > > Hi Tibor, > > > > On 18/03/18 19:50, Tibor Digana wrote: > >> Do you have permissions to close pull requests in our ASF Maven projects? > > > > Are you allowed to do merge a p

Re: Add permissions to close Pull Requests in ASF projects at GitHub

Am 2018-03-18 um 20:28 schrieb Karl Heinz Marbaise: Hi Tibor, On 18/03/18 19:50, Tibor Digana wrote: Do you have permissions to close pull requests in our ASF Maven projects? Are you allowed to do merge a pull request via GitHub ? Please don't do that. GitHub will -- by default -- do a no-f

Re: Add permissions to close Pull Requests in ASF projects at GitHub

Hi Tibor, On 18/03/18 19:50, Tibor Digana wrote: Do you have permissions to close pull requests in our ASF Maven projects? Are you allowed to do merge a pull request via GitHub ? Kind regards Karl Heinz Marbaise - To unsubs

Re: Add permissions to close Pull Requests in ASF projects at GitHub

>From my personal experience (as Bookkeeper committer) once Maven is migrated to gitbox committers will have permissions to close pull requests and even to add commits to pull requests of contributors Enrico Il dom 18 mar 2018, 19:58 Michael Osipov ha scritto: > Am 2018-03-18 um 19:50 schrieb T

Re: Add permissions to close Pull Requests in ASF projects at GitHub

Am 2018-03-18 um 19:50 schrieb Tibor Digana: Do you have permissions to close pull requests in our ASF Maven projects? Me either! I would like to close completed PRs which leak in the list at GitHub and the particular person does not respond to my request. Two options: 1. If you have merged, a

Add permissions to close Pull Requests in ASF projects at GitHub

Do you have permissions to close pull requests in our ASF Maven projects? Me either! I would like to close completed PRs which leak in the list at GitHub and the particular person does not respond to my request. T

Re: switch from Git WIP to GitBox

Simply a pure mapping (in the job GUI) would prevent from such issues subst X: F:\jenkins\jenkins-slave\workspace\n-wip_maven-surefire_master-VMXNEFVLKSG4Y4Q25OS6RZDPHGE56CJURNETLF6TR2V5RXK7KNVQ On Sun, Mar 18, 2018 at 4:51 PM, Stephen Connolly < stephen.alan.conno...@gmail.com> wrote: > On 18

Re: switch from Git WIP to GitBox

On 18 March 2018 at 12:55, Tibor Digana wrote: > Hi Stephen, > > You probably mean -Djenkins.branch.WorkspaceLocatorImpl.PATH_MAX=50 > Our INFRA set it to 50. > Can it be smaller as well? > The artifacts [1] says "The default value is 80; values as low as 54 (but > no lower) are possible." > Not

Re: Change of checksum policy in Apache

Le dimanche 18 mars 2018, 13:14:12 CET Karl Heinz Marbaise a écrit : > Hi to all, > > based on the checksum policy change in ASF[1] I would like to ask what > you think would be the best way to go. I have summarized my thoughts on > that...maybe you have some suggestions/supplementals etc. > > >

Re: switch from Git WIP to GitBox

Git-WIP to GitBox migration done: our RW Git repositories are now all on GitBox, with better GitHub integration We have now only 8 repos in svn: - archetypes is currently being migrated, should be done tomorrow - site and doxia-site are waiting for Jenkins svnpubsub configuration before we can s

Re: switch from Git WIP to GitBox

Hi Tibor, NP: I just updated master, without really checking which version it was you know better than me :) Regards, Hervé Le dimanche 18 mars 2018, 12:55:30 CET Tibor Digana a écrit : > Hi Herve, > > I have assigned your jira SUREFIRE-1504 to version 3.0.0-M1. > Are you fine with that? > >

Re: switch from Git WIP to GitBox

Hi Stephen, You probably mean -Djenkins.branch.WorkspaceLocatorImpl.PATH_MAX=50 Our INFRA set it to 50. Can it be smaller as well? The artifacts [1] says "The default value is 80; values as low as 54 (but no lower) are possible." Not sure if the min 54 is still valid after version 1.11 (2016). [1]

Re: switch from Git WIP to GitBox

On Sun 18 Mar 2018 at 12:13, Tibor Digana wrote: > The "maven-surefire" in > https://builds.apache.org/job/maven-box/job/maven-surefire is determined > by Git repo name? > If it was only "surefire" the Windows paths could be shorter. > Currently we have a problem with "Access denied.", see > htt

Change of checksum policy in Apache

Hi to all, based on the checksum policy change in ASF[1] I would like to ask what you think would be the best way to go. I have summarized my thoughts on that...maybe you have some suggestions/supplementals etc. Currently we have at least md5's in your release plugin repo[2] which means we s

Re: switch from Git WIP to GitBox

The "maven-surefire" in https://builds.apache.org/job/maven-box/job/maven-surefire is determined by Git repo name? If it was only "surefire" the Windows paths could be shorter. Currently we have a problem with "Access denied.", see https://issues.apache.org/jira/browse/INFRA-16191. I only guess it

Re: switch from Git WIP to GitBox

Hi Herve, I have assigned your jira SUREFIRE-1504 to version 3.0.0-M1. Are you fine with that? Cheers Tibor On Sun, Mar 18, 2018 at 11:20 AM, Hervé BOUTEMY wrote: > Hi, > > As you may have noticed, the issue was filed a long time ago > https://issues.apache.org/jira/browse/INFRA-15436 > and t

Re: Jenkins Build Question

Hi, On 18/03/18 12:33, Stephen Connolly wrote: On Sun 18 Mar 2018 at 11:24, Karl Heinz Marbaise > wrote: Hi Oliver, On 18/03/18 12:19, Olivier Lamy wrote: > Hi > Just migrated to gitbox so considered as a new job/project here? Yes I know but I

Re: Jenkins Build Question

On Sun 18 Mar 2018 at 11:24, Karl Heinz Marbaise wrote: > Hi Oliver, > > On 18/03/18 12:19, Olivier Lamy wrote: > > Hi > > Just migrated to gitbox so considered as a new job/project here? > > Yes I know but I observed that on other repos as well which are already > migrated..nevertheless need to

Re: switch from Git WIP to GitBox

Once the last one is moved, we should rename the organisation folder to just “maven” so that our job names in Jenkins are all nice and standard and everything is easier to find On Sun 18 Mar 2018 at 10:20, Hervé BOUTEMY wrote: > Hi, > > As you may have noticed, the issue was filed a long time ag

Re: Jenkins Build Question

Hi Oliver, On 18/03/18 12:19, Olivier Lamy wrote: Hi Just migrated to gitbox so considered as a new job/project here? Yes I know but I observed that on other repos as well which are already migrated..nevertheless need to continue to observe this... Kind regards Karl Heinz Marbaise On Sun

Re: Jenkins Build Question

Hi Just migrated to gitbox so considered as a new job/project here? On Sun, 18 Mar 2018 at 21:03, Karl Heinz Marbaise wrote: > Hi to all, > > currently observing things like[1] this in console output: > > Branch indexing > Obtained Jenkinsfile from 5e073791f9bb06cae1ed6513c8a5bde24844cf73 > Run

Jenkins Build Question

Hi to all, currently observing things like[1] this in console output: Branch indexing Obtained Jenkinsfile from 5e073791f9bb06cae1ed6513c8a5bde24844cf73 Running in Durability level: MAX_SURVIVABILITY Loading library jenkins-env@master Attempting to resolve master from remote references... > git

switch from Git WIP to GitBox

Hi, As you may have noticed, the issue was filed a long time ago https://issues.apache.org/jira/browse/INFRA-15436 and the work just started now: Wagon is migrated. Gavin should do the remaining 8 repos soon: if you're working on these Git repos currently, be prepared to the switch if anything i