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

[Chore] Replace buildkite ci with github-actions #267

Closed
wants to merge 2 commits into from

Conversation

PhilTaken
Copy link
Contributor

Description

Related issue(s)

Fixes #

✅ Checklist for your Pull Request

Ideally a PR has all of the checkmarks set.

If something in this list is irrelevant to your PR, you should still set this
checkmark indicating that you are sure it is dealt with (be that by irrelevance).

Related changes (conditional)

  • Tests

    • If I added new functionality, I added tests covering it.
    • If I fixed a bug, I added a regression test to prevent the bug from
      silently reappearing again.
  • Documentation

    • I checked whether I should update the docs and did so if necessary:
  • Public contracts

    • Any modifications of public contracts comply with the Evolution
      of Public Contracts
      policy.
    • I added an entry to the changelog if my changes are visible to the users
      and
    • provided a migration guide for breaking changes if possible

Stylistic guide (mandatory)

✓ Release Checklist

  • I updated the version number in package.yaml.
  • I updated the changelog and moved everything
    under the "Unreleased" section to a new section for this release version.
  • (After merging) I edited the auto-release.
    • Change the tag and title using the format vX.Y.Z.
    • Write a summary of all user-facing changes.
    • Deselect the "This is a pre-release" checkbox at the bottom.
  • (After merging) I updated xrefcheck-action.
  • (After merging) I uploaded the package to hackage.

@PhilTaken PhilTaken requested a review from rvem January 16, 2023 14:17
@Martoon-00
Copy link
Member

Martoon-00 commented Jan 16, 2023

1 Warning
⚠️ Bad issue ID in branch name.
Valid format for issue IDs: #123 or chore.

Generated by 🚫 Danger

@PhilTaken PhilTaken force-pushed the philtaken/replace-buildkite branch from c07bd1e to 63f53eb Compare January 16, 2023 14:18
@PhilTaken PhilTaken changed the title Replace buildkite ci with github-actions [Chore] Replace buildkite ci with github-actions Jan 16, 2023
@rvem
Copy link
Member

rvem commented Jan 18, 2023

I propose to rebase this on top of #258 and merge this PR afterwards

@PhilTaken PhilTaken force-pushed the philtaken/replace-buildkite branch from 59fca08 to a31d78f Compare January 18, 2023 11:21
@PhilTaken PhilTaken force-pushed the philtaken/replace-buildkite branch 2 times, most recently from 2d2bd78 to b279861 Compare February 25, 2023 15:23
@PhilTaken
Copy link
Contributor Author

@rvem there are a bunch of license notices still mentioning 2022, should I update them? I just rebased the pr onto master

@PhilTaken
Copy link
Contributor Author

Now why does xrefcheck fail 🤔 I didn't change anything about those files

@rvem rvem force-pushed the philtaken/replace-buildkite branch 2 times, most recently from ea8f514 to 53b6672 Compare June 15, 2023 10:00
run: |
nix build -L .#docker-image
nix shell .#skopeo -c ./scripts/upload-docker-image.sh "docker-archive:$(readlink result)" "docker://docker.io/serokell/xrefcheck:latest"

Copy link
Contributor

Choose a reason for hiding this comment

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

Extra newline at the end of the file.

Generated by 🚫 Danger

@serokell serokell deleted a comment from Martoon-00 Jun 15, 2023
@serokell serokell deleted a comment from Martoon-00 Jun 15, 2023
@serokell serokell deleted a comment from Martoon-00 Jun 15, 2023
@serokell serokell deleted a comment from Martoon-00 Jun 15, 2023
@serokell serokell deleted a comment from Martoon-00 Jun 15, 2023
@serokell serokell deleted a comment from Martoon-00 Jun 15, 2023
@serokell serokell deleted a comment from Martoon-00 Jun 15, 2023
@serokell serokell deleted a comment from Martoon-00 Jun 15, 2023
@serokell serokell deleted a comment from Martoon-00 Jun 15, 2023
@serokell serokell deleted a comment from Martoon-00 Jun 15, 2023
@serokell serokell deleted a comment from Martoon-00 Jun 15, 2023
@serokell serokell deleted a comment from Martoon-00 Jun 15, 2023
@serokell serokell deleted a comment from Martoon-00 Jun 15, 2023
@serokell serokell deleted a comment from Martoon-00 Jun 15, 2023
@serokell serokell deleted a comment from Martoon-00 Jun 15, 2023
@serokell serokell deleted a comment from Martoon-00 Jun 15, 2023
@serokell serokell deleted a comment from Martoon-00 Jun 15, 2023
@serokell serokell deleted a comment from Martoon-00 Jun 15, 2023
@serokell serokell deleted a comment from Martoon-00 Jun 15, 2023
@serokell serokell deleted a comment from Martoon-00 Jun 15, 2023
@serokell serokell deleted a comment from Martoon-00 Jun 15, 2023
@serokell serokell deleted a comment from Martoon-00 Jun 15, 2023
path: result/bin/xrefcheck

- name: Xrefcheck itself
run: nix run . -L
Copy link
Member

Choose a reason for hiding this comment

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

We had

    retry:
      automatic:
        limit: 2

for it

Copy link
Member

Choose a reason for hiding this comment

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

Ugh, nick-fields/retry@v2.8.3 doesn't work well with nix:(

Copy link
Member

Choose a reason for hiding this comment

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

Does it mean there is no way for us to configure some step to automatically retry N times?

Copy link
Member

Choose a reason for hiding this comment

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

I think there is a way, but this will require some additional research to fix but I didn't want to spend too much time on this right now:(

@rvem rvem force-pushed the philtaken/replace-buildkite branch 3 times, most recently from 3d2cce9 to 7dab3af Compare June 19, 2023 12:33
@rvem rvem requested a review from Sereja313 June 19, 2023 12:37
@rvem rvem force-pushed the philtaken/replace-buildkite branch from 7dab3af to b3c67d4 Compare June 21, 2023 09:49
steps:
- uses: actions/checkout@v3
with:
submodules: true
Copy link
Member

Choose a reason for hiding this comment

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

What does it mean? Do we have submodules?

Copy link
Member

@Sereja313 Sereja313 Jun 26, 2023

Choose a reason for hiding this comment

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

Copy link
Member

Choose a reason for hiding this comment

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

Oh, ok.

@rvem
Copy link
Member

rvem commented Jun 26, 2023

Seems like I need to recreate PR to disable the buildkite check

@rvem rvem closed this Jun 26, 2023
@delete-merged-branch delete-merged-branch bot deleted the philtaken/replace-buildkite branch June 26, 2023 11:29
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.

6 participants