-
Updated
Sep 27, 2021 - Go
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 176 public repositories matching this topic...
-
Updated
Dec 14, 2021 - Go
-
Updated
Oct 21, 2019 - Go
We are adding support custom resource ordering in kpt live with the introduction of the depends-on annotation (GoogleContainerTools/kpt#2565). The resource references includes the namespace and name of resources, which means we should make sure they are updated when using the set-namespace and ensure-name-substring functions are used. We should update the functions to
Describe the problem/challenge you have
currently Deployment waiting code looks at several conditions include FailedDelete [0]. there is another condition that would be useful to look at it FailedCreate. we should add that check in there so that we can show nice informational message to the users as part of the progress log. i do not think we need to consider progress as done though, in this
-
Updated
Nov 27, 2021 - Go
-
Updated
Nov 25, 2021 - Go
-
Updated
Aug 20, 2020 - Go
-
Updated
Dec 2, 2021 - Go
-
Updated
Apr 3, 2020 - Go
Currently build agents run mbt version command at the end of the build. We should add a smoke test for each command (mbt describe | build | apply) to this list for release builds.
-
Updated
May 18, 2018 - Go
Also for GetLatestImageTag function ghcr.io has REST API (given you have an authorization PAT). See https://docs.docker.com/registry/spec/api/#listing-image-tags
Tried doing a curl:
curl \
-H "Authorization: Bearer $(echo $PAT | base64)" \
-H "Accept: application/vnd.docker.distribution.manifest.list.v2+json" \
https://ghcr.io/v2/ubclaunchpad/inertiad/tags/list_Origi
-
Updated
Jul 15, 2020 - Go
-
Updated
Dec 30, 2021 - Go
-
Updated
Nov 3, 2017 - Go
-
Updated
Jan 8, 2021 - Go
Just spent an embarrassing amount of time trying to determine why the wsk CLI was working on one machine and not on another. The ultimate issue was that I ended up specifying the APIHOST variable as https://localhost:8443/ in the config file, with the trailing slash, which causes 404s since the CLI was sending requests to https://localhost:8443//api/v1/namespaces/_/triggers?limit=0&skip=0 (n
-
Updated
Dec 30, 2021 - Go
-
Updated
Nov 9, 2019 - Go
-
Updated
Aug 25, 2021 - Go
- Wikipedia
- Wikipedia
Deployment apps
Azure Pipelines
Continuously build, test, and deploy to any platform and cloud
Cloud 66 Skycap
Skycap is a container native CI/CD tool
Codefresh
A modern container-based CI/CD platform, easily assemble and run pipelines with high performance
Buddy
One-click delivery automation for Web Developers
Cloud 66 for Rails
Build, deploy, and maintain your Rails apps on any cloud or server
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
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.