move from current nightly publisher to per package publish via std ci (experimental)
Description
is blocked by
Activity

Former user November 7, 2016 at 8:51 AMEdited
Done
Can we start testing it without nsis and ovirt-release? When is a good time to start only on master? What we'll do is disable the nightly publisher job, rename the current repo folder and create a sym link from the current repo folder to the experimental (should be changed when it'll not be experimental anymore ) repo.

Eyal Edri November 2, 2016 at 2:54 PM
please verify all artifacts from node-ng jobs (3.6,4.0,master) are deployed to experimental.

Eyal Edri November 2, 2016 at 2:44 PM
I've talked with and the nsis-simple-plugin project will be fixed and have distro suffix.
please update when this project will be fixed.

Eyal Edri September 29, 2016 at 6:39 AM
Now that you synced all the projects to be experimental, see what we are missing in order to disable the master publisher.
To test it you can try to disable the master publisher and add soft link from latest-snapshot to experimental

Eyal Edri July 17, 2016 at 1:29 PM
do you know if repoman supports iso handling? We'll need to know how to add support for deploy-to-experimental jobs to push isos as well.
for e.g, for 3.6 i see these:
.
├── ovirt-node-iso
│ ├── ovirt-node-iso-3.6-0.999.201607131021.el7.centos.iso
│ ├── ovirt-node-iso-3.6-0.999.201607141021.el7.centos.iso
│ ├── ovirt-node-iso-3.6-0.999.201607151021.el7.centos.iso
│ └── ovirt-node-iso-3.6-0.999.201607161021.el7.centos.iso
├── ovirt-node-ng-installer-ovirt
└── oVirt-toolsSetup_3.6
Also,
not sure it supports .tar.gz files to upload all files under src dir.
Details
Assignee
Former userFormer user(Deactivated)Reporter
Eyal EdriEyal EdriPriority
High
Details
Details
Assignee

Reporter

Currently the nightly publisher is a single POF and highly dependent on job names of artifacts, and its enough for one job to get renamed or deleted to fail the entire publish of rpms.
Instead, we should move to how Lago is being deployed, which means each package is deploying itself rather than one central job.
It should be added as a standard CI feature, probably part of the build artifacts post merge code, so any new package that is added to standard ci can enjoy it.
We'll need to figure out how to create a central repo rather than a single repo per package which is what is done now in Lago.