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

Replace defunct Travis CI integration with GitHub Actions #1266

Merged
merged 2 commits into from
Aug 19, 2022
Merged

Replace defunct Travis CI integration with GitHub Actions #1266

merged 2 commits into from
Aug 19, 2022

Conversation

jviotti
Copy link
Member

@jviotti jviotti commented Aug 5, 2022

The GitHub Actions setup is equivalent to the Travis CI configuration
with two differences:

  • The GitHub Action setup does not set the TAG environment variable,
    as it didn't seem like xml2rfc would consume that at all (unless I'm
    missing something)

  • The GitHub Action preserves the spec output (txt and html) as
    artifacts that can be downloaded after a successful run (to see the
    changes without having to locally render the specs)

Fixes: #1262
Signed-off-by: Juan Cruz Viotti [email protected]

The GitHub Actions setup is equivalent to the Travis CI configuration
with two differences:

- The GitHub Action setup does not set the `TAG` environment variable,
  as it didn't seem like `xml2rfc` would consume that at all (unless I'm
  missing something)

- The GitHub Action preserves the spec output (txt and html) as
  artifacts that can be downloaded after a successful run (to see the
  changes without having to locally render the specs)

Fixes: #1262
Signed-off-by: Juan Cruz Viotti <[email protected]>
@jviotti
Copy link
Member Author

jviotti commented Aug 5, 2022

@Relequestual I think you might need to enable the repository to run GitHub Actions from forks to be able to test this out. Once it is merged, we should also make this check required.

@gregsdennis
Copy link
Member

What I've had to do in json-everything is merge fork PRs into a secondary branch, just to get all of the actions to run properly (even when you get them running, they don't always have all the permissions they need). Then I have another PR to pull into the primary branch.

Copy link
Contributor

@handrews handrews left a comment

Choose a reason for hiding this comment

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

Looks good to me.

@Relequestual
Copy link
Member

I believe this will also upload requirements.txt to the artifact bundle.

.github/workflows/ci.yml Outdated Show resolved Hide resolved
@jviotti
Copy link
Member Author

jviotti commented Aug 15, 2022

Good catch @Relequestual ! Fixed.

@Relequestual Relequestual merged commit d4a16e5 into json-schema-org:main Aug 19, 2022
@Relequestual
Copy link
Member

I decided to merge this immediatly as our current CI simply doesn't work.

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.

Check on and fix CI checks on spec repo
4 participants