Add retro-compatibility for Semaphore 1.x and maintain support for 2.x#145
Add retro-compatibility for Semaphore 1.x and maintain support for 2.x#145eddiemoore merged 3 commits intocodecov:masterfrom fabiendem:semaphore-compat
Conversation
Codecov Report
@@ Coverage Diff @@
## master #145 +/- ##
==========================================
+ Coverage 89.36% 89.55% +0.19%
==========================================
Files 21 22 +1
Lines 329 335 +6
Branches 80 82 +2
==========================================
+ Hits 294 300 +6
Misses 35 35
Continue to review full report at Codecov.
|
|
@ChristianJacobsen @eddiemoore codecov detects properly Semaphore 2.x, but during the upload of the report to codecov I realised that it fails with the following error: Is there some whitelisting needed server side at codecov for the new service keys?
If so, we would better off reverting this merge and ship instead #132 |
|
Fixing in #146 |
|
@fabiendem Please update to v3.6.1 and try again 👍 |
|
Testing... 🕐 |
|
✅ Great thanks @eddiemoore! It works now with #146 v3.6.1 And sorry about this, when I made my PR I wasn't aware of that constraint on the service name. |

Why
#132 removes compatibility with
Semaphore 1.x.This PR brings back compatibility with
Semaphore 1.xand maintain the support forSemaphore 2.x.Once merged it would reduce the risk of publishing a new
codecov-nodeversion and actually make the supportSemaphore 2.xpublic.What
Semaphore 1.x2.xcodecov-nodeis able to distinguish the versionsHow
SEMAPHORE_REPO_SLUG(not available in Semaphore 2.x)SEMAPHORE_WORKFLOW_ID(not available in Semaphore 1.x)