[sakai-core-team] Automatically creating git tags

[Earle Nietzel]

I might add in the future your typically going to want jenkins to do other
things as well so having the deploy key will help.

On Fri, Feb 27, 2015 at 5:49 AM, Matthew Buckett <
matthew.buckett at it.ox.ac.uk> wrote:

> One other possibility is to include the git short SHA in the build
> properties, this was you know exactly what version was checked out
> when the build was made.
>
> On 26 February 2015 at 20:51, 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
> >
>
>
>
> --
>   Matthew Buckett, VLE Developer, IT Services, University of Oxford
> _______________________________________________
> 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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-core-team/attachments/20150227/734e4c4e/attachment-0001.html