make patch generator code more modular #30
No reviewers
Labels
No labels
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
wontfix
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
HugeSpaceship/patchwork!30
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "chore/separate-patch-generator-code"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
moves patch generator code out of the main package and into a dedicated "patch_generator" package and moves some of the symbol finding logic out of the main method, still not sure this is the best way of going about it but it should be more reusable in other tools
Pipelines as Code CI/patchwork-pr-lkkmb is running.
Starting Pipelinerun patchwork-pr-lkkmb in namespace hugespaceship-ci
You can monitor the execution using the Not configured PipelineRun viewer or through the command line by
using the tkn CLI with the following command:
tkn pr logs -n hugespaceship-ci patchwork-pr-lkkmb -fPipelines as Code CI/patchwork-pr-lkkmb has failed.
Task Statuses:
fetch
build
go-build
Failure snippet:
task go-build has the status "Failed":/retest
Pipelines as Code CI/patchwork-pr-gcx5b is running.
Starting Pipelinerun patchwork-pr-gcx5b in namespace hugespaceship-ci
You can monitor the execution using the Not configured PipelineRun viewer or through the command line by
using the tkn CLI with the following command:
tkn pr logs -n hugespaceship-ci patchwork-pr-gcx5b -fPipelines as Code CI/patchwork-pr-gcx5b has failed.
Task Statuses:
fetch
build
go-build
Failure snippet:
task go-build has the status "Failed":/retest
Pipelines as Code CI/patchwork-pr-2p9p6 is running.
Starting Pipelinerun patchwork-pr-2p9p6 in namespace hugespaceship-ci
You can monitor the execution using the Tekton Dashboard PipelineRun viewer or through the command line by
using the tkn CLI with the following command:
tkn pr logs -n hugespaceship-ci patchwork-pr-2p9p6 -fPipelines as Code CI/patchwork-pr-2p9p6 has failed.
Task Statuses:
fetch
build
go-build
Failure snippet:
task go-build has the status "Failed":Pipelines as Code CI/patchwork-pr-wwsgb is running.
Starting Pipelinerun patchwork-pr-wwsgb in namespace hugespaceship-ci
You can monitor the execution using the Tekton Dashboard PipelineRun viewer or through the command line by
using the tkn CLI with the following command:
tkn pr logs -n hugespaceship-ci patchwork-pr-wwsgb -fPipelines as Code CI/patchwork-pr-wwsgb has failed.
Task Statuses:
fetch
build
go-build
Failure snippet:
task go-build has the status "Failed":Pipelines as Code CI/patchwork-pr-47tfm is running.
Starting Pipelinerun patchwork-pr-47tfm in namespace hugespaceship-ci
You can monitor the execution using the Tekton Dashboard PipelineRun viewer or through the command line by
using the tkn CLI with the following command:
tkn pr logs -n hugespaceship-ci patchwork-pr-47tfm -fPipelines as Code CI/patchwork-pr-47tfm has successfully validated your commit.
Task Statuses:
fetch
build
go-build
patch-generate
upload-artifacts
cleanup
Pipelines as Code CI/patchwork-pr-zmpk2 is running.
Starting Pipelinerun patchwork-pr-zmpk2 in namespace hugespaceship-ci
You can monitor the execution using the Tekton Dashboard PipelineRun viewer or through the command line by
using the tkn CLI with the following command:
tkn pr logs -n hugespaceship-ci patchwork-pr-zmpk2 -fPipelines as Code CI/patchwork-pr-zmpk2 has successfully validated your commit.
Task Statuses:
fetch
build
go-build
patch-generate
upload-artifacts
cleanup