[GitHub] maven-release pull request #12: [MRELEASE-979]: Allow VersionPolicies to man...

2017-01-26 Thread hgschmie
GitHub user hgschmie opened a pull request: https://github.com/apache/maven-release/pull/12 [MRELEASE-979]: Allow VersionPolicies to manage Branch and Tag names Introduces a new policy, NamingPolicy which allows managing branch and tag names. This is similar but independent from

Re: [IT MNG-5958 - Take 2]: Please review integration test for MNG-5958

2017-01-26 Thread Anton Tanasenko
Awesome, thanks! 2017-01-26 21:24 GMT+02:00 Christian Schulte : > Am 01/25/17 um 23:52 schrieb Christian Schulte: > > Am 01/25/17 um 23:44 schrieb Christian Schulte: > >> Am 01/16/17 um 02:48 schrieb Christian Schulte: > >>> Commit to review is here: > >>> > >>>

Re: [IT MNG-5958 - Take 2]: Please review integration test for MNG-5958

2017-01-26 Thread Christian Schulte
Am 01/25/17 um 23:52 schrieb Christian Schulte: > Am 01/25/17 um 23:44 schrieb Christian Schulte: >> Am 01/16/17 um 02:48 schrieb Christian Schulte: >>> Commit to review is here: >>> >>>

Re: Please delete branches after merge to master

2017-01-26 Thread Stephen Connolly
They will get cleaned up eventually... though with the custom workspace locator in multibranch I am not 100% confident ;-) On Thu 26 Jan 2017 at 19:05, Arnaud Héritier wrote: > It's a new feature ? > Because workspaces were never removed on jobs removals AFAIR ? > > Le jeu. 26 janv. 2017 à 18:21

Re: Please delete branches after merge to master

2017-01-26 Thread Arnaud Héritier
It's a new feature ? Because workspaces were never removed on jobs removals AFAIR ? Le jeu. 26 janv. 2017 à 18:21, Stephen Connolly < stephen.alan.conno...@gmail.com> a écrit : > It should... but may not if the node was off-line > > On 26 January 2017 at 16:37, Christian Schulte wrote: > > > Doe

Re: Please delete branches after merge to master

2017-01-26 Thread Stephen Connolly
It should... but may not if the node was off-line On 26 January 2017 at 16:37, Christian Schulte wrote: > Does this also purge all workspaces on all nodes? > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For a

Re: Please delete branches after merge to master

2017-01-26 Thread Christian Schulte
Does this also purge all workspaces on all nodes? - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org

Please delete branches after merge to master

2017-01-26 Thread Stephen Connolly

Re: Master build broken

2017-01-26 Thread Stephen Connolly
I've kicked off another build, see if the disk space issue has been resolved On 26 January 2017 at 11:26, Stephen Connolly < stephen.alan.conno...@gmail.com> wrote: > Caused by: hudson.plugins.git.GitException: Command "git init > f:\jenkins\jenkins-slave\workspace\maven-3.x-jenkinsfile\master\t

Re: Master build broken

2017-01-26 Thread Stephen Connolly
Caused by: hudson.plugins.git.GitException: Command "git init f:\jenkins\jenkins-slave\workspace\maven-3.x-jenkinsfile\master\test" returned status code 128: stdout: stderr: error: copy-fd: write returned: No space left on device fatal: cannot copy 'F:\Program Files\Git\mingw64/share/git-core/templ

Master build broken

2017-01-26 Thread Stephen Connolly
https://builds.apache.org/job/maven-3.x-jenkinsfile/job/master/16/

Re: Reviewing MNG-6105

2017-01-26 Thread Michael Osipov
Am 2017-01-26 um 00:08 schrieb Guillaume Boué: Hi, MNG-6105 was committed to a branch and there is a clean build of the IT https://builds.apache.org/job/maven-3.x-jenkinsfile/job/MNG-6105/. I will merge this into master Saturday if there are no objections. The related issues (MNG-5670 and MNG-60