ci
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 123 public repositories matching this topic...
Created containers in dockerpool don't have a name that we can use when calling docker ps. This should be change to help the usage of repairnator.
We also use a deprecated method for the volumes, we should check and change that.
-
Updated
Jun 12, 2017 - Java
-
Updated
Jun 26, 2019 - Java
-
Updated
Jun 21, 2020 - Java
-
Updated
Dec 24, 2017 - Java
Steps to reproduce
- Use local example to run
docker-compose up - Login as admin/admin
- Add new gitlab repo
- Add new SSH key
- Create new project
- Press button
+ New build
Expected
"New build" form
Actual
URL:
http://.../project/1/build/create
Message:
Oops! An Error Occurred
The server returned a "500 Internal Server Error".
Something is
-
Updated
Jun 22, 2020 - Java
-
Updated
Jun 11, 2020 - Java
-
Updated
Jun 1, 2020 - Java
Clicking the restart button in the app triggers a "Restart Build" independent of whether you are currently viewing the whole build or one specific build matrix job. When in the view for the latter, the button should trigger "Restart Build" instead, similar to the Travis-CI web UI:

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