Age | Commit message (Collapse) | Author | Files | Lines |
|
Change-Id: If84b310afdca95a4ffa85de218b549cecf1916e2
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
Change-Id: I42eceade9d24a237c2a0f725db9e39de53c5be8a
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
RPM Spec files now live in a subdirectory under build
Change-Id: Ifaba7c50b236843fa799ace8e464d0b2d4280eb9
Signed-off-by: Michael Chapman <woppin@gmail.com>
|
|
This is for the CII best practices badge.
Let me know if this effects your project and how we can adapt any scripts
that consume this information
Change-Id: I96b39181a075f381d81802b8464f632eea149549
Signed-off-by: Aric Gardner <agardner@linuxfoundation.org>
|
|
Changes include:
- Removing deprecated Brahmaputra support
- Properly passing CACHE_DIRECTORY without file:// prefix
JIRA: APEX-167
Change-Id: Ic52e394d682d59662006a74ec2d32eef7bc3b6c2
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
Having builders embedded in jjb makes maintenance harder than what
it could be and error prone so the builders have been taken out.
Apart from this, the upcoming change proposals will split yml files
in 2, aligning with the rest and jobs in these files can reuse same
builders when they are converted in shell scripts.
This is the first change in series, trying to align job structure
with the rest in order to ease the effort required to troubleshoot
the deployments during release verification. The changes are
- take builders out of jjb (this patch)
- align the main CI jobs with the rest; 1 parent job per scenario/branch
which controls triggering and execution of 3 downstream jobs;
deploy, yardstick, functest
- split yml file in 2; ci jobs ending in apex-ci-jobs.yml (daily) and
project jobs ending in apex-project-jobs.yml. (verify, merge, build)
Change-Id: I01f8bf351f0cbafbee1f41ec24ad5c2c6f21316f
Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
|