User tests: Successful: Unsuccessful:
The Appveyor setup was pretty outdated and did rarely any tests. This PR refactors all of this and hopefully improves this for the future. The following changes were done:
These changes mean that while we run 5 jobs instead of 3, it doesn't take longer than before, maybe it is even quicker. This can be merged when the Appveyor tests pass, no tests by humans needed.
Status | New | ⇒ | Pending |
Category | ⇒ | Unit Tests |
Labels |
Added:
?
?
|
Title |
|
Uh, I'm pretty sure that we don't actually check the hash of composer... I commented that line...
Uh, I'm pretty sure that we don't actually check the hash of composer... I commented that line...
? However, against what do you want check that hash? Do you want us to update our docker images, etc. each time a new composer is released?
That's what's happening now, weekly builds including hash check of all (current) docker images
Yeah, don't force me to do this again... Setting this up and making this work was not fun.
Status | Pending | ⇒ | Fixed in Code Base |
Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2022-04-01 13:49:17 |
Closed_By | ⇒ | HLeithner | |
Labels |
Added:
?
Removed: ? |
thanks
Title |
|
Any Chance to check hash check for composer? For drone we do this at image build time, but for appveyor you maybe have to do it at runtime