Skip to content
#

Continuous integration

Automatically build and test your code as you push it upstream, preventing bugs from being deployed to production. A complementary practice to CI is that before submitting work, each programmer must do a complete build and run (and pass) all unit tests. Integration tests are usually run automatically on a CI server when it detects a new commit.

Here are 2,019 public repositories matching this topic...

nightwatch
pmorch
pmorch commented Feb 11, 2019

This is a dup of #1620. However #1620 was closed by the stale bot and I can't reopen it. The issue still has merit so I (re-)submit the issue.

For our purposes, we'd just like the file names easily parsable and since the terminal's ls -l sorts by filename by default, make sure the filenames start with the year, month, day, hour etc.

Currently, lib/testsuite/screenshots.js:18 has:

st
GaneshSPatil
GaneshSPatil commented Mar 2, 2020

In order to make the UI/UX consistent across all pages of GoCD, GoCD is rebuilding the Pipeline Config Edit Page (changing into a Single Page App).

As part of this page rewrite, following changes needs to be done on the plugins:

Breaking Changes

Task Plugins View:

GoCD Task Plugins implements Get Task View extension call, which

jhfoo
jhfoo commented Jul 23, 2018

There's a list of deprecation warnings installing Strider. A sample as follows:

npm WARN deprecated minimatch@2.0.10: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated mailcomposer@0.2.12: This project is unmaintained
npm WARN deprecated browserslist@1.4.0: Browserslist 2 could fail on re
fspegni
fspegni commented Dec 17, 2019

I cannot find any reference, in the documentation, about how the history of past builds is handled. Is it stored in memory? On files? On the database?

I'm running buildbot in docker (one container for the master, one for the worker, as in the "simple" scenario). Whenever I have to modify the master.cfg I have to

  • stop the master container
  • remove the master container
  • start again the mas
jx
cake
prezire
prezire commented Aug 22, 2017

The online WIKI says anyone can edit via GitHub. Is this safe and gets validated by anyone?

Expected behaviour

  • Detailed step by step instruction about the installation and setup.

Actual behaviour

  • Missing steps such as renaming of htaccess and configuration details such as phpci.yaml.
  • Location of phpci.yaml is not explicitly defined.
  • *Examples of directory and fi
emattias
emattias commented Jan 20, 2020

With a .stylelintrc.json file with:

{
  "extends": [
    "stylelint-config-sass-guidelines",
    "stylelint-config-prettier"
  ],
  ...
}

I get this error:

Error: Could not find "stylelint-config-sass-guidelines". Do you need a `configBasedir`?
    at module.exports (/home/linters/app/node_modules/stylelint/lib/utils/configurationError.js:8:28)
    at getModulePat
werf
tox
lastbackend
Wikipedia
Wikipedia

Continuous integration apps

Cirrus CI

Enjoy unlimited concurrency for fast and secure development cycle

Flaptastic

Manage flaky unit tests. Click a checkbox to instantly disable any test on all branches. Works with your current test suite

AccessLint

Find accessibility issues in your pull requests

BuildPulse

Automatically track flaky builds. Measure improvement over time. Install in less than a minute. Works with your current CI

Percy

Automated visual review platform

GuardRails

GuardRails provides continuous security feedback for modern development teams

Semaphore

Test and deploy at the push of a button

Buddy

One-click delivery automation for Web Developers

Codefresh

A modern container-based CI/CD platform, easily assemble and run pipelines with high performance

App Center

Continuously build, test, release, and monitor apps for every platform

See more Continuous integration apps
You can’t perform that action at this time.