search

AICoE / aicoe-ci

AICoE-CI using TektonCD pipelines and triggers
13 stars 13 forks source link

Failed to update base image versions on elyra-aidevsecops-tutorial repository #175

Closed mayaCostantini closed 2 years ago

mayaCostantini commented 2 years ago

Describe the bug Log from the pipeline run:

remote: error: GH006: Protected branch update failed for refs/heads/aicoe-ci-base-image-updater.        
remote: error: Cannot force-push to this protected branch        
To github.com:AICoE/elyra-aidevsecops-tutorial.git
 ! [remote rejected] aicoe-ci-base-image-updater -> aicoe-ci-base-image-updater (protected branch hook declined)
error: failed to push some refs to 'github.com:AICoE/elyra-aidevsecops-tutorial.git'

To Reproduce

See https://tekton.operate-first.cloud/#/namespaces/opf-ci-pipelines/pipelineruns/aicoe-pipelinerun-42e0f0c2-ed35-40c0-ad9a-901f4afb555c?pipelineTask=base-image-update-run&step=rebase

codificat commented 2 years ago

I initially thought that the prow config for the AICoE org is missing some exclusions for branch protection.

However, the same pipeline actually works for the thoth-station org (right?) and there's no exclude pattern there...

/priority critical-urgent

mayaCostantini commented 2 years ago

/sig devsecops /remove priority-critical-urgent /priority important-soon

sesheta commented 2 years ago

@mayaCostantini: The label(s) sig/devsecops cannot be applied, because the repository doesn't have them.

In response to [this](https://github.com/AICoE/aicoe-ci/issues/175#issuecomment-1166964668): >/sig devsecops >/remove priority-critical-urgent >/priority important-soon Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.
sesheta commented 2 years ago

Issues go stale after 90d of inactivity. Mark the issue as fresh with /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

sesheta commented 2 years ago

Stale issues rot after 30d of inactivity. Mark the issue as fresh with /remove-lifecycle rotten. Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

/lifecycle rotten

sesheta commented 2 years ago

Rotten issues close after 30d of inactivity. Reopen the issue with /reopen. Mark the issue as fresh with /remove-lifecycle rotten.

/close

sesheta commented 2 years ago

@sesheta: Closing this issue.

In response to [this](https://github.com/AICoE/aicoe-ci/issues/175#issuecomment-1326104291): >Rotten issues close after 30d of inactivity. >Reopen the issue with `/reopen`. >Mark the issue as fresh with `/remove-lifecycle rotten`. > >/close Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.