[Gluster-devel] Fwd: Change in glusterfs[release-3.6]: glusterd: fix op-version bump up flow

Niels de Vos ndevos at redhat.com
Sat Aug 15 14:44:26 UTC 2015


On Fri, Aug 14, 2015 at 07:43:35PM +0200, Emmanuel Dreyfus wrote:
> Michael Scherer <mscherer at redhat.com> wrote:
> 
> > > > I recall adding a tweak somewhere in jenkins script so that NetBSD
> > > > always succeed for release-3.6 without running the test, but someone
> > > > probably wiped it. 
> > What job ? I didn't touch to netbsd specific stuff, but it could have
> > been a side effect of the cleaning.
> 
> IMO the simpliest way is to have regression.sh detecting that it is an
> unwanted branch and return success.
> 
> I guess a git command could tell us on what branch the changeset is
> based? Any git expert here? 

I think the Jenkins client exports a GERRIT_BRANCH environment variable.
If that is not the case, you can probably use "git describe" to find the
last tag in the branch and compare that to "v3.6*" or similar.

HTH,
Niels
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://www.gluster.org/pipermail/gluster-devel/attachments/20150815/a6c4d683/attachment.sig>


More information about the Gluster-devel mailing list