smoke-me branches, github, travis - wanting it all...

As Jim correctly observed, this should be its own message:

The "migration to github" was described as being about bugs from RT to
Github, with the potential of effectively swapping "master" and "mirror"
between https://perl5.git.perl.org/perl.git and GitHub

To my knowledge there's been nothing mentioned about how everything else is
supposed to work. Historically we'd been using smoke-me branches to get
automated testing. github "thinks" otherwise about how to describe something
that would like testing, but the existing smokers don't know that.

Likewise, historically all the requests I made in the other message here
went to the list. In the brave new future, er, present, what *is* the plan
for what goes where? We're now onto our third bug tracker, third hosting of
version control, and not-sure-what iteration of mail archives.

I feel that Github itself is in safer hands owned by Microsoft than in its
previous state (gratuitously cashflow negative), but I'm wary of assuming
that anything is going to be around forever, or is defaulting to what we
really need.


So how are things supposed to be done?

specifically - exploiting both any existing smoke-me smokers, but also
github and Travis (and anything else that is "free")

and more generally - getting the most out of github, without getting
railroaded by defaults and features that don't fit what we need

Nicholas Clark
0
nick
11/6/2019 2:18:25 PM
perl.perl5.porters 47863 articles. 1 followers. Follow

4 Replies
12 Views

Similar Articles

[PageSpeed] 22

On Wed, Nov 6, 2019 at 8:18 AM Nicholas Clark <nick@ccl4.org> wrote:
> So how are things supposed to be done?

> and more generally - getting the most out of github, without getting
> railroaded by defaults and features that don't fit what we need

My current pet peeve is that there is no replacement for the  "git
blame" interface of standard gitweb.  Try to do any blame view in
GitHub on any file more than a few hundred lines long and you'll get a
great big angry unicorn icon and a message that says, "This page is
taking way too long to load. Sorry about that. Please try refreshing
and contact us if the problem persists."  I don't know what metrics
they are using exactly, but whether it's number of lines in the file
or number of commits on the file, it gives up way too easily and hangs
up on you in a fraction of a second.  There seems to have been an
explicit decision made that making a version control system show
versions is too expensive and one shouldn't ask for it.

I know we had no choice, really, and that BitBucket or GitLab or
SourceForge or whatever would have had various different and possibly
worse problems. But not being able to do archive diving for a
long-running project with large source files is a major defect in
GitHub, and is something that standard gitweb does quite handily out
of the box.  I spent an hour a week or two ago trying to teach myself
how to do git blame with line ranges from the command line and it
didn't go well.  Is there any chance we could get
https://perl5.git.perl.org/perl.git to be a reasonably up-to-date
mirror?  If so, then all of the things GitHub doesn't do would be less
of a problem.
0
craig
11/8/2019 4:44:21 AM
On Wed, 6 Nov 2019, Nicholas Clark wrote:

> As Jim correctly observed, this should be its own message:
>
> The "migration to github" was described as being about bugs from RT to
> Github, with the potential of effectively swapping "master" and "mirror"
> between https://perl5.git.perl.org/perl.git and GitHub
>
> To my knowledge there's been nothing mentioned about how everything else is
> supposed to work. Historically we'd been using smoke-me branches to get
> automated testing. github "thinks" otherwise about how to describe something
> that would like testing, but the existing smokers don't know that.

Someone that is part of the Perl organization could set up repository web 
hooks to send events (like new branch) to a CI server (like Travis or 
Jenkins) and automatically kick off smokes on their machines that would be 
reported on the PRs are checks passing or failing. We run that setup with 
Jenkins at $WORK.

> Likewise, historically all the requests I made in the other message here
> went to the list. In the brave new future, er, present, what *is* the plan
> for what goes where? We're now onto our third bug tracker, third hosting of
> version control, and not-sure-what iteration of mail archives.

Carlos Guevara (it appears) and I have machines that smoke every 
"smoke-me" branch that appears, so no requesting necessary.

To get the reports, check the smoking reports mailing list or visit a page 
like: 
http://perl.develop-help.com/?b=smoke-me%2Fnicholas%2FIO-Handle-getline_XS

There's also http://perl5.test-smoke.org/search but it inexplicably 
doesn't allow searching by branch.

I stopped Cc:'ing people directly on smoke reports a while back due to 
controversy over whether that was worthwhile.

> So how are things supposed to be done?
>
> specifically - exploiting both any existing smoke-me smokers, but also
> github and Travis (and anything else that is "free")
>
> and more generally - getting the most out of github, without getting
> railroaded by defaults and features that don't fit what we need

The one nice thing that GitHub integration could give is I could set up a 
Jenkins server that OAuths to GitHub and lets anyone in the Perl 
organization kick off immediate builds with arbitrary configurations 
they've selected, instead of only asynchronous builds using the profiles 
I've chosen to run smokers under.

-- 
George Greer
0
perl
11/10/2019 6:23:40 AM
On Thu, Nov 07, 2019 at 10:44:21PM -0600, Craig A. Berry wrote:
> didn't go well.  Is there any chance we could get
> https://perl5.git.perl.org/perl.git to be a reasonably up-to-date
> mirror?  If so, then all of the things GitHub doesn't do would be less
> of a problem.

I have a mirror visible via gitweb at:

http://git.imager.perl.org/perl5.git

mirrored every 20 minutes.

I'm moving this to a new linode, so URLs might change.

I've been experimenting with other gitweb-ish UIs, but they've tended
to be much slower than gitweb.

Tony
0
tony
11/11/2019 2:42:22 AM
On Sun, Nov 10, 2019 at 8:42 PM Tony Cook <tony@develop-help.com> wrote:
>
> On Thu, Nov 07, 2019 at 10:44:21PM -0600, Craig A. Berry wrote:
> > didn't go well.  Is there any chance we could get
> > https://perl5.git.perl.org/perl.git to be a reasonably up-to-date
> > mirror?  If so, then all of the things GitHub doesn't do would be less
> > of a problem.
>
> I have a mirror visible via gitweb at:
>
> http://git.imager.perl.org/perl5.git
>
> mirrored every 20 minutes.

Thank you!  This has been very, very helpful.

> I'm moving this to a new linode, so URLs might change.

Keep us posted.
0
craig
11/17/2019 8:12:11 PM
Reply: