- Jan 28, 2025
-
-
Arran Walker authored
-
- Jan 10, 2025
-
-
Joe Burnett authored
Accept dir and file after /-/ Closes #16 See merge request !169
-
Joe Burnett authored
-
- Jan 07, 2025
-
-
Joe Burnett authored
-
Joe Burnett authored
-
- Jan 06, 2025
-
-
Joe Burnett authored
-
- Dec 13, 2024
-
-
Joe Burnett authored
v0.2.1 See merge request !167
-
Joe Burnett authored
-
Axel von Bertoldi authored
Ignore NoErrAlreadyUpToDate error when cloning a steps repo See merge request !166
-
Joe Burnett authored
Initial working dir CI_PROJECT_DIR in CI Closes #129 See merge request !165
-
- Dec 12, 2024
-
-
Axel von Bertoldi authored
The documentation for git.Repository.FetchContext states: Returns nil if the operation is successful, NoErrAlreadyUpToDate if there are no changes to be fetched, or an error. We need to ignore that "non"-error.
-
Joe Burnett authored
-
- Dec 10, 2024
-
-
Axel von Bertoldi authored
Upgrade tests to use the latest step runner See merge request !164
-
-
- Dec 06, 2024
-
-
Cameron Swords authored
Remove support for steps: syntax in JSON schema See merge request !145
-
Cameron Swords authored
-
- Dec 05, 2024
-
-
Cameron Swords authored
Increase end-to-end test coverage See merge request !151
-
Cameron Swords authored
-
- Dec 04, 2024
-
-
Cameron Swords authored
Add and test steps tutorial examples See merge request !163
-
Cameron Swords authored
-
- Dec 02, 2024
-
-
Axel von Bertoldi authored
Make the initial `Run` API call wait for the connection to be ready See merge request !161
-
Axel von Bertoldi authored
-
Axel von Bertoldi authored
Over in the runner repo, the steps-integration integration tests are failing withe following error: ERROR: Job failed (system failure): container exec on "fb713040a3f77c360ea1c8a7829c03c6a9f91cf3189952b03c9ae347df352e78" finished with: executing step request: running job request: rpc error: code = Unavailable desc = connection error: desc = "error reading server preface: io: read/write on closed pipe" The error appears to be caused by sending the Run request before the connection is actually ready. This CallOption waits for the connection to be ready before sending the Run request. See: * https://grpc.io/docs/guides/wait-for-ready/ * https://pkg.go.dev/google.golang.org/grpc#WaitForReady
-
Axel von Bertoldi authored
Note! To avoid a circular dependency I've had to move this to a separate package. However, because many of the tests reference the unexported `jobs` field, I used the export_test trick to make it accessible TO TEST IN THIS PACKAGE ONLY.
-
Axel von Bertoldi authored
-
Axel von Bertoldi authored
-
Axel von Bertoldi authored
This type just wraps the existing StepRunnerService and adds some test specific bits to it, like getting client connection and properly shutting down. Next I'll rework many of the existing tests to use this instead of the in-memory listener.
-
Axel von Bertoldi authored
I'll need use the code to get TCP listener at a free TCP port in another test type, so I'll refactor this a bit and export it.
-
- Nov 28, 2024
-
-
Axel von Bertoldi authored
The error trace in the relevant failed runner integration tests was actually sufficient to pinpoint the source of the failure, but ti could still be improved a bit.
-
Cameron Swords authored
Update the step file format to use a file with JSON on each line See merge request !159
-
Cameron Swords authored
-
- Nov 26, 2024
-
-
Cameron Swords authored
Log name of executable step See merge request !158
-
Cameron Swords authored
-
- Nov 22, 2024
-
-
Cameron Swords authored
The export_file format is the same as the output_file format See merge request !157
-
Cameron Swords authored
-
- Nov 19, 2024
-
-
Cameron Swords authored
Inline gitReference for simplicity and clarity See merge request !152
-
Cameron Swords authored
-
Cameron Swords authored
Merge union the changelog file See merge request !153
-
- Nov 18, 2024
-
-
Axel von Bertoldi authored
Remove obsolete service test See merge request !155
-
Axel von Bertoldi authored
Over in 31804b18 we removed explicit handling of context cancellation before job execution start. The test removed here was testing that case specifically. This test and the one immediately below it now effectively test the same scenario/code path, so this one is redundant.
-