[postgis-devel] manual-dev generation
Regina Obe
lr at pcorp.us
Mon Jun 19 22:47:54 PDT 2017
It appears Debbie is still using SVN for PostGIS
But Winnie is using Git for PostGIS
Debbie is using Git for GEOS
I think we hadn't switched her because we were worried because the web hook
is triggered on svn, the replication to Git may not be completed before she
starts her run.
I should check how Winnie is fairing with that. Winnie I think I let go to
git, cause she's just building windows experimental builds, so missing a
commit is not as big of a deal as Debbie missing it.
-----Original Message-----
From: strk at kbt.io [mailto:strk at kbt.io]
Sent: Monday, June 19, 2017 5:17 PM
To: Regina Obe <lr at pcorp.us>
Cc: postgis-devel at lists.osgeo.org
Subject: Re: manual-dev generation
On Mon, Jun 19, 2017 at 04:01:40PM -0400, Regina Obe wrote:
> That would save some cycles. Not sure off-hand how to detect that.
>
> Can you think of a shell way of doing that and maybe we can make a
> make_change_doc.sh that we run as part of this that only doesn't
> something if svn pulled an update in docs folder?
SVN ? I thought Jenkins was now using GIT ?
Either way, yes I can think of a script as long as the script knows the
revision number (or better GIT commit hash) of the last version for which
docs were built and uploaded successfully (a first step could be storing
this number somewhere at the end of the upload
process...)
> Alternatively I could have docs build even if the job fails.
Sounds like a good first step.
--strk;
More information about the postgis-devel
mailing list