Loading...

XML

Word

Printable

Epic Link:
As an Adoption team member, I want automation to deploy OpenStack 17.1 with control plane on RHEV that can be networked together with OpenShift, so that I can test adopting that deployment into podified 18.0.
Blocked:
False
Blocked Reason:

Hide

None

Show
None
Ready:
False
Status Summary:

Hide

I have added pre-commit hook to PR

However, a lot of files require update due to linting/styling recommendations. I am afraid to merge all this just before a release. I am converting this Story to Spike as

1) A lot of files needs update and everytime I run
```
pre-commit run --show-diff-on-failure --color=always --all-files
```
I get more and more files that require fixes.
2) Timing is not perfect to push code just before a release

Show
I have added pre-commit hook to PR However, a lot of files require update due to linting/styling recommendations. I am afraid to merge all this just before a release. I am converting this Story to Spike as 1) A lot of files needs update and everytime I run ``` pre-commit run --show-diff-on-failure --color=always --all-files ``` I get more and more files that require fixes. 2) Timing is not perfect to push code just before a release
Intelligence Requested:
Market:

As project grows it would be nice to have a CI to catch linting problems, bugs or even check the patch that it's actually works

I started playing with CI as [1], thus I am opening this task

mentioned on

Merge request - [DNM] Test CI in RHEV repo