-
Updated
Dec 3, 2020 - Java
continuous-deployment
Here are 673 public repositories matching this topic...
-
Updated
Dec 3, 2020 - Go
-
Updated
Dec 3, 2020 - Shell
-
Updated
Dec 3, 2020 - Java
-
Updated
Dec 1, 2020 - Go
-
Updated
Dec 1, 2020 - Java
-
Updated
Aug 21, 2020 - JavaScript
-
Updated
Nov 19, 2020 - JavaScript
Hi,
It seems like naming a remote is subject to certain limitations as groupadd is executed (potentially 32chars?).
Example
apiVersion: gitkube.sh/v1alpha1
kind: Remote
metadata:
name: app-remote
namespace: my-really-really-really-long-nsk logs po/gitkub-
Updated
Dec 2, 2020 - Java
-
Updated
Dec 2, 2020 - Go
First of all: thanks for working on this project and making it accessible to us!
Context
We are starting the unleash server in the same process as our backend server, using unleash.start().
When we receive a SIGINT or SIGTERm, we want to shutdown cleanly so that node exits on it's own because of an empty event loop.
What we tried
Our current attempt to do this boils down t
Environment
Liquibase Version: 4.0.0
Liquibase Integration & Version: spring boot 2.3.2
Liquibase Extension(s) & Version:
Database Vendor & Version: MySql 8.0.15
Operating System Type & Version: Ubuntu 18.04.3
Description
Fail when t
-
Updated
Sep 7, 2020 - Go
-
Updated
Nov 2, 2020 - Shell
-
Updated
Oct 30, 2020 - PHP
https://github.com/google/starlark-go/blob/master/doc/spec.md
It should satisfy our reproducibility needs (like jsonnet) and could be easier to write agola config files.
Like in #137 we should provide build context information.
-
Updated
Jan 8, 2019 - Python
Kudu plugin
-
Updated
Aug 11, 2020 - Go
-
Updated
Apr 14, 2020 - C#
-
Updated
Dec 3, 2020 - Go
-
Updated
Sep 13, 2018 - Go
-
Updated
Dec 2, 2020 - Go
-
Updated
Nov 17, 2020 - Shell
-
Updated
Mar 23, 2020 - Python
-
Updated
Jul 16, 2020 - JavaScript
Improve this page
Add a description, image, and links to the continuous-deployment topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the continuous-deployment topic, visit your repo's landing page and select "manage topics."


Found that if all pods end up on the same node (just happened to me) nothing works well at least on our cluster due to hairpin issues. Any chance the yaml could have anti-affinity set for the pods so they don't end up on the same node by accident?