Skip to content

gitignore: Add test/gke/registry-adder.yaml#12342

Merged
nebril merged 2 commits intomasterfrom
pr/jrajahalme/ignore-gke-temp-files-again
Jul 1, 2020
Merged

gitignore: Add test/gke/registry-adder.yaml#12342
nebril merged 2 commits intomasterfrom
pr/jrajahalme/ignore-gke-temp-files-again

Conversation

@jrajahalme
Copy link
Copy Markdown
Member

@jrajahalme jrajahalme commented Jun 30, 2020

(GKE) Builds fail now if there are any untracked, non-ignored files in the source tree.
Fix this by adding test/gke/registry-adder.yaml into .gitignore and deleting it in
release-cluster.sh.

Note: This was a race between the parallel step of building cilium images and selecting
the cluster. If cluster selection created the registry-adder.yaml before the build was
finished, the build would find an untracked file and fail.

Signed-off-by: Jarno Rajahalme jarno@covalent.io

(GKE) Builds fail now if there are any untracked, non-ignored files in the source tree.
Fix this by adding test/gke/registry-adder.yaml into .gitignore.

Signed-off-by: Jarno Rajahalme <jarno@covalent.io>
Remove the generated temp files after they are no longer needed.

Signed-off-by: Jarno Rajahalme <jarno@covalent.io>
@jrajahalme jrajahalme added release-note/minor This PR changes functionality that users may find relevant to operating Cilium. area/build Anything to do with the build, more general than area/CI needs-backport/1.8 labels Jun 30, 2020
@jrajahalme jrajahalme requested review from a team as code owners June 30, 2020 18:26
@jrajahalme
Copy link
Copy Markdown
Member Author

test-gke

1 similar comment
@jrajahalme
Copy link
Copy Markdown
Member Author

test-gke

@coveralls
Copy link
Copy Markdown

Coverage Status

Coverage decreased (-0.02%) to 36.929% when pulling 850f2df on pr/jrajahalme/ignore-gke-temp-files-again into 7856a77 on master.

@nebril nebril merged commit 0868c6c into master Jul 1, 2020
@nebril nebril deleted the pr/jrajahalme/ignore-gke-temp-files-again branch July 1, 2020 10:09
@joestringer
Copy link
Copy Markdown
Member

@jrajahalme is this user-facing? Typically if a change is not user-facing we'll mark it as release-note/misc. Or if the change is CI-relevant, release-note/ci.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/build Anything to do with the build, more general than area/CI release-note/minor This PR changes functionality that users may find relevant to operating Cilium.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants