Re: [rap-dev] branching... master and 2.3-maintenance

[Ralf Sternberg <rsternberg@xxxxxxxxxxxxxxxxx>]

> This bug is about the login problems you've been running into:
>
> Bug 436264 - Cannot log in to Hudson
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=436264

Yes, that was probably the issue, thanks. After trying all possible
combinations I found myself being logged in after refreshing the
page...

> I fixed the other build problems by disabling the Git plug-in and using a
> small shell-script with command line Git. Hey, I'm still a fan of good old
> command line tools that work instead of sometimes working, sometimes
> not-working sophisticated integrations... :(

Absolutely! The shell integration is probably the most useful feature
in Hudson. However, I wouldn't call the git integration sophisticated
;-) Shame that such a basic thing like fetching from a branch still
doesn't work.

Cheers,
Ralf


> On Mon, Jun 2, 2014 at 5:12 PM, Markus Knauer <mknauer@xxxxxxxxxxxxxxxxx>
> wrote:
>>
>> I think we are running into our old
>>
>> Fetching upstream changes from
>> git://git.eclipse.org/gitroot/rap/org.eclipse.rap.git
>> Nothing to do
>>
>> problem with Hudson that isn't able to detect changes on anything else
>> than master.
>> I will fix this now.
>>
>> Thanks,
>> Markus
>>
>>
>>
>>
>> On Mon, Jun 2, 2014 at 3:33 PM, Ralf Sternberg
>> <rsternberg@xxxxxxxxxxxxxxxxx> wrote:
>>>
>>> Thanks Markus.
>>>
>>> Now that all changes for 2.3 have been merged, I've created the 2.3
>>> maintenance branches in rap and rap.tools.
>>>
>>> Unfortunately, I'm unable to login to the build server to test-start a
>>> 2.3 build at the moment (working on this)...
>>>
>>> Cheers,
>>> Ralf
>>>
>>>
>>> On Fri, May 30, 2014 at 8:49 PM, Markus Knauer
>>> <mknauer@xxxxxxxxxxxxxxxxx> wrote:
>>> > Hi RAP Developers,
>>> >
>>> > I've created the new 2.3 build jobs in our HIPP [1], [2], and usually
>>> > I'd
>>> > just create the new 2.3-maintenance branch now, but... we've got some
>>> > changes in Gerrit that we need to apply to both branches, master *and*
>>> > 2.3-maintenance.
>>> >
>>> > That's why I stopped at this point. I think it makes sense to push the
>>> > changes to master first, and create the 2.3-maintenance branch after
>>> > that.
>>> >
>>> > What do other think?
>>> >
>>> > (Independent from everything else, I'll push my routine updates for RC3
>>> > over
>>> > the weekend.)
>>> >
>>> > [1] https://hudson.eclipse.org/rap/job/rap-2.3-runtime/
>>> > [2] https://hudson.eclipse.org/rap/job/rap-2.3-tools/
>>> >
>>> > Thanks,
>>> > Markus
>>> >
>>> > _______________________________________________
>>> > rap-dev mailing list
>>> > rap-dev@xxxxxxxxxxx
>>> > https://dev.eclipse.org/mailman/listinfo/rap-dev
>>> >
>>> _______________________________________________
>>> rap-dev mailing list
>>> rap-dev@xxxxxxxxxxx
>>> https://dev.eclipse.org/mailman/listinfo/rap-dev
>>
>>
>>
>
>
>
> _______________________________________________
> rap-dev mailing list
> rap-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/rap-dev
>