Skip to content
This repository has been archived by the owner on Jul 16, 2024. It is now read-only.

fix: pipeline down #35

Merged
merged 1 commit into from
Mar 31, 2022
Merged

fix: pipeline down #35

merged 1 commit into from
Mar 31, 2022

Conversation

yihong0618
Copy link
Contributor

No description provided.

Copy link
Member

@Sasasu Sasasu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

CI corrupted for almost 3 years. thanks!

- name: gcs
type: registry-image
source:
repository: frodenas/gcs-resource

resources:
# Image Resources
- name: centos-gpdb-dev-7
type: docker-image
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
type: docker-image
type: registry-image

we can use registry-image to get a colorful log.
and releng team like registry-image because it has less pull frequency

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

got it.

repository: pivotaldata/centos-gpdb-dev
tag: '7-gcc6.2-llvm3.7'
repository: gcr.io/data-gpdb-public-images/gpdb5-centos7-build-test
tag: latest

- name: ubuntu18-image-test
type: docker-image
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
type: docker-image
type: registry-image

same here.

repository: pivotaldata/centos-gpdb-dev
tag: '7-gcc6.2-llvm3.7'
repository: gcr.io/data-gpdb-public-images/gpdb5-centos7-build-test
tag: latest

- name: ubuntu18-image-test
type: docker-image
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

and here
just run sed -i s/docker-image/registry-image/g

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cool, learned that~

Copy link
Collaborator

@beeender beeender left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

BIG THANKS for fixing this!

region_name: ((aws-region))
secret_access_key: ((bucket-secret-access-key))
versioned_file: plugin-cache.tgz
type: s3
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this one is still on s3?

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is OK. in the gp-concourse-cluster-provisioner examples, the terraform.d resource is still using s3.

concourse/pipeline.yml Show resolved Hide resolved
reasons:
  1. url link change from pivotal -> gcr.io
  2. now we need to use terraform.d
  3. some ccp env changed
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants