AICoE / aicoe-ci

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

have a way to deploy only one overlay from Pull Request #125

Closed pacospace closed 2 years ago

pacospace commented 3 years ago

Is your feature request related to a problem? Please describe. As Developer,

I have 10 overlays and I open a feature only for one of them, I don't want to create images from PR for all overlays but only for one.

Describe the solution you'd like Alllow user to have /deploy {overlay-name}

Describe alternatives you've considered

Additional context after discussion with @harshad16

Gregory-Pereira commented 2 years ago

Could we use a .dockerignore file (see example) to scope what you are building, allowing for you to create the image for only the features that you are targeting? The problem is that this may become difficult to maintain if multiple people are merging specific features and are not sure what should be included or not included, so some other part would be required to call this a solution. What do you think?

harshad16 commented 2 years ago

cc: @Gregory-Pereira

Thanks for the kind feature requests. we will proceed with the following procedure to provide this feature:

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

harshad16 commented 2 years ago

/remove-lifecycle stale

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/125#issuecomment-1186731671): >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.