Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Customizable Folder/File Path for ProwJob inrepo Definitions #31809

Closed
zppinho opened this issue Feb 2, 2024 · 5 comments
Closed

Customizable Folder/File Path for ProwJob inrepo Definitions #31809

zppinho opened this issue Feb 2, 2024 · 5 comments
Labels
area/prow Issues or PRs related to prow kind/feature Categorizes issue or PR as related to a new feature. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. sig/testing Categorizes an issue or PR as relevant to SIG Testing.

Comments

@zppinho
Copy link

zppinho commented Feb 2, 2024

What would you like to be added:
Currently Prow allows for the definition of Jobs in the same repository as the code Inrepoconfig and this can be done with a .prow directory or .prow.yaml file.
See inrepoconfig
We would like to have the possibility to choose the folder or file path where these Jobs can be defined
e.g: .cicd/.prow/triggers.yaml
This defnition could be set in the config.yaml of prow:

in_repo_config:
  enabled:
    org/repo: true
    triggers_path: ".cicd/.prow/"

Why is this needed:
This enables the centralization of all CI/CD definitions in a dedicated folder within the repository. Which enhances the overall readability of the repository, minimizing confusion for new developers.

@zppinho zppinho added the kind/feature Categorizes issue or PR as related to a new feature. label Feb 2, 2024
@k8s-ci-robot k8s-ci-robot added the needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. label Feb 2, 2024
@zppinho
Copy link
Author

zppinho commented Feb 2, 2024

/sig testing

@k8s-ci-robot k8s-ci-robot added sig/testing Categorizes an issue or PR as relevant to SIG Testing. and removed needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. labels Feb 2, 2024
@cfradewavecom
Copy link

+1

@liangyuanpeng
Copy link
Contributor

/area prow

@k8s-ci-robot k8s-ci-robot added the area/prow Issues or PRs related to prow label Feb 6, 2024
@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 6, 2024
@BenTheElder
Copy link
Member

If you're still interested in this feature please file with the project's newly split out repo at https://github.com/kubernetes-sigs/prow

Unfortunately don't think we have maintainers with the bandwidth for feature requests like this currently and Kubernetes intentionally does NOT use inrepoconfig ourselves for security reasons.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/prow Issues or PRs related to prow kind/feature Categorizes issue or PR as related to a new feature. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. sig/testing Categorizes an issue or PR as relevant to SIG Testing.
Projects
None yet
Development

No branches or pull requests

6 participants