codefresh-io / docs.codefresh.io

Source for Codefresh documentation

docs.codefresh.io

This site is built with Jekyll. Documentation content is written in Markdown format located in './docs'

Deploying

The site is automatically deployed when commits are merged/pushed in master, hosted at https://codefresh.io/docs/

Preview documentation locally with Docker (Recommended)

1. Install docker-compose
2. Run docker-compose up
3. Open http://localhost:3131 in your browser, and voila!

To compile scss files into css run the command npm run css or in the live mode npm run watch-css. To compile js files into a bundle run the command npm run js or in the live mode npm run watch-js. Node version 9.11.2

Preview documentation locally (Legacy method)

1. Install Ruby, bundler, jekyll and other Ruby dependencies with bundle install.
2. Run npm install to install Node.js dependencies.
3. Run npm run css (or a specific npm script) to rebuild distributed CSS and JavaScript files, as well as our docs assets.
4. From the root directory, run npm run docs-serve-dev in the command line.
5. Open http://localhost:19002 in your browser, and voila.

docs.codefresh.io's Issues

Refreshing Codecov + Codefresh docs

Hey folks, I'm Jerrod from Codecov.

We notice this Codecov+Codefresh docs page is a bit dated and references deprecated technologies.

https://codefresh.io/docs/docs/example-catalog/ci-examples/codecov-testing/

Our team is going to take a pass at updating it. Any feedback or guidelines before we do a full page re-write?

Thanks!
Jerrod

IP range as a text endpoint

Howdy,

I am currently writing a terraform firewall for Digital ocean but have to manually locate your IP range.

Are you able to either:

1. Publish a Terraform Data Source
2. Provide an endpoint similar to how cloudflare do with their list of IP's as a text file

Page I came from for context

demo, picture mongo-service.png - not need to create external port

Hi,

while trying out the demo of the demochat app i noticed that in the picture for setting up the mongodb an external port is actived, that is not needed a ClusterIP should suffice, so in the checkbox this can be deactivated.

Bye,
Thorsten

Can a push to ECR example be added please?

Before opening an issue:

• Search for duplicate or closed issues
• Read the contributing guidelines

When reporting a bug, include:

• Operating system and version (Windows, Mac OS X, Android, iOS, Win10 Mobile)
• Browser and version (Chrome, Firefox, Safari, IE, MS Edge, Opera 15+, Android Browser)

dynamic pipeline tutorial is non-functional

Duplicated issue that was closed without actually resolving:
codefresh-io/cli#301

When I look for any information on dynamically generated pipelines these are the top three results for codefresh- of which most of it is incorrect and doesn't pass validation.
https://github.com/kostis-codefresh/dynamic-pipelines/blob/master/pipeline-creator-spec.yml
https://codefresh.io/devops-tutorial/programmatic-creation-codefresh-pipelines-part2/
https://codefresh.io/devops-tutorial/programmatic-creation-codefresh-pipelines-part1/

1. cli command is incorrect

@ msheiny , thanks.
There is no codefresh create pipeline command.
The ability to create a pipeline is via flag -f like codefresh create -f FILE that contains a valid yaml descriptor.

2. The provided files don't work and the provided validation errors fail due to the name having a slash in it.
   codefresh-io/cli#334

Documentation currently has incorrect references. It appears there is a way to get a spec only by manually creating a pipeline and then using CLI to output.

What's the proper way to matrix list_arguments

This is a fairly contrived example but this type of matrix but matrix variants are very common when having to support multiple versions.

version: '1.0'
steps:
  BuildVariants:    
    image_name: java_variant
    type: build
    dockerfile: Dockerfile.variants
    matrix:      
      build_arguments:
        - [JDK_VERSION=7]
        - [JDK_VERSION=8]
        - [JDK_VERSION=9]
      build_arguments:
        - [MAVEN_VERSION=1]
        - [MAVEN_VERSION=2]

FROM alpine
ARG JDK_VERSION
ARG MAVEN_VERSION
RUN echo "${JDK_VERSION} {MAVEN_VERSION}"

Unless I'm missing something the above doesn't appear to be possible unless I do something involve multiple steps.

If I have the same build step parrallelized I can use the same "${{BuildVariants}}" reference to run against the same later steps up to and including the publish.