August 2018 - Zuul-announce - lists.opendev.org

zuul-jobs: Deprecation of the "emit-ara-html" role in favor of "ara-report"
by David Moreau Simard 14 Oct '18

14 Oct '18

Hello, The "emit-ara-html" [1] role, typically part of Zuul base jobs, has been used to generate ARA [2] static HTML Ansible reports. These files end up being stored as part of the logs of a job in the "ara" directory. This role has been superseded by "ara-report" [3] which provides the same functionality and defaults out of the box. This new role adds support for saving raw databases and is meant to be compatible with the use of the ARA sqlite WSGI middleware. This new middleware implementation may be of particular interest for Zuul operators since it translates to improved job performance and reduced storage overhead. For reference, the OpenStack Infrastructure implementation can be found here [4]. The announcement to openstack-dev can be found here [5] for additional details and context. Please refer to the ARA documentation for more details [6]. Feel free to reply to this thread or reach out to us in #zuul if you have any questions! [1]: https://git.zuul-ci.org/cgit/zuul-jobs/tree/roles/emit-ara-html [2]: https://github.com/openstack/ara [3]: https://git.zuul-ci.org/cgit/zuul-jobs/tree/roles/ara-report/README.rst [4]: https://review.openstack.org/#/q/project:openstack-infra/puppet-openstackci… [5]: http://lists.openstack.org/pipermail/openstack-dev/2018-March/128902.html [6]: https://ara.readthedocs.io/en/latest/advanced.html David Moreau Simard Senior Software Engineer | OpenStack RDO dmsimard = [irc, github, twitter]

1 1

zuul-jobs : Removal of readthedocs playbook
by Ian Wienand 08 Aug '18

08 Aug '18

Hello, The zuul-jobs:playbooks/python/readthedocs.yaml playbook is scheduled for removal [1] in two weeks on or about 27th August, 2018 (per the deprecation policy [2]). This playbook was used to trigger documentation builds on the readthedocs.org service. The playbook uses an API endpoint that is no longer available [3]. The trigger-readthedocs role is provided for anyone wishing to migrate to the authenticated API endpoint [4]. For more details, see [5]. Thanks, -i [1] https://review.openstack.org/#/c/583836/ [2] https://docs.openstack.org/infra/zuul-jobs/deprecation.html [3] https://github.com/rtfd/readthedocs.org/commit/a66bd56bada66f99c778aa424042… [4] https://zuul-ci.org/docs/zuul-jobs/roles.html#role-trigger-readthedocs [5] http://lists.openstack.org/pipermail/openstack-dev/2018-August/132836.html

1 0

Zuul 3.2.0 released
by corvus＠inaugust.com 08 Aug '18

08 Aug '18

The Zuul team is pleased to announce the release of Zuul 3.2.0. Download it from PyPI: https://pypi.org/project/zuul/ The release notes, included below, are also available in the documentation with hyperlink references: https://zuul-ci.org/docs/zuul/releasenotes.html#relnotes-3-2-0 New Features ============ * Zuul client got a new command ‘tenant-conf-check’. This command validates the schema of the tenant configuration and exits -1 if errors have been detected. * A new Ansible inventory variable zuul.child_jobs which is a list of the first level child jobs to be run after a job has finished successfully. * Jobs are now able to use the job.extra-vars which will use the --extra-vars flag when a job runs. * Project and project-templates may now create variables via a vars configuration entry. Jobs can access these at runtime in the same manner as job variables. * The supercedent pipeline manager has been added. It is designed to make post-merge artifact build pipelines more efficient. * The dequeue command has been added to the Zuul CLI. It allows operators to stop a given buildset at will. * It is now possible to use zuul_return to skip child jobs. You can use the zuul.child_jobs inventory variable to get a list of child jobs configured to run, then use zuul_return to modify the list. Any child job not in zuul_return zuul.child_jobs will be skipped. See Return Values for examples. Bug Fixes ========= * Project Templates are now branch-aware and behave more like project stanzas. If a template is defined on a branch, it will only apply to changes to that branch. * The timer trigger does not enqueue an event for every branch of every project anymore and it now only processes projects actually using the pipeline triggered by a timer.

1 0