51 строка (44 слот) 1.11 KB
версия : 2.0

рабочие места :
строить :
докер :
- изображение : circleci / ruby: 2.4-node
- изображение : circleci / postgres: 9.4.12-альпийский
Рабочий_каталог : ~ / circleci-demo-workflows
шаги :
- выписка
# Связать установки
- запустить : пакет установить -path поставщика / пакет

  # Настройка базы данных
  - run : bundle exec rake db: create db: schema: load

  - запустить :
      name : Run tests
      команда : rake

развертывание :
машина :
enabled : true
Рабочий_каталог : ~ / circleci-demo-workflows
окружающая среда :
HEROKU_APP : " сонный-убежище-55486 "
шаги :
- выписка
- запустить :
имя : Настройка Heroku
команда : bash .circleci / setup-heroku.sh

  - запустить :
      команда : |
        git push heroku sequential-branch-filter: master
        heroku run rake db: migrate
        sleep 5 # sleep в течение 5 секунд, чтобы дождаться динозавров
        Перезагрузка героя

рабочие процессы :
версия : 2
сборка и развертывание :
рабочие места :
- строить
- развертывание :
требует :
- строить
фильтры :
ветви :
только : фильтр последовательной ветви
© 2018 GitHub , Inc.

https://circleci.com/gh/CircleCI-Public/circleci-demo-workflows/24

This is because the app was already pushed from another project, before consolidating onto here. Also, there exists an issue where we do Heroku Deploy in separate branches (to the same $HEROKU_APP) which would have the same result, push rejected.

When I try to use the workspace-forwarding example, I get the following error in the checkout_code job:

Error locating workspace root directory: stat ~/alumni-network: no such file or directory

You have this functionality documented differently in several places, and none of them are functional.

Get screenshots from CircleCI Workflos screen to show each Workflow in the Readme

codefresh

Commands:
codefresh completion generate bash completion script
codefresh tag [tags..] Add an image tag.
codefresh untag [tags..] Untag an image.
codefresh annotate Annotate a resource with labels.
codefresh patch Patch a resource by filename or stdin.
codefresh auth Manage authentication contexts.
codefresh create Create a resource from a file or stdin.
codefresh delete Delete a resource by file or resource name.
codefresh generate Generate resources as Kubernetes image pull secret and Codefresh Registry token.
codefresh get Display one or many resources.
codefresh replace Replace a resource by filename.
codefresh version Print version.
codefresh logs Show logs of a build.
codefresh restart Restart a build by its id.
codefresh terminate Terminate a build by its id.
codefresh wait <id..> Wait until a condition will be met on a build.
codefresh run Run a pipeline by id or name and attach the created workflow logs.
codefresh delete-release [name] Delete a helm release from a kubernetes cluster.
codefresh install-chart Install or upgrade a Helm chart Repository flag can be either absolute url or saved repository in Codefresh.
codefresh test-release [name] Test a helm release.

Options:
--cfconfig Custom path for authentication contexts config file [default: "/Users/itaigendler/.cfconfig"]
--help Show help [boolean]

cron: "*/5 * * * *" is being treated as * * * * * in circle. any ideas?

Currently uses cache, which is brittle and overly verbose in config.

Should we have a separate demo for workspace forwarding or incorporate it here?

Hi,

Looking at the Fan-in-out example - https://github.com/CircleCI-Public/circleci-demo-workflows/tree/fan-in-fan-out/.circleci

I'm trying to do a similar heroku deploy with circleci v2.0. I'm looking at the command on line 93 in the deploy job of the config.yml I can't understand how the assets, restored from the previous jobs, are added to git? In my build I get failures telling me the build artifacts I am trying to push to the remote heroku git repo haven't been added and there's nothing to push.

According to this document - https://devcenter.heroku.com/articles/git you need to run

git init
git add
git commit

before pushing the build to heroku's repo from where it is deployed. I have added those commands before pushing but I then get errors such as

*** Please tell me who you are.

even though Ive added the user credentials by runing the setup-heroku.sh script.

am I missing something?

P.S. Sorry, I can't put this on the forum but I can't access it for some reason.

I've created a scheduled workflow (cron) where the job is supposed to run regression test scripts against the current dev-environment server application every day at midnight. For now, it is expected to fail and just continue without issue, but earlier I observed that the scheduled workflow automatically re-runs on fail, thus spamming the workflow page with a lot of new executions of the workflow.

Here's my example workflow.
regression: triggers: - schedule: cron: "* 0 * * *" # Runs everyday at approximate past midnight filters: branches: only: - dev jobs: - regressionTest
How can I make it so that when it fails, it just fails and do not re-run?

I have a yaml file that looks like this:

version: 2.0
anchors:
  - &container_config
    docker:
      - image: docker:stable
    resource_class: small
    working_directory: /root/checkout
jobs:
  build:
    <<: *container_config
    steps:
    - checkout
    - setup_remote_docker:
        docker_layer_caching: true
    - run:
        name: Simple build command
        command: command
  scheduled_build:
    <<: *container_config
    steps:
    - checkout
    - setup_remote_docker:
        docker_layer_caching: true
    - run:
        name: simple command
        command: command
workflows:
  version: 2
  commit-workflow:
    jobs:
      - build
  scheduled-workflow:
    triggers:
      - schedule:
          cron: "0 12 ? * 5"
          filters:
            branches:
              only: release
    jobs:
      - scheduled_build

But whenever this is pushed to github, circleci doesn't even see the commit and doesn't build anything. Removing the triggers section I'm able to build as normal.

It's likely a syntax issue, but it's odd that circleci isn't even seeing the commits anymore. Usually the build would fail saying there is a syntax issue with the yaml file.

documentation on triggers & schedule

Hi there,

I'm trying to run my tests on multiple versions of Node.js, and I'm noticing how repetitive the config is in this example: https://github.com/CircleCI-Public/circleci-demo-workflows/blob/parallel-jobs/.circleci/config.yml#L8-L34 (Selected: all the lines that are repeated.)

Is there any less repetitive way to define this configuration? Especially for configs with multiple steps, the configuration grows much faster than seems necessary.

Is there some way I could at least define sets of steps and use them? Maybe something like:

version: 2.0

procedures:
  install-and-test:
      - checkout
      - run: bundle install --path vendor/bundle
      - run: bundle exec rake db:create db:schema:load
      - run:
          name: Run tests
          command: rake
jobs:
  "ruby-2.2":
    docker:
      - image: circleci/ruby:2.2-node
      - image: circleci/postgres:9.4.12-alpine
    working_directory: ~/circleci-demo-workflows
    steps:
      - procedure: install-and-test

  "ruby-2.3":
    docker:
      - image: circleci/ruby:2.3-node
      - image: circleci/postgres:9.4.12-alpine
    working_directory: ~/circleci-demo-workflows
    steps:
      - procedure: install-and-test

  "ruby-2.4":
    docker:
      - image: circleci/ruby:2.4-node
      - image: circleci/postgres:9.4.12-alpine
    working_directory: ~/circleci-demo-workflows
    steps:
      - procedure: install-and-test

workflows:
  version: 2
  build:
    jobs:
      - "ruby-2.2"
      - "ruby-2.3"
      - "ruby-2.4"

Thanks!

https://github.com/piskelapp/piskel

should be on branch "sequential-branch-filter"

The readme takes you here: https://github.com/CircleCI-Public/circleci-demo-workflows/tree/sequential-branch-filter.
same for main document here: https://circleci.com/docs/2.0/tutorials/