Re: [tei-council] Are we jumping to GitHub or are we not?

Can’t disagree with that. From a little googling though, it sounds like the email-ext and Git plugins support working with committer emails in Git. So there may not be much work involved.

On Sep 4, 2015, at 12:50 , Martin Holmes wrote:

It's part of the core functionality of the build job that it knows the committer; and it can construct an email address by using that committer's id and appending a domain to it. Anything more than that would get very complicated, I think.

I really don't want to start writing or modifying custom Jenkins plugins at this point. I think it's sufficient for the Council list to be notified, and that may require that Kevin add a couple of senders to the list (I see that the Oxford Jinks sends from tei@it.ox.ac.uk, while mine sends from me, mholmes@uvic.ca). If we're going to get clever with all this, and find ways for Jenkins to look up appropriate email addresses through a plugin, I think that's a job for later, when everything else is working, and we're all comfortable on GitHub.

I could be missing something in the Jenkins configuration that enables this sort of thing, but I don't see it.

Cheers, Martin

On 15-09-04 09:24 AM, Hugh Cayless wrote:

...

How does Jinks get the email? Would it not be possible just to read it out of the repo HEAD?

...

On Sep 4, 2015, at 11:58 , Martin Holmes wrote:

Hi all,

My Jinks is able to build the TEI products from GitHub, thanks to some help from Hugh, and James's will also be switched today as a secondary test. The only wrinkle is that Jinks will not be able to notify committers when a build fails, because GitHub doesn't have a transparent way of automatically associating committer ids with email addresses, but we can handle this by having it notify the Council mailing list instead. I've set that up, and I think it might just work out of the box but if not Kevin will be able to allow it.

We now want to start revising those "Editing the Guidelines" and similar documents to point to GitHub, and consider what we're going to do about tickets.

Is there anyone at this point who objects to moving the repo to GitHub?

If not, then I suggest we start updating documentation.

Tickets can stay on SF until we have a comfortable migration path for them.

Cheers, Martin -- tei-council mailing list tei-council@lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council

PLEASE NOTE: postings to this list are publicly archived

-- tei-council mailing list tei-council@lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council

PLEASE NOTE: postings to this list are publicly archived