OK :)
Will try to find unused modules and maybe speed-up the build somehow :)
On Thu, 27 Dec 2018 at 14:18, Martin Grigorov wrote:
> Hi Maxim,
>
> I am not TravisCI user and I do not know its tricks :-/
> For me it has been always too fragile. Because it shares its resources to
> build thousands
Hi Maxim,
I am not TravisCI user and I do not know its tricks :-/
For me it has been always too fragile. Because it shares its resources to
build thousands of OSS projects the builds there are very unstable.
On Wed, Dec 26, 2018 at 6:31 AM Maxim Solodovnik
wrote:
> Hello Martin,
>
> Could you p
Hello Martin,
Could you please help me to fix wicketstuff build
Local build is successful, but Travis fails for some reason :(
BTW maybe you know is it possible to set bigger timeout? 50 minutes seems
to be not enough :(
On Tue, 25 Dec 2018 at 18:19, vineet semwal
wrote:
> Thank you maxim ..
>
Thank you maxim ..
On Tue, Dec 25, 2018 at 3:04 PM Maxim Solodovnik
wrote:
> I'm fixing wicketstuff-core:master build failures right now (was caused by
> wicket code clean-up)
>
> On Tue, 25 Dec 2018 at 01:20, vineet semwal
> wrote:
>
> > Thank you Maxim,i assumed yesterday that
> > git push o
I'm fixing wicketstuff-core:master build failures right now (was caused by
wicket code clean-up)
On Tue, 25 Dec 2018 at 01:20, vineet semwal
wrote:
> Thank you Maxim,i assumed yesterday that
> git push origin local:remotes/origin/wicket-8.x
> will push to wicket-8.x branch, instead it pushed a
Thank you Maxim,i assumed yesterday that
git push origin local:remotes/origin/wicket-8.x
will push to wicket-8.x branch, instead it pushed a new branch at remote..
today i pushed to wicket-8.x correctly...
On Mon, 24 Dec 2018 20:47 Maxim Solodovnik Hello Vineet,
>
> It seems you commit
> to
> r
Hello Vineet,
It seems you commit
to
remotes/origin/wicket-8.x
and to
wicket-8.x
every commit trigger build, you can check it here:
https://travis-ci.org/wicketstuff/core/branches :))
On Mon, 24 Dec 2018 at 21:11, vineet semwal wrote:
>
> Thank you martin,i understand now..yeah i will push in
Thank you martin,i understand now..yeah i will push in master branch too..
On Mon, 24 Dec 2018 18:59 Martin Grigorov Hi Vineet,
>
> I think all you need is:
> $ git checkout local8x
> $ edit files
> $ git commit -a -m "did something cool"
> $ git push
>
> "git push" will push local8x to its rem
Hi Vineet,
I think all you need is:
$ git checkout local8x
$ edit files
$ git commit -a -m "did something cool"
$ git push
"git push" will push local8x to its remote, which I suppose is wicket-8.x.
You can check this in ./.git/config file.
But please also merge your changes to 'master' branch. O
i see... ,i should have done git push origin local8x:wicket-8.x ?
Thanks !
On Mon, Dec 24, 2018 at 12:35 PM Maxim Solodovnik
wrote:
> I believe all enhancements should go to `wicket-8.x` and master
>
> On Mon, 24 Dec 2018 at 13:27, vineet semwal
> wrote:
> >
> > Hi,
> > For wickstuff : Are f
I believe all enhancements should go to `wicket-8.x` and master
On Mon, 24 Dec 2018 at 13:27, vineet semwal wrote:
>
> Hi,
> For wickstuff : Are following the branches to which i should push changes ?
> 8.x remotes/origin/wicket-8.x
> 7.x remotes/origin/wicket-7.x
> 6.x remotes/origin/wick
Hi,
For wickstuff : Are following the branches to which i should push changes ?
8.x remotes/origin/wicket-8.x
7.x remotes/origin/wicket-7.x
6.x remotes/origin/wicket-6.x
yesterday i did git push origin local8x:remotes/origin/wicket-8.x
is my workflow ok ?
Thanks !
--
Freelance developer o
12 matches
Mail list logo
