#codefresh (2019-10)

codefresh

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

2019-10-31

2019-10-29

2019-10-28

dustinvb avatar
dustinvb

Cool, will wrap this up into a step and produce an image for this. Appreciate the example.

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

Great thanks for putting that together

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

@mumoshu they are adding an official helmfile step to Codefresh :-)

mumoshu avatar
mumoshu

wow, that’s great news!

David Holsgrove avatar
David Holsgrove

Hi - I’d like to trigger a pipeline by codefresh API, with a specific branch and variable set. The api doc https://g.codefresh.io/api/#operation/pipelines-run doesnt have an example of the acceptable body to POST - anyone got any examples?

Andriy Knysh (Cloud Posse) avatar
Andriy Knysh (Cloud Posse)

this is an example of calling one pipeline from another using Codefresh CLI and providing branch and variables https://github.com/cloudposse/example-app/blob/master/codefresh/release.yaml#L42

cloudposse/example-app

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

David Holsgrove avatar
David Holsgrove

Thanks @Andriy Knysh (Cloud Posse) - I was hoping for the API equivalent to that level of cli execution

dustinvb avatar
dustinvb

Example of a Lambda function for the API is available here: https://codefresh.io/continuous-integration/integrate-aws-codecommit-repository-codefresh/

The API endpoint is documented here: https://g.codefresh.io/api/#operation/pipelines-run

How to integrate your AWS CodeCommit repository to Codefresh - Codefresh

AWS CodeCommit is a managed source control service provided by Amazon. This blog post will show how to integrate a CodeCommit repository into a Codefresh pipeline. AWS CodeCommit only allows workflows that trigger lambda functions so we need to use that to trigger Codefresh. This is how we will do it: Once we commit a … Continued

dustinvb avatar
dustinvb
codefresh-io/js-sdk

Contribute to codefresh-io/js-sdk development by creating an account on GitHub.

dustinvb avatar
dustinvb

It’s also available in our Go SDK https://github.com/codefresh-io/go-sdk

codefresh-io/go-sdk

Codefresh SDK for Golang. Contribute to codefresh-io/go-sdk development by creating an account on GitHub.

dustinvb avatar
dustinvb

Curl Example:

curl '<https://g.codefresh.io/api/builds/5b1a78d1bdbf074c8a9b3458>' --compressed -H 'content-type:application/json; charset=utf-8' -H 'Authorization: <your_key_here>' --data-binary '{"serviceId":"5b1a78d1bdbf074c8a9b3458","type":"build","repoOwner":"kostis-codefresh","branch":"master","repoName":"nestjs-example","variables":{"sample-var1":"sample1","SAMPLE_VAR2":"SAMPLE2"}}'
Andriy Knysh (Cloud Posse) avatar
Andriy Knysh (Cloud Posse)

thanks @dustinvb

Andriy Knysh (Cloud Posse) avatar
Andriy Knysh (Cloud Posse)

@David Holsgrove ^

David Holsgrove avatar
David Holsgrove

fantastic thanks @dustinvb and @Andriy Knysh (Cloud Posse)!

superfresh1

2019-10-27

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

@dustinvb something like this…

  deploy_helmfile:
    title: Deploy with helmfile
    stage: Deploy
    image: "...."
    working_directory: /conf/
    environment:
      - 'KUBECONFIG=${{CF_KUBECONFIG_PATH}}'
      - 'REPO_ROOT=${{CF_VOLUME_PATH}}/${{CF_REPO_NAME}}'
    shell: bash
    commands:
      - kubectl config use-context "${KUBE_CONTEXT}"
      - helmfile  --environment="${FLAVOR}"
        -f "${REPO_ROOT}/deploy/helmfile.yaml" sync
    when:
      steps:
      - name: ask_for_permission
        on:
        - approved
Erik Osterman (Cloud Posse) avatar
Erik Osterman (Cloud Posse)

this assumes there’s a file in the repo called deploy/helmfile.yaml

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

this is a great way to deploy a microservice and all of it’s dependencies

dustinvb avatar
dustinvb

@Erik Osterman (Cloud Posse) I don’t know if this is possible or not. I seen indications that this can remove the need possibly of an Umbrella chart but it looks to me that removing that will split my one single release up into a release per chart. Is this true or is there a way to format the release to use multiple charts without the umbrella? I can’t seem to locate an example. Your repo of helmfiles all seem to do a release per chart.

2019-10-26

dustinvb avatar
dustinvb

Anyone know off hand where I find a Codefresh build definition example using Helmfile? Need to jump into this and would like to see an example to accelerate learning.

2019-10-22

Codefresh Status - Incident History avatar
Codefresh Status - Incident History
07:39:37 AM

Codefresh UI outage Oct 22, 07:29 UTC Update - We are continuing to investigate this issue.Oct 22, 07:28 UTC Investigating - We are currently investigating this issue.

Codefresh UI outage

Codefresh’s Status Page - Codefresh UI outage.

Kostis (Codefresh) avatar
Kostis (Codefresh)

@btai every cluster is automatically available to all pipelines (even with free plans). You can just use kubectl straight in a pipeline and it will work. Could you please clarify?

btai avatar

@Kostis (Codefresh) yeah I know, my preference would be to not to have that by default because of security reasons. I’d prefer to explicitly allow access to specific clusters for each pipeline

Kostis (Codefresh) avatar
Kostis (Codefresh)

@btai ah I see. If you are talking about Policy on clusters then I think that this is indeed enterprise only https://codefresh.io/docs/docs/enterprise/access-control/#marking-kubernetes-clusters-with-policy-attributes

Access control

How to restrict resources in a company environment

Kostis (Codefresh) avatar
Kostis (Codefresh)

but let me ask internally to verify that…

btai avatar

thanks @Kostis (Codefresh)

Kostis (Codefresh) avatar
Kostis (Codefresh)

@btai yes that feature is enterprise only normally. However, I was told that we might support custom ad-hoc plans in some cases. If you are already a customer, can you ask your Codefresh contact if this can be integrated in your plan?

Codefresh Status - Incident History avatar
Codefresh Status - Incident History
08:09:37 AM

Codefresh UI outage Oct 22, 07:52 UTC Resolved - This incident has been resolved.Oct 22, 07:29 UTC Update - We are continuing to investigate this issue.Oct 22, 07:28 UTC Investigating - We are currently investigating this issue.

Codefresh Status - Incident History avatar
Codefresh Status - Incident History
07:04:52 PM

Potential Webhook delivery issues with Github Oct 22, 19:04 UTC Investigating - Github reported an ongoing issue that is being investigated on their end with users experiencing difficulties with webhook delivery logs.

We are keeping a close eye on their updates and any potential disruption on the actual webhook delivery. Although at this point the report only refers to the logs on webhooks.

Potential Webhook delivery issues with Github

Codefresh’s Status Page - Potential Webhook delivery issues with Github.

Codefresh Status - Incident History avatar
Codefresh Status - Incident History
09:39:42 PM

Potential Webhook delivery issues with Github Oct 22, 21:28 UTC Monitoring - GitHub updated the affected components:

  • webhook delivery logs, attachments and git lfs.

Issues on lfs could affect your builds if your pipeline relies on git lfs.

More info here: https://www.githubstatus.com/incidents/fdl6khghfsp3Oct 22, 19:04 UTC Investigating - Github reported an ongoing issue that is being investigated on their end with users experiencing difficulties with webhook delivery logs.

We are keeping a close eye on their updates and any…

Potential Webhook delivery issues with Github

Codefresh’s Status Page - Potential Webhook delivery issues with Github.

GitHub Status

Welcome to GitHub’s home for real-time and historical data on system performance.

Codefresh Status - Incident History avatar
Codefresh Status - Incident History
12:14:44 AM

Potential Webhook delivery issues with Github Oct 23, 00:11 UTC Resolved - Github has reported resolution of all of their webhook issuesOct 22, 21:28 UTC Monitoring - GitHub updated the affected components:

  • webhook delivery logs, attachments and git lfs.

Issues on lfs could affect your builds if your pipeline relies on git lfs.

More info here: https://www.githubstatus.com/incidents/fdl6khghfsp3Oct 22, 19:04 UTC Investigating - Github reported an ongoing issue that is being investigated on their end with users experiencing…

Potential Webhook delivery issues with Github

Codefresh’s Status Page - Potential Webhook delivery issues with Github.

GitHub Status

Welcome to GitHub’s home for real-time and historical data on system performance.

2019-10-21

btai avatar

is the only way to not import every cluster in codefresh to every pipeline by being on enterprise codefresh?

2019-10-19

deftunix avatar
deftunix

hi all, do you have any example of usage of codefresh to deploy on vm (not using packer, I have seen the example package-gcp) and/or aws beanstalk?

Kostis (Codefresh) avatar
Kostis (Codefresh)

@deftunix that example only uses packer to create an image. The actual VM is deployed with Gcloud. So it should be the same thing for AWS (cli) or Azure (cli). What is your use case?

deftunix avatar
deftunix

just another quick one: do you have any example of integration with monitoring system to measure quality, productivity and velocity?

Codefresh Status - Incident History avatar
Codefresh Status - Incident History
03:04:40 PM

Docker has reported an incident Oct 19, 14:52 UTC Resolved - This incident has been resolvedOct 18, 23:06 UTC Identified - Docker has reported an incident. It’s affecting the following components:

  • Docker Package Repositories

More information here:

Docker has reported an incident

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

Docker System Status

Our system status page is a real-time view of the performance and uptime of Docker products and services.

Docker System Status

Our system status page is a real-time view of the performance and uptime of Docker products and services.

2019-10-18

mfrohberg avatar
mfrohberg

Our team has decided to bite the bullet and start using helm 3. In looking at the source code for the official helm step, it appears as though the helm version can be passed as an argument. Has anyone successfully done this or will I need to fork the step

Harrison Heck avatar
Harrison Heck

Any way to exclude a file in the modified files expression in the triggers?

Kristofer Svardstal avatar
Kristofer Svardstal

@Harrison Heck Glob expressions aren’t great at excluding, but you could try !(filenamehere). Or, if you have conditions in your steps, you could run a check in one step to manually extract it and go from there.

Harrison Heck avatar
Harrison Heck

I’ve tried that exclusion but it didn’t work. Specifically it was /!(docker/pulumi/*). I’m not sure if it’s supposed to work in CF or if they don’t support negation.

Harrison Heck avatar
Harrison Heck

The whole point of these trigger rules though are to bypass starting a job for this. That’s a LOT of overhead for no reason.

Kristofer Svardstal avatar
Kristofer Svardstal

Understandable. Let me see what I can come up with.

Harrison Heck avatar
Harrison Heck

I was able to get it to work. The leading slash was the issue.

Codefresh Status - Incident History avatar
Codefresh Status - Incident History
11:24:39 PM

Docker has reported an incident Oct 18, 23:06 UTC Identified - Docker has reported an incident. It’s affecting the following components:

  • Docker Package Repositories

More information here:

Docker has reported an incident

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

Docker System Status

Our system status page is a real-time view of the performance and uptime of Docker products and services.

Docker System Status

Our system status page is a real-time view of the performance and uptime of Docker products and services.

2019-10-17

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

Not likely…

Alex Siegman avatar
Alex Siegman

I’m confused. Why would you not be able to do that? Take the “passed in” stuff, have a step that does some logic and does a cf_export on the desired build args, then in the build step use the ${{}} to snag those exported environment variables. Doesn’t cf_export make the variables available to the pipeline and all future steps? Granted, I may not be understanding the initial problem.

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

Docker Build args have a special section

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

If there’s a deterministic number of args, each one could be defined and mapped to an env

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

But if the list I’d build args vary uncontrollably not sure how to do it

Alex Siegman avatar
Alex Siegman

Yeah, if you want a different number of build args, that might not be possible with the build step’s build args, but if you want the same build args with different values or whatever, then I think that’s doable.

Codefresh Status - Incident History avatar
Codefresh Status - Incident History
05:09:38 PM

Docker Hub has reported an ongoing incident Oct 17, 16:55 UTC Resolved - Docker System Status Current system status information:

All Systems OperationalOct 16, 15:41 UTC Investigating - This could affect your Codefresh builds.

More information here: https://status.docker.com/pages/incident/533c6539221ae15e3f000031/5da5fc78c7b1c11cd8603721

Docker Hub has reported an ongoing incident

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

Docker System Status

Our system status page is a real-time view of the performance and uptime of Docker products and services.

btai avatar

@Alex Siegman different number of build args and different arg names

btai avatar

I just have some very similar applications which i’ve wanted to share pipelines for because they build & deploy the same way

btai avatar

its just one builds w/ a couple build args and the others do not

btai avatar

i could add a conditional step (on the repo name) for that project, but at that point i think id prefer to just use a seperate pipeline

2019-10-16

Codefresh Status - Incident History avatar
Codefresh Status - Incident History
03:59:39 PM

Docker Hub has reported an ongoing incident Oct 16, 15:41 UTC Investigating - This could affect your Codefresh builds.

More information here: https://status.docker.com/pages/incident/533c6539221ae15e3f000031/5da5fc78c7b1c11cd8603721

Docker Hub has reported an ongoing incident

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

Docker System Status

Our system status page is a real-time view of the performance and uptime of Docker products and services.

btai avatar

codefresh users, do you use a single github CI user token to add triggers on all pipelines? have you found a more secure way of doing this that is still maintainable

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

One thing to consider is introducing a gitops style workflow for adding pipelines.

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

Basically, make everyone a ‘user’ in codefresh with no specific permissions

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

cerate the github CI integration with trigger admin permissions

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

then use PR review/approval process to rollout the pipelines using the codefresh cli

Alex Siegman avatar
Alex Siegman

Anyone set up Codefresh with GSuite SAML custom app for SSO? I did so a couple days ago and can’t get it to work, and it’s been 2 days with no response from support =/ . I followed their docs, and when I try to sync team, I get a BAD REQUEST response code. Just want to make sure I lined up the right properties in the right places.

oriel avatar
oriel

@Alex Siegman can you send me the ticket number please ?

michal.matyjek avatar
michal.matyjek

looking for help in escaping yaml… need to run ~this in Codefresh pipeline:

commands:
      - kubectl run --env ...

and the env variable is: LOGIN='{"randomDelay": 120000, "pauseAfter": 90000}'

how do I escape that to be valid…?

Alex Siegman avatar
Alex Siegman

Use a block scalar with >- perhaps? https://yaml-multiline.info/

YAML Multiline Strings

Find the right syntax for your YAML multiline strings.

:--1:1
Alex Siegman avatar
Alex Siegman

something like:

commands:
  - >-
    kubectl run --env LOGIN='{"randomDelay": 120000, "pauseAfter": 90000}'
    more command that will be folded in to a single line above
  - next new command

No clue if that’ll work, but I’m pretty sure you can use : in block scalars since they are terminated by indentation

michal.matyjek avatar
michal.matyjek

yeah this totally worked, small note on our specific case, had to do: ... --env "LOGIN={\"randomDelay\": 120000, \"pauseAfter\": 90000}" - more escaping

:--1:1
michal.matyjek avatar
michal.matyjek

thanks, I think that may work!

Erik Osterman (Cloud Posse) avatar
Erik Osterman (Cloud Posse)
codefresh-io/codefresh-pipeline-runner

GitHub action with ability to run codefresh pipeline - codefresh-io/codefresh-pipeline-runner

btai avatar

has anyone tried to dynamically pass in build args in the build step (in a shared pipeline setting where you could have multiple triggers from different services)

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

…as in Docker build args?

btai avatar

yeah

btai avatar

prob not possible using their builtin build step huh

2019-10-15

Codefresh Status - Incident History avatar
Codefresh Status - Incident History
05:34:46 PM

Docker Hub Incident Oct 15, 17:24 UTC Update - More information here:

Docker Hub Incident

Codefresh’s Status Page - Docker Hub Incident.

Docker System Status

Our system status page is a real-time view of the performance and uptime of Docker products and services.

Codefresh Status - Incident History avatar
Codefresh Status - Incident History
06:19:52 PM

Docker Hub Incident Oct 15, 18:07 UTC Resolved - Docker Hub has reported that the affected services are operational again.Oct 15, 17:24 UTC Update - More information here:

Harrison Heck avatar
Harrison Heck

Anyone know how to have cf_export not actually echo the value? Not sure why it does this.

Kostis (Codefresh) avatar
Kostis (Codefresh)

@Harrison Heck you can write directly to the underlying file https://codefresh.io/docs/docs/codefresh-yaml/variables/#directly-writing-to-the-file

Variables

Codefresh is a Docker-native CI/CD platform. Instantly build , test and deploy Docker images.

Harrison Heck avatar
Harrison Heck

That’s it though huh? I’m not sure why cf_export echos the value by default anyways, it’s a security risk.

Harrison Heck avatar
Harrison Heck

Having to echo to the file is not the best experience.

Codefresh Status - Incident History avatar
Codefresh Status - Incident History
07:54:42 PM

Docker Hub has reported an ongoing incident Oct 15, 19:43 UTC Investigating - Docker Hub has reported an ongoing incident

This could affect your Codefresh builds.

More information here: https://status.docker.com/pages/incident/533c6539221ae15e3f000031/5da5fc78c7b1c11cd8603721

Docker Hub has reported an ongoing incident

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

Docker System Status

Our system status page is a real-time view of the performance and uptime of Docker products and services.

Codefresh Status - Incident History avatar
Codefresh Status - Incident History
09:14:40 PM

Docker Hub has reported an ongoing incident Oct 15, 20:59 UTC Monitoring - From DokerHub: [Monitoring] Docker hub web login is working again. We will continue to monitor the situation.

More information here: https://status.docker.com/pages/incident/533c6539221ae15e3f000031/5da5fc78c7b1c11cd8603721Oct 15, 19:43 UTC Investigating - Docker Hub has reported an ongoing incident

This could affect your Codefresh builds.

More information here: https://status.docker.com/pages/incident/533c6539221ae15e3f000031/5da5fc78c7b1c11cd8603721

Docker Hub has reported an ongoing incident

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

Docker System Status

Our system status page is a real-time view of the performance and uptime of Docker products and services.

Codefresh Status - Incident History avatar
Codefresh Status - Incident History
10:49:38 PM

Docker Hub has reported an ongoing incident Oct 15, 22:32 UTC Resolved - From DockerHub:

All Systems OperationalUpdated a few seconds ago Our system status page is a real-time view of the performance and uptime of Docker products and services.

More information here: https://status.docker.comOct 15, 20:59 UTC Monitoring - From DokerHub: [Monitoring] Docker hub web login is working again. We will continue to monitor the situation.

More information here:…

Docker Hub has reported an ongoing incident

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

2019-10-11

michal.matyjek avatar
michal.matyjek

can I set this from within codefresh.yml?

dustinvb avatar
dustinvb

Yes, under the spec section of the pipeline.

spec:
  terminationPolicy:
    - type: branch
      event: onCreate
      ignoreBranch: true
  concurrency: 1
  triggerConcurrency: 1
  externalResources: []

Looks like our spec examples need to be updated. Will put in that request now.

michal.matyjek avatar
michal.matyjek

what happens to the other builds if I set concurrency: 1? do they get queued or do they get terminated?

dustinvb avatar
dustinvb

They are queued.

Then you set a termination policy that enforces the behavior selected when they get scheduled to run.

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

this is great!

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

@Igor Rodionov @Andriy Knysh (Cloud Posse) @Jeremy (Cloud Posse)

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

@Alex Siegman

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

we should drop the check for concurrency and just use this.

Andriy Knysh (Cloud Posse) avatar
Andriy Knysh (Cloud Posse)

yea that’s good

Jeremy (Cloud Posse) avatar
Jeremy (Cloud Posse)

But @Erik Osterman (Cloud Posse) aren’t we generally testing for concurrency of a build in a different pipeline?

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

no

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

same pipeline

Jeremy (Cloud Posse) avatar
Jeremy (Cloud Posse)

I’m thinking we check to make sure all PR build/deploys are finished before running destroy. That’s the only concurrency check that comes to mind.

Andriy Knysh (Cloud Posse) avatar
Andriy Knysh (Cloud Posse)

we check if the same pipeline is running and wait if it is

2019-10-10

michal.matyjek avatar
michal.matyjek

Codefresh still does not support limiting pipeline concurrency?

If I wanted to only ever have 1 instance of pipeline running, and all others to queue - this is still only done by a step with codefresh cli script?

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

I think there’s an option to cancel previous build

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

but not limit concurrency

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

@dustinvb did this change?

dustinvb avatar
dustinvb

This is found under the pipeline SETTINGS -> POLICIES tab.

2019-10-09

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

https://community.codefresh.io/ launched! that’s nice

Codefresh

The official Codefresh Community Forums

2019-10-08

Harrison Heck avatar
Harrison Heck

Has anyone integration CodeFresh with DataDog? This way we can see all of the events there and create monitors from it? For example, we were using this to create an alert that got sent to OpsGenie whenever our infrastructure repo failed.

dustinvb avatar
dustinvb

You can try this. Not certain it is what you’re looking for but it’s what I have on hand.

 SendDatadogEvent:
    title: Sending Datadog Event
    image: concourse/datadog-event-resource:latest
    commands:
      - >-
        echo '
        {
          "source": {
            "application_key": "${{DATADOG_APPLICATION_KEY}}",
            "api_key": "${{DATADOG_API_KEY}}",
            "filter": ""
           },
           "params": {
             "title": "${{CF_REPO_NAME}}",
             "text": "${{CF_BUILD_URL}}",
             "priority": "low",
             "alert_type": "success",
             "host": "<https://g.codefresh.io>",
             "aggregation_key": "${{CF_BUILD_ID}}",
             "source_type": "codefresh",
             "tags": [
               "codefresh"
             ]
           }
        }' | /opt/resource/out ./event.json
:--1:1
Harrison Heck avatar
Harrison Heck

Perfect, I can adapt that as needed. Hopefully one day there is native integration.

2019-10-07

Michael Kolb avatar
Michael Kolb

@mfrohberg Thanks for the sharing the information

Michael Kolb avatar
Michael Kolb

Anyone else having issues with support response times from [email protected]?

Alex Siegman avatar
Alex Siegman

I regularly have multiple days go by on seemingly simple tickets. I’ve only put a handful in. Luckily nothing has been an outage incident, but it took something like 2 weeks to get a “it doesn’t work that way here’s a link to relevant documentation” which is not service I could brag about or recommend. I’m hoping my first few tickets have been a fluke though.

Oleg Sucharevich avatar
Oleg Sucharevich

@Michael Kolb what is the issue?

Michael Kolb avatar
Michael Kolb

@Oleg Sucharevich I have a technical issue with image push to ECR that is outstanding now for over 2 days with multiple emails threads

Michael Kolb avatar
Michael Kolb

From the logging that i get the pipeline is not finding the image in r.cfcr.io/navican/ from the candidate that is built. The sha256 references are not matching up

Oleg Sucharevich avatar
Oleg Sucharevich

Can you please send me the build id?

Oleg Sucharevich avatar
Oleg Sucharevich

Will escalate it

Oleg Sucharevich avatar
Oleg Sucharevich

Thanks!

Michael Kolb avatar
Michael Kolb

@Oleg Sucharevich Thanks for the help

Oleg Sucharevich avatar
Oleg Sucharevich

Sure

2019-10-04

mfrohberg avatar
mfrohberg

@Michael Kolb … I just had the same issue with variables in manual pipelines. It happens because the CodeFresh environment variables are left undefined. The key is to override the variables in the ‘options’ passed to the run

 if (servicePipelineMap.has(key)) {
          const { pipeline, trigger } = servicePipelineMap.get(key)
          const data = {
            trigger,
            sha,
            branch: targetBranch,
            variables: {
              CF_PULL_REQUEST_ID: id,
              CF_PULL_REQUEST_NUMBER: number,
              CF_BRANCH: targetBranch,
              CF_BASE_BRANCH: prBranch,
              CF_PULL_REQUEST_TARGET: targetBranch,
              CF_COMMIT_AUTHOR: user.login,
            },
          }
          app.log(data.variables)
          const workflowId = await sdk.pipelines.run({ name: pipeline }, data)
          app.log(
            `${pipeline} triggered a pipeline with id ${workflowId} on PR ${number} to ${ref}`
          )
        } else {
          app.log(`There is no pipeline associated with this service`)
        }
Erik Osterman (Cloud Posse) avatar
Erik Osterman (Cloud Posse)

@Michael Kolb this is with the codefresh js sdk?

Erik Osterman (Cloud Posse) avatar
Erik Osterman (Cloud Posse)
codefresh-io/js-sdk

Contribute to codefresh-io/js-sdk development by creating an account on GitHub.

mfrohberg avatar
mfrohberg

They need to do a sprint or two on properly documenting their API/SDK. The swagger doc is not very helpful as it lacks example responses. The CLI is much more reliable and is entirely based off the SDK. The SDK is powerful but lacks documentation. The only way I was able to not be blocked was by forking the CLI and reading the source code…

codefresh-io/js-sdk

Contribute to codefresh-io/js-sdk development by creating an account on GitHub.

mfrohberg avatar
mfrohberg

Yes @Erik Osterman (Cloud Posse) Being as I need to manually trigger pipelines outside of CodeFresh I found the JS-SDK to be the easiest to work with. They should make a point of featuring it.

dustinvb avatar
dustinvb

@Kostis (Codefresh) Can you add this to our documentation backlog to document our JS and GO SDK?

mfrohberg avatar
mfrohberg

I found it only by going through their github org

2019-10-02

Michael Kolb avatar
Michael Kolb

yes, i have been running automatically and manually. The manual iterations appear to be the iterations that fail. I have had to run the pipeline manually at times, since I have been experiencing intermittent Push step failures to AWS ECR. It is unfortunate that this attribute of the variable is not documented. https://codefresh.io/docs/docs/codefresh-yaml/variables/

Variables

Codefresh is a Docker-native CI/CD platform. Instantly build , test and deploy Docker images.

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

@here public #office-hours starting now! join us to talk shop https://zoom.us/j/508587304

2019-10-01

Michael Kolb avatar
Michael Kolb

Anyone else out there having issues with pushing images to AWS ECR? Codefresh support has gone dark and all my pipelines now fail to push to AWS ECR.

Alex Siegman avatar
Alex Siegman

As if there’s an outage, I don’t think so, i’ve successfully pushed a few to ECRs in us-east-1 in the last hour or so

Michael Kolb avatar
Michael Kolb

thanks… my pipelines push to us-west-2. All of them are failing including ones that worked before

Michael Kolb avatar
Michael Kolb

are you using the integrated registries or

provider: ecr
Michael Kolb avatar
Michael Kolb

Has anyone seen issues with codefresh variables interpolating with the build step?

stage: build-images
type: build
title: Build Api Image
description: build api image
working_directory: '${{CF_VOLUME_PATH}}/${{CF_REPO_NAME}}'
dockerfile: '${{dockerfile}}'
image_name: '${{image_name}}'
tag: '${{vtag}}-${{CF_PULL_REQUEST_NUMBER}}'

I am getting a scenario where the build step fails on subsequent commits to the feature branch and will not interpolate the ${{CF_PULL_REQUEST_NUMBER}} at run time.

I get the following at build time:

Building image: my_image_name:0.1.0-${{cf_pull_request_number}} using unique hash: 6903d14a13db6d2cef7a7134925ea0f68468bd00
Erik Osterman (Cloud Posse) avatar
Erik Osterman (Cloud Posse)

That variable is only populated when pipeline is triggered by a Pr webhook

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

Are you running it manually by any Chance?

    keyboard_arrow_up