CI

@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.

@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?

I was thinking maybe there is a way to compare all branches from two systems?

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?

@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.

@yuri could you explain why you need to push branches that have no new content? What is the objective of that?

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.

@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.