You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2019/12/19 17:42:00 UTC
[jira] [Commented] (GEODE-7599) Use GCI Concourse resource to track
compute image versions
[ https://issues.apache.org/jira/browse/GEODE-7599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17000239#comment-17000239 ]
ASF subversion and git services commented on GEODE-7599:
--------------------------------------------------------
Commit 5113f5275494057750e82019c1b274c6b7e5b683 in geode's branch refs/heads/develop from Robert Houghton
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=5113f52 ]
GEODE-7599 - Use Google Compute Image resource in Concourse. (#4504)
* Parameterize gcp image-family-name.
* Change geode-build template to set image-family-name.
* Remove reduntant 'do' in pipeline definition.
* Add image-family-name for pr and examples pipelines.
* Remove intermediatary files when deploying meta pipeline.
* Test jobs track when new compute image is used.
* Use gci-resource correctly per platform image family
Authored-by: Robert Houghton <rh...@pivotal.io>
> Use GCI Concourse resource to track compute image versions
> ----------------------------------------------------------
>
> Key: GEODE-7599
> URL: https://issues.apache.org/jira/browse/GEODE-7599
> Project: Geode
> Issue Type: Improvement
> Components: ci
> Reporter: Robert Houghton
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Use the Google Compute Image resource in concourse as an input to jobs that use the heavy-lifter pattern. This will make it easier to track job failures due to an image rebuild.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)