Age | Commit message (Collapse) | Author | Files | Lines |
|
The logic should have been checking for stable/fraser and didn't account
for newer branches other than master.
Change-Id: I1164ce57338ba1734aa68c98bfe22a8a5f4209ac
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
With the move to upstream artifacts post-fraser the checks to use
upstream artifacts were relying on BRANCH == 'master'. This doesn't
scale as we preserve fraser functionality but add more branches like
gambia. Therefore inversing the logic to accomodate for new branches.
Change-Id: Ice17f6afd33744f44d253d320a194c3f6d02d8bf
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
Change-Id: Ie2d0a730801bc7f5bb784ee90e60e8e30562ef47
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
Now that we only build apex python rpm in master, we can afford to build
RPM everytime and ensure it builds correctly.
Change-Id: Ica1efe1cc2c3db0dfe1c5677b5ab47df121c0966
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
Change-Id: I92635178ddc354dd7773cd372a34d46f5ee0bf2a
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
There is a bug where if there are multiple builds queued and daily build
completes, the following iso verify job will try to use the workspace of
the completed daily build to get the iso file. However, if another
build job has already started it may clean and overwrite the workspace
of the daily build job, and the iso verify job will fail because the
file is now gone. This makes the build job copy the iso to a tmp
directory for apex iso verify to consume.
This should be safe since only one daily can run at a time on the host
and daily jobs build and iso verify have to always execute on the same
node.
Change-Id: Ie8e32c4abefbc311e505688d6da2b26ae08ed98f
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
Change-Id: I503250b2152686cb1c9168aeaa6a11f614b0e954
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
Since we do not install the package for build process we need to ensure
the PYTHONPATH is set to WORKSPACE so that build.py can find the libs it
needs in Apex.
Change-Id: I4e7f28ce5220206c7f4a8244199b00f762d72648
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
We dont need to use the apex/ci directory anymore and the ci scripts
should be in releng. A follow up patch will remove the ci/clean script
usage.
Change-Id: Ib2c7bd3d2dfee360bb13b42852ff2010a691a018
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
Change-Id: I2dae20c688ccd2cb690c01a843cb75d5743e129b
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
Change-Id: I8f283f6db366fc55a7eb52789affed7426521d17
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
Change-Id: I2de72d983035cbf79f9f09850cd98dfd349783ca
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
- Remove any build blockers on 'apex-build-*' jobs.
- Adds script to download latest build artifacts before deployment.
- Make each deploy download the needed artifacts before running.
- ARTIFACT_VERSION now set to dev for verify builds to indicate tarball
should be uploaded to artifacts repo
- apex.yml jjb is now generated by using apex-jjb-renderer
- scenarios are managed in scenarios.yaml
JIRA: APEX-328
Change-Id: I4a51565686bd2011a310c3926d8260cd4641dca5
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
Change-Id: Idc5ca86dbc51d83860f26244a4ed7d88015552d0
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
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>
|