I’m trying to create a Lambda that will trigger Codefresh pipelines from CloudWatch events, trying to follow the API docs, but not sure what to do here:
https://g.codefresh.io/api/#operation/pipelines-run-yaml – is there any additional documentation about
• type – is this the type of pipeline, type of trigger, is this actually an enum or does this really take any string?
• trigger – enum or any string?
• isYamlService – what is this?
Example with Rust/Cargo - documentation () (Feed generated with FetchRSS)
Global Docker registry prefix/repository - documentation () (Feed generated with FetchRSS)
Multiple Dockerhub integrations - documentation () (Feed generated with FetchRSS)
Using multiple Registry integrations with the same domain - documentation () (Feed generated with FetchRSS)
anyone having codefresh issues?
@Robert Horrox We’re not seeing any outage related issues. Can you tell us what issue you are facing?
@Vidhya Vijayakumar Codefresh apparently had an issue, they resolved it. Our builds were failing at the init stage
@Robert Horrox Yes! We were working on some issues regarding hybrid builds it looks like. The issue was more prevalent than we first though
If you had your choice of ECS or EKS, what would you recommend?
That’s more of a question of “To Kubernetes, or not to Kubernetes”
EKS is Kubernetes, ECS is not
yes, I know
If you already use Kubernetes, then EKS. If you don’t, but want to start, EKS. if you don’t, and don’t want to start, then ECS
Caching Registry selection - documentation () (Feed generated with FetchRSS)
New Codefresh Runner installation - documentation () (Feed generated with FetchRSS)
Running and maintaining CI/CD infrastructure has long been a headache for engineering teams which has led to the popularity of SAAS solutions like Codefresh cloud. But for many, this doesn’t meet their strict security requirements or allow them to access on-prem code, artifacts, or other resources. To help those engineering teams, today we’re releasing Codefresh … Continued
Does this mean if we wanted to use our own runners we could essentially run runtimes w/ more juice? (we currently pay for XLarge boxes in codefresh for some of our pipelines)
Yup - even better than that, you can give those runners IAM roles
what I’m also wondering is will we still be able to get concurrent steps / builds as well (that usually are defined by what size boxes you have and how many).
looks like unless you’re on the enterprise plan you can only have 1 concurrent runner running
That’s a shame to find out. I was hoping that now that they made this available to everyone that it would go the way of GitHub and allow for unlimited runners since it is in our own infrastructure anyways.
Pro customers are allowed 1 Hybrid runner. The size of the box is defined by your infrastructure. We’ll provide the runner you can use and the concurrency on your account will apply to this runner as well.
The runners were only available for Enterprise customers till now, but being made available to Pro customers at this time as an introduction to the option.
Please tell me if I’ve answered your question
The point is that if it runs on our infrastructure, there shouldn’t be a limit
This is an issue we had when we signed up for the enterprise plan, but didn’t really have other options at the time.
Unless I am misunderstanding this.
For example, we pay for 5 concurrency. However, we should have unlimited given that it is on our infrastructure.
I can take this feedback to our Sales team, but we do not plan to make it unlimited at this time.
I figured as much. GitHub and GitLab definitely went the right way with this.
Unfortunately the launch of the runner seems poorly executed. The documentation is horrendous.
@Harrison Heck Happy to take any feedback you have about this and maybe we can record a demo for the users so we can share that with the teams
Sure. I’m just going to be spitting out a lot of information in this thread.
Still no way to change the runtime memory and CPU in the UI
No documentation on how to change the memory and CPU via the CLI
Documentation is under Enterprise, though this is no longer an enterprise feature
Documentation still heavily mentions venona, which while it mentions it is legacy, this is the only place that mentions caching and such
No examples on using the installation options
For example, how do we use the
storage-class-name’s purpose? The way storage is handled is not documented.
No helm chart was provided (how is this ready for enterprise at all?)
The documentation is poorly laid out and hard to read
During the installation a token is printed out but not explained why we need to keep it
Local SSD is mentioned under
Storage space, but no documentation on what to do with it
Local SSD and
EBS are not
space, they are options. So
Storage space as a header makes no sense.
@Harrison Heck Have you already installed the runner? Is this something you would like to do with help at this time?
I’ve already installed it, that part isn’t hard.
The problem is there is no documentation on configuring it
So right now it is useless
I’ll take these questions back and see if we can answer them at least to help you configure it
My honest suggestion is ask your customers to review stuff before releasing things. Because in no way shape or form was the runner’s release done professionally.
The actual GH releases are not following semver
If it requires a ticket to understand how to use it, it wasn’t ready for release.
Thanks Harrison! I understand there are quite a few gaps here
I will take this back to the docs team to make sure all this is filled
I may sound pretty frustrated and I am. CodeFresh does not seem ready for prime time. It feels like an alpha product nearly a year after we started using it.
@Harrison Heck hey Harrison, just wanted to let you know that we’re currently revamping the docs to simplify them. We’ve built up a lot of examples and different areas overtime which makes it confusing to go through.
While there should be some immediate improvements, the larger revamp is underway and will hopefully be ready soon. Thanks for the feedback.
Hey, while that makes sense for other docs, this is documentation for a newly released feature. There isn’t any justification for having launched something new with docs that don’t meet standards.
Codefresh UI Outage Jun 24, 14:41 UTC Resolved - This incident has been resolved.Jun 24, 14:06 UTC Update - We are continuing to investigate this issue.Jun 24, 13:57 UTC Investigating - We are currently investigating this issue.
Integration with the GitHub App mechanism - documentation () (Feed generated with FetchRSS)
Codefresh UI Outage Jun 26, 18:52 UTC Investigating - We are currently investigating UI outage.
Codefresh UI Outage Jun 26, 19:16 UTC Update - UI is back to operational. We are continuing to investigate this issue.Jun 26, 18:52 UTC Investigating - We are currently investigating UI outage.
Codefresh UI Outage Jun 27, 00:07 UTC Resolved - Performance issue identified and resolved on one of our key services causing heavy delays in the app and cli.Jun 26, 19:16 UTC Update - UI is back to operational. We are continuing to investigate this issue.Jun 26, 18:52 UTC Investigating - We are currently investigating UI outage.