Comments (6)
👋 just sent a PR to bump the chart for the moment here #7176
from dagger.
Hehe... theoretically, your CD automation should be able to take care of this (with Dagger??? 😁 ). 😝
Scott
from dagger.
Hehe... theoretically, your CD automation should be able to take care of this (with Dagger??? 😁 ). 😝
yep 😛
from dagger.
I'm currently going through the upgrade to v0.11.1 for our internal pipelines so I'll take a look at this one! The helm chart is a bit forgotten at the moment but with the new dynamic CI we can definitely make some tests that raise this for us since we can simply target runs-on: dagger-v0-11-1
. Maybe we could integrate some of this as part of the follow ups for the release? cc @gerhard @jedevc
from dagger.
Partly addressed in:
The follow-up is to automate this.
from dagger.
we have improved the release process and we're already bumping the helm chart on each release. Thx @gerhard
from dagger.
Related Issues (20)
- 🐞 Warning (`WRN`) from `dagger` cli when in an empty `git` repo without a `HEAD` commit HOT 1
- docs: Improve more complex Dockerfile Example
- ✨ It should be really easy to get the most popular IDEs/editors set up for Dagger SDKs
- ✨ improve error in python when dependency is missing
- test issue (will delete)
- 🐞 daggerverse: python docstring list losing newline in daggerverse HOT 1
- 🐞 Windows user home directory support with ~ HOT 3
- 🐞 Cannot pull engine container (engine v0.8.8) HOT 3
- ✨ Add support for updating dagger modules via the CLI
- 🐞 unable to export files with Windows CLI HOT 4
- 🐞 error output in Windows is difficult to read HOT 9
- 🐞 Windows Installation Instructions parameters don't work HOT 8
- 🐞 dagger init go SDK takes an excessive amount of time in codegen for large Go repositoryies
- 'dagger listen' without arguments is unusable HOT 1
- Update Dagger Cloud docs for `dagger login` HOT 1
- Can't return an interface HOT 1
- All Typescript modules fail to run due to `Transforming JavaScript decorators` HOT 1
- Make all SDKs usable from git refs
- Place for community-supported `dagger` install methods in docs that has distinction between official and community HOT 2
- Allow `dagger <func name>` vs `dagger call <func name>` if no conflict
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from dagger.