[sakai-core-team] Automatically creating git tags

[Earle Nietzel]

So typically you run jenkins as the jenkins user you set the keys up in
that users ssh keys.

On Thu, Feb 26, 2015 at 4:26 PM, Matthew Jones <matthew at longsight.com>
wrote:

> Yeah I saw that page but where do you put that into Jenkins for the Github
> plugin (https://wiki.jenkins-ci.org/display/JENKINS/Git+Plugin) to be
> able to publish?
>
> I see this guide (with a bunch of steps) but it *seems* like that only
> sets it up so it can checkout from a private repository (
> http://blogs.perficient.com/multi-shoring/blog/2014/03/26/using-git-deploy-key-in-jenkins-written-by-tom-tang/
> )
>
> I feel like I'd rather spend a half an hour just setting up a new generic
> user in the place it gives me in the UI than half a day on some solution
> that may or may not work? Unless there's some guide or Stack Overflow that
> says exactly how to do it with Jenkins, Github and Git Publisher?
>
> On Thu, Feb 26, 2015 at 4:12 PM, Earle Nietzel <enietzel at anisakai.com>
> wrote:
>
>> There is a feature in github called Deploy Keys this is how we manage
>> processes that need to access to the github repo.
>>
>> see https://developer.github.com/guides/managing-deploy-keys/
>>
>>
>>
>> On Thu, Feb 26, 2015 at 3:51 PM, Matthew Jones <matthew at longsight.com>
>> wrote:
>>
>>> We talked this morning on the release call about having Jenkins auto
>>> create a tag on every build so it's easier to find out what build is
>>> running on the nightlies and easier to reference a build on a date.
>>> Otherwise the syntax for checking out by date seems semi difficult to
>>> remember and not 100% agreed on what the answer is. [1]
>>>
>>> So I tried to setup a process (As a Post Action on the trunkbuild) on
>>> our Jenkins to automatically create git tags but Jenkins failed to publish
>>> it. I believe it needs credentials either in the form of private key or
>>> username password. Most likely if we did this we'd have to create a
>>> 'generic' account held by the foundation and give it access to that.
>>>
>>> There's also an option for "Certificate" (PKCS#12 certificate and
>>> password) but I don't 100% know where to find that?
>>>
>>> It feels like there should be some other way to publish but I don't see
>>> that in the options here for this plugin.
>>>
>>> Also at the moment this issue is broken in Jenkins (
>>> https://issues.jenkins-ci.org/browse/JENKINS-26520) so there is no way
>>> to reference the timestamp for creating timestamp tags. Like for instance
>>> if we wanted a tag
>>>
>>> master/2014-02-26-15-00-00 or something. I'm guessing we'd have to go
>>> all the way out to the minute since we could potentially build multiple
>>> times an hour? In any case that's impossible and it only allows for the
>>> build number (master/116).
>>>
>>> Anyway, it seems like a great process but there are a few hurdles at the
>>> moment.
>>>
>>> [1] http://blog.endpoint.com/2014/05/git-checkout-at-specific-date.html
>>>
>>> _______________________________________________
>>> sakai-core-team mailing list
>>> sakai-core-team at collab.sakaiproject.org
>>> http://collab.sakaiproject.org/mailman/listinfo/sakai-core-team
>>>
>>>
>>
>>
>> --
>> earle,
>> asahi net int.
>>
>
>


-- 
earle,
asahi net int.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-core-team/attachments/20150226/05dd6c29/attachment-0001.html