search

AICoE / aicoe-ci

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

creating environments pipeline to run tag deploy for each deployment environmet #179

Closed Gregory-Pereira closed 1 year ago

Gregory-Pereira commented 2 years ago

Related Issues and Dependencies

Addresses: https://github.com/AICoE/aicoe-ci/issues/176

This introduces a breaking change

Anything that utilizes the old structure of .aicoe-ci.yaml file will no longer function because the deploy section now has different environments rather than the deployment variables.

Description

Created a pipeline as task (similar to overlay pipeline) that will allow sesheta to make version bumps and changes as pull request instead of simply pushing to master branch. /cc @harshad16

sesheta commented 2 years ago

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: To complete the pull request process, please ask for approval from gregory-pereira after the PR has been reviewed.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files: - **[OWNERS](https://github.com/AICoE/aicoe-ci/blob/master/OWNERS)** Approvers can indicate their approval by writing `/approve` in a comment Approvers can cancel approval by writing `/approve cancel` in a comment
Gregory-Pereira commented 2 years ago

Next steps to get his approved / merged is to test this with overlay pipeline

sesheta commented 1 year 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

goern commented 1 year ago

any update on this?

harshad16 commented 1 year ago

It is blocked by me, i needed to test this out. currently out of cycle , will get this in soon.

sesheta commented 1 year 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 1 year 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 1 year 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 1 year ago

@sesheta: Closed this PR.

In response to [this](https://github.com/AICoE/aicoe-ci/pull/179#issuecomment-1528732664): >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.