Tests and commits

classic Classic list List threaded Threaded
31 messages Options
12
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Tests and commits

mavrothal
Administrator
It is nice that there is a flux of changes in woof.
I was wondering however if we should open a "testing branch" where the new commits can go, test that they allow building a sane puppy and then move to master.

Alternatively we can use the WCES(woof community edition stable)-number tag to indicate commits that are tested to build a _sane_ puppy.
The idea behind it is that will be very hard for a newcomer or even a developer to work with a constantly moving git HEAD

So what I think is that someone should build in regular intervals the last puppy build from BK's tree, ie Precise, release it under Precise-testing-WCES#, verify that they are _no regressions_ and then pull to master or mark with WCES. In the second case only commits that fix the regressions would be allowed in (the single) master branch.

When a "stable" release is made, then that can be used for regression testing instead of Precise-5.7.1

Thoughts?
 

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Tests and commits

01micko
Administrator
I think you are onto something there, especially with the limited number of testers available.

Which way to go do you think? 1st or 2nd option? Maybe the 2nd is more practical.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Tests and commits

Karl Godt
Administrator
In reply to this post by mavrothal
Thoughts ? Hmmm ...
I still have  to learn what words like fork, branch, tag, ref, head and so forth exactly mean and how to work with them.

About building from woof : I have not used woof until now, just fired up the gui several times and downloaded woof few times "just in case" and looked into the expanded tar balls . Am also on a 5GB/month full-speed internet limit, so not too much interested in downloading binary packages from whatever repository all the time .

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Tests and commits

mavrothal
In reply to this post by 01micko
2 is easier to administer but potentially harder to debug.
The Big question is who is going to make and release the builds (sing me out ;)
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Tests and commits

01micko
Administrator
In reply to this post by Karl Godt
KRG,

You know, you can essentially build everything yourself and keep your own local repository inside the woof tree... you don't need a full featured distro, just build it with essentials, will preserve your fragile download limit.

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Tests and commits

01micko
Administrator
In reply to this post by mavrothal
Well obviously me... and hopefully pemasu, when/if he gets time/inclination.

I agree 2 is more difficult to maintain but surely we can track well and roll back with git, no?
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Tests and commits

mavrothal
2 it is then.
Regarding building, could be anyone with the bandwidth and the hardware but I'll take you or pemasu ;D
(have you seen your gmail?)
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Tests and commits

01micko
Administrator
Ok, merged #6

Only thing is to adjust the PKGS_SPECS_TABLE variables for each build. I'll get onto it soon, I'll create an issue so I don't forget!
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Tests and commits

Karl Godt
Administrator
In reply to this post by mavrothal
In regards to WCES :
Is it worth , to add such VARIABLE to /etc/DISTRO_SPECS ?

Myself am playing with the idea to suggest to add a PUPPY_RELEASE_STATUS variable, with values like TEST, RC and RELEASE .
That would add the possibility to add debugging lines to scripts like

[ "$PUPPY_RELEASE_STATUS" = TEST ] && echo  "Some values" >>/tmp/${0##*/}.log

without the need to add and run everything manually with options  ..  
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Tests and commits

01micko
Administrator
In reply to this post by mavrothal
I made a 'testing' branch and committed the symlink fixes and will do a test build from that today. It should be save to merge with master.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Tests and commits

01micko
Administrator
I merged the testing branch because I built a reasonably stable slacko. Since though a couple more broken symlinks have been found, fix now pushed to testing.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Tests and commits

mavrothal
just pulled igu's commits so can be included in the new build (I guess he does not want to do it himself).
Should not be a problem for the build I think
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Tests and commits

01micko
Administrator
They are pretty sane and TBH I don't know why BK left them there. I have merged it in the testing branch too, but funny, github is telling me I'm 1 commit behind and 3 ahead of master

I know the 3 ahead but 1 behind? Anyway, if I merge with master will it sort itself out?
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Tests and commits

mavrothal
I guess there is a commit in master that is not in your local tree and you have made 3 new commits to your local tree
If I remember correctly you have to pull/merge first before you push.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Tests and commits

Karl Godt
Administrator
In reply to this post by 01micko
Please don't forget to announce  it also here at the mailing list :
"Ok here it is, a whopping 193M, but I put google-chrome in it, it's for a project I'm doing so never mind that, it works ok"
http://murga-linux.com/puppy/viewtopic.php?p=737368#737368

I am actually opening this mailing list and GitHub before the murga forum in the browser .


Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Tests and commits

01micko
Administrator
In reply to this post by mavrothal
I found the conflict by merging master with testing then pushed testing and then master, so it worked out in the end. Karl, your issue might be more fun since you have several of your own commits. Iguleder might be able to help.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Tests and commits

01micko
Administrator
In reply to this post by Karl Godt
Sure Karl, next time I will
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Tests and commits

Karl Godt
Administrator
In reply to this post by 01micko
I think , I have manged it by adding the

git remote add puppylinux-woof-CE https://github.com/puppylinux-woof-CE/woof-CE

main repo to my local repo and

git fetch puppylinux-woof-CE

that dowloaded a little
and

git pull puppylinux-woof-CE master

that updated my local repo .

Now I think have to commit it to my remote fork .
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Tests and commits

Karl Godt
Administrator
Done by

git push

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Tests and commits

Karl Godt
Administrator
In reply to this post by Karl Godt
Done by

git push

Did not even need a commit message.
12
Loading...