Bug #17527
closedSome branches are not being build in shaman
0%
Description
Compare http://ceph.com/gitbuilder.cgi vs https://shaman.ceph.com/builds/ceph/ for completeness of all branches.
Examples of missing:
wip-mon-forward_2016_09_27
master_2016_*
Updated by Zack Cerza over 7 years ago
- Project changed from Infrastructure to CI
Updated by Alfredo Deza over 7 years ago
- Status changed from New to 4
@yuri it looks like you aren't pushing any changes to these branches (correct me if I am wrong here). The system builds when new changes are pushed. We will need
to get creative on how to be able to build these branches of yours without new changes.
Updated by Alfredo Deza over 7 years ago
@yuri what is the intention on creating these branches with no new changes in them? what is the purpose?
Maybe if we can understand the "why" we can provide a better solution.
Updated by Yuri Weinstein over 7 years ago
@Alfredo - Maybe you are right, I added wip-yuri-testing2_2016_09_24_4 and I see it, but not sure why say master_2016_10_05 is not there?
Updated by Yuri Weinstein over 7 years ago
I was thinking maybe there is a way to compare all branches from two systems?
Updated by Andrew Schoen over 7 years ago
Yuri Weinstein wrote:
@Alfredo - Maybe you are right, I added wip-yuri-testing2_2016_09_24_4 and I see it, but not sure why say master_2016_10_05 is not there?
@Yuri, what did you do differently in wip-yuri-testing2_2016_09_24_4 than master_2016_10_05?
Did you create the branches in different ways?
Updated by Yuri Weinstein over 7 years ago
@Alfredo - nothing different ! one thing I noticed (maybe unrelated) when I push wip_<name> branch vs master_<name> branch, wip_<name> shows up on https://github.com/ceph/ceph in the yellow and master_<name> won't.
Maybe it can you some clues.
Updated by Alfredo Deza over 7 years ago
@yuri could you explain why you need to push branches that have no new content? What is the objective of that?
Updated by Yuri Weinstein over 7 years ago
One more instance wip-yuri-master_2016_10_13
@Alfredo - when we do master baseline tests, we date master branch with a date string to indicate when it was done to simplify analysis and troubleshooting and therefor it has no changes.
Updated by Andrew Schoen over 7 years ago
- Status changed from 12 to Resolved
We haven't seen this recently, if it happens again feel free to reopen.
Updated by Yuri Weinstein over 7 years ago
@Andrew Thomas I think we said it's "by design", a branch pushed with no changes won't build and this is different withe current build system. We may have to change if needed.