Skip to content

Migrate CI into GitHub workflows #2516

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 4 commits into
base: main
Choose a base branch
from

Conversation

vdemeester
Copy link
Member

Changes

  • .github/workflows: update codeql job
  • .github/workflows: add slack and retest workflows
  • .github/workflows: add a ci workflow…

Closes #2452

Submitter Checklist

These are the criteria that every PR should meet, please check them off as you
review them:

  • Includes tests (if functionality changed/added)
  • Run the code checkers with make check
  • Regenerate the manpages, docs and go formatting with make generated
  • Commit messages follow commit message best practices

See the contribution guide
for more details.

Release Notes

NONE

@tekton-robot tekton-robot added the release-note-none Denotes a PR that doesnt merit a release note. label Mar 13, 2025
@tekton-robot tekton-robot added the size/XL Denotes a PR that changes 500-999 lines, ignoring generated files. label Mar 13, 2025
@vdemeester vdemeester force-pushed the ci-in-workflows branch 3 times, most recently from 477255f to 7f70c7d Compare March 13, 2025 15:44
@waveywaves
Copy link
Member

/retest

@vdemeester
Copy link
Member Author

We can ignore pull-tekton-cli-build-tests, it will be removed 👼🏼

vdemeester added a commit to vdemeester/tektoncd-plumbing that referenced this pull request Mar 17, 2025
With tektoncd/cli#2516 those are no more needed.

Signed-off-by: Vincent Demeester <vdemeest@redhat.com>
@vdemeester
Copy link
Member Author

/retest

@vdemeester
Copy link
Member Author

/retest

@tekton-robot tekton-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Mar 19, 2025
Importing this from the tektoncd/pipeline repsitory.

Signed-off-by: Vincent Demeester <vdemeest@redhat.com>
… The goal is to remove the prow jobs.
This is imported from tektoncd/pipeline.

Signed-off-by: Vincent Demeester <vdemeest@redhat.com>
Let's share code 🙃.

Signed-off-by: Vincent Demeester <vdemeest@redhat.com>
@tekton-robot tekton-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Mar 21, 2025
paths-ignore:
- '**/*.md'
- '**/*.txt'
- '**/*.yaml'

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should this also include **/*.yml?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

probably 😛 not sure how many we have.

Comment on lines -45 to +65
uses: github/codeql-action/init@v3
uses: github/codeql-action/init@6bb031afdd8eb862ea3fc1848194185e076637e5 # v3.28.11

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🔒 🙏🏼


- name: Run tests
run: |
./hack/setup-kind.sh \

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This script seems to exist in the plumbing repo. Any reason we wouldn't want to reference it instead of copying it?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No valid reason I can see, I just ported what we had in tektoncd/pipeline.
I would probably want to create an issue to follow-up 😛

yamllint -c .yamllint $(find . -path ./vendor -prune -o -type f -regex ".*y[a]ml" -print | tr '\n' ' ')
- name: check-license
run: |
go install github.com/google/go-licenses@v1.0.0
Copy link
Member

@divyansh42 divyansh42 Mar 22, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we have any specific reason for using 1.0.0?
I can see 1.6.0 as the latest version

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, after 1.0.0 a behavior breaks our usage, we had to pin this in test-runner, …

@pratap0007
Copy link
Contributor

/retest

@pratap0007
Copy link
Contributor

/lgtm

@tekton-robot
Copy link
Contributor

@pratap0007: changing LGTM is restricted to collaborators

In response to this:

/lgtm

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@vdemeester
Copy link
Member Author

/retest

Copy link
Member

@divyansh42 divyansh42 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@tekton-robot tekton-robot added the lgtm Indicates that a PR is ready to be merged. label Mar 25, 2025
@vdemeester
Copy link
Member Author

/retest

@pratap0007
Copy link
Contributor

@piyush-garg @vinamra28 can you please review and merge this PR? Thanks!

@piyush-garg
Copy link
Contributor

/approve

@tekton-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: aThorp96, piyush-garg

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@tekton-robot tekton-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label May 3, 2025
@piyush-garg
Copy link
Contributor

/retest

2 similar comments
@divyansh42
Copy link
Member

/retest

@pratap0007
Copy link
Contributor

/retest

@waveywaves
Copy link
Member

/test pull-tekton-cli-integration-tests

@tekton-robot
Copy link
Contributor

@vdemeester: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
pull-tekton-cli-integration-tests a6d0b8e link true /test pull-tekton-cli-integration-tests

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@vdemeester
Copy link
Member Author

@waveywaves @piyush-garg the prow job will always fail 😛

@waveywaves
Copy link
Member

my ask for the retest was a bit mindless 😅 sorry about that

@vdemeester
Copy link
Member Author

I can force merge, but we need to remove the prow configuration. One "problem" is that it will remove the prow check for branches : tektoncd/plumbing#2510.

We'll have to figure out what we do about bugfix releases, but I would love for this to get merged now.

@tekton-robot tekton-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label May 19, 2025
@tekton-robot
Copy link
Contributor

@vdemeester: PR needs rebase.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. release-note-none Denotes a PR that doesnt merit a release note. size/XL Denotes a PR that changes 500-999 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Migrate most jobs in GitHub workflow
8 participants