[Tendrl-devel] CentOS CI status (packages build trigger and validation tests)

[Timothy Asir Jeyasingh]

Brilliant job!, Perfectly done, Thank you.
We need only these packages for now.
Please fix those package validation test issues also.

Thanks and Regards,
Tim

On Tue, Aug 8, 2017 at 1:48 PM, Daniel Horák <dahorak at redhat.com> wrote:

> Hi Timothy,
>
> I've switched the master branch builds to tendrl/tendrl repo and it seems
> to work as expected[1,2].
>
> The build job for each package is configured to trigger once peer 4 hours,
> if there is any change in the repo/branch (hopefully it will work
> correctly).
>
> Also it is possible to trigger build of all packages manually via "Tendrl
> build- (master) - BUILD ALL PACKAGES" job. This will also trigger all the
> package validation tests.
>
> Now the jobs are configured to build following packages:
> - api
> - commons
> - gluster-integration
> - monitoring-integration
> - node-agent
> - ui
> Is the list correct? Or should I add some other (for example
> ceph-integration)?
>
> There are some issues with the package validation tests, I'll work on that.
>
> [1] https://ci.centos.org/view/tendrl-build-master/
> [2] https://ci.centos.org/view/Tendrl-master/
>
> Regards,
> Daniel
>
> On 08/08/17 09:31, Timothy Asir Jeyasingh wrote:
>
>> Hi Daniel,
>>
>> Please see my inline messages.
>>
>> Thanks,
>> Timothy
>>
>> On Fri, Aug 4, 2017 at 6:19 PM, Daniel Horák <dahorak at redhat.com <mailto:
>> dahorak at redhat.com>> wrote:
>>
>>     Hi Timothy,
>>
>>     I have few updates (and two questions) related to the CentOS CI
>>     jobs, mainly to the jobs for triggering new builds.
>>
>>     I've created jobs for building packages from master branch[1] (the
>>     job names are quite descriptive what they do).
>>
>>     The building process works quite fine, the packages are now stored
>>     in my testing copr repository[2].
>>     If you think, everything looks ok, we can switch them to the
>>     official tendrl copr repo.
>>     For that change, I need two things from you:
>>
>>     * Copr configuration file in following location:
>>          slave01.ci.centos.org:/home/tendrl/.copr-tendrl.conf
>>        If you don't have access to the slave01 machine, send me the
>>     content privately and I'll create it there.
>>
>> Have some access issue, i will send you a mail
>>
>>     * Which Copr repo is intended for the tendrl packages from master
>>     branch?
>>
>> tendrl/tendrl
>>
>>     There are also jobs for building packages from release[3] and
>>     feature[4] branches, but those jobs might not be fully ready as I'm
>>     not able to properly test them (until there will be new release or
>>     some feature branch).
>>
>> That's fine
>>
>>     The jobs containing "pkgval" are for package validation (rpmlint,
>>     rpmdeplint,...).
>>     If for example "Tendrl build- (master) - BUILD ALL PACKAGES" job is
>>     triggered, the all the packages from master branch are built and
>>     then respective validation test jobs are launched.
>>
>>     [1] https://ci.centos.org/view/tendrl-build-master/
>>     <https://ci.centos.org/view/tendrl-build-master/>
>>     [2]
>>     https://copr.fedorainfracloud.org/coprs/dahorak/tendrl-test-
>> master/packages/
>>     <https://copr.fedorainfracloud.org/coprs/dahorak/tendrl-
>> test-master/packages/>
>>     [3] https://ci.centos.org/view/tendrl-build-release/
>>     <https://ci.centos.org/view/tendrl-build-release/>
>>     [4] https://ci.centos.org/view/tendrl-build-feature/
>>     <https://ci.centos.org/view/tendrl-build-feature/>
>>
>>     Thanks,
>>     Daniel
>>
>>
>>
>