You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When Travis fails without logs it is impossible to tell what's going on without setting up all the environment locally. Which is tedious. Need a script to automate the task.
#!/bin/bash# [ ] get https://travis-ci.org/github/fedora-infra/fmn/jobs/684072799# [ ] parse instance line# instance: travis-job-e83417dd-07c1-44a4-b6d0-29b945442c5f travis-ci-ubuntu-1804-1582576938-a9b1ae58 (via amqp)# [ ] convert "travis-ci-ubuntu-1804-1582576938-a9b1ae58" -> "travisci/ci-ubuntu-1804:packer-1582574251-a9b1ae58"# [ ]
INSTANCE="travisci/ci-ubuntu-1804:packer-1582574251-a9b1ae58"# name of current dir
--NAME=$(basename "$PWD")
podman run -it -v "$(pwd):/app":Z "$INSTANCE" /bin/bash
# -t -- allocate TTY# -i -- keep STDIN open# su - travis# cp -r /app workdir# cd workdir# ^^^ copy, because of permissions (`travis` user can not write to volume)
When Travis fails without logs it is impossible to tell what's going on without setting up all the environment locally. Which is tedious. Need a script to automate the task.
https://stackoverflow.com/questions/21053657/how-to-run-travis-ci-locally contains some info, which might be outdated.
It should be automated. Take a look at https://github.com/nektos/act for an inspiration.
The text was updated successfully, but these errors were encountered: