This repository has been archived by the owner on Jun 13, 2021. It is now read-only.
Run fossa analysis in a distinct pipeline #670
Merged
Conversation
This file contains 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
Signed-off-by: Nicolas De Loof <nicolas.deloof@gmail.com>
Codecov Report
@@ Coverage Diff @@
## master #670 +/- ##
=======================================
Coverage 73.63% 73.63%
=======================================
Files 52 52
Lines 2852 2852
=======================================
Hits 2100 2100
Misses 497 497
Partials 255 255Continue to review full report at Codecov.
|
glours
approved these changes
Oct 6, 2019
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
- What I did
Moved fossa analysis stage in a dedicated pipeline, so timeout won't fail CI
- How I did it
Cut'n Paste
- How to verify it
This PR should trigger both
- Description for the changelog
- A picture of a cute animal (not mandatory but encouraged)
