Adds jenkins build/publish/pipeline scripts to utils repo#23
Adds jenkins build/publish/pipeline scripts to utils repo#23IgorTodorovskiIBM wants to merge 5 commits intozopencommunity:mainfrom
Conversation
| @@ -0,0 +1,33 @@ | |||
| # Assumes utils repo is cloned into PWD | |||
There was a problem hiding this comment.
This is 'groovy' code correct?
| export PATH="$PWD/bin:$PATH" | ||
|
|
||
| # Get port name based on git repo | ||
| PORT_NAME=$(basename "${PORT_GITHUB_URL}") |
There was a problem hiding this comment.
shouldn't this be PORT_GIT_URL and not PORT_GITHUB_URL ?
| @@ -0,0 +1,33 @@ | |||
| # Assumes utils repo is cloned into PWD | |||
|
|
|||
There was a problem hiding this comment.
can you add a description? I'm not sure which env vars are set in /jenkins/.env and which (if any) are set before-hand? This appears to also only work for a GIT port and not a TARBALL port.
| export PORT_INSTALL_DIR="${PWD}/install" | ||
| mkdir -p ${PORT_INSTALL_DIR} | ||
|
|
||
| git clone -b "${BRANCH}" "${PORT_GITHUB_URL}" ${PORT_NAME} && cd ${PORT_NAME} |
There was a problem hiding this comment.
how is BRANCH related to the PORT_GIT_BRANCH ?
| @@ -0,0 +1,18 @@ | |||
| def repo = params.get("REPO") | |||
There was a problem hiding this comment.
As with the other jenkins files, a description would be good. Do we want to have some sort of correlation between 'sh' env vars and these jenkins vars? Should they be consistently named?
|
Closing in favour of zopencommunity/meta#11 |
2 participants
pipeline.jenkinsscripts drive the Jenkins pipeline, which calls the Build and Promote jobbuild.jenkinsscript builds a utils compliant project and generates a pax.Z artifactpublish.jenkinsscript publishes a pax.Z to as a github releasehttps://128.168.139.253:8443/view/Framework/ has been updated to call these scripts