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,078 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

d3rp
d3rp commented Sep 19, 2019

For context: here's an excerpt from the buildbot source that is responsible for querying a secret from the hashicorp vault:
ret = json.get('data', {}).get('data', {}).get('value')

When reading vault documentation, the version data section is not emphasized leading to believe this is a typical key value store i.o.w. one has to land on the specific section covering the kv secrets e

jx
mcabrito
mcabrito commented Apr 15, 2020

Summary

I’m trying to use a Chart Repository by external Nexus, but I’d a problem in pipeline when I’m using the command:

jx step helm release

When this command do the upload chart file, my $CHART_REPOSITORY is changing and including the /api/charts

+ jx step helm release --verbose
DEBUG: Using helmBinary helm with feature flag: template-mode
DEBUG: Initialising Helm 'i
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

AppVeyor

Cloud service for building, testing and deploying Windows apps

Semaphore

Test and deploy at the push of a button

Cirrus CI

Enjoy unlimited concurrency for fast and secure development cycle

Codefresh

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

Flaptastic

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

Percy

Automated visual review platform

AccessLint

Find accessibility issues in your pull requests

Buddy

One-click delivery automation for Web Developers

App Center

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

Hound

Automated code reviews

BuildPulse

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

CircleCI

Automatically build, test, and deploy your project in minutes

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