Skip to content

Check alternatives to GitHub actions and pages #19

Open

Description

@acka47

As usual, there are several options:

  • Set up a similar process for gitlab.com and maybe others.
  • Think about running the build process on hbz servers.
  • evaluate git hooks
  • ...

We should aim at making this as forge-agnostic as possible

Activity

  1. moved this from Backlog to Ready in SkoHubon Feb 5, 2024
  2. naturzukunft commented on Apr 15, 2024

    @naturzukunft
  3. naturzukunft commented on Apr 16, 2024

    @naturzukunft

    I currently have trouble with the links!

    solved, the problem was the missing inScheme

  4. acka47 commented on Apr 16, 2024

    @acka47
    MemberAuthor

    solved, the problem was the missing inScheme

    You might add an automatic validation step in your workflow, @naturzukunft, to be notified about things that will hinder a proper SkoHub build. The documentation for adding it in GitHub Actions is here: https://github.com/skohub-io/shapes?tab=-ov-file#add-validation-in-a-vocabulary-repository

  5. naturzukunft commented on Apr 16, 2024

    @naturzukunft

    @acka47 are we talking about a jena docker image by "Check with Docker"
    Do you maybe have a more detailed sample ?

  6. naturzukunft commented on Apr 16, 2024

    @naturzukunft

    Check with Docker"

    Ah, I found it in this terrible script ;-)
    https://hub.docker.com/r/skohub/jena

    Did I already say that I am not a script person :-)

  7. naturzukunft commented on Apr 16, 2024

    @naturzukunft

    In general, it would be helpful to move the script parts into files so that they can be reused more easily.

  8. sroertgen commented on Apr 16, 2024

    @sroertgen
    Contributor

    In general, it would be helpful to move the script parts into files so that they can be reused more easily.

    I don't really get what you mean. Can you please elaborate with what you mean to move the script parts into files?

    Here is the general idea:

    How to use the shape with your vocabs. There are multiple ways:

    To have all vocabularies in a github repository checked we wrote a bash script that we use in the CI pipeline. It's just a composition of the docker approach run for every .ttl file:

    curl -s https://raw.githubusercontent.com/skohub-io/shapes/main/scripts/checkForWarning.rq >> checkForWarning.rq
    find . -type f -name '*.ttl' | while read file; do
      # Adjust the file path to remove the './' part
      adjusted_file_path=$(echo "$file" | sed 's|^./||')
      echo "Processing $adjusted_file_path with Docker..."
      docker run --rm -v "$(pwd)/$adjusted_file_path:/rdf/test.ttl" skohub/jena:4.6.1 shacl validate --shapes https://raw.githubusercontent.com/skohub-io/shapes/main/skohub.shacl.ttl --data /rdf/test.ttl >> result.ttl
      validation_result="$(docker run --rm --mount type=bind,source=./checkForWarning.rq,target=/rdf/checkForViolation.rq --mount type=bind,source=./result.ttl,target=/rdf/result.ttl skohub/jena:4.6.1 arq --data /rdf/result.ttl --query /rdf/checkForViolation.rq)"
      echo $validation_result
      lines=$(echo "$validation_result" | wc -l )
      # Correct validation has 4 lines of output
      [[ ${lines} -eq 4 ]] || exit 1
    done
  9. naturzukunft commented on Apr 16, 2024

    @naturzukunft

    To have all vocabularies in a github repository checked we wrote a bash script that we use in the CI pipeline. It's just a composition of the docker approach run for every .ttl file:

    And if this batch script is in it's own file, you can also use it from gitlab ci !
    Currently it's in a github action, if i understand that right.

    However, i've added the validation now in my build.sh that i use locally.

    Info: i moved the gitlab project!

  10. sroertgen commented on Apr 16, 2024

    @sroertgen
    Contributor

    Alright. Got it. Will do so, when coming to this issue.

  11. moved this from Ready to Backlog in SkoHubon Sep 25, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

questionFurther information is requested

Type

No type

Projects

  • Status
    Backlog

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions