[OpenIndiana-discuss] Latest update problems should be fixed now

[Till Wegmueller]

Hey Joshua

It can certainly be done, Jenkins listens to the Jenkinsfile inside 
oi-userland [0]. We also have a recent Vagrantfile in there to do 
ephemeral VM's [1]. We have some place for Automation on the Machine we 
have at Hetzner aswell and a VM we can use to provision nlipkg zones. 
VM's would need a Linux Physical Host. But I am not willing to foot the 
bill for that at the moment. The Question is how would we want to test 
that. Do we want to test the build on git changes? Is that enough or 
should we run the Testsuite?

[0] https://github.com/OpenIndiana/oi-userland/blob/oi/hipster/Jenkinsfile
[1] https://github.com/OpenIndiana/oi-userland/blob/oi/hipster/Vagrantfile
[2]


On 30/06/2022 18.00, Joshua M. Clulow via openindiana-discuss wrote:
> On Thu, 30 Jun 2022 at 12:32, Andreas Wacknitz <A.Wacknitz at gmx.de> wrote:
>> Am 30.06.22 um 20:56 schrieb Joshua M. Clulow via openindiana-discuss:
>>> Is there some way that we can gate future publishing to the public
>>> repository on a successful test install/update?
>> We need more volunteers as I already stated several times in the past.
>> I am doing most of everything with only very few helpers. I try to test
>> all PR's but my time and test environment is limited.
>> Besides me it is quite seldom that anybody is testing anything. The
>> situation is similar in all areas of the project you can imagine.
>> In the past I have been waiting for others to do tests but that happened
>> only very rarely and typically with days to weeks of delays.
> 
> So, to be clear, my question is not about looking for more manual
> testing.  I know we're all limited in time and resources.
> 
> I was more trying to ask about automated testing we could have done.
> Presumably there's already automation (Jenkins?) that does the build,
> and then publishes the packages.
> 
> It seems like it would be good if it was also able to create an
> ephemeral VM, then log in and use pkg to install the built bits (to
> make sure they can be installed), then reboot and make sure the
> machine at least comes up (as a basic smoke test).  If that all
> succeeds, _then_ push the packages to the public repository.
> 
> Hopefully having that automated would not then require a bunch of
> extra hands-on manual work for each PR?
> 
> 
> Cheers.
>