[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [che-dev] Managing website issues and source code in github?
|
Thanks - at least this confirms for me that my problems are unexpected.
I have been getting this on a clone:
[dneary@localhost.localdomain]$ git clone
ssh://dnearybwk@xxxxxxxxxxxxxxx:29418/www.eclipse.org/che.git che-website
Cloning into 'che-website'...
remote: Counting objects: 830, done
remote: Finding sources: 100% (167/167)
fatal: internal server error6/13454), 2.00 MiB | 28.00 KiB/s
fatal: the remote end hung up unexpectedly
fatal: early EOF
fatal: index-pack failed
I don't know if this is the same issue that the github importer was
having, but at least it confirms that there is an unexpected issue. I've
had this error twice now on the command line.
Thanks,
Dave.
On 20/03/2019 15:49, Nick Boldt wrote:
> Here's what I did:
>
> 1. create a new repo on
> github https://github.com/new -> https://github.com/nickboldt/www.eclipse.org__che
>
> 2. fetch the Eclipse mirror as the origin:
>
> git clone ssh://nickb@xxxxxxxxxxxxxxx:29418/www.eclipse.org/che.git
> <http://nickb@xxxxxxxxxxxxxxx:29418/www.eclipse.org/che.git>
> www.eclipse.org__che
> cd www.eclipse.org__che
>
> 3. Add my new fork as another replica:
>
> git remote add nickboldt git@xxxxxxxxxx:nickboldt/www.eclipse.org__che.git
>
> 4. push content to the mirror:
>
> git push -u nickboldt master
>
> And voila!
>
> There's also a way to run the Eclipse website in a docker container to
> make it easier to set up a dev env for testing pages, but ... I can't
> find where I documented that process. If that's useful to you I can ask
> around from the webmasters and see where the wiki page went.
>
> Nick
>
> On Tue, Mar 19, 2019 at 7:13 PM Dave Neary <dneary@xxxxxxxxxx
> <mailto:dneary@xxxxxxxxxx>> wrote:
>
> Hi,
>
> On 13/03/2019 15:51, Nick Boldt wrote:
> > If you're an eclipse committer, you only need to do this:
> >
> > git clone
> >
> ssh://eclipse-username-goes-here@xxxxxxxxxxxxxxx:29418/www.eclipse.org/che.git
> <http://eclipse-username-goes-here@xxxxxxxxxxxxxxx:29418/www.eclipse.org/che.git>
>
> >
> <http://eclipse-username-goes-here@xxxxxxxxxxxxxxx:29418/www.eclipse.org/che.git>
> >
> > then make your edits and submit a gerrit request for the change.
> >
> > git commit -s -m "there, I fixed it" badfile.txt
> > git push origin HEAD:refs/for/master
> >
> > Your gerrit will then appear here:
> >
> > https://git.eclipse.org/r/#/q/project:www.eclipse.org/che
> >
> > Why do you need to import to github?
>
> "Need" is strong. I want to use github issues and PRs to enable broader
> participaton in the website maintenance. Right now, we have about 10-15
> pages in the website, several of which need updates, and I would
> like to
> use community-visible and accessible infrastructure to manage the
> updates. In addition, I have enlisted the help of a colleague, and
> would
> like to point him at a public resource rather than using a private
> resource to manage our collaboration.
>
> > If you want a copy of the repo, Eclipse Foundation can provide a
> synched
> > one automatically into github, should you request one.
> >
> > Otherwise if you want it in your own fork, create an empty repo and
> > simply push to that repo from the www.eclipse.org/che
> <http://www.eclipse.org/che>
> > <http://www.eclipse.org/che> one.
>
> I have tried to clone the repo to a privcate repo as a POC to know that
> I can do this, but it has failed every time I have tried it for some
> reason.
>
> Thanks,
> Dave.
>
> > Here's an example of a private fork of a git.eclipse.org
> <http://git.eclipse.org>
> > <http://git.eclipse.org> repo:
> >
> > https://github.com/nickboldt/org.eclipse.tm
> >
> > ... so it works. But again, do you need it?
> >
> >
> > On Wed, Mar 13, 2019 at 1:45 PM Dave Neary <dneary@xxxxxxxxxx
> <mailto:dneary@xxxxxxxxxx>
> > <mailto:dneary@xxxxxxxxxx <mailto:dneary@xxxxxxxxxx>>> wrote:
> >
> > Thanks Nick, Florent!
> >
> > I don't know what the issue is, but when I tried to import the Che
> > website repo into github today (under my own namespace), the
> import
> > failed ("something went wrong", a massively useful error message).
> >
> > Have either of you succeeded in importing a repo into github from
> > Eclipse Git? Can it be done anonymously with the https://
> clone URI, or
> > do you need to use git:// or ssh:// to be able to push back there?
> >
> > Thanks,
> > Dave.
> >
> > On 12/03/2019 09:40, Nick Boldt wrote:
> > > As it happens I maintain several PR build jobs configured
> on various
> > > Eclipse jenkins instances (for Webtools, Datatools, and
> TM/RSE)
> > so I'm
> > > happy to contribute advice or sample config.xml scripts to
> > demonstrate
> > > how to set this up, if it's decided that you want to use
> Eclipse
> > > jenkins + Eclipse gerrit + Eclipse bugzilla to manage the
> > > workflow/builds/contributions.
> > >
> > > The only missing piece (if not already in place) is to request
> > from the
> > > Eclipse webmaster (via a BZ) that the git.eclipse.org
> <http://git.eclipse.org>
> > <http://git.eclipse.org>
> > > <http://git.eclipse.org> instance be mirrored to github, should
> > you want
> > > that additional way to see the sources.
> > >
> > > Nick
> > >
> > >
> > > On Tue, Mar 12, 2019 at 2:52 AM Florent Benoit
> > <florent@xxxxxxxxxx <mailto:florent@xxxxxxxxxx>
> <mailto:florent@xxxxxxxxxx <mailto:florent@xxxxxxxxxx>>
> > > <mailto:florent@xxxxxxxxxx <mailto:florent@xxxxxxxxxx>
> <mailto:florent@xxxxxxxxxx <mailto:florent@xxxxxxxxxx>>>> wrote:
> > >
> > > Hello, jenkins instances on eclipse infra allow to do PR
> > builds and
> > > push commits to git.eclipse.org
> <http://git.eclipse.org> <http://git.eclipse.org>
> > <http://git.eclipse.org> as well so
> > > there is no issue performing all the stuff on a pure github
> > project.
> > >
> > > On Mon, Mar 11, 2019 at 4:20 PM Nick Boldt
> <nboldt@xxxxxxxxxx <mailto:nboldt@xxxxxxxxxx>
> > <mailto:nboldt@xxxxxxxxxx <mailto:nboldt@xxxxxxxxxx>>
> > > <mailto:nboldt@xxxxxxxxxx <mailto:nboldt@xxxxxxxxxx>
> <mailto:nboldt@xxxxxxxxxx <mailto:nboldt@xxxxxxxxxx>>>> wrote:
> > >
> > > Not that I'm a fan of Bugzilla, but if you use BZ
> for website
> > > change issues, it's automatically integrated into
> the gerrit
> > > workflow so that gerrits/PRs for the website can
> link to
> > the BZ
> > > if the commit message includes the string "Bug xxxx" or
> > > "[xxxxx]" at the start of the message.
> > >
> > > And of course by using git.eclipse.org
> <http://git.eclipse.org>
> > <http://git.eclipse.org> <http://git.eclipse.org>
> > > directly, you'll get the ability to trigger gerrit
> builds
> > of PRs
> > > before they're pushed to the website.
> > >
> > > So... perhaps not ideal, but path of least resistance?
> > >
> > > FAILING THAT, there's also the option of doing PR
> builds w/
> > > Travis as integrated in GH... but you'd still then
> have to
> > > figure out how to push github commits to
> git.eclipse.org <http://git.eclipse.org>
> > <http://git.eclipse.org>
> > > <http://git.eclipse.org>.
> > >
> > > Nick
> > >
> > > On Fri, Mar 8, 2019 at 9:34 AM Dave Neary
> > <dneary@xxxxxxxxxx <mailto:dneary@xxxxxxxxxx>
> <mailto:dneary@xxxxxxxxxx <mailto:dneary@xxxxxxxxxx>>
> > > <mailto:dneary@xxxxxxxxxx
> <mailto:dneary@xxxxxxxxxx> <mailto:dneary@xxxxxxxxxx
> <mailto:dneary@xxxxxxxxxx>>>> wrote:
> > >
> > > Hi all,
> > >
> > > I would like to use github to track website
> updates and
> > > issues, but
> > > having asked the Eclipse Foundation whether it's
> > possible,
> > > the issue is
> > > kicking off a website deploy after new PR
> merges - there
> > > would need to
> > > be a manual step to pull changes from github
> into the
> > > git.eclipse.org <http://git.eclipse.org>
> <http://git.eclipse.org> <http://git.eclipse.org>
> > > repo and kick off a website deploy, it won't happen
> > > automatically.
> > >
> > > The main issue I have is, I would like to be
> able to
> > track
> > > individual
> > > changes we need to make to update the content,
> and group
> > > changes into
> > > epics related to Che 7 website changes to allow
> > > collaboration and
> > > tracking of progress.
> > >
> > > Does anyone have a good suggestion for handling
> this?
> > I have
> > > thought of
> > > using github for issue tracking, but not for
> PRs, and
> > manage
> > > commits to
> > > https://git.eclipse.org/c/www.eclipse.org/che.git
> > > separately. Anyone
> > > have a better idea?
> > >
> > > Thanks,
> > > Dave.
> > >
> > > --
> > > Dave Neary - Eclipse Che Ecosystem & Community
> Manager
> > > Open Source and Standards - Red Hat
> > > E: dneary@xxxxxxxxxx <mailto:dneary@xxxxxxxxxx>
> <mailto:dneary@xxxxxxxxxx <mailto:dneary@xxxxxxxxxx>>
> > <mailto:dneary@xxxxxxxxxx <mailto:dneary@xxxxxxxxxx>
> <mailto:dneary@xxxxxxxxxx <mailto:dneary@xxxxxxxxxx>>> / T: @nearyd
> > > / Ph: +1-978-799-3338
> > > _______________________________________________
> > > che-dev mailing list
> > > che-dev@xxxxxxxxxxx <mailto:che-dev@xxxxxxxxxxx>
> <mailto:che-dev@xxxxxxxxxxx <mailto:che-dev@xxxxxxxxxxx>>
> > <mailto:che-dev@xxxxxxxxxxx <mailto:che-dev@xxxxxxxxxxx>
> <mailto:che-dev@xxxxxxxxxxx <mailto:che-dev@xxxxxxxxxxx>>>
> > > To change your delivery options, retrieve your
> > password, or
> > > unsubscribe from this list, visit
> > > https://www.eclipse.org/mailman/listinfo/che-dev
> > >
> > >
> > >
> > > --
> > >
> > > Nick Boldt
> > >
> > > Principal Software Engineer, RHCSA
> > >
> > > Productization Lead :: JBoss Tools & Dev Studio
> > >
> > > IM: @nickboldt / @nboldt / http://nick.divbyzero.com
> > >
> > > <https://red.ht/sig>
> > > TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
> > >
> > > @ @redhatnews <https://twitter.com/redhatnews>
> Red Hat
> > > <https://www.facebook.com/RedHatInc>
> > > <https://www.facebook.com/RedHatInc>
> > >
> > >
> > > “The Only Thing That Is Constant Is Change” -
> Heraclitus
> > > _______________________________________________
> > > che-dev mailing list
> > > che-dev@xxxxxxxxxxx <mailto:che-dev@xxxxxxxxxxx>
> <mailto:che-dev@xxxxxxxxxxx <mailto:che-dev@xxxxxxxxxxx>>
> > <mailto:che-dev@xxxxxxxxxxx <mailto:che-dev@xxxxxxxxxxx>
> <mailto:che-dev@xxxxxxxxxxx <mailto:che-dev@xxxxxxxxxxx>>>
> > > To change your delivery options, retrieve your
> password, or
> > > unsubscribe from this list, visit
> > > https://www.eclipse.org/mailman/listinfo/che-dev
> > >
> > > _______________________________________________
> > > che-dev mailing list
> > > che-dev@xxxxxxxxxxx <mailto:che-dev@xxxxxxxxxxx>
> <mailto:che-dev@xxxxxxxxxxx <mailto:che-dev@xxxxxxxxxxx>>
> > <mailto:che-dev@xxxxxxxxxxx <mailto:che-dev@xxxxxxxxxxx>
> <mailto:che-dev@xxxxxxxxxxx <mailto:che-dev@xxxxxxxxxxx>>>
> > > To change your delivery options, retrieve your password, or
> > > unsubscribe from this list, visit
> > > https://www.eclipse.org/mailman/listinfo/che-dev
> > >
> > >
> > >
> > > --
> > >
> > > Nick Boldt
> > >
> > > Principal Software Engineer, RHCSA
> > >
> > > Productization Lead :: JBoss Tools & Dev Studio
> > >
> > > IM: @nickboldt / @nboldt / http://nick.divbyzero.com
> > >
> > > <https://red.ht/sig>
> > > TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
> > >
> > > @ @redhatnews <https://twitter.com/redhatnews> Red Hat
> > > <https://www.facebook.com/RedHatInc>
> > > <https://www.facebook.com/RedHatInc>
> > >
> > >
> > > “The Only Thing That Is Constant Is Change” - Heraclitus
> > >
> > > _______________________________________________
> > > che-dev mailing list
> > > che-dev@xxxxxxxxxxx <mailto:che-dev@xxxxxxxxxxx>
> <mailto:che-dev@xxxxxxxxxxx <mailto:che-dev@xxxxxxxxxxx>>
> > > To change your delivery options, retrieve your password, or
> > unsubscribe from this list, visit
> > > https://www.eclipse.org/mailman/listinfo/che-dev
> > >
> >
> > --
> > Dave Neary - Eclipse Che Ecosystem & Community Manager
> > Open Source and Standards - Red Hat
> > E: dneary@xxxxxxxxxx <mailto:dneary@xxxxxxxxxx>
> <mailto:dneary@xxxxxxxxxx <mailto:dneary@xxxxxxxxxx>> / T: @nearyd / Ph:
> > +1-978-799-3338
> > _______________________________________________
> > che-dev mailing list
> > che-dev@xxxxxxxxxxx <mailto:che-dev@xxxxxxxxxxx>
> <mailto:che-dev@xxxxxxxxxxx <mailto:che-dev@xxxxxxxxxxx>>
> > To change your delivery options, retrieve your password, or
> > unsubscribe from this list, visit
> > https://www.eclipse.org/mailman/listinfo/che-dev
> >
> >
> >
> > --
> >
> > Nick Boldt
> >
> > Principal Software Engineer, RHCSA
> >
> > Productization Lead :: JBoss Tools & Dev Studio
> >
> > IM: @nickboldt / @nboldt / http://nick.divbyzero.com
> >
> > <https://red.ht/sig>
> > TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
> >
> > @ @redhatnews <https://twitter.com/redhatnews> Red Hat
> > <https://www.facebook.com/RedHatInc>
> > <https://www.facebook.com/RedHatInc>
> >
> >
> > “The Only Thing That Is Constant Is Change” - Heraclitus
> >
> > _______________________________________________
> > che-dev mailing list
> > che-dev@xxxxxxxxxxx <mailto:che-dev@xxxxxxxxxxx>
> > To change your delivery options, retrieve your password, or
> unsubscribe from this list, visit
> > https://www.eclipse.org/mailman/listinfo/che-dev
> >
>
> --
> Dave Neary - Eclipse Che Ecosystem & Community Manager
> Open Source and Standards - Red Hat
> E: dneary@xxxxxxxxxx <mailto:dneary@xxxxxxxxxx> / T: @nearyd / Ph:
> +1-978-799-3338
>
>
>
> --
>
> Nick Boldt
>
> Principal Software Engineer, RHCSA
>
> Productization Lead :: JBoss Tools & Dev Studio
>
> IM: @nickboldt / @nboldt / http://nick.divbyzero.com
>
> <https://red.ht/sig>
> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
>
> @ @redhatnews <https://twitter.com/redhatnews> Red Hat
> <https://www.facebook.com/RedHatInc>
> <https://www.facebook.com/RedHatInc>
>
>
> “The Only Thing That Is Constant Is Change” - Heraclitus
--
Dave Neary - Eclipse Che Ecosystem & Community Manager
Open Source and Standards - Red Hat
E: dneary@xxxxxxxxxx / T: @nearyd / Ph: +1-978-799-3338
