Bug 1663089 - Make GD2 container nightly and push it docker hub
Summary: Make GD2 container nightly and push it docker hub
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: project-infrastructure
Version: mainline
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: bugs@gluster.org
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-01-03 06:12 UTC by Atin Mukherjee
Modified: 2019-01-03 10:07 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-01-03 10:07:56 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:

Attachments (Terms of Use)

Description Atin Mukherjee 2019-01-03 06:12:45 UTC 
Description of problem:

During GCS scale testing effort, we identified couple of major issues in GD2 for which the PRs were posted and merged yesterday night, but apparently they missed the window of yesterday's nightly build and hence we're sort of blocked till today evening for picking up the GD2 container image.

If we can build the container from the latest GD2 head and push it to docker hub right away, it'd be great and we should get unblocked.
Comment 1 Nigel Babu 2019-01-03 06:15:05 UTC 
Did it make it to the GD2 nightly RPM build?
Comment 2 Atin Mukherjee 2019-01-03 07:00:46 UTC 
As per https://ci.centos.org/view/Gluster/job/gluster_gd2-nightly-rpms/ , it seems like the last build was 6 hours 49 minutes ago which means the required PRs should be in as part of the rpms.
Comment 3 Nigel Babu 2019-01-03 10:07:56 UTC 
ALright, Deepshika retriggerd the Jenkins job and we're good now.
Note You need to log in before you can comment on or make changes to this bug.