On 10/24/2011 04:01 AM, Rohan McGovern wrote:
Hi Rohan,
> The build logs issue is tracked by
> https://bugreports.qt.nokia.com/browse/QTQAINFRA-139 and should be
> solvable with a less drastic solution than an entire switchover of the CI
> tool.
I was not asking for a drastic move. I asked for
On 11/28/2011 02:53 AM, Rohan McGovern wrote:
>
> Alternatively, if someone knows of a publicly available and good quality
> caching wrapper or similar for git, please speak up :)
The other alternative is to keep the git clones around. E.g. with the Osmocom
jenkins[1] we have a trivial shell scr
Holger Hans Peter Freyther said:
> On 11/25/2011 02:40 PM, Holger Hans Peter Freyther wrote:
> > On 10/31/2011 11:30 PM, Sergio Ahumada Navea wrote:
> >
> >> 2) Build -> Execute Shell
> >> Command (without the #):
> >># git clean -dqffx
>
>
> > I finally had a little time and my ques
Hi,
On 11/25/2011 02:52 PM, Holger Hans Peter Freyther wrote:
> On 11/25/2011 02:40 PM, Holger Hans Peter Freyther wrote:
>> On 10/31/2011 11:30 PM, Sergio Ahumada Navea wrote:
>>
>>> 2) Build -> Execute Shell
>>> Command (without the #):
>>> # git clean -dqffx
>
>
>> I finally had a
On 11/25/2011 02:40 PM, Holger Hans Peter Freyther wrote:
> On 10/31/2011 11:30 PM, Sergio Ahumada Navea wrote:
>
>> 2) Build -> Execute Shell
>> Command (without the #):
>># git clean -dqffx
> I finally had a little time and my question would be.. What should I set
> qtgitreadonly t
On 10/31/2011 11:30 PM, Sergio Ahumada Navea wrote:
> 2) Build -> Execute Shell
> Command (without the #):
># git clean -dqffx
># git clone git://gitorious.org/qtqa/testconfig.git _testconfig
># perl _testconfig/test.pl --project "QtBase master Integration"
> --stage "
Holger Hans Peter Freyther said:
> On 11/03/2011 07:06 PM, lars.kn...@nokia.com wrote:
>
> > Yes, I agree that it'd be nice to avoid the recompile in that case.
> > However, this is the best way to be really certain your module works
> > against whatever it depends upon. It's not a huge issue on a
On 11/03/2011 07:06 PM, lars.kn...@nokia.com wrote:
> Yes, I agree that it'd be nice to avoid the recompile in that case.
> However, this is the best way to be really certain your module works
> against whatever it depends upon. It's not a huge issue on a decent
> machine, at least if the dependen
On 11/2/11 11:32 AM, "ext Holger Hans Peter Freyther"
wrote:
>On 11/02/2011 03:15 AM, Alan Alpert wrote:
>
>> Until the first release of Qt 5 though I don't see anyway to avoid
>> QtDeclarative needing a 'sufficiently' recent QtBase. sync.profile
>>implements
>> providing that knowledge, althoug
On 11/02/2011 03:15 AM, Alan Alpert wrote:
> Until the first release of Qt 5 though I don't see anyway to avoid
> QtDeclarative needing a 'sufficiently' recent QtBase. sync.profile implements
> providing that knowledge, although we currently prefer to just always build
> against master. Modular
On Wed, 2 Nov 2011 10:13:20 ext Holger Hans Peter Freyther wrote:
> To be the devils advocate: Can we have QtDeclarative and QtBase decoupled
> in a way that QtDeclarative works on a week old QtBase? a month? the one
> from the last stable/minor release? What would it mean if we can not do
> it?
I
Holger Hans Peter Freyther said:
>
> >> how difficult will it be to only checkout/update/build qtbase and not
> >> _all_ of
> >> Qt? Is this something that is planned?
> >
> > That is already the way it works - as Shane Kearns pointed out in a
> > followup mail. For testing qtbase, you get qt5,
On 11/02/2011 12:06 AM, Rohan McGovern wrote:
> Holger Hans Peter Freyther said:
>> how difficult will it be to only checkout/update/build qtbase and not _all_
>> of
>> Qt? Is this something that is planned?
>
> That is already the way it works - as Shane Kearns pointed out in a
> followup mail.
Holger Hans Peter Freyther said:
> On 10/31/2011 11:30 PM, Sergio Ahumada Navea wrote:
>
> > 1) Source Code Management -> Git
> > URL of repository: git://gitorious.org/qt/qtbase.git
> > Branch Specifier : master
>
>
> > Finally, you can see my build log: http://pastebin.com/iNVph7DP . T
r Hans Peter Freyther [mailto:hol...@freyther.de]
> Sent: Tuesday, November 01, 2011 15:56
> To: Kearns, Shane
> Cc: development@qt-project.org
> Subject: Re: [Development] [Qt5-feedback] 3rdpart platform plugins,
> tests and CI
>
> On 11/01/2011 04:01 PM, shane.kea...@accentur
On 11/01/2011 04:01 PM, shane.kea...@accenture.com wrote:
> I checkout and build qtbase.git as the normal way of working (to work on core
> / network libraries)
> I don't know how easy it is to build qtdeclarative.git (for example) on its
> own.
>
Sure, I build qtbase directly as well, but if y
project.org
> [mailto:development-bounces+shane.kearns=accenture@qt-project.org]
> On Behalf Of Holger Hans Peter Freyther
> Sent: Tuesday, November 01, 2011 14:52
> To: development@qt-project.org
> Subject: Re: [Development] [Qt5-feedback] 3rdpart platform plugins,
> tests and CI
>
> On
On 10/31/2011 11:30 PM, Sergio Ahumada Navea wrote:
> 1) Source Code Management -> Git
> URL of repository: git://gitorious.org/qt/qtbase.git
> Branch Specifier : master
> Finally, you can see my build log: http://pastebin.com/iNVph7DP . This
> is almost the same that the CI system is d
On 10/31/2011 11:05 AM, Rohan McGovern wrote:
> Holger Hans Peter Freyther said:
>> On 10/24/2011 04:21 PM, Holger Hans Peter Freyther wrote:
>>> On 10/24/2011 04:01 AM, Rohan McGovern wrote:
>>
>> Hi again,
>>
>> the response I am responding to ended up in moderation, I am now properly
>> subscrib
Holger Hans Peter Freyther said:
> On 10/24/2011 04:21 PM, Holger Hans Peter Freyther wrote:
> > On 10/24/2011 04:01 AM, Rohan McGovern wrote:
>
> Hi again,
>
> the response I am responding to ended up in moderation, I am now properly
> subscribed (in contrast of using gmane.org). Just to recap,
On 10/24/2011 04:21 PM, Holger Hans Peter Freyther wrote:
> On 10/24/2011 04:01 AM, Rohan McGovern wrote:
Hi again,
the response I am responding to ended up in moderation, I am now properly
subscribed (in contrast of using gmane.org). Just to recap, I have not
asked/intended to just switch off pu
21 matches
Mail list logo
