Jenkinsfile - opensearch 3.7.0 - #1277
Conversation
Signed-off-by: irapandey <ira.pandey2001@gmail.com>
|
Build-scripts PR with Dockerfile and patch file - ppc64le/build-scripts#8622 |
Signed-off-by: irapandey <ira.pandey2001@gmail.com>
Signed-off-by: irapandey <ira.pandey2001@gmail.com>
| environment { | ||
|
|
||
| // OpenSearch | ||
| OPENSEARCH_VERSION = "3.7.0" |
There was a problem hiding this comment.
Can we take OPENSEARCH_VERSION as a parameter
There was a problem hiding this comment.
I am trying to build 3.8.0 locally right now - if the same patch can be used 3.8.0 as well, I will take OPENSEARCH_VERSION as a param, it not, I would want to keep separate jenkinsfiles
There was a problem hiding this comment.
Instead of separate Jenkinsfiles you should maintain separate patch files and enable the job for any build version.
There was a problem hiding this comment.
Yup, on second thought, that's the approach I would take. Provided I was able to build 3.8.0 with the same approach
| ICR_REGISTRY = "icr.io" | ||
|
|
||
| IMAGE_NAME = "icr.io/ai-services-private/opensearch" | ||
| RELEASE_TAG_IMAGE_NAME = "icr.io/ai-services-cicd/opensearch" |
There was a problem hiding this comment.
are we pushing images in two namespaces?
There was a problem hiding this comment.
yes, pushing tag 3.7.0-ppc64le-{BUILD_NUMBER} to private for each job
and pushing3.7.0-ppc64le to ai-services-cicd when toggle is enabled
|
\hold |
3 participants
Jenkinsfile to build, validate and push Opensearch image v3.7.0 for AI-services