Skip to content
#

Deployment

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.

Here are 2,804 public repositories matching this topic...

deliahu
deliahu commented Jan 30, 2020

Command: cortex debug exec API_NAME

Behavior: choose a running API pod (at random is ok if there are multiple), and run e.g. kubectl exec -it api-iris-classifier-6d866654f8-pwz62 --container api -- /bin/bash

This command should be executed in the manager container, similar to how the cortex cluster up command works. However unlike cortex cluster up, this command will require interact

AppImageKit
probonopd
probonopd commented Sep 3, 2020

Trying to --appimage-extract-and-run a x86_64 Linux AppImage on FreeBSD 12.1-RELEASE-p8 with the Linux compatibility layer:

[email protected]$  /home/user/Downloads/Akira-26-x86_64.AppImage --appimage-extract-and-run
mkdir_p error: Permission denied
Failed to extract AppImage

but

[email protected]$  /home/user/Downloads/Akira-26-x86_64.AppImage --appimage-extract
brecke
brecke commented May 2, 2018

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
wfgydbu
wfgydbu commented Feb 5, 2021

SUMMARY

I just faced an embarrassed problem that command st2 action list keeps return 503.

I tried st2 --debug action list and the result in line HTTP_PROXY(uppercase) was empty. This mislead me that the proxy info was set(which is not).

I finally found that the root cause is a lowercase http_proxy env variable was set in the system.

So I think it maybe more friend

RafalSkolasinski
RafalSkolasinski commented Feb 24, 2021

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.

nodeg
nodeg commented May 4, 2021

To effectively introduce more useful features and fix old stuff, it is necessary to have more unit tests and increase our test coverage. At the moment we have ~28 % code coverage according to Codecov.
Furthermore some of our currently implemented tests are too rudimentary and have to be improved dramatically.

Related i

Wikipedia
Wikipedia

Deployment apps

Flaptastic

Manage flaky unit tests. Click a checkbox to instantly disable any test on all branches. Works with your current test suite

Semaphore

Test and deploy at the push of a button

Codefresh

A modern container-based CI/CD platform, easily assemble and run pipelines with high performance

Buddy

One-click delivery automation for Web Developers

Azure Pipelines

Continuously build, test, and deploy to any platform and cloud

See more Deployment apps