Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Trigger PR builds #4795

Merged
merged 4 commits into from
Oct 10, 2023
Merged

Trigger PR builds #4795

merged 4 commits into from
Oct 10, 2023

Conversation

KapilPowar
Copy link
Contributor

#1182
Signed-off-by: Kapil Powar [email protected]

CC: @llxia

@KapilPowar KapilPowar marked this pull request as ready for review October 2, 2023 12:06
@KapilPowar
Copy link
Contributor Author

Below are the test job links
Grinder Test -- PR #55 created
Grinder Test -- No updates.

buildenv/jenkins/jck_sync Outdated Show resolved Hide resolved
buildenv/jenkins/jck_sync Outdated Show resolved Hide resolved
buildenv/jenkins/jck_sync Outdated Show resolved Hide resolved
buildenv/jenkins/jck_sync Outdated Show resolved Hide resolved
buildenv/jenkins/jck_sync Outdated Show resolved Hide resolved
buildenv/jenkins/jck_sync Outdated Show resolved Hide resolved
buildenv/jenkins/jck_sync Outdated Show resolved Hide resolved
buildenv/jenkins/jck_sync Outdated Show resolved Hide resolved
buildenv/jenkins/jck_sync Outdated Show resolved Hide resolved
buildenv/jenkins/jck_sync Outdated Show resolved Hide resolved
@KapilPowar KapilPowar force-pushed the jcksync branch 2 times, most recently from 291d66e to 9bd601d Compare October 3, 2023 09:40
@KapilPowar
Copy link
Contributor Author

Below are the test job links
Grinder Test -- PR #57 created
Grinder Test -- No updates.

@KapilPowar KapilPowar requested a review from llxia October 3, 2023 11:00
buildenv/jenkins/jck_sync Outdated Show resolved Hide resolved
buildenv/jenkins/jck_sync Outdated Show resolved Hide resolved
buildenv/jenkins/jck_sync Outdated Show resolved Hide resolved
if (EXITCODE == 2) {
echo "Script returned exit code 2, No new update available. Marking the job as SUCCESS. "
} else if (EXITCODE == 0) {
echo "Script returned exit code 0, new update is available and PR is created."
def matcher = (scriptOutput =~ /PR_NUMBER=\s*(\d+)/)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I do not see any scriptOutput when EXITCODE = 2

buildenv/jenkins/jck_sync Outdated Show resolved Hide resolved
buildenv/jenkins/jck_sync Outdated Show resolved Hide resolved
buildenv/jenkins/jck_sync Outdated Show resolved Hide resolved
buildenv/jenkins/jck_sync Outdated Show resolved Hide resolved
if (EXITCODE == 2) {
echo "Script returned exit code 2, No new update available. Marking the job as SUCCESS. "
echo "Script returned exit code 2, No new update available. The job is completed without further action. "
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

When EXITCODE = 2, there is nothing to do. We should return. See #4795 (comment)

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

if EXITCODE = 2 using error to stop the execution. And marking the currentBuild.result = "SUCCESS"
return is not working here.

buildenv/jenkins/jck_sync Outdated Show resolved Hide resolved
@KapilPowar
Copy link
Contributor Author

KapilPowar commented Oct 5, 2023

Below are the test job links
Grinder Test -- PR #58 created
Grinder Test -- No updates.

@llxia llxia changed the title Running Grinder sanity test Trigger PR builds Oct 5, 2023
CHILD_PARAMS << booleanParam(name: param.key, value: value.toBoolean())
} else {
CHILD_PARAMS << string(name: param.key, value: value)
}
}
}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  • No, SDK_RESOURCE = releases is not correct. I meant if CUSTOMIZED_SDK_URL is pointing to a specific URL, then we cannot pass the parent CUSTOMIZED_SDK_URL to the child jobs as the child jobs can run on multiple platforms. The best way to do it is to add a comment in the Jenkins job config to warn the users. Please remove the settings of SDK_RESOURCE and CUSTOMIZED_SDK_URL.
  • Also, to simplify this, I think we should not use LABEL for two separate purposes. We should rename the LABEL to SYNC_LABEL. See line 6 - 10

buildenv/jenkins/jck_sync Outdated Show resolved Hide resolved
buildenv/jenkins/jck_sync Outdated Show resolved Hide resolved
buildenv/jenkins/jck_sync Outdated Show resolved Hide resolved
buildenv/jenkins/jck_sync Outdated Show resolved Hide resolved
buildenv/jenkins/jck_sync Outdated Show resolved Hide resolved
buildenv/jenkins/jck_sync Outdated Show resolved Hide resolved
buildenv/jenkins/jck_sync Outdated Show resolved Hide resolved
buildenv/jenkins/jck_sync Outdated Show resolved Hide resolved
@KapilPowar
Copy link
Contributor Author

Below are the test job links
Grinder Test -- PR #59 created
Grinder Test -- No updates.

@KapilPowar KapilPowar requested a review from llxia October 6, 2023 07:29
Copy link
Contributor

@llxia llxia left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@llxia llxia requested a review from LongyuZhang October 10, 2023 19:49
Copy link
Contributor

@LongyuZhang LongyuZhang left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@LongyuZhang LongyuZhang merged commit 3548555 into adoptium:master Oct 10, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants