-
Notifications
You must be signed in to change notification settings - Fork 304
Support repository-less builds #233
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
Comments
To do this now you can create an agent with a customized
and with meta-data |
I would also find this useful. I have a pipeline that has a build step which uploads the build as an artefact for multiple test steps (different environments) to run. Having to check out doesn't break anything, but it is unnecessary and does mean poking another hole in the sandbox so the test host(s) can reach Github. |
Just slated this for a 4.0 release, gotta have it! |
As an example, I have an ansible task that runs in a different repo (the ansible one) after each successful commit/tests on the active projects. Currently I do a little hack:
which works, but unfortunately triggers another source code checkout. Having metadata Ideally repository-less pipeline steps could co-exist in the same build agent config as git-triggered builds, which @toolmantim 's hack would block, I think. Is there an alternative arrangement? |
I ran into something similar today where some steps needed to run scripts on a mounted volume without needing a checkout. Instead of running a separate no-checkout agent, I threw together a quick plugin that wraps up a no-op 🎉 https://github.com/thedyrt/skip-checkout-buildkite-plugin |
Implemented in #909. |
In some you just want to run a pipeline that executes a script on a machine… there's actually no repository attached.
One way to support this, without any changes to the web UI, would be to allow people to
export BUILDKITE_REPO=""
in a pre-checkout hook. In this case the build would justmkdir -p $BUILDKITE_PROJECT_SLUG; cd $BUILDKITE_PROJECT_SLUG
, so the build directory is the same as the checked out ones (builds/my-org/my-builds
)The text was updated successfully, but these errors were encountered: