From: "R. Tyler Croy" <tyler@monkeypox.org>
To: git@vger.kernel.org
Subject: Interactive session on Jenkins and Git (May 18th 18:00 UTC)
Date: Tue, 17 May 2011 14:44:48 -0700 [thread overview]
Message-ID: <20110517214448.GB5856@kiwi.flexilis.local> (raw)
[-- Attachment #1: Type: text/plain, Size: 746 bytes --]
I apologize if this seems spammy, I've been on this list for ages, I promise!
:)
Anywho, I'm hosting a session (WebEx :/) tomorrow going over setting up Jenkins
(http://jenkins-ci.org) with Git and offering some live support in doing so.
I'm planning on covering some basic Git polling use-cases as well as
post-receive hooks, things like that, and if there's interest I'll go into the
juicy Gerrit Trigger plugin integration bits :)
I wanted to drop a link and see if perhaps there was interest in the Git
community: <http://jenkins-ci.org/event/user-session-week-20>
Cheers
- R. Tyler Croy
--------------------------------------
Code: http://github.com/rtyler
Chatter: http://identi.ca/agentdero
http://twitter.com/agentdero
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
reply other threads:[~2011-05-17 21:44 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110517214448.GB5856@kiwi.flexilis.local \
--to=tyler@monkeypox.org \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).