Skip to content
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

Add GH action CI workflows to replace travis CI. #3312

Closed
wants to merge 3 commits into from
Closed

Add GH action CI workflows to replace travis CI. #3312

wants to merge 3 commits into from

Conversation

milosgajdos
Copy link
Member

@milosgajdos milosgajdos commented Dec 17, 2020

This is a WIP for replacing travis CI with GH actions.

Signed-off-by: Milos Gajdos milosgajdos83@gmail.com

@milosgajdos milosgajdos changed the title [WIP] Add GH action CI workflows to replace travis CI. Add GH action CI workflows to replace travis CI. Dec 18, 2020
@arkodg
Copy link
Contributor

arkodg commented Dec 18, 2020

hey @milosgajdos , thanks to @crazy-max , he raised a PR to add a dummy GHA (#3314) which enabled GH actions on this repo.
Merged it and can see the run https://github.com/docker/distribution/actions/runs/431561790
Rebasing your PR should trigger the new GHAs in your PR

Copy link
Contributor

@crazy-max crazy-max left a comment

Choose a reason for hiding this comment

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

@milosgajdos We can talk about it in the community Slack if you want

Comment on lines +32 to +36
- name: Validate DCO
env:
DCO_VERBOSITY: "-q"
GIT_CHECK_EXCLUDE: "./vendor:./script/validate/template"
run: git-validation "${DCO_VERBOSITY}" -run DCO,short-subject,dangling-whitespace
Copy link
Contributor

Choose a reason for hiding this comment

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

DCO can be handled directly through the DCO Probot App like we currently do on moby or buildx:

image

Just need to enable it for this repo.

Copy link
Member Author

Choose a reason for hiding this comment

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

Sounds good, as a first step I wanted to "copy" the existing travis build process and iterate on it once this repo has something working. The sooner this repo gets off travis the better.

Comment on lines +38 to +48
- name: Check go.mod matches the source code in the module
run: go mod tidy

- name: Vendor go modules
run: go mod vendor

- name: Checking for unused packages in vendor
run: |
git diff --exit-code -- go.sum go.mod vendor/
untracked=$(git ls-files --others vendor | wc -l | awk '{ print $1 }')
[[ "${untracked}" == "0" ]]
Copy link
Contributor

Choose a reason for hiding this comment

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

I think it would be more efficient to handle vendors validation (and update) through a dedicated Dockerfile to be able to reproduce locally. I've started to work on it but didn't saw your PR since yesterday ^^

Copy link
Contributor

Choose a reason for hiding this comment

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

As reference, you can find more info about the migration plan of buildx and buildkit in docker/buildx#451.

Copy link
Member Author

Choose a reason for hiding this comment

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

Gotcha. Yeah, that looks interesting. Need to look into that, thanks.

Btw, if you are keen on getting actions working I'm happy to close this PR. I just wanted to get the ball rolling quickly on this. I'm not hung on getting this into master. As long as it's done by anyone I'm happy.

Copy link
Contributor

Choose a reason for hiding this comment

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

@milosgajdos Yeah sure I can work on it if you don't mind!

Copy link
Member Author

Choose a reason for hiding this comment

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

Not at all! Thanks. I'm just glad someone else other than me cares about this now :-)

@milosgajdos
Copy link
Member Author

Closing this and leaving it in dedicated and capable hands of @crazy-max

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants