Hi,

On behalf of Tizen development tools team and all other contributors, we are
pleased to announce the new bug-fix version of Tizen backend Jenkins service
(0.15.13) is released on download.tizen.org<http://download.tizen.org>, and 
already deployed on tizen.org<http://tizen.org>.

For more information about Services repositories, please refer to

  [Services Repository] http://download.tizen.org/services/archive/0.15.13/

Major Enhancements
=============
1. Two new jenkins jobs, sync-obs and re which will facilitate release 
engineer’s
daily work, was implemented by Eduard.

* sync-obs - Job to automatically sync content of scm/meta/obs to OBS.
Job runs on every update of master branch of scm/meta/obs and syncs its content
to OBS. In particular it syncs the following meta data for all active projects:
  - project config
  - project meta
  - all package links
  - all package aggregates
  - all package meta

Note: syncing also means removing meta data from OBS if it's not present in 
scm/meta/obs,
so current the job is running dry-run mode.

* re - job to perform the following operations:
  - accept submission
  - reject submission
  - rebuild submission or package (this is done by re-triggerring gbs service)
  - remove submission
  - lock submission (disabling build for prerelease project)
  - unlock submission

Note: origin job accept-or-reject-submission was removed as its functionality 
is included
into new re job.

2. Grant maintainer permission of prerelease project to release engineer
When create prerelease project, scan the maintainer list of OBS target project, 
for example
Tizen:IVI, grant maintainer permission of new prerelease project to those 
people. With it,
release engineer has fully control of prerelease project.

3. Fix aggregate package broken in prerelease project
Those aggregate packages always have specific meta config, not the same with 
project
config. Because OBS cannot follow that specific meta as expect when link to 
aggregate
package, those aggregate packages build will be broken in prerelease project. 
So copy
those package and meta into prerelease project when create it.

4. Fix link package issue in prerelease project
When submit one package, which has other derived package in target project, 
also create
that derived package in prerelease project to point to new package.

For more detail of this release, please refer to [Release Notes][1].

Links
====

[1]: 
http://download.tizen.org/services/archive/0.15.13/RELEASE_NOTES_JENKINS-SCRIPTS-COMMON.txt
      Jenkins Jobs 0.15.13 release notes


Thanks,
Tizen Development Tools Team
_______________________________________________
Dev mailing list
[email protected]
https://lists.tizen.org/listinfo/dev

Reply via email to