Hi Alex,

This is what I get:

  ~/toaster_1_6/poky$ git remote add contrib 
http://git.yoctoproject.org/git/poky-contrib
  ~/toaster_1_6/poky$ git checkout contrib/toaster/master -b toaster-master
  fatal: Cannot update paths and switch to branch 'toaster-master' at the same 
time.
  Did you intend to checkout 'contrib/toaster/master' which can not be resolved 
as commit?
  ~/toaster_1_6/poky

> Toaster will only record builds that happen after you started it, i.e. after 
> launching "source toaster start".

Hmm. With my unregistered project, if I do a clean (on at least one package) 
and a rebuild, will I get the whole project, only the parts that updated, or do 
I have to create and build the entire project from scratch?

- David

From: Damian, Alexandru [mailto:[email protected]]
Sent: Thursday, December 19, 2013 3:55 AM
To: Reyna, David; [email protected]
Cc: Barros Pena, Belen; Zhang, Jessica; Ravi Chintakunta; Bansal, Atul; 
Eggleton, Paul; Voicu, Cristiana
Subject: Re: Toaster meeting notes (Dec 18th)

Hi David,

I got some comments below, I hope I got your questions right.

Cheers,
Alex

On Thu, Dec 19, 2013 at 9:28 AM, Reyna, David 
<[email protected]<mailto:[email protected]>> wrote:
________________________________

Hi Alex,

You had us originally pull against master, but your notes indicate that your 
updates are it not in master yet. How would we pull this intermediate content 
into our cloned installations? Do we indicate a specific branch? I am new to 
your process so I am trying not to guess :=) I very much want to replicate what 
you demonstrated before the break so that I can continue working on it, because 
we have of course little time after we return to make the M2 dates.

In your poky directory do:

# git remote add contrib http://git.yoctoproject.org/git/poky-contrib
# git checkout contrib/toaster/master -b toaster-master

This will get your local toaster-master branch in sync with the current updates 
that are not in the master.
To start working on a new feature do:

# git checkout toaster-master -b new_feature_01012014

Commit all changes to this branch, and push it to contrib:

# git push contrib new_feature_01012014:dreyna/new_feature_01012014

And let us know that you pushed on the 
[email protected]<mailto:[email protected]> mailing list (CCed in 
this email).




Also, when you generally do a pull of the latest Toaster code, do you find that 
you need to rebuild your projects also? In other words, is there a way to just 
update the Toaster code with affecting the rest of the Poky installation, such 
that projects can be persistent?


You can switch at any time between different branches of what you have on your 
disk. Toaster is designed to not retrigger or interfere with what's already 
built, i.e. will not affect the signatures or recipes or trigger rebuilds.


I noticed that even though I had a built project, nothing came up in the 
toaster web view. I assume that this is because we had pulled the older code. 
Just in case, could you point me to were in the code the database picks up the 
available projects, in case I need to debug this while you are away on vacation?


Toaster will only record builds that happen after you started it, i.e. after 
launching "source toaster start". Any build ran without Toaster running will 
not be recorded. Toaster doesn't search and integrate for projects built prior 
to having it running.


Thanks!
David


Hope this helps :)

Alex

From: Damian, Alexandru 
[mailto:[email protected]<mailto:[email protected]>]
Sent: Wednesday, December 18, 2013 3:11 PM
To: Barros Pena, Belen
Cc: Reyna, David; Zhang, Jessica; Ravi Chintakunta; Bansal, Atul; Eggleton, 
Paul; Voicu, Cristiana
Subject: Re: Toaster meeting notes (Dec 18th)

Hi,

I have pushed a new version of poky-contrib/toaster-master with:
- the UI now lives in toastergui/ application, instead of advui/
- the complete filters set-up for Builds landing page are now working,
- new comments.

This version will suffer a revision in the next couple of days to prepare it 
for integration into origin/master,
but any work on top of it should be easily rebase-able after the revision.

Cheers,
Alex

On Wed, Dec 18, 2013 at 7:27 PM, Barros Pena, Belen 
<[email protected]<mailto:[email protected]>> wrote:
Just a few notes from the meeting. If I have forgotten anything, please let em 
know.

About the development and patch submission process

* Alex will send around (through the Toaster mailing list) an stable base of 
toaster/master that can be used for development  (Paul would like to see 
development on top of master as soon as it is possible / manageable)
* This base can then be forked for individual development work
* Individual development branches can be pushed to the poky-contrib repository 
(http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/), where they are 
public and can be seeing by the whole team
* For the moment, we can use the Toaster mailing list to request review / 
comments of work in progress
* Work in progress will then be merged to toaster/master, and a single pull 
request is sent out to the bitbake-devel mailing list to be merged to 
origin/master
* Please remember to cc the Toaster mailing list on any emails we exchange

What everybody needs:

* Push access to poky-contrib (please contact Michael Halstead at 
[email protected]<mailto:[email protected]>)
* Open an account in the Yocto Project Bugzilla instance 
(https://bugzilla.yoctoproject.org/createaccount.cgi)

Suggested front-end development tools: 2 Firefox extensions

* Firebug (https://getfirebug.com/)
* HtmlValidator (http://users.skynet.be/mgueury/mozilla/)

Bugzilla features:

These are the 3 features we identified as good next steps.

https://bugzilla.yoctoproject.org/show_bug.cgi?id=4283
https://bugzilla.yoctoproject.org/show_bug.cgi?id=4328
https://bugzilla.yoctoproject.org/show_bug.cgi?id=4299

I will set the status of all front-end Bugzilla features to "accepted". Once 
you have identified a feature you would like to work on, you can change the 
assignee to yourselves and change the status to "In progress implementation". 
If you have any questions about a feature, reach to Alex and Belén (via IRC or 
the Toaster mailing list).

Our next meeting should be on January 8th.

Have a great break!

Belén


From: 
[email protected]<mailto:[email protected]><mailto:[email protected]<mailto:[email protected]>>
When: 17:00 - 18:00 18 December 2013
Subject: WebEx: toaster meeting
Location: 1-800-730-2996x7494529#


WebEx for the Toaster meeting.




DAVID REYNA invites you to an online meeting using WebEx.

Meeting Number: 591 835 399
Meeting Password: This meeting does not require a password.

-------------------------------------------------------
To join this meeting (Now from mobile devices!)
-------------------------------------------------------
1. Go to https://windriver.webex.com/windriver/j.php?J=591835399
2. If requested, enter your name and email address.
3. If a password is required, enter the meeting password: This meeting does not 
require a password.
4. Click "Join".
5. Follow the instructions that appear on your screen.



-------------------------------------------------------
Teleconference information
-------------------------------------------------------
Provide your phone number when you join the meeting to receive a call back. 
Alternatively, you can call:
Conference dial-in number: 1-8007302996  (US)
Access Code: 749 452 9

http://www.webex.com



IMPORTANT NOTICE: This WebEx service includes a feature that allows audio and 
any documents and other materials exchanged or viewed during the session to be 
recorded. By joining this session, you automatically consent to such 
recordings. If you do not consent to the recording, discuss your concerns with 
the meeting host prior to the start of the recording or do not join the 
session. Please note that any such recordings may be subject to discovery in 
the event of litigation.



--
Alex Damian
Yocto Project
SSG / OTC



--
Alex Damian
Yocto Project
SSG / OTC
_______________________________________________
toaster mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/toaster

Reply via email to