continuous-testing
Here are 150 public repositories matching this topic...
Hi, thanks for a great plugin. We wonder, instead of ending up in the Jenkins job page when clicking jobname status in a box, we want to show another page on the Jenkins machine. As it is now, we first have to click in the box (your nice plugin) and then again on a link. That link shows a deeper result of the job with test results.
So we just want to skip one click and go directly to that result
Issue description or question
The coverage markers usually remain green for the lines that contain the test declaration in Jest. This is usually not a problem until those tests are collapsed (folded). When the tests are folded, then it becomes more difficult to tell that the tests did not run just by scanning the coverage markers.
For example:
 and I think it would be awesome if there was a template / manifests to deploy alloy on kubernetes.
This would make trying it out for evaluation purposes much easier.
Have no strong opinions on how a k8s example templates should be packaged but these are some options that come to my mind:
- simpl
Bug report
Expected behaviour?
All projects should be included or excluded without any delay.
Actual behaviour?
All projects are included or excluded with a noticeable delay.
Steps to reproduce?
- Add a feed with lots of projects (mine has ~140 projects)
- Click the "exclude all" button
This is because it loops through all projects and triggers an include/exclude
-
Updated
Jun 22, 2017 - Groovy
fledge beta
Git error. Command: git log origin/dev..dev
fatal: ambiguous argument 'origin/dev..dev': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions, like this:
'git [...] -- [...]'
Please suggest something to fix this...
Add by default in terrahub cli:
terraform.varFile: ['default.tfvars']if workspace == defaultterraform.varFile: ['default.tfvars', 'workspace/[workspace].tfvars']otherwisecomponent.mapping: ['.']default mapping of current folder
-
Updated
Jun 22, 2020 - Java
-
Updated
Jul 9, 2020 - C#
The package.json of our packages are missing some fields. For example, they have no repository field, which means the link to GitHub does not show up in npm.
-
Updated
Jul 10, 2020 - Python
-
Updated
Jul 11, 2019 - Python
Look at creating a custom GitHub Action for config-lint.
Resources:
https://github.com/actions/toolkit
https://help.github.com/en/actions/building-actions/creating-a-docker-container-action
-
Updated
Jun 30, 2018 - JavaScript
-
Updated
Jul 9, 2020 - JavaScript
Specially for failure scenarios
-
Updated
Jun 23, 2020 - Python
-
Updated
Jun 6, 2020 - JavaScript
-
Updated
Jun 24, 2020 - Python
Improve this page
Add a description, image, and links to the continuous-testing topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the continuous-testing topic, visit your repo's landing page and select "manage topics."

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