Added rpm package as part of build by TejaswiniIBM · Pull Request #1149 · zopencommunity/meta

TejaswiniIBM · 2026-03-17T10:10:32Z

What type of PR is this? (check all applicable)

Description

Added support to generate and publish RPM

Related Issues

Related Issue #
Closes #

[optional] Are there any post-deployment tasks or follow-up actions required?

TejaswiniIBM · 2026-03-17T10:11:03Z

augment review

augmentcode · 2026-03-17T10:14:19Z

🤖 Augment PR Summary

Summary: This PR adds RPM generation and publishing alongside the existing pax.Z artifact flow.

Changes:

Adds a new --generate-rpm (-gr) option to bin/zopen-build and wires it into the install step (with RPM generation triggered after the pax archive is produced).
Introduces bin/zopen-pax2rpm, a new helper that generates an RPM spec from a zopen-generated pax archive and can optionally validate/build via rpmbuild.
Updates CI build invocation (cicd/build.groovy) to run zopen build with -gr (and signing via -sp).
Adjusts the Jenkins pipeline (cicd/pipeline.jenkins) to use the Port-Build-Test job and to copy artifacts from that job.
Extends the publish script (cicd/publish.groovy) to detect RPM artifacts under rpmbuild/RPMS and upload them to the GitHub release when present.

Technical Notes: RPM building is performed through rpmbuild using a configurable buildroot, with optional spec validation via rpmlint when available.

_{🤖 Was this summary useful? React with 👍 or 👎}

augmentcode

Review completed. 5 suggestions posted.

Comment augment review to trigger a new review at any time.

augmentcode · 2026-03-17T10:14:20Z

bin/zopen-build

    "-gp" | "--generate-pax")
      generatePax=true
      ;;
+     "-gr" | "--generate-rpm")


--generate-rpm currently only flips generateRPM=true, but the RPM creation logic is nested under the pax-generation flow, so using --generate-rpm by itself appears to do nothing (and won’t hit the “ensure --generate-pax” error). Consider either enforcing the pairing or making the behavior explicit to users.

Severity: medium

Other Locations

bin/zopen-build:2222

_{🤖 Was this useful? React with 👍 or 👎, or 🚀 if it prevented an incident/outage.}

bin/zopen-build

bin/zopen-pax2rpm

cicd/publish.groovy

augmentcode

Review completed. 6 suggestions posted.

Comment augment review to trigger a new review at any time.

augmentcode · 2026-03-17T10:14:52Z

bin/zopen-build

+      if ${generateRPM}; then
+        if [ -f "${paxFileName}" ]; then
+          printHeader "Generating RPM from ${ZOPEN_INSTALL_DIR}"
+	  rpm_deps=$(echo "${ZOPEN_RUNTIME_DEPS}" | xargs -n1 | sort -u | xargs)


rpm_deps is computed but never used; if this was meant to feed RPM Requires, it currently isn’t passed to zopen-pax2rpm, so generated RPMs may miss dependency metadata.

Severity: medium

_{🤖 Was this useful? React with 👍 or 👎, or 🚀 if it prevented an incident/outage.}

augmentcode · 2026-03-17T10:14:52Z

cicd/publish.groovy


 # PAX file should be a copied artifact
 PAX=`find . -type f -path "*install/*zos.pax.Z"`
+RPM=`find rpmbuild/RPMS -type f -name "*.rpm"`


RPM is populated via find, which can return 0 or multiple matches; in the multi-match case, [ -f "$RPM" ], basename, and github-release --file "$RPM" will fail or pick an unintended path.

Severity: high

Other Locations

cicd/publish.groovy:37

cicd/publish.groovy:66

cicd/publish.groovy:210

_{🤖 Was this useful? React with 👍 or 👎, or 🚀 if it prevented an incident/outage.}

augmentcode · 2026-03-17T10:14:52Z

bin/zopen-pax2rpm

+    if [[ "$source_file" == *.pax.Z ]]; then
+        cat >> "$output_file" << 'EOF'
+# Extract compressed pax archive
+pax -rzf %{SOURCE0}


The generated spec runs pax -r... %{SOURCE0} after cd into %{_builddir}/%{name}-%{version}; %{SOURCE0} is typically located in %{_sourcedir}, so extraction may fail at build time.

Severity: high

Other Locations

bin/zopen-pax2rpm:338

_{🤖 Was this useful? React with 👍 or 👎, or 🚀 if it prevented an incident/outage.}

augmentcode · 2026-03-17T10:14:52Z

bin/zopen-pax2rpm

+
+    if [ -n "$FOUND_PATH" ]; then
+        FOUND_PATH=${FOUND_PATH#./}
+        if [[ "$FOUND_PATH" == */pyz ]]; then


This heredoc emits [[ ... ]] into the spec’s %install script; RPM executes %install under /bin/sh, so non-POSIX [[ can break builds on systems where sh isn’t bash.

Severity: medium

_{🤖 Was this useful? React with 👍 or 👎, or 🚀 if it prevented an incident/outage.}

augmentcode · 2026-03-17T10:14:52Z

bin/zopen-pax2rpm

+
+    # Run rpmlint
+    local rpmlint_output
+    rpmlint_output=$(rpmlint "$spec_file" 2>&1)


With set -e, a non-zero rpmlint exit in rpmlint_output=$(rpmlint ...) will abort the script before the error/warning parsing runs, making --validate unexpectedly terminate.

Severity: medium

_{🤖 Was this useful? React with 👍 or 👎, or 🚀 if it prevented an incident/outage.}

augmentcode · 2026-03-17T10:14:53Z

bin/zopen-build

                        with the .rej extension.
  -g, --get-source      get the source and apply patch without building.
  -gp, --generate-pax   generate a pax.Z file based on the install contents.
+  -gr, --generate-rpm   generate an RPM package from the pax archive.


This PR also adds a top-level zopen-build file that appears as a binary/empty file in the checkout; if it’s intended as an entrypoint wrapper, it may be an accidentally committed artifact or missing content.

Severity: medium

_{🤖 Was this useful? React with 👍 or 👎, or 🚀 if it prevented an incident/outage.}

TejaswiniIBM · 2026-03-23T05:22:05Z

augment review

augmentcode

Review completed. 2 suggestions posted.

Comment augment review to trigger a new review at any time.

augmentcode · 2026-03-23T05:26:06Z

bin/zopen-pax2rpm

+
+    mkdir -p "$buildroot"/{BUILD,BUILDROOT,RPMS,SOURCES,SPECS,SRPMS}
+
+    if [ ! -f "$HOME/.rpmmacros" ]; then


If the user already has ~/.rpmmacros, rpmbuild may still use an existing %_topdir and ignore the script’s chosen --buildroot, which can make later steps (like finding artifacts under $buildroot/RPMS) inconsistent or fail unexpectedly. Consider ensuring the requested build root is honored even when ~/.rpmmacros already exists (or at least warning the user).

Severity: medium

_{🤖 Was this useful? React with 👍 or 👎, or 🚀 if it prevented an incident/outage.}

augmentcode · 2026-03-23T05:26:06Z

cicd/publish.groovy

-PAX=`find . -type f -path "*install/*zos.pax.Z"`
-METADATA=`find . -type f -path "*install/metadata.json"`
+PAX=`find . -type f -path "*install/*zos.pax.Z" | head -n 1`
+RPM=`find rpmbuild/RPMS -type f -name "*.rpm" | head -n 1`


find ... | head -n 1 will silently pick an arbitrary RPM if more than one is present (e.g., multiple output RPMs/arches), which can cause CI to upload the wrong asset without failing. Consider asserting there’s exactly one match or selecting deterministically.

Severity: medium

_{🤖 Was this useful? React with 👍 or 👎, or 🚀 if it prevented an incident/outage.}

TejaswiniIBM · 2026-03-23T05:52:44Z

augment review

augmentcode

Review completed. 2 suggestions posted.

Comment augment review to trigger a new review at any time.

augmentcode · 2026-03-23T05:56:09Z

bin/zopen-pax2rpm

+    # This will check syntax without actually building
+    # Use --nodeps to check syntax/prep logic without requiring local RPM DB to have all deps
+    local temp_output=$(mktemp)
+    if rpmbuild --define "_topdir $buildroot" -bp --nodeps "$spec_file" &> "$temp_output"; then


validate_spec_syntax calls rpmbuild --define "_topdir $buildroot" ..., but $buildroot isn’t set in this function (the script otherwise uses BUILDROOT/function parameters). This makes --validate potentially run against the wrong topdir (or an empty one) and fail unexpectedly.

Severity: medium

Other Locations

bin/zopen-pax2rpm:657

_{🤖 Was this useful? React with 👍 or 👎, or 🚀 if it prevented an incident/outage.}

augmentcode · 2026-03-23T05:56:09Z

bin/zopen-pax2rpm

+    local date=$(date "+%a %b %d %Y")
+
+    # Analyze the pax contents first (populate global DIR_STRUCTURE)
+    analyze_pax_contents "$source_file"


generate_spec calls analyze_pax_contents unguarded, but analyze_pax_contents can return 1 on an empty/failed listing; with set -e this will abort the whole script. That seems to contradict the “using default structure” warning path and can prevent spec generation in edge cases.

Severity: medium

_{🤖 Was this useful? React with 👍 or 👎, or 🚀 if it prevented an incident/outage.}

TejaswiniIBM · 2026-03-23T09:03:30Z

augment review

augmentcode

Review completed. 5 suggestions posted.

Comment augment review to trigger a new review at any time.

augmentcode · 2026-03-23T09:09:34Z

bin/zopen-build

+      if [ -f "${paxFileName}" ]; then
+        printHeader "Generating RPM from ${ZOPEN_INSTALL_DIR}"
+        rpm_deps=$(echo "${ZOPEN_RUNTIME_DEPS}" | xargs -n1 | sort -u | xargs)
+        PATH="${ZOPEN_ROOTFS}/usr/local/bin:${PATH}" "${MYDIR}/zopen-pax2rpm" "${paxFileName}" --summary "${ZOPEN_NAME} package" --requires "${rpm_deps}" --build


zopen-pax2rpm defaults --buildroot to ${HOME}/rpmbuild, but cicd/publish.groovy later searches for RPMs under ./rpmbuild/RPMS, so the publish step may not find the built RPM depending on HOME. Consider aligning the output location between build and publish (e.g., by explicitly setting the buildroot used here).

Severity: high

_{🤖 Was this useful? React with 👍 or 👎, or 🚀 if it prevented an incident/outage.}

augmentcode · 2026-03-23T09:09:34Z

bin/zopen-pax2rpm

+    mkdir -p "$buildroot"/{BUILD,BUILDROOT,RPMS,SOURCES,SPECS,SRPMS}
+
+    if [ ! -f "$HOME/.rpmmacros" ]; then
+        cat > "$HOME/.rpmmacros" << EOF


setup_rpmbuild writes ~/.rpmmacros, which can fail in CI where $HOME is read-only and can also have surprising side effects for users. Since the script already passes --define "_topdir ...", consider making the ~/.rpmmacros write best-effort (or avoiding it) so builds don't fail unnecessarily.

Severity: medium

_{🤖 Was this useful? React with 👍 or 👎, or 🚀 if it prevented an incident/outage.}

augmentcode · 2026-03-23T09:09:34Z

bin/zopen-pax2rpm

+# Function to analyze pax contents and categorize files
+analyze_pax_contents() {
+    local pax_file="$1"
+    local temp_dir=$(mktemp -d)


analyze_pax_contents creates temp_dir via mktemp -d but never uses it, and with set -e a missing/failed mktemp would abort the entire run. Consider removing this dependency or guarding it so content analysis can't hard-fail for an unused temp directory.

Severity: low

_{🤖 Was this useful? React with 👍 or 👎, or 🚀 if it prevented an incident/outage.}

augmentcode · 2026-03-23T09:09:34Z

cicd/publish.groovy

+  exit 1
+fi
+
+RPM=`find rpmbuild/RPMS -type f -name "*.rpm"`


Publish now hard-fails unless exactly one RPM exists under rpmbuild/RPMS; this will break publish runs for ports/builds that still only produce a pax artifact (or produce multiple RPM subpackages). Consider confirming the Port-Build job always generates exactly one RPM before enforcing this check.

Severity: medium

_{🤖 Was this useful? React with 👍 or 👎, or 🚀 if it prevented an incident/outage.}

augmentcode · 2026-03-23T09:09:34Z

bin/zopen-build

                        with the .rej extension.
  -g, --get-source      get the source and apply patch without building.
  -gp, --generate-pax   generate a pax.Z file based on the install contents.
+  -gr, --generate-rpm   generate an RPM package from the pax archive.


This PR also changes the binary zopen-diagnostics file (shown as a binary diff); please confirm this binary update is intentional and reproducible from source, not an accidentally committed artifact.

Severity: low

_{🤖 Was this useful? React with 👍 or 👎, or 🚀 if it prevented an incident/outage.}

TejaswiniIBM · 2026-03-26T05:25:11Z

augment review

augmentcode

Review completed. 4 suggestions posted.

Comment augment review to trigger a new review at any time.

bin/zopen-build

bin/zopen-pax2rpm

augmentcode · 2026-03-26T05:31:10Z

bin/zopen-pax2rpm

+    # Parse command line options
+    while [ $# -gt 0 ]; do
+        case "$1" in
+            --name)


Option parsing assumes every flag has a value (e.g., --name), and with set -e a missing $2 will cause a confusing shift error instead of a clear message. This can make CLI failures hard to diagnose for users/CI.

Severity: low

_{🤖 Was this useful? React with 👍 or 👎, or 🚀 if it prevented an incident/outage.}

augmentcode · 2026-03-26T05:31:10Z

bin/zopen-pax2rpm

+
+    # Check for rpmbuild if building or validating
+    if [ "$BUILD_RPM" = true ] || [ "$VALIDATE_SPEC" = true ]; then
+        echo "DEBUG: Current PATH is $PATH" >&2


check_required_tools always prints DEBUG: Current PATH... whenever --build or --validate is set, even when --verbose isn’t enabled. This can clutter normal output and makes “debug” logging hard to interpret.

Severity: low

_{🤖 Was this useful? React with 👍 or 👎, or 🚀 if it prevented an incident/outage.}

TejaswiniIBM · 2026-03-31T11:14:15Z

augment review

augmentcode

Review completed. 2 suggestions posted.

Comment augment review to trigger a new review at any time.

augmentcode · 2026-03-31T11:18:40Z

bin/zopen-pax2rpm

+    echo "# Pax file contents (first 100 entries):" >&2
+
+    if [[ "$pax_file" == *.pax.Z ]]; then
+        pax -rvzf "$pax_file" 2>&1 | head -100


bin/zopen-pax2rpm:213: list_pax_contents uses pax -r..., which extracts files into the current working directory (and piping to head can interrupt extraction), even though the function says it’s listing contents. Consider switching this helper to pax’s list mode so it can’t mutate the caller’s workspace.

Severity: high

_{🤖 Was this useful? React with 👍 or 👎, or 🚀 if it prevented an incident/outage.}

augmentcode · 2026-03-31T11:18:40Z

bin/zopen-build

+      if [ -f "${paxFileName}" ]; then
+        printHeader "Generating RPM from ${ZOPEN_INSTALL_DIR}"
+        rpm_deps=$(echo "${ZOPEN_RUNTIME_DEPS}" | xargs -n1 | sort -u | xargs)
+        if ! runAndLog "PATH=\"${ZOPEN_ROOTFS}/usr/local/bin:${PATH}\" \"${MYDIR}/zopen-pax2rpm\" \"${paxFileName}\" --summary \"${ZOPEN_NAME} package\" --requires \"${rpm_deps}\" --build --buildroot \"${ZOPEN_ROOT}/rpmbuild\""; then


bin/zopen-build:2229: This always passes --requires "${rpm_deps}"; if ZOPEN_RUNTIME_DEPS is empty/unset in some build contexts, that expands to an empty value and zopen-pax2rpm will fail option parsing (--requires demands a non-empty argument). Consider only including --requires when there’s at least one dependency to emit.

Severity: low

_{🤖 Was this useful? React with 👍 or 👎, or 🚀 if it prevented an incident/outage.}

TejaswiniIBM · 2026-03-31T11:55:22Z

augment review

augmentcode

Review completed. 3 suggestions posted.

Comment augment review to trigger a new review at any time.

augmentcode · 2026-03-31T12:00:56Z

bin/zopen-pax2rpm

+     --url "https://www.ibm.com"
+
+EOF
+    exit 1


usage() always exits with status 1, so --help will look like a failure in CI/scripts even when it’s just printing help output. Consider exiting 0 for the help path.

Severity: low

_{🤖 Was this useful? React with 👍 or 👎, or 🚀 if it prevented an incident/outage.}

augmentcode · 2026-03-31T12:00:56Z

bin/zopen-pax2rpm

+    fi
+
+    # Check for uncompress if dealing with .Z files
+    if [[ "$pax_file" == *.pax.Z ]] && ! command -v uncompress &> /dev/null; then


check_required_tools() hard-requires uncompress for *.pax.Z, but this script never invokes uncompress directly and relies on pax -z for (de)compression. This can cause a false “missing tool” failure on systems where pax handles the archive without uncompress (or uses gzip instead).

Severity: medium

_{🤖 Was this useful? React with 👍 or 👎, or 🚀 if it prevented an incident/outage.}

augmentcode · 2026-03-31T12:00:56Z

bin/zopen-pax2rpm

+RELEASE="1"
+LICENSE="Proprietary"
+BUILD_ARCH=$(uname -m 2>/dev/null || echo "s390x")
+PACKAGER_NAME="${USER}"


PACKAGER_NAME/PACKAGER_EMAIL are derived from $USER, which is often unset in non-interactive CI environments. If these end up empty, the generated spec’s %changelog header line may be malformed and could trigger rpmbuild/rpmlint warnings or failures.

Severity: low

_{🤖 Was this useful? React with 👍 or 👎, or 🚀 if it prevented an incident/outage.}

TejaswiniIBM · 2026-03-31T15:08:20Z

augment review

augmentcode

Review completed. 2 suggestions posted.

Comment augment review to trigger a new review at any time.

augmentcode · 2026-03-31T15:13:02Z

bin/zopen-pax2rpm

+  ME=$(basename "$0")
+  MYDIR="$( cd "$(dirname "$0")" >/dev/null 2>&1 && pwd -P )"
+  INCDIR="${MYDIR}/../include"
+  if ! [ -d "${INCDIR}" ] && ! [ -f "${INCDIR}/common.sh" ]; then


bin/zopen-pax2rpm:30: The setupMyself guard only errors when both the include dir is missing and common.sh is missing (&&), so if the directory exists but common.sh is absent/mispackaged the script will fall through and fail later at the . with a less clear error.

Severity: low

_{🤖 Was this useful? React with 👍 or 👎, or 🚀 if it prevented an incident/outage.}

augmentcode · 2026-03-31T15:13:02Z

bin/zopen-build

+        if [ -n "${rpm_deps}" ]; then
+          cmd="${cmd} --requires \"${rpm_deps}\""
+        fi
+        if ! runAndLog "${cmd}"; then


bin/zopen-build:2233: runAndLog executes via eval, so building cmd from variables like paxFileName/ZOPEN_NAME means any unexpected shell metacharacters or quotes in those values can break the command line or be interpreted as additional shell syntax.

Severity: medium

_{🤖 Was this useful? React with 👍 or 👎, or 🚀 if it prevented an incident/outage.}

TejaswiniIBM · 2026-04-02T04:03:52Z

augment review

augmentcode

Review completed. 3 suggestions posted.

Comment augment review to trigger a new review at any time.

augmentcode · 2026-04-02T04:08:55Z

bin/zopen-pax2rpm

+    fi
+    echo "Detected nested root: $ROOT_DIR"
+    mkdir -p %{buildroot}%{install_dir}
+    cp -RP "$ROOT_DIR"/* %{buildroot}%{install_dir}/


bin/zopen-pax2rpm:279 The generated %install snippet copies with "$ROOT_DIR"/* (and later "$SUB_DIR"/* / *), which will skip dotfiles like .env/.depsenv and can also fail when a directory contains only dotfiles (glob expands to a literal *). This risks producing RPMs missing critical runtime files or causing build-time copy failures.

Other locations where this applies: bin/zopen-pax2rpm:285, bin/zopen-pax2rpm:290

Severity: high

_{🤖 Was this useful? React with 👍 or 👎, or 🚀 if it prevented an incident/outage.}

augmentcode · 2026-04-02T04:08:55Z

bin/zopen-pax2rpm

+generate_files_list() {
+    cat << 'EOF'
+%defattr(-,root,root,-)
+%{install_dir}


bin/zopen-pax2rpm:308 The generated %files list only contains %{install_dir}, which typically won’t include the directory contents; rpmbuild commonly errors with “Installed (but unpackaged) file(s) found” (or produces an RPM with an empty payload). Consider ensuring the %files section captures the installed tree under %{buildroot}%{install_dir}.

Severity: high

_{🤖 Was this useful? React with 👍 or 👎, or 🚀 if it prevented an incident/outage.}

augmentcode · 2026-04-02T04:08:55Z

bin/zopen-pax2rpm

+# Default values
+RELEASE="1"
+LICENSE="Proprietary"
+BUILD_ARCH=$(uname -m 2>/dev/null || echo "s390x")


bin/zopen-pax2rpm:41 BUILD_ARCH is taken directly from uname -m, but some environments return values that RPM may not recognize as valid arches (which can make BuildArch: invalid or mislabel the artifact). Consider normalizing/mapping the output to RPM architecture names expected by your target build environment.

Severity: medium

_{🤖 Was this useful? React with 👍 or 👎, or 🚀 if it prevented an incident/outage.}

TejaswiniIBM · 2026-04-06T14:43:04Z

augment review

Signed-off-by: TejaswiniIBM <tejaswini.r1@ibm.com>

augmentcode

Review completed. 1 suggestion posted.

Comment augment review to trigger a new review at any time.

augmentcode · 2026-04-06T22:44:05Z

bin/zopen-pax2rpm

+    is_os_layout=false
+
+    # Analyze each file
+    echo "$pax_listing" | while IFS= read -r line; do


analyze_pax_contents sets has_* flags inside a while loop that’s fed by a pipeline (echo ... | while ...), which runs in a subshell under POSIX sh; those assignments won’t persist, so the later "Detected structure" output will likely always be empty/misleading.

Severity: low

_{🤖 Was this useful? React with 👍 or 👎, or 🚀 if it prevented an incident/outage.}

Signed-off-by: TejaswiniIBM <tejaswini.r1@ibm.com>

TejaswiniIBM · 2026-04-07T04:08:39Z

augment review

Signed-off-by: TejaswiniIBM <tejaswini.r1@ibm.com>

augmentcode

Review completed. 2 suggestions posted.

Comment augment review to trigger a new review at any time.

augmentcode · 2026-04-07T04:12:23Z

bin/zopen-build

+    if ${generateRPM}; then
+      if [ -f "${paxFileName}" ]; then
+        printHeader "Generating RPM from ${ZOPEN_INSTALL_DIR}"
+        rpm_deps=$(echo "${ZOPEN_RUNTIME_DEPS}" | xargs -n1 | sort -u | xargs)


rpm_deps is normalized via xargs -n1 | sort -u, which splits dependency expressions on whitespace; this will break versioned deps like oef >= 1.1.0 into separate tokens and can produce an invalid --requires/Requires: value in the generated spec.

Severity: medium

_{🤖 Was this useful? React with 👍 or 👎, or 🚀 if it prevented an incident/outage.}

augmentcode · 2026-04-07T04:12:24Z

bin/zopen-pax2rpm

+        fi
+    else
+        # Check if _topdir is already defined and different
+existing_topdir=$(grep "%_topdir" "$HOME/.rpmmacros" | awk '{print $2}')


In setup_rpmbuild, if ~/.rpmmacros exists but doesn’t define %_topdir, existing_topdir becomes empty and the script still emits a warning claiming _topdir is set to '', which is misleading and can confuse debugging.

Severity: low

_{🤖 Was this useful? React with 👍 or 👎, or 🚀 if it prevented an incident/outage.}

Signed-off-by: TejaswiniIBM <tejaswini.r1@ibm.com>

TejaswiniIBM · 2026-04-08T10:28:04Z

augment review

augmentcode

Review completed. No suggestions at this time.

Comment augment review to trigger a new review at any time.

Signed-off-by: TejaswiniIBM <tejaswini.r1@ibm.com>

TejaswiniIBM requested review from DevonianTeuchter, HarithaIBM, IgorTodorovskiIBM, MikeFultonDev, sachintu47 and v1gnesh as code owners March 17, 2026 10:10

augmentcode bot reviewed Mar 17, 2026

View reviewed changes

IgorTodorovskiIBM approved these changes Mar 18, 2026

View reviewed changes

augmentcode bot reviewed Mar 23, 2026

View reviewed changes

augmentcode bot reviewed Mar 26, 2026

View reviewed changes

augmentcode bot reviewed Mar 31, 2026

View reviewed changes

TejaswiniIBM force-pushed the zopen_pax2rpm branch from 1f61ea5 to 34d084a Compare April 1, 2026 05:55

augmentcode bot reviewed Apr 2, 2026

View reviewed changes

Added rpm package as part of build

0e5c922

Signed-off-by: TejaswiniIBM <tejaswini.r1@ibm.com>

TejaswiniIBM added 11 commits April 6, 2026 11:24

Resolved augment comments

993c3ea

Signed-off-by: TejaswiniIBM <tejaswini.r1@ibm.com>

Resolved PR reviews in zopen-pax2rpm, pubilsh.groovy

f271bac

Signed-off-by: TejaswiniIBM <tejaswini.r1@ibm.com>

Resolved PR reviews in zopen-pax2rpm

d9b16e5

Signed-off-by: TejaswiniIBM <tejaswini.r1@ibm.com>

Resolved PR comments

5531b9b

Signed-off-by: TejaswiniIBM <tejaswini.r1@ibm.com>

Fixing the review comments

9da910e

Signed-off-by: TejaswiniIBM <tejaswini.r1@ibm.com>

Resolved the pr review comments v2

962d0b3

Signed-off-by: TejaswiniIBM <tejaswini.r1@ibm.com>

resolved pr comments 3

541aa2e

Signed-off-by: TejaswiniIBM <tejaswini.r1@ibm.com>

versioning added

057745d

Signed-off-by: TejaswiniIBM <tejaswini.r1@ibm.com>

refactored the script to matchother zopen tools

edb4824

Signed-off-by: TejaswiniIBM <tejaswini.r1@ibm.com>

Fixed the build errors

2fa9f22

Signed-off-by: TejaswiniIBM <tejaswini.r1@ibm.com>

Fixed the build issues

703956e

Signed-off-by: TejaswiniIBM <tejaswini.r1@ibm.com>

TejaswiniIBM force-pushed the zopen_pax2rpm branch from 16e647f to 703956e Compare April 6, 2026 15:24

augmentcode bot reviewed Apr 6, 2026

View reviewed changes

Fixed the review comments

5eb36a2

Signed-off-by: TejaswiniIBM <tejaswini.r1@ibm.com>

Updated the build command to test rpm

c04a514

Signed-off-by: TejaswiniIBM <tejaswini.r1@ibm.com>

augmentcode bot reviewed Apr 7, 2026

View reviewed changes

TejaswiniIBM added 3 commits April 7, 2026 04:32

Changed the portbuild to portbuild test for testing the command

eacfd78

Signed-off-by: TejaswiniIBM <tejaswini.r1@ibm.com>

Fixed the test build error No compatible architectures found for build

eb99671

Signed-off-by: TejaswiniIBM <tejaswini.r1@ibm.com>

Fixed the test build error - RPM build errors:

36ee648

Signed-off-by: TejaswiniIBM <tejaswini.r1@ibm.com>

augmentcode bot reviewed Apr 8, 2026

View reviewed changes

TejaswiniIBM added 2 commits April 8, 2026 07:33

Reverted the Port-Build-Test to Port-Build

e7315bb

Signed-off-by: TejaswiniIBM <tejaswini.r1@ibm.com>

updating the branch to main

de65cc5

Signed-off-by: TejaswiniIBM <tejaswini.r1@ibm.com>


		mkdir -p "$buildroot"/{BUILD,BUILDROOT,RPMS,SOURCES,SPECS,SRPMS}

		if [ ! -f "$HOME/.rpmmacros" ]; then

Conversation

TejaswiniIBM commented Mar 17, 2026

What type of PR is this? (check all applicable)

Category

Description

Related Issues

[optional] Are there any post-deployment tasks or follow-up actions required?

Uh oh!

TejaswiniIBM commented Mar 17, 2026

Uh oh!

augmentcode bot commented Mar 17, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

augmentcode bot left a comment

Choose a reason for hiding this comment

Uh oh!

augmentcode bot Mar 17, 2026

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

augmentcode bot left a comment

Choose a reason for hiding this comment

Uh oh!

augmentcode bot Mar 17, 2026

Choose a reason for hiding this comment

Uh oh!

augmentcode bot Mar 17, 2026

Choose a reason for hiding this comment

Uh oh!

augmentcode bot Mar 17, 2026

Choose a reason for hiding this comment

Uh oh!

augmentcode bot Mar 17, 2026

Choose a reason for hiding this comment

Uh oh!

augmentcode bot Mar 17, 2026

Choose a reason for hiding this comment

Uh oh!

augmentcode bot Mar 17, 2026

Choose a reason for hiding this comment

Uh oh!

TejaswiniIBM commented Mar 23, 2026

Uh oh!

augmentcode bot left a comment

Choose a reason for hiding this comment

Uh oh!

augmentcode bot Mar 23, 2026

Choose a reason for hiding this comment

Uh oh!

augmentcode bot Mar 23, 2026

Choose a reason for hiding this comment

Uh oh!

TejaswiniIBM commented Mar 23, 2026

Uh oh!

augmentcode bot left a comment

Choose a reason for hiding this comment

Uh oh!

augmentcode bot Mar 23, 2026

Choose a reason for hiding this comment

Uh oh!

augmentcode bot Mar 23, 2026

Choose a reason for hiding this comment

Uh oh!

TejaswiniIBM commented Mar 23, 2026

Uh oh!

augmentcode bot left a comment

Choose a reason for hiding this comment

Uh oh!

augmentcode bot Mar 23, 2026

Choose a reason for hiding this comment

Uh oh!

augmentcode bot Mar 23, 2026

Choose a reason for hiding this comment

Uh oh!

augmentcode bot Mar 23, 2026

Choose a reason for hiding this comment

Uh oh!

augmentcode bot commented Mar 17, 2026 •

edited

Loading