Broken master

If your Gerrit change based on recent master gets aborted by Jenkins, rebase it atop at least  "Revert "tdf#43175: Adapt ranges when copying or moving several sheets"". (And please take

Broken master Gerrit Jenkins Windows builds

It looks promising that "Revert 'WIN replace clipboard update thread with Idle' et al" should end the master Gerrit Jenkins Windows builds timing out and aborting. Please rebase your outstanding changes accordin

Broken master

If your Gerrit change based on recent master gets aborted by Jenkins, rebase it atop at least "Revert 'tdf#95425 follow-up: enable "Source format" checkbox of data label'". (And please take

Broken master on iOS.

Hi Commit: commit 3a36cf434fb4a967c9ea767cb7ac5f4da0502a0d Author: Noel Grandin Date: Tue Apr 25 15:09:53 2017 +0200 loplugin:checkunusedparams in configmgr and vcl Change-Id: I7226d01f38e6edaf3868d7267d9b02dbdbc9e5ba Reviewed-on: https://gerrit.libreoffice.org/36975 Test

Re: Possibly broken master branch with Android Viwer

Hi Mert, On Thu, Jul 28, 2016 at 01:04:12PM +, Mert Tümer wrote: > I am working on Android Viewer for a while. I know that most of you > are not Android Viewer developer but my problem is about build > process. I think current master branch is broken. When i try to build > libreoffice with "

Re: Possibly broken master branch with Android Viwer

Hi, On Thu, Jul 28, 2016 at 01:04:12PM +, Mert Tümer wrote: > after that i tried to do make clew and it gave me this error: > /home/mert/libreoffice/external/clew/Library_clew.mk:10: *** Library clew > must be registered in Repository.mk or RepositoryExternal.mk. Stop. > and also i got the s

Possibly broken master branch with Android Viwer

Hi, I am working on Android Viewer for a while. I know that most of you are not Android Viewer developer but my problem is about build process. I think current master branch is broken. When i try to build libreoffice with "with-distro=LibreOfficeAndorid" i am getting error like this; in open

Re: Broken master and newcomers.

This is Interesting - http://www.3d-architectural-rendering.com -- View this message in context: http://nabble.documentfoundation.org/Broken-master-and-newcomers-tp4180386p4182075.html Sent from the Dev mailing list archive at Nabble.com

Re: Broken master and newcomers.

On Thu, Apr 21, 2016 at 6:14 AM, jan iversen wrote: > Sorry for double mail, to this theme, but speaking with a good friend of mine > (who runs a very big ci system), I got an idea, which might solve the problem > for good. > > Whenever jenkins builds a gerrit job, jenkins master knows when all

Re: Broken master and newcomers.

Sorry for double mail, to this theme, but speaking with a good friend of mine (who runs a very big ci system), I got an idea, which might solve the problem for good. Whenever jenkins builds a gerrit job, jenkins master knows when all platforms for that patch is compiled, so it should be possibl

Re: Broken master and newcomers.

Just had an interesting IRC chat on the infra channel. It seems it would be easy to have our ci system maintain a tag pr. platform. The idea would be: when master compiles on platform Foo, set/move tag "buildable_on_". Doing that would have a very minimal effect on the build job, but give (

Re: Broken master and newcomers.

On 07/04/16 00:17, Norbert Thiebaud wrote: > On Wed, Apr 6, 2016 at 6:14 PM, Anthonys Lists > wrote: >> On 07/04/2016 00:08, Norbert Thiebaud wrote: Imho, IF we do something like this, we should use the git facilities to > create a shallow clone backup, that people can then use ftp

Re: Broken master and newcomers.

On Wed, Apr 6, 2016 at 6:14 PM, Anthonys Lists wrote: > On 07/04/2016 00:08, Norbert Thiebaud wrote: >>> >>> Imho, IF we do something like this, we should use the git facilities to >>> >create a shallow clone backup, that people can then use ftp or rsync or >>> > some >>> >other interruptible prot

Re: Broken master and newcomers.

On 07/04/2016 00:08, Norbert Thiebaud wrote: Imho, IF we do something like this, we should use the git facilities to >create a shallow clone backup, that people can then use ftp or rsync or some >other interruptible protocol to download. We have been doing that for years: http://dev-www.libreof

Re: Broken master and newcomers.

On Wed, Apr 6, 2016 at 5:58 PM, Anthonys Lists wrote: > On 06/04/2016 08:21, Bjoern Michaelsen wrote: >>> >>> An alternative (which I have seen used in another project), would be to >>> let >>> >jenkins generate a source tar ball, incl. the .git directory, of the >>> > latest >>> >sane build. >> >

Re: Broken master and newcomers.

On 06/04/2016 08:21, Bjoern Michaelsen wrote: An alternative (which I have seen used in another project), would be to let >jenkins generate a source tar ball, incl. the .git directory, of the latest >sane build. No, thats horrible -- it make onboarding to git even harder. What quite do you mean

Re: Broken master and newcomers.

On Wed, Apr 6, 2016 at 1:04 AM, jan iversen wrote: > Hi. > > I experience quite frequently that new contributors follow the instructions, > but end up with a master that will not compile, these day that is unlucky: here are the stats for the last 14 days: from:Wed Mar 23 21:30:24 2016

Re: Broken master and newcomers.

Hi, On Wed, Apr 06, 2016 at 07:08:06PM +0200, jan iversen wrote: > > http://people.canonical.com/~bjoern/presentations/tb3.odp > > http://people.canonical.com/~bjoern/presentations/tb3-2014.odp > > https://gerrit.libreoffice.org/gitweb?p=tb3-django.git;a=summary > > https://gerrit.libreoffice.org/

Re: Broken master and newcomers.

> > That idea is old -- and yes, having it directly in as a note, tag or brach git > would be awesome. Personally, I would love to see a "master-ci-verfied" > _branch_ > that is following the master branch up to the point that is known good by CI. > A > branch has the advantage that it would all

Re: Broken master and newcomers.

Hi, On Wed, Apr 06, 2016 at 08:04:39AM +0200, jan iversen wrote: > I have been thinking for a while, if we could get jenkins to keep a marker of > the last buildable version, store it somwhere easy to grap (preferable in the > repo itself), and then extend our build instructions to do "git checkou

Broken master and newcomers.

Hi. I experience quite frequently that new contributors follow the instructions, but end up with a master that will not compile, leaving a frustrated contributors, and causing us to use time here on the list (or my private mailbox). I have been thinking for a while, if we could get jenkins to