How to resolve conflict between local app.yaml and remote one in pipeline GCP?

André Avilla November 18, 2017

Hi, everybody.

I have a scenario where I develop a GAE app in my machine (local), then commit it to Bitbucket, which has a pipeline integration with GCP.

My problem is a conflict in the file app.yaml.

In Bitbucket, I have to comment the application and version tags in app.yaml:

# application: devop-sportsys
# version: 1
runtime: python27
api_version: 1
threadsafe: true

So the pipeline process is sucessfull. Otherwise, the command gcloud shows this error:

gcloud app deploy -q app.yaml

ERROR: (gcloud.app.deploy) The [application] field is specified in file

[/opt/atlassian/pipelines/agent/build/app.yaml]. This field is not used by gcloud

and must be removed. Project name should instead be specified either by `gcloud

config set project MY_PROJECT` or by setting the `--project` flag on individual

command executions.

But if I comment the tags, GAE Laucher locally doesn't reconize the project and I have to uncomment.


So I change the file app.yaml many times. When I change the file locally, git commit it to Bitbucket and the pipeline process fails.

bitbucket-pipelines.yml

image: google/cloud-sdk

pipelines:
branches:
master:
- step:
script:
- gcloud auth activate-service-account devop-sportsys@appspot.gserviceaccount.com --key-file DEVOP-SportSys-228f797382d8.json
- gcloud app deploy -q app.yaml
- gcloud app deploy -q queue.yaml

How to solve this inconvenience?

0 answers

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events