-
Updated
Apr 4, 2021 - Go
continuous-delivery
Here are 842 public repositories matching this topic...
-
Updated
Apr 24, 2021 - Java
-
Updated
Apr 25, 2021 - Go
-
Updated
Feb 10, 2021 - Shell
-
Updated
Apr 24, 2021 - Go
-
Updated
Apr 23, 2021 - Java
-
Updated
Apr 23, 2021 - Java
Checklist:
- [ x] I've searched in the docs and FAQ for my answer: https://bit.ly/argocd-faq.
- [ x] I've included steps to reproduce the bug.
- [ x] I've pasted the output of
argocd version.
Describe the bug
Values from an Application CRD values block that overrides values from value files are not visualized under the App Details -> Parameters -> Parameters section.
**To Repro
Summary
#6369 tracks the user who created the build (either manual trigger or rerun) and also tweaked the api/v1/user endpoint to contain a new display_user_id field. The new field should be used to show the user in the top bar, since it reflects the same value that Concourse tracks as the build creator.
We should be able to replace [this function](https://github.com/concourse/concour
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.
Summary
When creating docker images for Java applications in the current setup in Jenkins-X the application and all dependencies are all placed in one jar file, meaning it will be in one layer in the docker image.
This means that when new versions of the application are created the unchanged dependencies can't be reused.
It would be a great enhancement if the application code where p
-
Updated
Apr 22, 2021 - JavaScript
Hi all
We already released the addon-framework where we want to provide out-of the box integrations with third party tools. It would be super helpful if someone familiar with Microsoft Teams could assist on building the Teams integration.
We have already written the integration for Slack, and relevant code for this is:
-
Updated
Apr 21, 2021 - Go
Environment
Liquibase Version: 3.8.9
Liquibase Integration & Version: spring boot 2.3.7
Liquibase Extension(s) & Version: -
Database Vendor & Version: MariaDB 10.3.25 + H2 1.4.200
Operating System Type & Version: Ubuntu 20.04 LTS
Des
-
Updated
Apr 24, 2021 - Go
-
Updated
Mar 30, 2021 - Go
-
Updated
Oct 8, 2020
The TOC on the right hand side of https://toolkit.fluxcd.io/guides/helm-operator-migration/ is very crowded, let's add a mini-TOC at the top of the document to provide links to:
- discussion of breaking changes
- api spec changes
- migration strategy
- FAQ
-
Updated
Dec 18, 2020 - Go
-
Updated
Apr 24, 2021 - Go
-
Updated
Jan 6, 2021 - Shell
-
Updated
Apr 20, 2021 - Ruby
-
Updated
Apr 23, 2021 - Java
I was thinking that we could extract the eslint config file into his own module so that we can easily reuse this across any OC related repo in the form of eslint extends.
This because we now have the @opencomponents organization and quite few repos, and i
-
Updated
Oct 30, 2020 - PHP
-
Updated
Apr 19, 2021 - Go
stelligent / mu
While testing another PR, I found that mu pipeline logs command displays information from the pipelines, but also shows this error:
$ mu pipeline logs
[... normal, expected output ...]
func1 ▶ ERROR ResourceNotFoundException: The specified log group does not exist.
status code: 400, request id: f7260741-7f69-4772-b4cc-7c6a9c22d264This error does not occur with the `-f
What happened:
Accessibility report shows various issues that need to be addressed.
What you expected to happen:
Accessibility report should be clean.
How to reproduce it:
Improve this page
Add a description, image, and links to the continuous-delivery topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the continuous-delivery topic, visit your repo's landing page and select "manage topics."


Originally posted by @simskij in containrrr/watchtower#647 (reply in thread)