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.

Sign up for GitHub

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

Jump to bottom

Schedule nightly job on prow #1613

Closed
amitkrout opened this issue Apr 15, 2019 · 3 comments
Closed

Schedule nightly job on prow #1613

amitkrout opened this issue Apr 15, 2019 · 3 comments
Labels
area/release-eng Issues or PRs related to the Release Engineering kind/feature Categorizes issue as a feature request. For PRs, that means that the PR is the implementation

Comments

@amitkrout
Copy link
Contributor

[kind/Enhancement]

Which functionality do you think we should update/improve?

Nightly job for running odo tests (Integration + e2e) on prow

Why is this needed?

To reduce total time taken for pr testing job.
@amitkrout amitkrout added kind/enhancement area/testing Issues or PRs related to testing, Quality Assurance or Quality Engineering labels Apr 15, 2019
@mohammedzee1000
Copy link
Contributor

I guess it would help in the way you say if we rebalance pr tests accordingly

@openshift-ci-robot openshift-ci-robot added kind/feature Categorizes issue as a feature request. For PRs, that means that the PR is the implementation and removed kind/enhancement labels Apr 16, 2019
@amitkrout
Copy link
Contributor Author

Yes, Just waiting for my another pr #1612 to go in first then only we can implement this issue in more efficient and stable way.

@amitkrout amitkrout added this to For consideration in Sprint 167 via automation May 20, 2019
@amitkrout amitkrout removed this from For consideration in Sprint 167 May 20, 2019
@girishramnani girishramnani added area/release-eng Issues or PRs related to the Release Engineering kind/test and removed area/testing Issues or PRs related to testing, Quality Assurance or Quality Engineering labels Jan 2, 2020
@girishramnani
Copy link
Contributor

In one of the discussions with @kadel we decided to not run tests as nightly but on each PR.
Hence I think this issue becomes invalid. Closing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/release-eng Issues or PRs related to the Release Engineering kind/feature Categorizes issue as a feature request. For PRs, that means that the PR is the implementation
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@girishramnani @mohammedzee1000 @amitkrout @openshift-ci-robot