The general deployment process consists of several interrelated activities with possible transitions between them. These activities can occur at the producer side or at the consumer side or both.
Trying to --appimage-extract-and-run a x86_64 Linux AppImage on FreeBSD 12.1-RELEASE-p8 with the Linux compatibility layer:
user@FreeBSD$ /home/user/Downloads/Akira-26-x86_64.AppImage --appimage-extract-and-run
mkdir_p error: Permission denied
Failed to extract AppImage
but
user@FreeBSD$ /home/user/Downloads/Akira-26-x86_64.AppImage --appimage-extract
hi there,
Just installed latest versions of shipit packages and here's something new:
Running 'deploy:fetch' task...
Create workspace...
Workspace created: "/var/folders/s0/scv46d414cd28hyzsd5_pcrw0000gn/T/tmp-72206PXTF2WKB77Ro"
Initialize local repository in "/var/folders/s0/scv46d414cd28hyzsd5_pcrw0000gn/T/tmp-72206PXTF2WKB77Ro"
Running "git init" on local.
@ Initialized empty Gi
Apart from Unit and Integration tests, we should also run the st2-self-check script for every PR as part of the CI pipeline.
Something we do in e2e and manual testing.
It should be possible with the Github Actions and would help us to catch bugs before merging into master.
Ex #5489.
We are using font-awesome V4 and should migrate to font-awesome V5 which comes with its own vue.js module: https://github.com/FortAwesome/vue-fontawesome
Migration includes removing old font-awesome V4 module and changing all existing icons to new vue.js tag.
This is blocked until #114 is merged which comes with first initial integration.
For SC Operator it may be a good idea to generate CRD manifests from inside a docker container.
This should provide reproducible generation step and avoid "produces different output on my machine" issues.
Linter should also fail if generation of manifests produce diff with the commited version.
No.
After replacing most of the generic CX exceptions with #2643, I saw that there are still some generic CX exceptions which could not be replaced with Python built-ins. To replace those with more meaningful ones we should extend the CobblerException class to include more exceptio
(suggested by Berndinox in #205; been bugging me for a while too)
Currently, the Docker image exposes port 80. We should change this so that running Meli doesn't require root access.
We'll need to update the deployment docs.
Build, deploy, and maintain your Rails apps on any cloud or server
Manage flaky unit tests. Click a checkbox to instantly disable any test on all branches. Works with your current test suite
One-click delivery automation for Web Developers
Continuously build, test, and deploy to any platform and cloud
Test and deploy at the push of a button
Skycap is a container native CI/CD tool
A modern container-based CI/CD platform, easily assemble and run pipelines with high performance
When users starts Serve cluster with a set of options (http options, checkpoint path) and then connects to it with a different set of options, we should either update it, or error out.