search

patch-graph / pass-the-fork

[WIP] inject forked dependencies into CI builds
MIT License
1 stars 1 forks source link

build of master with injected deps shows up as broken "master" in Travis Branches view #2

Open cben opened 6 years ago

cben commented 6 years ago

Consider https://travis-ci.org/cben/manageiq-providers-openshift/builds/337188063, a gitjection build "of master" with custom before_install and INJECT_GEMS. It failed. It shows up as red master in Branches view — Travis doesn't understand that's not a representative build of master: https://travis-ci.org/cben/manageiq-providers-openshift/branches branches master 105 failed

Good news: that's in my fork of the repo.

https://travis-ci.org/ManageIQ/manageiq-providers-openshift/branches is all green. But if you run gitjection on your own project (or given permissions, on upstream repo instead of your fork) it will get confusing...

cben commented 5 years ago

Possible workaround: don't run build "of" master but of a special branch pushed by this tool.

Another possible reason to want this is when testing unmodified repo A with injected modified B, I need my fork of A to have an up-to-date branch with upstream A master, but automatically pushing master on my fork without asking is maybe rude; pushing a special branch is more polite? OTOH it'll cause branch pollution with time...