[feedhenry-dev] Update to workflow for APB development

[Phil Brookes]

Hey John,

For pointing the oc cluster at your local docker, that is done from the
installer directory of the mcp-standalone cluster:

ansible-playbook playbook.yml -e "dockerhub_username=<dockerusername>"
-e "dockerhub_password=<dockerpassword>" -e
"dockerhub_org=<USE_THIS_VALUE>" --ask-become-pass

To move the images you need into your own org, you could do something like:

for image in aerogear-digger-apb android-app-apb cordova-app-apb
ios-app-apb 3scale-apb keycloak-apb; do docker pull
docker.io/feedhenry/$image:latest; docker tag
docker.io/feedhenry/$image:latest
​<YOUR_DOCKER_ORG>/$image:latest; docker push
<YOUR_DOCKER_ORG>/$image:latest; done
​

There might be a way to improve this (if we could pull the name of all the
*-apbs from the docker repo that would be ideal), but this will work for
now.​

Let me know if you have any thoughts.
Phil.
​

On Tue, Oct 10, 2017 at 9:01 PM, John Frizelle <jfrizell at redhat.com> wrote:

> Hi Phil,
>
> Thanks for the mail & agree with the suggestions.
>
> Are there any docs available that detail how to "point the ASB of your
> local oc cluster at your own docker org and push a copy of any APBs you
> wish to use into that org from the feedhenry org"?
>
> Cheers,
> John.
>
> --
> John Frizelle
> Chief Architect, Red Hat Mobile
> Consulting Engineer
>
> mobile: *+353 87 290 1644 <//+353872901644>*
> twitter:* @johnfriz*
> skype: *john_frizelle*
> mail: *jfrizell at redhat.com <jfrizell at redhat.com>*
>
>
>
>
> On 10 October 2017 at 15:55, Phil Brookes <pbrookes at redhat.com> wrote:
>
>> Hello Everyone,
>>
>> The current development workflow for APB’s is to run a local oc cluster
>> with the ASB scanning the feedhenry docker org for APB images. Then pushing
>> our development images to the feedhenry repo to test them.
>>
>> As more developers start using these images we increase the possibility
>> that they will pull a broken development image which could lead to a pretty
>> significant waste of developer time trying to identify the problem and
>> could also reduce developers trust in the feedhenry APB images.
>>
>> To address this it is now only possible to update the APB images in the
>> feedhenry org via a merged PR to the master branch of that images github
>> repo.
>>
>> To develop your own changes to an APB you should instead point the ASB of
>> your local oc cluster at your own docker org and push a copy of any APBs
>> you wish to use into that org from the feedhenry org. When building
>> experimental APB images you should update the image in that APB’s apb.yml
>> file, and use make DOCKERORG=<yourorg> to build and push the development
>> APB image.
>>
>> I will be updating the ansible installer in the mcp-standalone repo to
>> automatically pull the APB images from feedhenry and push them into the
>> specified dockerorg in the near future, so we have less manual work to do.
>>
>> Any questions or concerns, please let me know.
>>
>> Thanks,
>> Phil.
>> ​
>>
>> _______________________________________________
>> feedhenry-dev mailing list
>> feedhenry-dev at redhat.com
>> https://www.redhat.com/mailman/listinfo/feedhenry-dev
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/feedhenry-dev/attachments/20171011/4581607e/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: logo.png
Type: image/png
Size: 11472 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/feedhenry-dev/attachments/20171011/4581607e/attachment.png>