forked from cloudfoundry/cf-for-k8s
-
Notifications
You must be signed in to change notification settings - Fork 0
Implement dev to master CI #1
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
Open
acosta11
wants to merge
10
commits into
develop
Choose a base branch
from
update-ci
base: develop
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
[finishes #171549565]
This reverts commit 137581e.
This is the more functional version of a broken commit I had to revert.
We previously tried to create a subdomain with a timestamp in it to address some of the DNS flakiness we were seeing. However, it seems that that change didn't actually make things better, so we're reverting it to reduce the complexity of our DNS script. [#171452798] Signed-off-by: Jen Spinney <[email protected]>
[#171452798] Signed-off-by: Jen Spinney <[email protected]>
Instead of running stability tests and commit validation in the same job, we now have a separate job just for stability tests. This new job lives in a separate group in the same pipeline as the commit validation pipeline. [#171451722] [skip ci] Signed-off-by: Jen Spinney <[email protected]>
Previously, the job that validated new commits and the job that tested the stabilty of cf-for-k8s by running tests every 20 minutes shared the same pool of environments. Going forward, we'd like to grow the environment pool for testing commits and PRs, but if the stability tests consume from the same environment, we run into the risk of flakes consuming all available environments. Because of this, we decided to isolate the stability environment pool. [#171451722]
- also update development doc to include image reference guidance. [finishes #171454907](https://www.pivotaltracker.com/story/show/171454907) Co-authored-by: Sebastian Vidrio <[email protected]> Co-authored-by: Dave Walter <[email protected]>
also refactor cf-for-k8s-pr and reliability testing into groups under single pipeline [#171524414](https://www.pivotaltracker.com/story/show/171524414) [#171451722](https://www.pivotaltracker.com/story/show/171451722) Co-authored-by: Sebastian Vidrio <[email protected]>
Hello friend, it looks like your pull request has failed one or more of our checks. Please take a look! 👀 |
Hello friend, it looks like your pull request has failed one or more of our checks. Please take a look! 👀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Future self, this is a test PR, please ignore.
We expect a failure for the branch check.