Update upload stage RPMs to new host #420
Conversation
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
ehelms
force-pushed
the
testing-new-rpm-host
branch
from
c3e43cf to
7e652a0
Compare
ehelms
force-pushed
the
testing-new-rpm-host
branch
from
7e652a0 to
6293ee1
Compare
| REPO_PATH="foreman/$VERSION/$PROJECT/$os" | ||
| fi | ||
|
|
||
| ssh "$USER@$HOST" "$REPO_PATH" "$REPO_PATH" "$OVERWRITE" "$MERGE" |
Check notice
Code scanning / shellcheck
Note that, unescaped, this expands on the client side. Note
|
This adds a script to handle publishing of release RPMs from staging that was previously done by Jenkins code and can replace all of it. This is helped by unifying stage and release to the same structure. The code that can be replaced -- https://github.com/theforeman/jenkins-jobs/blob/master/theforeman.org/pipelines/lib/release.groovy From examining that code and our usage, I think OVERWRITE and MERGE are now redundant and unused because we construct the structure when generating the staging repository and copy staging directly to release. I believe that means we can also simplify this script (https://github.com/theforeman/foreman-infra/pull/2118/files#diff-3e9ef4a756e78bc155bf6740dd575970bbeb6ceb4338f577e6b12723320e0168). |
ehelms
force-pushed
the
testing-new-rpm-host
branch
from
6293ee1 to
a20269e
Compare
This would accompany our change to where RPMs are hosted -- theforeman/foreman-infra#2118
For staging RPMs, the structure remains the same and nothing but the host will have to change when we are ready.