Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [mylyn-reviews-dev] Mylyn Reviews and Builds in Indigo?

I just put that in as a place holder. 15 minutes are a very short time
to show a meaningful demo of the Git/Gerrit/Hudson but having an
additional EGit demo is even better. I have updated the wiki page.
Order wise it would probably make sense to show EGit first since the
other stuff builds on it.

Steffen


On Wed, May 4, 2011 at 11:57 PM, Matthias Sohn
<matthias.sohn@xxxxxxxxxxxxxx> wrote:
> 2011/5/3 Steffen Pingel <steffen.pingel@xxxxxxxxxxx>
>>
>> Hi Sascha,
>>
>> that sounds good. I can share the slides from Benjamin's and my
>> EclipseCon talk and we also have a VM with a demo setup and workspace
>> etc. that I may be able to send to you. I have put down my name on the
>> Wiki page and will contact you to figure out the details how to split
>> up the presentation.
>
> Currently you have registered another talk "Task-focused continuous
> integration with Mylyn"
> Is that meant to be part of your joined talk with Sascha or is this
> something different ?
> We would also like to give another session to demonstrate the new EGit
> features since
> Helios and egit-github but we don't want to overload the democamp with too
> many demo sessions.
> --
> Matthias
>
>>
>> On Tue, May 3, 2011 at 10:55 AM, Sascha Scholz <sascha.scholz@xxxxxxxxx>
>> wrote:
>> > Hi Steffen,
>> >
>> > On Sun, May 1, 2011 at 11:36 PM, Steffen Pingel
>> > <steffen.pingel@xxxxxxxxxxx> wrote:
>> >> I am thinking about going to the DemoCamp as well. Would you be up for
>> >> splitting the presentation into a Git/Gerrit part and a Jenkins part
>> >> (I would like do the latter)?
>> >
>> > Sure, really good idea. Here's the script for the demo I have in mind so
>> > far:
>> >
>> > * Prerequisites:
>> > ** Git Repository is cloned and set up (push configuration "review")
>> > ** Helloworld Maven project is imported (includes a test for sayHello()
>> > method)
>> > ** Query for task repository is created
>> > ** Build job for Helloworld project is set up and Jenkins is added as
>> > build server
>> > ** Gerrit connector query (open changes for project) is created
>> > ** Automatic synchronization for tasks, builds and reviews is disabled
>> > * Developer 1
>> > ** Start working on a task: Improve Greeting (change "Hello World" to
>> > "Hello Eclipse")
>> > * Commit and push to Gerrit (have commit message populated by EGit
>> > Mylyn integration)
>> > * Have a quick look at change in Gerrit UI, then in Mylyn integration
>> > and add Developer 2 as reviewer (+ show what can else could be done in
>> > task editor)
>> > * Developer 1 goes to vacation...
>> > * Developer 2
>> > ** On the next day Developer 2 sees the Gerrit review request in task
>> > list
>> > ** Open change and review code (vote +2)
>> > ** Try to submit, but that fails because Jenkins Voter has voted -1 in
>> > verified category (build failed)
>> > ** Open build log by clicking link in review comment (would be cool if
>> > that could open it directly in Mylyn Builds editor. Is this somehow
>> > possible?)
>> > ** Discover that build failed due to test failure (tests still
>> > expected "Hello World")
>> > ** Fetch change from Gerrit
>> > ** Register for build plan and show console, then check test results
>> > in Hudson view, then re-run test from junit view
>> > * Fix test and upload new patchset
>> > * See that Hudson build is green
>> > * Vote +2 in code review category, then submit
>> > * Optional: Register to CI build plan and Trigger CI build to deploy
>> > artifact
>> > * Resolve task (how can it be associated with a specific Gerrit change
>> > and CI build? Only manually?)
>> >
>> > Developer 2 in this script shows Jenkins integration, so that could be
>> > your part if you like. What do you think, any suggestions?
>> >
>> > Additionally, I think it would be good to provide some background
>> > information about Git, Gerrit, Jenkins Mylyn in the beginning and
>> > provide pointers to the update sites, Mylyn bugzilla, mailing list
>> > etc. at the end. But as it's only 15 minutes (at least for Walldorf)
>> > this has to be kept very short. Do you already have some slides which
>> > could be used?
>> >
>> > So far I proposed talks for Walldorf [1] and Darmstadt [2] (it the
>> > title OK for you or do you have a better idea?). Maybe I'm going to do
>> > a proposal for Bonn as well, but I'm not sure about this yet. What are
>> > your plans?
>> >
>> > Regards,
>> > Sascha
>> >
>> > [1] http://wiki.eclipse.org/Eclipse_DemoCamps_Indigo_2011/Walldorf
>> > [2] http://wiki.eclipse.org/Eclipse_DemoCamps_Indigo_2011/Darmstadt
>> > [3] http://wiki.eclipse.org/Eclipse_DemoCamps_Indigo_2011/Bonn
>> > _______________________________________________
>> > mylyn-reviews-dev mailing list
>> > mylyn-reviews-dev@xxxxxxxxxxx
>> > https://dev.eclipse.org/mailman/listinfo/mylyn-reviews-dev
>> >
>>
>>
>>
>> --
>> Steffen Pingel
>> Committer, http://eclipse.org/mylyn
>> Senior Developer, http://tasktop.com
>> _______________________________________________
>> mylyn-reviews-dev mailing list
>> mylyn-reviews-dev@xxxxxxxxxxx
>> https://dev.eclipse.org/mailman/listinfo/mylyn-reviews-dev
>
>
>
> _______________________________________________
> mylyn-reviews-dev mailing list
> mylyn-reviews-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/mylyn-reviews-dev
>
>



-- 
Steffen Pingel
Committer, http://eclipse.org/mylyn
Senior Developer, http://tasktop.com


Back to the top