#codefresh (2019-11)

codefresh

Archive: https://archive.sweetops.com/codefresh/

2019-11-01

mfrohberg avatar
mfrohberg

I would be interested to get a cost benefit analysis of continuing our current codefresh-managed vs doing the on-prem solution…?

Alex Siegman avatar
Alex Siegman

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.

mfrohberg avatar
mfrohberg

And further, how does the on prem solution differ from the hosted…?

mfrohberg avatar
mfrohberg

I noticed in https://github.com/cloudposse/helmfiles/ all the on-prem codefresh bootstrap files

cloudposse/helmfiles

Comprehensive Distribution of Helmfiles. Works with helmfile.d - cloudposse/helmfiles

dustinvb avatar
dustinvb

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.

Erik Osterman (Cloud Posse) avatar
Erik Osterman (Cloud Posse)
cloudposse/terraform-aws-codefresh-backing-services

Terraform module to provision AWS backing services necessary to run Codefresh Enterprise - cloudposse/terraform-aws-codefresh-backing-services

Erik Osterman (Cloud Posse) avatar
Erik Osterman (Cloud Posse)

Which deploys all the backing services we needed for codefresh onprem using AWS managed services

Erik Osterman (Cloud Posse) avatar
Erik Osterman (Cloud Posse)

unfortunately, codefresh is incompatible with DocumentDB

Erik Osterman (Cloud Posse) avatar
Erik Osterman (Cloud Posse)

And to be covered by support we couldn’t use EFS or Redis

Erik Osterman (Cloud Posse) avatar
Erik Osterman (Cloud Posse)

I would have really preferred operating Codefresh on-prem using the AWS managed backing services rather than in cluster services.

2019-11-05

Codefresh Status - Incident History avatar
Codefresh Status - Incident History
02:59:42 PM

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

Docker Hub has reported an ongoing incident

Codefresh’s Status Page - Docker Hub has reported an ongoing incident.

Codefresh Status - Incident History avatar
Codefresh Status - Incident History
04:14:50 PM

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

GitHub has reported an ongoing incident

Codefresh’s Status Page - GitHub has reported an ongoing incident.

Kostis (Codefresh) avatar
Kostis (Codefresh)

Do we have examples of pipelines that use this plugin? https://github.com/cloudposse/slack-notifier

cloudposse/slack-notifier

Command line utility to send messages with attachments to Slack channels via Incoming Webhooks - cloudposse/slack-notifier

Erik Osterman (Cloud Posse) avatar
Erik Osterman (Cloud Posse)

We have the way we use it

1
Erik Osterman (Cloud Posse) avatar
Erik Osterman (Cloud Posse)

but not the way codefresh might want to publish it

Erik Osterman (Cloud Posse) avatar
Erik Osterman (Cloud Posse)

It’s a bit convoluted because we call slack-notifier from our build-harness

Erik Osterman (Cloud Posse) avatar
Erik Osterman (Cloud Posse)
cloudposse/example-app

Example application for CI/CD demonstrations of Codefresh - cloudposse/example-app

Erik Osterman (Cloud Posse) avatar
Erik Osterman (Cloud Posse)
cloudposse/build-harness

Collection of Makefiles to facilitate building Golang projects, Dockerfiles, Helm charts, and more - cloudposse/build-harness

Erik Osterman (Cloud Posse) avatar
Erik Osterman (Cloud Posse)

There are just so many derived environment variables

Erik Osterman (Cloud Posse) avatar
Erik Osterman (Cloud Posse)
cloudposse/build-harness

Collection of Makefiles to facilitate building Golang projects, Dockerfiles, Helm charts, and more - cloudposse/build-harness

Codefresh Status - Incident History avatar
Codefresh Status - Incident History
09:29:41 PM

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

GitHub has reported an ongoing incident

Codefresh’s Status Page - GitHub has reported an ongoing incident.

2019-11-08

Jonathan Bus avatar
Jonathan Bus

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.

Erik Osterman (Cloud Posse) avatar
Erik Osterman (Cloud Posse)

Could it be related to maxing out the number of concurrent steps for the size of builder?

Jonathan Bus avatar
Jonathan Bus

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.

Alex Siegman avatar
Alex Siegman

To clarify, we’re seeing this across multiple projects/pipelines, and it’s been repeatable the last couple of hours

Jonathan Bus avatar
Jonathan Bus

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.

Dan Garfield avatar
Dan Garfield

This is a bug we’ve seen in a few builds. I believe it’s being activity worked on but worth opening a ticket if you have a minute to increase attention.

btai avatar

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

Debugging Codefresh pipelines

How to pause and inspect pipelines

Darren Cunningham avatar
Darren Cunningham

Note: This feature is currently available only to select customers. If you want to use debugging in your own pipelines please contact us.

Debugging Codefresh pipelines

How to pause and inspect pipelines

1
Darren Cunningham avatar
Darren Cunningham
Contact us we are here to help | Codefresh

Codefresh’s continuous integration and delivery platform for Docker and Kubernetes empowers teams of all sizes to build and release pipelines faster at scale.

btai avatar

Thanks!

Darren Cunningham avatar
Darren Cunningham

no problem

2019-11-11

btai avatar

debugger in codefresh is awesome!!

party_parrot3
1
Dan Garfield avatar
Dan Garfield

Did someone get you access so you could try it out?

btai avatar

@Dan Garfield yes I reached out to Oriel

Dan Garfield avatar
Dan Garfield

Awesome, would you mind if I screenshot and share this note publicly?

btai avatar

@Dan Garfield go for it!

Dan Garfield avatar
Dan Garfield

thanks!

2019-11-12

2019-11-25

Harrison Heck avatar
Harrison Heck

Anyone having issues with CF notifying GitHub for status updates?

Alex Siegman avatar
Alex Siegman

I’m having issues with some unlisted quota trying to build and push a docker image to my codefresh repository.

The push refers to repository [r.cfcr.io/myaccount/myimage]                                                                          
error parsing HTTP 429 response body: invalid character 'Q' looking for beginning of value: "Quota Exceeded."

The docs here: https://codefresh.io/docs/docs/docker-registries/codefresh-registry/#remove-images-from-codefresh-registry Quite specifically say that I shouldn’t have any kind of space issues, it’s “fully managed”

The Codefresh Registry is fully managed for you and the amount of space it consumes does not affect you in any way (Codefresh pricing does not depend on the space you consume for Docker images). Anyone run in to this? It kind of has ground a bunch of work to a halt.

In fact, I can’t even find the word “quota” in all of their documentation.

I’ll file a support ticket, but maybe someone else has a quick win on this I’m hoping.

Codefresh Docker Registry

How to use the integrated Docker registry of your account

Codefresh Status - Incident History avatar
Codefresh Status - Incident History
06:04:44 AM

Docker Pull from GCR not working (Quota Exceeded) Nov 26, 05:57 UTC Identified - Issue is currently under investigation by Codefresh Engineering.

Docker Pull from GCR not working (Quota Exceeded)

Codefresh’s Status Page - Docker Pull from GCR not working (Quota Exceeded).

Alex Siegman avatar
Alex Siegman

Well maybe that’s related~

1
Codefresh Status - Incident History avatar
Codefresh Status - Incident History
07:24:47 AM

Docker Pull from GCR not working (Quota Exceeded) Nov 26, 07:18 UTC Resolved - This incident has been resolved.Nov 26, 07:18 UTC Update - We are continuing to work on a fix for this issue.Nov 26, 07:17 UTC Update - We are continuing to work on a fix for this issue.Nov 26, 05:57 UTC Identified - Issue is currently under investigation by Codefresh Engineering.

Docker Pull from GCR not working (Quota Exceeded)

Codefresh’s Status Page - Docker Pull from GCR not working (Quota Exceeded).

2019-11-28

Codefresh Status - Incident History avatar
Codefresh Status - Incident History
01:04:29 PM

GitLab has reported an ongoing incident Nov 28, 12:46 UTC Investigating - GitLab Incident Status: Service Disruption Components Website, API, Git (ssh and https), Pages, Registry, CI/CD, Background Processing, Support Services, packages.gitlab.com, customers.gitlab.com, version.gitlab.com, forum.gitlab.com

This could affect your Codefresh builds.

More information here: https://status.gitlab.com/

GitLab has reported an ongoing incident

Codefresh’s Status Page - GitLab has reported an ongoing incident.

GitLab System Status

We continuously monitor gitlab.com and all its services. If there are any performance or service interruptions, an update will be posted here.

Codefresh Status - Incident History avatar
Codefresh Status - Incident History
01:14:36 PM

GitLab has reported an ongoing incident Nov 28, 13:00 UTC Resolved - This incident has been resolved.Nov 28, 12:46 UTC Investigating - GitLab Incident Status: Service Disruption Components Website, API, Git (ssh and https), Pages, Registry, CI/CD, Background Processing, Support Services, packages.gitlab.com, customers.gitlab.com, version.gitlab.com, forum.gitlab.com

This could affect your Codefresh builds.

More information here: https://status.gitlab.com/

    keyboard_arrow_up