<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Clement Ozemoya on Medium]]></title>
        <description><![CDATA[Stories by Clement Ozemoya on Medium]]></description>
        <link>https://medium.com/@clementozemoya?source=rss-2802b0bc21c0------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*cH0yIvLwm6OgD7RZWDn6Kw.png</url>
            <title>Stories by Clement Ozemoya on Medium</title>
            <link>https://medium.com/@clementozemoya?source=rss-2802b0bc21c0------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 12:27:11 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@clementozemoya/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Agent Teams + Goals Finally Fixed the Recall Engine I’d Given Up On]]></title>
            <link>https://medium.com/@clementozemoya/agent-teams-goals-finally-fixed-the-recall-engine-id-given-up-on-d3425f212c7b?source=rss-2802b0bc21c0------2</link>
            <guid isPermaLink="false">https://medium.com/p/d3425f212c7b</guid>
            <category><![CDATA[ai-agent]]></category>
            <category><![CDATA[agent-team]]></category>
            <category><![CDATA[claude]]></category>
            <category><![CDATA[claude-code]]></category>
            <dc:creator><![CDATA[Clement Ozemoya]]></dc:creator>
            <pubDate>Wed, 10 Jun 2026 08:45:23 GMT</pubDate>
            <atom:updated>2026-06-10T20:44:09.249Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*OTsTbNxkAD2jvIT3.png" /></figure><p><em>Originally published at </em><a href="https://clementozemoya.com/posts/agent-teams-goals-fixed-my-recall-engine/">https://clementozemoya.com/posts/agent-teams-goals-fixed-my-recall-engine</a> <em>on June 10, 2026.</em></p><p>For months, my recall engine was quietly broken, and I’d made my peace with it.</p><p>I built it myself, on top of my <strong>PAI</strong> <a href="https://github.com/danielmiessler/Personal_AI_Infrastructure">harness</a>. The job is simple: when Claude needs something I told it before, the engine hands it all back in one quick call. One shot, no digging.</p><p>Long texts broke that. Feed it enough and it would choke, so Claude would go find the information itself instead, the slow way. Maybe <strong>70% accuracy</strong>, off the top. Not great, but good enough that I never bothered to fix it.</p><p>Then I’d been reading about <a href="https://code.claude.com/docs/en/agent-teams"><strong>Agent Teams</strong></a> and , and the idea of combining the two, and I figured this was the thing to test it on.</p><p>And the part that stuck with me wasn’t that it worked. It was realizing the moment I’d normally step in to help was the exact moment I should keep my hands off. I’ll get to why, but first the setup.</p><p>If you haven’t met them, the plain version: a <strong>Goal</strong> is you handing the agent a picture of “done” instead of a list of steps, and letting it judge its own progress against that picture until it gets there. A <strong>Team</strong> is more than one agent on the job, some doing the work, others checking it. Put them together and you don’t just get a task done. You get a task done, graded, and reopened wherever it’s still wrong.</p><p>You give it a goal with the /goal command, then simply tell Claude to start a team (interchangeable with agent team, team-mates, team-members).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*j9BZO5Kc9jL6VdJj.png" /></figure><p>It spins up new subagents as team members you can click into, watching each one work while the main agent coordinates them all. This is what makes it powerful: each team member is an entirely new Claude instance with its own fresh context window, and you can steer or divert any of them at any point.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ETM2WbDFVu6jR250.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*VE9uZpZenq-pwv4f.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*OElhXJon5EtG-RBh.png" /></figure><p>Thirty minutes in, I had one word for it: <strong>GOATed</strong>.</p><p>It didn’t just attempt the fix. It verified its own work, caught the problems it had created, and autonomously kept fixing them, on and on, without me.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*r1TgZH41SiTwYcq2.png" /></figure><p>And here’s the part I keep coming back to: I never had to step in.</p><p>That’s the quiet promise of teams. You can hand off for a long stretch and still jump back in to steer the moment you catch the agents wandering. I just didn’t need to. The main agent knew this domain better than I do, and honestly, if I <em>had</em> jumped in, I think I’d have made it worse. I’d have picked a smaller, safer path, the one I could fully picture in my head, and capped the whole thing at the edge of my own understanding. Left alone, it went further than I would have let it.</p><p>The result was the kind you don’t argue with: no new dependencies added, <strong>100% accuracy</strong>, on a query that’s now lightning fast. Nothing extra to maintain. Nothing new to worry about.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*8yxXmD-aTXUXuNry.png" /></figure><p>Somewhere in there I was reminiscing about my last few posts and noticed I’ve been writing about automation for years without ever clocking the pattern. I think I just like it. It makes me genuinely happy when something works seamlessly and quietly hands me back my time and energy, the things that mundane, repetitive work bleeds out of your day before you ever get to the real stuff.</p><p>Six years ago, the thrill was shipping an <a href="https://clementozemoya.com/posts/automated-android-deployments-fastlane-firebase/">Android beta build with a single <strong>Fastlane</strong> command</a>. Killing one manual step. This week it was a team of agents fixing a system I built and checking their own work while I sat on my hands. Same instinct, much bigger machine. I think teams and workflows are the point where agents start earning their keep: you can be far more ambitious with a prompt and a long handoff, and still keep your hand on the wheel for when you need it.</p><p>I’ll watch how it holds up over the next few days and follow up if it slips. Honestly, I don’t think it will. But that’s roughly what I said about the last version too, so we’ll see.</p><p>So, your turn: are you going to try <strong>Agent Teams</strong> and <strong>Goals</strong> together? Tell me the first thing you’d point them at, I’m curious whether yours is a mess like mine or something more ambitious.</p><p><em>Originally published at </em><a href="https://clementozemoya.com/posts/agent-teams-goals-fixed-my-recall-engine/"><em>https://clementozemoya.com</em></a><em> on June 10, 2026.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d3425f212c7b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Automated android deployments with Fastlane   and Firebase app distribution]]></title>
            <link>https://medium.com/@clementozemoya/automated-android-deployments-with-fastlane-and-firebase-app-distribution-b1d1905a4fe6?source=rss-2802b0bc21c0------2</link>
            <guid isPermaLink="false">https://medium.com/p/b1d1905a4fe6</guid>
            <category><![CDATA[firebase-app-distribution]]></category>
            <category><![CDATA[firebase]]></category>
            <category><![CDATA[android]]></category>
            <category><![CDATA[fastlane]]></category>
            <category><![CDATA[slack]]></category>
            <dc:creator><![CDATA[Clement Ozemoya]]></dc:creator>
            <pubDate>Sun, 23 Feb 2020 13:29:34 GMT</pubDate>
            <atom:updated>2020-02-23T13:29:34.081Z</atom:updated>
            <content:encoded><![CDATA[<h3>Automated android deployments with Fastlane 🚀 and Firebase app distribution</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tJovtBKLV8qHBam4I2yZeg.jpeg" /><figcaption>Photo by SpaceX on Unsplash</figcaption></figure><p>The code-compile-deploy process can be pretty hectic and take long periods of waiting for an average Android developer. When it comes to deploying your shiny new feature to test environments, the developer often has to build, test, generate an executable file (apk) and manually upload the apk by using <a href="https://firebase.google.com/docs/app-distribution"><strong>Firebase App Distribution</strong></a>, this requires a number of steps and a series of wait-time at intervals.</p><p>In this article, I will be talking about speeding up the process of deploying beta builds to testers with a run of a command.</p><h3>Getting Started with Fastlane</h3><p><a href="https://fastlane.tools/">Fastlane</a> is an open-source app automation platform that helps in automating development and release processes. It works for both Android and iOS platforms and is open source so you can check them out.</p><p>You can automate tasks like:</p><ul><li>Distributing beta builds to appropriate testers</li><li>Screenshots generation for your app’s store listing</li><li>Publishing a new release to the app store</li><li>Code signing</li></ul><h3>Automating beta build distribution</h3><p>Let’s focus on making our beta distribution processes a bit quicker. Then we can look at improving every other step of our deployment pipeline.</p><p><strong>Installing fastlane</strong></p><p>Install the latest Xcode command-line tools</p><pre>xcode-select — install</pre><p>Install fastlane</p><pre><em># Using Homebrew<br></em>brew install fastlane</pre><pre><em># Alternatively using RubyGems</em> <br>sudo gem install fastlane -NV</pre><p>Install Firebase CLI</p><p>Download the standalone binary for your OS if you don’t already have it by clicking <a href="https://firebase.google.com/docs/cli#install_the_firebase_cli\">here</a>, select the appropriate OS and navigating to the standalone binary tab. After downloading the binary you should make it executable by using this command</p><pre>chmod +x ./firebase-tools-macos</pre><p>Add the binary to your PATH to enable global access. Login with the <strong>login </strong>command and give firebase access.</p><p><strong>Setting up</strong></p><p>Open up terminal and change your directory to your project root folder and hit</p><pre>fastlane init</pre><p>You will be prompted to answer some setup questions:</p><ul><li>Confirm your package name</li><li>A path to service action json secret file — configuration used to connect and authenticate with Google play api. Press enter to skip this, as we won’t be doing that now</li><li>Confirm if you will be uploading builds to Google play — again skip this by pressing ‘<strong>n</strong>’</li></ul><p>Once completed, fastlane will automatically generate a configuration based on your answers to the prompts during setup. This might take a minute or two, hold tight. You may need to press enter multiple times to complete the setup process.</p><p>It basically generates a Fastlane folder in the root of your application which contains two important files: <strong>Appfile</strong> and <strong>Fastfile</strong></p><p>Appfile defines configuration global to your app, like your application identifier for example.</p><p>Fastlane uses <strong>Fastfile</strong> to store automation configurations, within it you’ll see different <em>lanes. </em>Each of these lanes is used to automate different and actions.</p><p>Make sure you’re using the latest version if you already had fastlane installed by updating using</p><pre>fastlane update_fastlane</pre><p>Add App Distribution to your fastlane by running the following command</p><pre>fastlane add_plugin firebase_app_distribution</pre><h3>Fastfile Configuration</h3><p>You do not need to change the contents of Appfile, the default works for now.</p><p>A typical Fastfile configuration looks like this</p><pre>fastlane_version &quot;2.68.0&quot;</pre><pre>default_platform :android</pre><pre>platform :android do</pre><pre>    lane :{<em>lane_name</em>} do<br>        # Take some action<br>        # Take some more action...<br>    end<br>    <br>    lane :{lane_name} do<br>        # actions<br>    end</pre><pre>end</pre><p>Where you get to input some actions in the lane to carry out a form of automation, possible actions include running git commands, building your app, distributing to deployment channels and sending a notification message and many more.</p><p>Input this into your Fastfile</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/2493e896935cf8e2280757d26c323d8e/href">https://medium.com/media/2493e896935cf8e2280757d26c323d8e/href</a></iframe><p>A fastfile can have several lanes, to run our fastlane command,</p><p>Let’s break it down, shall we?</p><p>The first thing to note is that right from the first command in the lane, we build our android app using this command</p><pre>build_android_app(task: &quot;assembleRelease&quot;)</pre><p>There are several other actions that you can take here but our immediate path to glory would be</p><p>build -&gt; distribute -&gt; notify</p><p>Next, distributing our app using <strong>firebase_app_distribution </strong>command</p><pre>firebase_app_distribution(<br>  app: &quot;1:123456789:android:abcd1234&quot;,<br>  testers: &quot;tester1@company.com, tester2@company.com&quot;,<br>  release_notes: changelog,<br>  groups: &quot;qa-team, dev-team&quot;,<br>  firebase_cli_path: &quot;/absolute/path/to/firebase/cli/binary&quot;<br>)</pre><p>This command takes a few parameters:</p><p><strong>app</strong>: firebase app id</p><p><strong>testers</strong>: comma-separated string list of emails of the testers, this can also be a text file of comma-separated email list</p><p><strong>release_notes: </strong>can either be a string or a file (My preferred method is a file, which can be updated right before deployment)</p><p><strong>groups: </strong>comma-separated list of group aliases to be added to the build</p><p><strong>firebase_cli_path: </strong>Absolute path to firebase cli binary</p><pre>slack(<br>  slack_url: &quot;https://hooks.slack.com/services/...&quot;,<br>  message: &quot;New build is available for testing&quot;,<br>  success: true,<br>  default_payloads: [:git_branch, :last_git_commit_message]<br>)</pre><p>This block enables a success/failure notification to be sent to a <a href="http://www.slack.com/">Slack</a> channel immediately after the process is complete. You must have completed setting up a hook on slack and get the url which is passed as <strong>slack_url</strong>. Set <strong>success </strong>to true. If you haven’t already done this, you can check out <a href="https://api.slack.com/messaging/webhooks">Sending messages using webhooks</a> for how to set it up.</p><p><strong>default_payloads </strong>specifies how much information is displayed in the slack message.</p><p>More options to customize the slack message can be seen <a href="https://docs.fastlane.tools/actions/slack/"><strong>here</strong></a><strong>.</strong></p><p>We add an error block after the lane to also notify the channel when an error occurs during the process, here we set slack success to <strong>false.</strong></p><pre>error do |lane, exception, options|<br><br>  # send slack failure notification<br>  slack(<br>      message: &quot;Build failed with exception: #{exception}&quot;,<br>      slack_url: &quot;https://hooks.slack.com/services/...&quot;,<br>      success: false,<br>      default_payloads: [:git_branch, :last_git_commit_message]<br>  )<br><br>end</pre><p>Indentation matters here so make sure you’re not missing anything.</p><h4>Running our beta deployment</h4><p>To deploy we just have to run the following command</p><pre>fastlane <em>beta</em></pre><p><strong>beta </strong>here can be any name you give your lanes, only the commands under that lane would be executed.</p><p>You may get an error that says App distribution could not find your app if you haven’t activated App distribution in your app like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1RlOGbgVZzeTya2VpVOIMQ.png" /><figcaption>App Distribution error</figcaption></figure><p>So head to your firebase console, Select YOURAPP — &gt; App distribution and click “Get started”. Then try again.</p><p><strong>SUCCESS</strong>!!!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YHBOtThVEc8Rq3qdUpXfqA.png" /></figure><p>A notification is posted on slack immediately the app distribution completes with a success message</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jBKsjUxW6ZhEujZl735BRw.png" /><figcaption>Slack success notification</figcaption></figure><p>An error message would look like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6uEGXj2Owyy-G-PvmVtvjw.png" /></figure><p>We can further improve our setup by creating another lane in our fastfile for distributing to google play store<em>. </em>Let’s leave this for another day.</p><p><em>I would like to hear your views and several other ways you are using fastlane on your projects!</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b1d1905a4fe6" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Setting up a continuous integration system on Android using CircleCi 2.0]]></title>
            <link>https://medium.com/@clementozemoya/setting-up-a-continuous-integration-system-on-android-using-circleci-2-0-6e51201b3e9b?source=rss-2802b0bc21c0------2</link>
            <guid isPermaLink="false">https://medium.com/p/6e51201b3e9b</guid>
            <category><![CDATA[android]]></category>
            <category><![CDATA[continuous-integration]]></category>
            <category><![CDATA[circleci]]></category>
            <dc:creator><![CDATA[Clement Ozemoya]]></dc:creator>
            <pubDate>Mon, 13 Aug 2018 12:38:20 GMT</pubDate>
            <atom:updated>2018-08-13T12:40:05.305Z</atom:updated>
            <content:encoded><![CDATA[<h4>Introduction</h4><p>In this article, I would be showing you how to set up continuous integration for Android projects. Now, for those of you who really don’t know much about continuous integration or don’t know what the benefits are, in simple terms, it is a software development practise where multiple integrations for changes are done frequently, including automated builds and testing for each changes integrated. This makes it easy to detect errors in the code early on with a realtime feedback loop.</p><p>I decided to use <a href="https://circleci.com/">CircleCi</a> for this mainly because it is cloud-based, does not require a dedicated server and the hassle that comes with that. There are other options available out there though, like <a href="https://jenkins.io/">Jenkins</a>, <a href="https://travis-ci.org/">TravisCi</a>, <a href="http://www.jetbrains.com/teamcity/">TeamCity</a>, <a href="http://codeship.com/">CodeShip</a> and many others. Check out <a href="https://stackify.com/top-continuous-integration-tools/?utm_referrer=https%3A%2F%2Fwww.google.com.ng%2F">this article</a> by Stackify which lists and breaks down their features.</p><h4>First Steps</h4><p>To start using CircleCi in your project, you must have it checked in to a git repository. CircleCi supports both <a href="http://www.github.com/">Github</a> and <a href="https://bitbucket.org/">bitbucket</a>.</p><p>Go to <a href="https://circleci.com/">CircleCi</a> and log in with either your github or bitbucket account and give circleci the appropriate authorization.</p><p>The next page shows you a list of projects in your profile with a “<strong>Setup project</strong>” button next to each one. When you click on “<strong>setup project</strong>” for the project you’re trying to configure, it displays an initial setup screen. You are required to add a configuration file to start building your project using circleci.</p><h4>Configuration file</h4><p>CircleCi uses a <a href="https://en.wikipedia.org/wiki/YAML">YAML</a> file to identify how you want your testing environmnet setup and how you want your builds, tests and deployment to be executed. You would have to add a .circleci directory in the root of your project and a config.yml file inside it, as par CircleCi 2.0, so the path looks like this <strong>.circleci/config.yml</strong></p><p>Add this to your config.yml</p><pre><em># Java Gradle CircleCI 2.0 configuration file<br>#<br># Check https://circleci.com/docs/2.0/language-java/ for more details<br>#<br></em><strong>version: </strong>2<br><strong>jobs:<br>  build:<br>    working_directory: </strong>~/repo<br><strong>    docker:<br>      </strong><em># specify the version you desire here<br>      </em>- <strong>image: </strong>circleci/android:api-28-alpha<br>      <br>      <em># Specify service dependencies here if necessary<br>      # CircleCI maintains a library of pre-built images<br>      # documented at https://circleci.com/docs/2.0/circleci-images/<br></em><br>    <strong>environment:<br>      </strong><em># Customize the JVM maximum heap limit<br>      </em><strong>JVM_OPTS: </strong>-Xmx3200m<br>      <strong>TERM: </strong>dumb<br>    <br>    <strong>steps:<br>      </strong>- checkout<br><br>      <em># Set Fabric Api Key with environment variables<br>      </em>- <strong>run: </strong>echo &quot;fabricApiKey=$FABRIC_API_KEY&quot; &gt;&gt; ~/repo/local.properties<br><br>      <em># Download and cache dependencies<br>      </em>- <strong>restore_cache:<br>          keys:<br>          </strong>- v1-dependencies-{{ checksum &quot;build.gradle&quot; }}<br>          <em># fallback to using the latest cache if no exact match is found<br>          </em>- v1-dependencies-<br><br>      - <strong>run: </strong>./gradlew androidDependencies<br><br>      - <strong>save_cache:<br>          paths:<br>            </strong>- ~/.gradle<br>          <strong>key: </strong>v1-dependencies-{{ checksum &quot;build.gradle&quot; }}<br>        <br>      <em># run tests!<br>      </em>- <strong>run: </strong>./gradlew lint test</pre><pre>      # Store test results<br>      - <strong>store_artifacts:<br>          path: </strong>app/build/reports<br>          <strong>destination: </strong>reports<br><br>      - <strong>store_test_results:<br>          path: </strong>app/build/test-results<br></pre><p>The first line here obviously states that we want our builds to run on version 2 of circleci (note that this article is about setting up circleci 2.0 which is recommended as version 1 is deprecated).</p><pre><strong>version: </strong>2</pre><p>Next is a <strong>jobs </strong>key, a job is usually a collection of steps and each one represents a phase in your build-test-deploy process. For this example we only need a build job, so everything else is going to be under that key.</p><p>For each job we can specify a working directory where our code will be checked out to and this would be used as the default working directory unless otherwise specified.</p><pre><strong>version: </strong>2<br><strong>jobs:<br>  build:<br>    working_directory: </strong>~/repo</pre><p>Next we add a docker image under the working directory to setup our initial environment. There is a list of publicly available container images that can be used ranging from android to other languages and platforms like javascript, node, python, etc. You can check out <a href="https://circleci.com/docs/2.0/circleci-images/">https://circleci.com/docs/2.0/circleci-images/</a> for information on other available images.</p><p>Now we add a list of steps in the build job, first a <strong>checkout </strong>step — to pull down our code so we can work on it.</p><p>If your project requires certain environment variables, there is an option to add these variables to our circleci build settings by clicking on the project setting on the dashboard and navigating to <strong>Environment Variables</strong> which can be located under <strong>Build Settings</strong>. Make use of the “<strong>Add Variable</strong>” button at the right side of the page.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0GWhUlF5V_1XdjZGTvCQ7g.png" /><figcaption>Environment Variables in Build settings of CircleCi project</figcaption></figure><p>For this project, I had a <strong>local.properties</strong> file on my local machine which wasn’t checked into git. Now for the build to run successfully I had to duplicate this on the circleci remote repository. This can be achieved by adding a <strong>run </strong>step with some basic bash command to the <strong>build </strong>job.</p><pre><strong>version: </strong>2<br><strong>jobs:<br>  build:<br>    working_directory: </strong>~/repo<br><strong>    ...</strong><br>    <strong>steps:<br>      </strong>- checkout</pre><pre>      <em># Set Fabric Api Key with environment variables<br>      </em>- <strong>run: </strong>echo &quot;fabricApiKey=$FABRIC_API_KEY&quot; &gt;&gt; ~/repo/local.properties</pre><p>This creates a local.properties file in the root of the project with the content: fabricApiKey=$FABRIC_API_KEY (This is automatically replaced by the value of the corresponding Environment variable)</p><p>After that, we have a <strong>restore_cache </strong>key, which basically restores the cache of the project dependencies.</p><pre>     ...<br>     - <strong>restore_cache:<br>          keys:<br>          </strong>- v1-dependencies-{{ checksum &quot;build.gradle&quot; }}<br>          <em># fallback to using the latest cache if no exact match is found<br>          </em>- v1-dependencies-</pre><p>Next, we run <strong>./gradlew androidDependencies</strong> to download the project dependencies</p><pre>- <strong>run: </strong>./gradlew androidDependencies</pre><p>After that, we have a <strong>save_cache </strong>key, this saves a cache of the project dependencies, this will be applied when next our build runs and our gradle files has not been changed in the <strong>restore_cache</strong> step</p><p>Then we are free to run our tests! <strong>./gradlew lint test</strong></p><p><strong>store_artifacts</strong> and <strong>store_test_results</strong> saves the results of the tests ran, this will be accessible on the build screen on your circleci dashboard.</p><pre>    ...<br>    - <strong>store_artifacts:<br>          path: </strong>app/build/reports<br>          <strong>destination: </strong>reports</pre><pre>    - <strong>store_test_results:<br>          path: </strong>app/build/test-results</pre><p>After setting up your config file and pushing it to your repository, you can now click on <strong>Start building </strong>on your project setup screen to see circleci run the build and test.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aKU8Wtw_61DPPuIo2hSQ8w.png" /><figcaption>Project setup screen on circleci</figcaption></figure><p>Immediately <strong>Start building</strong> is clicked, CircleCi runs the first build and automatically runs subsequent builds everytime a change is detected in the repo i.e when you push new changes to your repo.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NShWCk7OqGUQ7o5lBpKv4w.png" /></figure><p>For further information and more advanced configurations, checkout <a href="https://circleci.com/docs/2.0">CircleCi’s documentation</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6e51201b3e9b" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>