Bug 1504713
| Summary: | Move planet build to be triggered by Jenkins | ||
|---|---|---|---|
| Product: | [Community] GlusterFS | Reporter: | M. Scherer <mscherer> |
| Component: | project-infrastructure | Assignee: | bugs <bugs> |
| Status: | CLOSED UPSTREAM | QA Contact: | |
| Severity: | low | Docs Contact: | |
| Priority: | low | ||
| Version: | mainline | CC: | bugs, gluster-infra |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2020-03-12 12:52:03 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
M. Scherer
2017-10-20 13:09:59 UTC
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. (In reply to M. Scherer from comment #1) > 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. Is this now in place? The last time I checked with Deepshikha, there was a refrain of the cron behind the planet scripts failing randomly. Nope, nothing changed. That's kinda a lower priority, since the system work well enough most of the time, and has a rather low impact. This bug is moved to https://github.com/gluster/project-infrastructure/issues/26, and will be tracked there from now on. Visit GitHub issues URL for further details |