debugger in codefresh is awesome!!
Did someone get you access so you could try it out?
@Dan Garfield yes I reached out to Oriel
Awesome, would you mind if I screenshot and share this note publicly?
@Dan Garfield go for it!
We’re having an issue where pipelines are getting stuck after the approval step. The step after ask for approval is to clone the app repo. It starts that but quickly goes back to Initializing Process. I entered a support issue but thought I’d post here to see if anyone can help. It’s blocking some important work for us. Issue number is 1992.
Could it be related to maxing out the number of concurrent steps for the size of builder?
I don’t think so. One has been fine on small for a while now and it’s having the problem. I’ll try it on a large to see if it makes a difference.
To clarify, we’re seeing this across multiple projects/pipelines, and it’s been repeatable the last couple of hours
The builds are showing up as green and red in the builds screen but still blue in the build details screen. I wondered if they were finishing and the UI was not updating so I pulled the logs for the build with the codefresh CLI and it didn’t have any more info than the build detail screen in the UI.
does anyone know if https://codefresh.io/docs/docs/configure-ci-cd-pipeline/debugging-pipelines/ is an enterprise feature? if not, how can we turn on the debugger
https://status.codefresh.io/incidents/89zhxhzj59lb\|Docker Hub has reported an ongoing incident Nov 5, 14:42 UTC Investigating - Investigating - Currently investigating increase in queue backlogs affecting Pages builds and some webhooks deliveries. More info: https://www.githubstatus.com/incidents/42hkbtl63nmn
Codefresh’s Status Page - Docker Hub has reported an ongoing incident.
https://status.codefresh.io/incidents/89zhxhzj59lb\|GitHub has reported an ongoing incident Nov 5, 14:42 UTC Investigating - Investigating - Currently investigating increase in queue backlogs affecting Pages builds and some webhooks deliveries. More info: https://www.githubstatus.com/incidents/42hkbtl63nmn
We have the way we use it
but not the way codefresh might want to publish it
It’s a bit convoluted because we call
slack-notifier from our
Example application for CI/CD demonstrations of Codefresh - cloudposse/example-app
There are just so many derived environment variables
https://status.codefresh.io/incidents/89zhxhzj59lb\|GitHub has reported an ongoing incident Nov 5, 21:17 UTC Resolved - Github reports all systems operational. Webhooks are back to normal time deliveries.Nov 5, 14:42 UTC Investigating - Investigating - Currently investigating increase in queue backlogs affecting Pages builds and some webhooks deliveries. More info: https://www.githubstatus.com/incidents/42hkbtl63nmn
I would be interested to get a cost benefit analysis of continuing our current codefresh-managed vs doing the on-prem solution…?
In my situation, on-prem was not cheaper. They still bill you a LOT for basically a license to use a runner. So, just because you have a giant kube cluster with lots of availability, you’re still paying more for increased concurrency. This was as of about 6 months ago, maybe they’ve changed, but it’s how I understood it when I chatted to my sales rep about it.
And further, how does the on prem solution differ from the hosted…?
The only difference is the release cycle is delayed as we need to do additional testing of features before we can send them out to on premise customers.
You deploy with the same Helm chart we do with some minor tweaks to a couple images.
All in all you’ll have about ~29 micro-services running on your cluster deployed via Helm Chart.
We wrote this module: https://github.com/cloudposse/terraform-aws-codefresh-backing-services
Terraform module to provision AWS backing services necessary to run Codefresh Enterprise - cloudposse/terraform-aws-codefresh-backing-services
Which deploys all the backing services we needed for codefresh onprem using AWS managed services
unfortunately, codefresh is incompatible with DocumentDB
And to be covered by support we couldn’t use EFS or Redis
I would have really preferred operating Codefresh on-prem using the AWS managed backing services rather than in cluster services.