We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
We currently integrate with GitHub actions like this:
- name: Build run: | curl --fail --location --silent --output bob https://function61.com/go/turbobob-latest-linux-amd64 && chmod +x bob CI_REVISION_ID="$GITHUB_SHA" ./bob build --publish-artefacts
If we released Bob as a native GitHub action, it would look something like:
- uses: function61/bob-action
Benefits: I think GitHub can cache the Docker image more aggressively.
Cons: not sure if this is possible, if Docker-based steps themselves can invoke Docker commands?
The text was updated successfully, but these errors were encountered:
Being worked at @ https://github.com/function61/turbobob-action
Sorry, something went wrong.
They can
Looks like one can directly run containers as well: https://docs.github.com/en/actions/using-jobs/running-jobs-in-a-container
No branches or pull requests
We currently integrate with GitHub actions like this:
If we released Bob as a native GitHub action, it would look something like:
Benefits: I think GitHub can cache the Docker image more aggressively.
Cons: not sure if this is possible, if Docker-based steps themselves can invoke Docker commands?
The text was updated successfully, but these errors were encountered: