[Gluster-infra] [Bug 1504713] Move planet build to be triggered by Jenkins

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1504713



--- Comment #1 from M. Scherer  ---
I also wonder if we could integrate jenkins with github, to replace the travis
build. It tend to change underneat us and may surprise users.

Ideally, I also would like a system that open ticket when a feed fail for too
long.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug 
https://bugzilla.redhat.com/token.cgi?t=q0grxDCU1l&a=cc_unsubscribe
___
Gluster-infra mailing list
Gluster-infra@gluster.org
http://lists.gluster.org/mailman/listinfo/gluster-infra

[Gluster-infra] [Bug 1504713] New: Move planet build to be triggered by Jenkins

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1504713

Bug ID: 1504713
   Summary: Move planet build to be triggered by Jenkins
   Product: GlusterFS
   Version: mainline
 Component: project-infrastructure
  Assignee: b...@gluster.org
  Reporter: msche...@redhat.com
CC: b...@gluster.org, gluster-infra@gluster.org



Right now, planet.gluster.org is built on webbuilder.int.gluster.org. It
occured to me that using Jenkins would increase transparency, I have submitted
some change for that upstream (aka, the OSAS repo):

https://github.com/OSAS/ansible-role-web_builder/pull/19

Then gluster side, we would just need to add the ssh key of jenkins on the
builder, and have it run the script when the repository is change and/or on a
regular cadence.

Then in turn, this would let people look from time to time to the log and see
if there is issues.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug 
https://bugzilla.redhat.com/token.cgi?t=ivp5pxiwNF&a=cc_unsubscribe
___
Gluster-infra mailing list
Gluster-infra@gluster.org
http://lists.gluster.org/mailman/listinfo/gluster-infra