slapos.cookbook: Add _failsafe publish type recipes
In some contexts it's required to not stop buildout processing on publishing errors, thus such recipe is required in those cases. By providing -error-status-file it's possible to check status of the publish, the file will be created on error and removed on successful call or during uninstall. It's responsibility of the caller to handle such errors, for example by using proper promises.
Status | Job ID | Name | Coverage | ||||||
---|---|---|---|---|---|---|---|---|---|
External | |||||||||
passed |
#539775
external
|
ERP5.StandaloneDeploymentScriptTest-Debian.Buster |
|
||||||
passed |
#540030
external
|
ERP5.StandaloneDeploymentScriptTest-Debian.Buster.Master |
|
||||||
passed |
#539778
external
|
SlapOS-Master.StandaloneDeploymentScriptTest-Debian.Buster |
|
||||||
passed |
#539745
external
|
SlapOS.Eggs.UnitTest-Master.Python2 |
|
||||||
passed |
#539744
external
|
SlapOS.Eggs.UnitTest-Master.Python3 |
|
||||||
passed |
#539772
external
|
SlapOS.KVM.ResilienceTest-Master |
|
||||||
failed |
#539823
external
|
SlapOS.SlapRunner.ResilienceTest-Master.ERP5 |
|
||||||
failed |
#540000
external
|
SlapOS.SoftwareReleases.IntegrationTest-Master |
|
||||||
passed |
#539782
external
|
Wendelin.StandaloneDeploymentScriptTest-Debian.Buster |
|
||||||