summaryrefslogtreecommitdiffstats
path: root/jjb/apex/apex-upload-artifact.sh
AgeCommit message (Collapse)AuthorFilesLines
2016-10-20Apex: removes opendaylight-sfc rpm from uploadTim Rozet1-2/+2
We no longer build a separate RPM for opendaylight-sfc, so this needs to be removed. Change-Id: I6dc10d4dbc1c42336f299e4b05955e95a67bb1a0 Signed-off-by: Tim Rozet <trozet@redhat.com>
2016-07-07Fix password for apex signingAric Gardner1-1/+1
Change-Id: Icd9dd9050f5eaee2733cacd925fb8c71c16b59d3 Signed-off-by: Aric Gardner <agardner@linuxfoundation.org>
2016-07-06Fix for gpg-agent.Aric Gardner1-3/+3
I might need to force call an $(eval gpg-agent) Buuut I think this should work. Change-Id: I6b3311bc1a1f19d74f4668bfe717fdd67757fc72 Signed-off-by: Aric Gardner <agardner@linuxfoundation.org>
2016-07-06For artifact signing we need the releng repo.Aric Gardner1-1/+7
Forgot to clone the releng repo so that my script is avaliable Change-Id: I5e8658123140c0c173138e597730263753099503 Signed-off-by: Aric Gardner <agardner@linuxfoundation.org>
2016-07-05This will enable artifact signing for apex uploadsAric Gardner1-0/+41
sources gpg_import_key.sh which: -installs gpg2 -imports key -grabs proper key based on $NODE_NAME only tries to sign if the key is correctly imported otherwise it will skip signing and just do the upload Keys have only been created for lf intel and ericsson labs Keys are only unique per company Master pubkey has not been sent to the key server Or brought into the web of trust. Lets see that this works as I expected rather than having to go through the pain of revoking these keys. Change-Id: Ifa4bc4e11407c53f8174f6c64945949bf66d6535 Signed-off-by: Aric Gardner <agardner@linuxfoundation.org>
2016-05-27Apex: Fixes artifact uploadTim Rozet1-4/+9
Fixes include: - SRPM extension was wrong, causing SRPMs to not be uploaded correctly - No more redirecting stderr to stdout - More print statements to Jenkins Change-Id: Ib96bb1efd967d9510d14a2e63bdf7d97b5d07cb2 Signed-off-by: Tim Rozet <trozet@redhat.com>
2016-05-26apex: Take builders out of jjbFatih Degirmenci1-0/+37
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>