Enterprise-Grade Continuous Delivery & DevOps Automation Open Source Platform

Overview

CDS: Continuous Delivery Service

Join the chat at https://gitter.im/ovh-cds/Lobby Go Report Card GoDoc

CDS is an Enterprise-Grade Continuous Delivery & DevOps Automation Platform written in Go(lang).

This project is under active development

Documentation

Intuitive UI

CDS provides an intuitive UI that allows you to build complex workflows, run them and dig into the logs when needed.

create and run workflow with CDS ui Create and run workflow with CDS ui.

The most powerful Command Line for a CI/CD Platform

cdsctl is the CDS Command Line - you can script everything with it, cdsctl also provide some cool commands such as cdsctl shell to browse your projects and workflows without the need to open a browser.

See all cdsctl commands

create workflow as code with CDS command line Create workflow as code with CDS command line.

Want a try?

Docker-Compose is your friend, see Ready To Run Tutorials

Blog posts and talks

FAQ

Why CDS? Discover the Origins

What is a CDS workflow?

Most of the CI/CD Tools play with jobs inside a pipeline. CDS introduce a new concept named CDS Workflows. A CDS Workflow allows you to chain pipelines with triggers. A pipeline is structured in sequential stages containing one or multiple concurrent jobs.

Can I use it in production?

Yes! CDS is used in production since 2015 @OVH and it launches more than 7M CDS workers per year. You can install the official release available on https://github.com/ovh/cds/releases

CDS provides everything needed to monitor and measure production activity (logs, metrics, monitoring)

How to backup?

All data are stored in the database - nothing on filesystem. Just backup your database regularly and you will be safe.

Need some help?

Core Team is available on Gitter

Comparison Matrix

All the features of the table are detailed below.

Feature CDS Bamboo Buildbot Gitlab CI Jenkins
Pipeline
Workflow *17
Visual configuration with Web UI *1
Configuration on Git Repository
Configuration as code on UI *2
Native Git branching *3
Job's Services
Secure Remote Caching *4
Enterprise Notification Bus & Built-in Hooks
Continuous Deployment & Environment Support *5
Enterprise-grade permissions, Support of ACLs delegation *6
Build Artifacts Cloud *7
Tests & Vulnerabilities Reports *8
Self-Service Project Creation - ability to create a tenant *9
Execution Environment Customization *10
Multi-Tenancy *11
Command Line Interface (cdsctl): 100% features supported & User Friendly *12
REST API & SDK
Self-Hosting
High Availability & Scalability & Upgrade without User Downtime *13
Built-in Metrics *14
Extensibility Plugins
OS/Arch Compatibility
Auto-Scale OnDemand multi-cloud *15 *16

CDS User features

Pipeline

Ability to run multiple jobs simultaneously while keeping an isolation between them. See doc about stages & jobs inside a pipeline. A pipeline is started with a context: 0 or 1 application, 0 or 1 environment.

Workflow

A Workflow makes it possible to chain the pipelines. This is a key Feature of CDS. You can create workflows using one or more pipelines, pipelines that can be linked together with joins or forks.

You can imagine having only one builder workflow and deploying your entire microservice stack. The same pipeline can be used several times in a workflow, you can associate an application, an environment. You will have only one deployment pipeline and only one build pipeline to maintain, even if you have hundreds of applications.

Workflow templates

A workflow template allow to share and reuse workflows across multiple teams. Any user can create a Workflow Template, maintain it as code or from UI, and bulk update a set of workflows with a single action.

As a company, you can offer a predefined catalog of workflows allowing you to standardize test and deployment practices across all your teams.

This also reduces the maintenance efforts since templates allow a scalable centralized management.

Visual configuration with Web UI

You can configure everything with the web UI. Even if you have complex use cases, it's usually easier to create your workflow graphically.

Configuration on Git Repository

Pipeline as code is a well-known concept of CI / CD tools. CDS, goes a step further and offers workflow as code. This is done by git-pushing using yaml configuration files of your workflow (+ pipeline, + applications, + environment). This is particularly useful as you can test your new workflow on a dev branch, before merging the changes on the master branch.

Configuration as code on UI

You can modify your workflow with the UI, you can also modify the configuration by editing the yml directly in the UI if you wish. This is an excellent way to learn how to use the workflow-as-code feature.

Native Git branching

Ability to launch builds based on a branch pattern. This allows, for example, to deploy dev/* branches to "staging" and deploy the master branch to "prod".

Note that CDS's default behavior is to launch the whole workflow on every git commit. This behavior can be altered using "run conditions".

Native GitHub / Bitbucket Server / GitLab / Gerrit integration

2-way integration with most popular git-based products.

  1. Ability to get notified and start a build when a change is pushed .
  2. Ability to notify the git-based tool of the success/failure of the build.

CDS natively supports GitHub, GitLab, Bitbucket Server and Gerrit. The link between your repo git and CDS is via a CDS application: 1 Git repository == a CDS application. Through this integration, CDS will push build status of your commits : Building, Success or Failed.

Multiple VCS Support in Pipeline/Job

CDS gives you the possibility to clone from different git repositories within a single workflow. A CDS workflow can involve several different applications - or none if you do not want to have a connection with a git repo.

Job's Services

Ability to start ephemeral services (a database, a web server, etc.) to support your job. This is particularly handy while testing your code.

In CDS these services are called Service Prerequisites. You just need to specify the corresponding docker image and run params.

Take a simple example: you have a pipeline that builds a docker image containing your application. Your application needs a redis and a postgreSQL to work. You can in a CDS job put three prerequisites service: a redis, a postgreSQL and your application. CDS will take care of making a private network between its services so that they can communicate with each other. Your CDS job can thus perform integration tests on your application started with a real database and a real cache.

Please read: https://ovh.github.io/cds/docs/concepts/requirement/requirement_service/

Secure Remote Caching

A remote cache is used by a team of developers and/or a continuous integration (CI) system to share build outputs. If your build is reproducible, the outputs from one machine can be safely reused on another machine, which can make builds significantly faster

Doc: https://ovh.github.io/cds/docs/components/worker/cache/

Enterprise Notification Bus

As an Enterprise-Grade platform, CDS can send a wide range of its internal events (e.g. build finished) in an event bus. This event flow can then feed other services (reporting, notifications, etc., ).

Built-in Hooks

Ability to launch a workflow manually or with git pushes or via a scheduler or via a webhook. In addition to the above, CDS can also be triggered using an event bus to (kafka or RabbitMQ).

Continuous Deployment & Environment Support

Ability to manage multiple environments (e.g. dev/prod/staging) in a secure way with segregated access rights. In practice, an environment is a just set of variables that you can use within your workflows.

With CDS, You can use a deployment pipeline on your preproduction environment and use that same deployment pipeline on your production environment. The ability to deploy to production can be limited to a pre-established group of users.

Enterprise-grade permissions / Support of ACLs delegation

Users are free to create groups and manage users in their groups. A group can have the rights to read, write, execute on their projects and their workflows. You can also restrict the execution of some pipelines to some groups if you wish.

Build Artifacts Cloud

If you use CDS as a CI / CD tool, you will probably have built artifacts. CDS jobs are isolated from each other, but you can pass artifacts from one job to another using the Artifact Upload and Artifact Download actions. At the end of a CDS job, all the files are deleted from the workers. To persist artifacts, CDS can use a Swift Storage or on a given filesystem (not recommended though).

Tests & Vulnerabilities Reports

CDS clearly displays the results of unit tests and vulnerabilities detected during builds.

Self-Service Project Creation

A CDS project is like a tenant. All users can create a CDS project, this project will bring together applications, environments, pipelines and of course workflows.

CDS projects are isolated from one another, but the same group may have access rights to multiple projects if you wish.

Execution Environment Customization

A worker model is a worker execution context. Let's say, you need to run a job that requires GoLang v1.11.5. In CDS, you just need to create a Go worker model, containing a go in version 1.11.5. A worker model can be a docker image, an openstack image, a VSphere image. Although CDS administrators can offer shared worker models, users can create their own template workers if they wish.

Self Service User’s Integrations

On a CDS project, you can add integrations like openstack, kubernetes, etc .... This will offer you features within your workflows. For example, with the Kubernetes integration, you can add your own cluster to your CDS project and thus be able to use the Deploy Application action to deploy your newly built application on your cluster, in helm format if you wish. You can of course develop your own integrations.

Multi-Tenancy

After reading the previous points, you've understood: self-service everywhere. All users can do their project / workflow / worker models / workflow templates / actions ... And run Jobs in a totally isolated environment. CDS projects are builders, on which you can add integrations. All this allows you to have only one instance of CDS for your entire company.

Command Line Interface (cdsctl): 100% features supported

All you can do with the UI is available via the Command-Line Interface (CLI), named "cdsctl". cdsctl is available on all the OS: darwin, freebsd, linux, openbsd ... cdsctl will allow you to create, launch, export, import your workflows, monitor your CDS, navigate through your projects, workflows. No need to go to the UI of CDS or your repository manager to check the status of your commit, git push && cdsctl workflow --track will display your workflow in your command line.

REST API & SDK

Do you have even more advanced automation needs, or the desire to develop an application that queries CDS? the REST API and the SDK will allow you to easily develop your software.

CDS Administration features

Self-Hosting

CDS is open-source since October 2016. You can install it freely in your company or at home. Some tutorials are available to help you start a CDS, docker-compose, Install with binaries.

High Availability / Scalability / Upgrade without User Downtime

High availability is a very important point for a CI / CD tool. CDS is stateless, nothing is stored on the filesystem. This makes it possible to launch several CDS APIs behind a load balancer. Thus, you can scale the API of CDS to your needs. It also allows upgrades of CDS in full day without impact for users. In production @OVH, CDS can be updated several times a day, without impacting users or stopping CDS workers. Asking your users to stop working while updating the Continuous Delivery tool would be ironic, isn't it? ;-)

Built-in Metrics

CDS natively exposes monitoring data. You will be able to feed your instance prometheus or warp10 using beamium.

Extensibility Plugins

A CDS job consists of steps. Each step is a built-in type action (script, checkoutApplication, Artifact upload / download ...). You can create your own actions, using existing actions - or develop your own action as a plugin. All languages are supported, as long as the language supports GRPC.

OS/Arch Compatibility

CDS is agnostic to languages and platforms. Users can launch Jobs on linux, windows, freebsd, osx, raspberry ... in Virtual Machine spawn on demand, in a docker container, on a dedicated host.

So, if your company uses multiple technologies, CDS will not be a blocker for building and deploying your internal software.

Auto-Scale OnDemand multi-cloud

One of the initial objectives of CDS at OVH: builder and deploy 150 applications as a container in less than 7 minutes. This has become reality since 2015. What is the secret key? Auto-Scale on Demand!

Thus, you can have hundreds of workers model and when necessary, CDS will start the workers using the hatcheries.

A hatchery is like an incubator, it gives birth to the CDS Workers and the right of life and death over them.

Several types of hatchery are available:

So yes, buzzwords or not, a multi-cloud Auto-scale OnDemand is a reality with CDS :-)

Some explanations on the comparison matrix

License

3-clause BSD

Issues
  • refactor/authentication (#4290)

    refactor/authentication (#4290)

    Description

    DOING

    • [x] Don't create authentified user while its local consumer has not been verified through it email address. @richardlt
    • [x] ui: edit "Patterns of configuration scripts" as admin. @richardlt
    • [x] ui: edit Worker model as admin. @richardlt
    • [ ] shared.infra should be removed from the worker consumer groups.
    • [x] api: update consumer if Ring change. @richardlt
    • [ ] doc: explain auth entities and scopes. @richardlt
    • [x] cdsctl: signup and reset (send mail that gives cdsctl instructions). @fsamin
    • [x] ui: component password strength, add it to reset page. @richardlt
    • [x] ui: password limit size (256). @richardlt
    • [x] cdsctl: merge refact context ctl #4576. @fsamin
    • [x] to merge #4573. @fsamin
    • [x] api: to encrypt data we should add some extra, use a value that allows to access the data (ex: key name). @fsamin
    • [x] instrumentation: router metrics. @fsamin
    • [x] ui: access /auth/signin should redirect if already signed in. @richardlt
    • [x] database downgrade
    • [x] user migration

    TODO

    • [x] Engine config file external key file management.
    • [x] update RUST client.

    TEST:

    • [x] it: create a test to init CDS to replace exiting scripting.
    • [x] it: test change group of a consumer should disabled or invalid part of it.
    • [x] it: clictl_access_token.yml
    • [x] it: clictl_action.yml
    • [x] it: clictl_admin_broadcast.yml
    • [x] it: clictl_admin_database.yml
    • [x] it: clictl_admin_integration_model.yml
    • [x] it: clictl_admin_metadata.yml
    • [x] it: clictl_admin_plugin_and_integrations.yml
    • [x] it: clictl_admin_services.yml
    • [x] it: clictl_common_options.yml
    • [x] it: clictl_group.yml
    • [x] it: clictl_project.yml
    • [x] it: clictl_template.yml
    • [x] it: clictl_template_apply.yml
    • [x] it: clictl_template_bulk.yml
    • [x] it: clictl_token.yml
    • [x] it: clictl_user.yml
    • [x] it: clictl_version.yml
    • [x] it: clictl_worker_model.yml
    • [x] it: sc_workflow_check_secret.yml
    • [x] it: sc_workflow_create_run_join.yml
    • [x] it: sc_workflow_create_simple.yml
    • [x] it: sc_workflow_edit_scheduler.yml
    • [x] it: sc_workflow_git_clone_tag.yml
    • [x] it: sc_workflow_integration_deploy_plugin_req.yml
    • [x] it: sc_workflow_key_install.yml
    • [x] it: sc_workflow_run_cache.yml
    • [x] it: sc_workflow_run_check_payload.yml
    • [x] it: sc_workflow_run_cmd_tmpl.yml
    • [x] it: sc_workflow_run_node_perm.yml
    • [x] it: sc_workflow_run_simple.yml
    • [x] it: sc_workflow_simple_serve.yml
    • [x] it: sc_workflow_stop_simple.yml
    • [x] it: sc_workflow_storage_awss3_artifact.yml
    • [x] it: sc_workflow_storage_awss3_worker_artifact.yml
    • [x] it: sc_workflow_storage_awss3_worker_cache.yml
    • [x] it: sc_workflow_storage_swift_artifact.yml
    • [x] it: sc_workflow_storage_swift_staticfiles.yml
    • [x] it: sc_workflow_storage_swift_worker_artifact.yml
    • [x] it: sc_workflow_storage_swift_worker_cache.yml
    • [x] it: sc_workflow_update_run.yml

    TO PLAN

    • [ ] cdsctl: signout (and clean context and secret)
    • [ ] cdsctl getting started: on first cdsctl run (without any context), run a login to configure all the things
    • [ ] api: update all requirements when renaming a group.
    • [ ] ui,api: add XSRF for signin local and ldap.
    • [ ] api: session lifetime should be based on last usage.
    • [ ] api: consumer "data" map should be scoped to authentication package.
    • [ ] Send mail on primary contact when a new consumer is added.
    • [ ] Active sessions managements, show all consulmers an session in an admin page.
    • [ ] instrumentation: Logger with session ID Field.
    • [ ] instrumentation: Expose TLS.
    • [ ] managed in memory cache of prepare statement in the gorpmapping layer
    • [ ] managed in memory cache of entities in the gorpmapping layer - to be used with sticky session on LB
    • [ ] remove deprecated tables

    DONE

    • [x] Test_checkWorkflowPermissionsByUser.
    • [x] ui: detach, delete, signin
    • [x] ui,api: regen consumers (should also invalidate old signin token).
    • [x] ui: show password not enough strong.
    • [x] api: username check syntax backend.
    • [x] api: consumer lifecycle. When a user is removed from a group, when a group is deleted, check if some consumers need to be revoked or updated.
    • [x] api: signin external should detect if there is a current consumer in session, then retrieve the user from it instead of username or email.
    • [x] api: implement session clean goroutine on API side.
    • [x] api: startup authentication drivers initialization.
    • [x] api: implement permActionBuiltinName.
    • [x] cdsctl: consumer & sessions management.
    • [x] cdsctl: login with external driver.
    • [x] cdsctl: if a signin token is given try to signin auto with builtin driver.
    • [x] LDAP authentication drivers
    • [x] api debug handlers getProfileIndexHandler
    • [x] updateGroupHandlerchecks number of remaining admins
    • [x] GetUserWorkflowEventssend email notifications- [x] postServiceRegisterHandler: for hatcheries, the user who created the used token must be admin of all groups in the token
    • [x] serviceAPIHeartbeat: fake user ?
    • [x] bookWorkerModelHandler: permModelID middleware
    • [x] Implement a unit test for checkGroupPermissions
    • [x] Implement a unit test for checkActionPermissions
    • [x] Implement a unit tests for checkTemplateSlugPermissions
    • [x] [ERROR] error executing query UPDATE services SET sig = $2 WHERE id = $1 with parameters services, id: pq: payload string too long
    • [x] Worker is revoked while building a job.
    • [x] admin: API symmecript rolling keys.
    • [x] list all TODOs in the code.
    • [x] ui,api: sse, send event based on permission need refacts. @fsamin
    • [x] getActionsForGroupHandler, getWorkerModelsForGroupHandler: move this in a permGroupName middleware, check usage of the handlers and change it. @richardlt
    • [x] Test_checkWorkerModelPermissionsByUser.
    • [x] hook: get 403 when at startup, check scopes. @fsamin
    • [x] Check the "triggered by" data when a workflow is run by a uService. @fsamin
    • [x] Implement a unit test for checkWorkerModelPermissions.
    • [x] secure the JWT cookie (http cookie attributes, path = "/"...). @richardlt
    • [x] services should stay up when register failed then retry (useful for cds init and upgrade). @fsamin
    • [x] test local hatchery
    • [x] test swarm hatchery
    • [x] test marathon hatchery
    • [x] test k8s hatchery
    • [x] test openstack hatchery
    • [x] ui: missing shared infra in new consumer modal. @richardlt
    • [x] api: handler /worker/model returns duplicate worker models
    • [x] Asynchronous handlers not working anymore.
    • [x] remove "communication with API" from worker model UI
    • [x] starting multiple hatcheries on the same engine failed: jobs_sse_count: cannot register view "jobs_sse_count"; a different view with the same name is already registered
    opened by richardlt 190
  • Refactor/users

    Refactor/users

    1. Description
    • [ ] When a user is removed from a group, removed from admins, when a group is deleted, check if some consumers need to be revoked or updated.
    • [ ] Use of a builtin signin token in CLI, should use the client that automatically signin. We can also signin manually.
    • [ ] Consumer "data" map should be scoped to authentication package.

    TODOs

    • [ ] cdsclt consumer & sessions management
    • [ ] getActionsForGroupHandler, getWorkerModelsForGroupHandler: move this in a permGroupID middleware
    • [x] api startup authentication drivers initialization
    • [x] LDAP authentication drivers
    • [x] api debug handlers getProfileIndexHandler
    • [x] updateGroupHandlerchecks number of remaining admins
    • [ ] GetUserWorkflowEventssend email notifications
    • [ ] Test_checkWorkerModelPermissionsByUser
    • [x] Test_checkWorkflowPermissionsByUser
    • [x] postServiceRegisterHandler: for hatcheries, the user who created the used token must be admin of all groups in the token
    • [x] serviceAPIHeartbeat: fake user ?
    • [x] bookWorkerModelHandler: permModelID middleware
    • [x] Implement a unit test for checkGroupPermissions
    • [ ] Implement a unit test for checkWorkerModelPermissions
    • [ ] Implement a unit test for checkActionPermissions
    • [ ] Implement permActionBuiltinName
    • [x] Implement a unit tests for checkTemplateSlugPermissions
    • [ ] Check the "triggered by" data when a workflow is run by a uService
    • [x] [ERROR] error executing query UPDATE services SET sig = $2 WHERE id = $1 with parameters services, id: pq: payload string too long
    • [x] Implement session clean goroutine on API side
    • [ ] Add XSRF signin local and ldap
    • [ ] username check syntax backend
    • [ ] Update all requirements that was using the group name
    refactor api 
    opened by fsamin 111
  • feat(smtpmock): refact server and add auth, create command line client

    feat(smtpmock): refact server and add auth, create command line client

    1. Description
    2. Related issues
    3. About tests
    4. Mentions

    @ovh/cds

    ready-to-merge 
    opened by richardlt 30
  • fix: take snapshot of secrets when running a workflow

    fix: take snapshot of secrets when running a workflow

    1. Description
    2. Related issues
    3. About tests
    4. Mentions

    @ovh/cds

    opened by sguiheux 26
  • feat(cdsctl): cdsctl context

    feat(cdsctl): cdsctl context

    opened by yesnault 24
  • fix(cdn): update swift lib + remove pipe

    fix(cdn): update swift lib + remove pipe

    1. Description
    2. Related issues
    3. About tests
    4. Mentions

    @ovh/cds

    opened by sguiheux 23
  • feat(cdn): artifact support

    feat(cdn): artifact support

    1. Description
    2. Related issues
    3. About tests
    4. Mentions

    @ovh/cds

    opened by bnjjj 22
  • test: add test on marathon and swarm hatchery

    test: add test on marathon and swarm hatchery

    1. Description
    2. Related issues
    3. About tests
    4. Mentions

    @ovh/cds

    opened by sguiheux 19
  • feat(cdn): store job step logs

    feat(cdn): store job step logs

    • [x] Store logs from step
      • [x] Update Item when last logs
      • [x] Add api ref information in logs send by worker
    • [x] Store Sevice Logs
      • [x] Use the same algo
      • [x] Update Book Handler to have all api_ref data in hatchery
      • [x] Add api ref information in logs send by hatchery
      • [x] Append Logs
      • [x] Send Status information ( send done message when deleting the containers )
        • [x] Swarm send status
        • [x] Kube send status

    @ovh/cds

    opened by sguiheux 19
  • feat(cdsctl): cdsctl admin database for cdn service

    feat(cdsctl): cdsctl admin database for cdn service

    $ cdsctl admin database unlock api id-to-unlock $ cdsctl admin database unlock cdn id-to-unlock $ cdsctl admin database delete api id-migration-to-delete $ cdsctl admin database delete cdn id-migration-to-delete $ cdsctl admin database list api $ cdsctl admin database list cdn

    Signed-off-by: Yvonnick Esnault [email protected]

    opened by yesnault 19
  • fix(ui): display spawn info when job is waiting into queue

    fix(ui): display spawn info when job is waiting into queue

    1. Description
    2. Related issues
    3. About tests
    4. Mentions

    @ovh/cds

    opened by sguiheux 1
  • docs: contact update

    docs: contact update

    opened by yesnault 1
  • feat: log if 401/403 on signin

    feat: log if 401/403 on signin

    opened by yesnault 2
  • fix(engine): export step + validate workflow

    fix(engine): export step + validate workflow

    1. Description
    2. Related issues
    3. About tests
    4. Mentions

    @ovh/cds

    opened by sguiheux 1
  • Leaving a comment to a (scheduled) run

    Leaving a comment to a (scheduled) run

    It could be great to leave a comment or a tag to a (scheduled) run, like : "checked", "not interesting this time" or "big issue here".

    opened by Linkid 0
  • Jobs waiting after installation

    Jobs waiting after installation

    I tried the docker compose installation guide, but all the workers are waiting. What's the posssible causes of this?

    image

    image

    opened by karfianto 4
  • fix(contrib,engine,sdk,tools) jwt-go CVE-2020-26160

    fix(contrib,engine,sdk,tools) jwt-go CVE-2020-26160

    Fix jwt-go CVE: https://github.com/advisories/GHSA-w73w-5m7g-f7qc Go 1.15+ is required

    @ovh/cds

    opened by mdouchement 9
  • feat(plugin): artifactory release bundle create plugin

    feat(plugin): artifactory release bundle create plugin

    opened by fsamin 3
  • gitlab clone with https basic auth doesnt work

    gitlab clone with https basic auth doesnt work

    CheckoutApplication
    [INFO] Starting step "CheckoutApplication"
    [INFO] Executing: git clone --depth 50 --branch master --recursive...  
    
    Executing: git reset --hard f176bbcbdba63dbebd76e3sdc44346962b60f64a
    [WARN] Cloning into '/app/hatchery-local/5f033981b0245d4e/130378c623fe9aegt67d100a13b5416f/run'...
    remote: HTTP Basic: Access denied
    fatal: Authentication failed for 'https://root:@gitlab.example.com/my-app/my-app.git/'
    [ERROR] Unable to git clone: Command fail: 128
    [INFO] End of step "CheckoutApplication"
    

    Notice how https://root:@gitlab.example.com/my-app/my-app.git/ only contains the username root but after the colon, does not contain the password i specified. This is a bug.

    opened by SnGmng 0
  • Archive Plugin - symlinks

    Archive Plugin - symlinks

    Hello,

    When using the builtin plugin-archive, symlinks are not compressed properly. Example:

    ls -l node_modules/.bin
     webpack-dev-server -> ~/node_modules/.bin/webpack-dev-server
    

    instead of

    ls -l node_modules/.bin
    webpack-dev-server -> ../webpack-dev-server/bin/webpack-dev-server.js
    

    This seems related to https://github.com/mholt/archiver/issues/222

    Thanks

    opened by marie-j 0
Releases(0.49.0)
goveralls - Go integration for Coveralls.io continuous code coverage tracking system.

goveralls Go integration for Coveralls.io continuous code coverage tracking system. Installation goveralls requires a working Go installation (Go-1.2

mattn 701 Oct 18, 2021
tbls is a CI-Friendly tool for document a database, written in Go.

tbls is a CI-Friendly tool for document a database, written in Go. Key features of tbls are: Document a database automatically in GFM format. Output d

Ken’ichiro Oyama 1.2k Oct 16, 2021
syncd是一款开源的代码部署工具,它具有简单、高效、易用等特点,可以提高团队的工作效率.

Syncd - 自动化部署工具 Syncd是一款开源的代码部署工具,它具有简单、高效、易用等特点,可以提高团队的工作效率。 码云GVP项目 文档 查看文档 特性 Go语言开发,编译简单、运行高效 Web界面访问,交互友好 权限模型灵活自由 支持自定义构建 支持Git仓库 支持分支、Tag上线 部署H

Dreamans 2k Oct 9, 2021
Powerful workflow engine and end-to-end pipeline solutions implemented with native Kubernetes resources. https://cyclone.dev

Cyclone Cyclone is a powerful workflow engine and end-to-end pipeline solution implemented with native Kubernetes resources, with no extra dependencie

Caicloud 1000 Oct 9, 2021
暴走皮皮虾之代码发布系统,是现代的持续集成发布系统,由后台管理系统和agent两部分组成,一个运行着的agent就是一个节点,本系统并不是造轮子,是"鸟枪"到"大炮"的创新,对"前朝遗老"的革命.

暴走皮皮虾之代码发布系统,是现代的持续集成发布系统,由后台管理系统和agent两部分组成,一个运行着的agent就是一个节点,本系统并不是造轮子,是"鸟枪"到"大炮"的创新,对"前朝遗老"的革命. 特点 基于golang编写,站在巨人肩膀上,充分利用golang的协程,channel还有高并发的特点

暴走皮皮虾 478 Sep 26, 2021
The simple ci server

duci duci [zushi] (Docker Under Continuous Integration) is a simple ci server. DSL is Unnecessary For CI Let's define the task in the task runner. Let

Shunsuke Maeda 67 Oct 8, 2021
vue.js(element框架)+golang(beego框架)开发的运维发布系统,支持git,jenkins版本发布,go ssh,BT两种文件传输方式选择,支持部署前准备任务和部署后任务钩子函数

该项目已停止开发,不再新增功能,十分欢迎开发同学贡献PR。本项目适合有vue+go开发经验的同学作为二次开发框架,不适合小白用户使用,请慎重选择! gopub(基于vue.js element框架+golang beego框架开发)是一个基于运维场景设计的企业级运维发布系统。配置简单、功能完善、界面

LC 1.3k Oct 16, 2021
:jeans:Multi-Package go project coverprofile for tools like goveralls

Package overalls Package overalls takes multi-package go projects, runs test coverage tests on all packages in each directory and finally concatenates

Go Playgound 106 Mar 6, 2021
A tool for testing, building, signing, and publishing binaries.

gomason Tool for testing, building, signing and publishing binaries. Think of it as an on premesis CI/CD system- that also performs code signing and p

Nik Ogura 51 Jul 26, 2021