<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Exchange Server">
<!-- converted from text --><style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left: #800000 2px solid; } --></style>
</head>
<body>
<div>
<div dir="ltr">This has been a goal for a while. There are some ftc commands you can run outside the container now. On a recent business trip (for the Automated Testing Summit) I made some patches for expanding the number of ftc commands that can be run outside
the container. However, I ended up deciding that integrating the patches in the master branch was too dangerous right now, just before the 1.4 release. I'm trying to pin down the 1.4 release real soon.</div>
<br>
<div dir="ltr">The most important commands to run outside docker are "ftc run-test" and "ftc gen-report". Of these, 'gen-report' should be easy to get running outside docker. 'run-test' has a few Jenkins dependencies, but I don't think it would be a huge effort
to make these optional.</div>
<br>
<div dir="ltr">I'm inclined to put the current work in my 'next' branch. Would you be interested in experimenting with this? If so, I could probably get something ready in a few days.</div>
<br>
<div dir="ltr">- - Tim </div>
<br>
<br>
<div dir="ltr">-------- Original Message --------</div>
<div dir="ltr">Subject: [Fuego] Fuego without Jenkins and Docker</div>
<div dir="ltr">From: Georg Piewald <gpi@mailbox.org></div>
<div dir="ltr">Date: Nov 5, 2018, 12:20 AM</div>
<div dir="ltr">To: fuego@lists.linuxfoundation.org</div>
</div>
<font size="2"><span style="font-size:10pt;">
<div class="PlainText">Hi,<br>
<br>
Can anyone give me a hint if it is easily possible to use Fuego without <br>
the accompanying Jenkins server and Docker container? I would like to <br>
run (i.e. build, deploy, execute, analyze) test cases and test plans <br>
just from command line and get the results in any machine-readable form. <br>
What bits and pieces would I need to do that?<br>
<br>
I hoped that it would be as simple as just using the fuego-core repo, <br>
but the configuration of boards and toolchains is in the fuego repo, so <br>
I will need that too.<br>
<br>
Thanks, Georg<br>
<br>
<br>
PS: Reason is that I have a rather complex build environment, with <br>
Jenkins and Docker already in place. If I run Fuego in a parallel <br>
infrastructure, it's not only extra maintenance effort, but also more <br>
complicated to establish communication between the two environments <br>
(trigger test runs directly from builds and report the results back).<br>
_______________________________________________<br>
Fuego mailing list<br>
Fuego@lists.linuxfoundation.org<br>
<a href="https://lists.linuxfoundation.org/mailman/listinfo/fuego">https://lists.linuxfoundation.org/mailman/listinfo/fuego</a><br>
</div>
</span></font>
</body>
</html>