RHD-278 Index Red Hat Developer Blog #353
Conversation
|
Triggering build using a merge of 7a0ac2f on branch master: |
|
Build 669 is now running using a merge of 7a0ac2f on branch master: |
|
Related issue: RHD-278 |
|
Build 669 outcome was success using a merge of 7a0ac2f on branch master: |
1 similar comment
|
Build 669 outcome was success using a merge of 7a0ac2f on branch master: |
|
retest this please |
|
Triggering build using a merge of 7a0ac2f on branch master: |
|
Build 679 is now running using a merge of 7a0ac2f on branch master: |
|
Build 679 outcome was success using a merge of 7a0ac2f on branch master: |
|
The buzz query is returning no results: http://dcp2-searchisko.rhcloud.com/v2/rest/search?field=sys_url_view&field=sys_title&field=sys_contributors&field=sys_description&field=sys_created&field=author&field=sys_tags&field=sys_content_id&tag=softwarecollections&size=8&sys_type=blogpost&sortBy=new-create&from=0 I've not yet had chance to investigate why. This can't be merged until this is fixed. |
|
Build 679 outcome was success using a merge of 7a0ac2f on branch master: |
6 similar comments
|
Build 679 outcome was success using a merge of 7a0ac2f on branch master: |
|
Build 679 outcome was success using a merge of 7a0ac2f on branch master: |
|
Build 679 outcome was success using a merge of 7a0ac2f on branch master: |
|
Build 679 outcome was success using a merge of 7a0ac2f on branch master: |
|
Build 679 outcome was success using a merge of 7a0ac2f on branch master: |
|
Build 679 outcome was success using a merge of 7a0ac2f on branch master: |
|
I'm not sure what this fix has to do with the proposed issue... bad naming? |
|
Can one of the admins verify this patch? |
1 similar comment
|
Can one of the admins verify this patch? |
|
Triggering build using a merge of 7a0ac2f on branch master: |
|
Build 1156 is now running using a merge of 7a0ac2f on branch master: |
|
Build 1156 outcome was success using a merge of 7a0ac2f on branch master: |
|
Triggering build using a merge of 857682e on branch master: |
|
Build 1269 is now running using a merge of 857682e on branch master: |
|
Build 1269 outcome was failure using a merge of 857682e on branch master: |
1 similar comment
|
Build 1269 outcome was failure using a merge of 857682e on branch master: |
|
Build 1269 outcome was failure using a merge of 857682e on branch master: |
1 similar comment
|
Build 1269 outcome was failure using a merge of 857682e on branch master: |
|
retest this please |
|
Triggering build using a merge of 857682e on branch master: |
|
Build 1285 outcome was failure using a merge of 857682e on branch master: |
|
retest this please |
|
Triggering build using a merge of 857682e on branch master: |
|
Build 1294 is now running using a merge of 857682e on branch master: |
|
Build 1294 outcome was failure using a merge of 857682e on branch master: |
|
@wesbos you might need to speak to @RubyGemTSL about how to write / change the acceptance tests for the new code you're adding. cc @paulrobinson |
|
Build 1294 outcome was failure using a merge of 857682e on branch master: |
2 similar comments
|
Build 1294 outcome was failure using a merge of 857682e on branch master: |
|
Build 1294 outcome was failure using a merge of 857682e on branch master: |
|
@paulrobinson can you rebase please |
|
retest this please |
|
Replaced with another PR, which I'm about to raise. |
6 participants
No description provided.