-
Notifications
You must be signed in to change notification settings - Fork 27
Conversation
There was a problem hiding this 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!
concourse/pipeline-release.yml
Outdated
- name: gcs | ||
type: registry-image | ||
source: | ||
repository: frodenas/gcs-resource | ||
|
||
resources: | ||
# Image Resources | ||
- name: centos-gpdb-dev-7 | ||
type: docker-image |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
got it.
concourse/pipeline-release.yml
Outdated
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 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
type: docker-image | |
type: registry-image |
same here.
concourse/pipeline.yml
Outdated
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 |
There was a problem hiding this comment.
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
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Cool, learned that~
There was a problem hiding this 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 |
There was a problem hiding this comment.
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?
There was a problem hiding this comment.
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.
reasons: 1. url link change from pivotal -> gcr.io 2. now we need to use terraform.d 3. some ccp env changed
a6e204f
to
fb54c0e
Compare
No description provided.