-
-
Notifications
You must be signed in to change notification settings - Fork 317
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
Setting CUSTOMIZED_SDK_URL and SDK_RESOURCE as non-customized ignores the SDK_RESOURCE value #2097
Setting CUSTOMIZED_SDK_URL and SDK_RESOURCE as non-customized ignores the SDK_RESOURCE value #2097
Comments
I would like to work on this issue. |
A follow-up question for this issue. Please, I just to confirm that I understand what I am to do. I am to update this line https://github.com/adoptium/aqa-tests/blob/master/get.sh#L180 with |
The logic is a little bit different as now we also allow users to provide a base artifactory URL (URL before the build number). For this issue we can update jenkinsfileBase only. No need to update get.sh anymore. For jenkinsfileBase the Line360-L365 https://github.com/adoptium/aqa-tests/blob/master/buildenv/jenkins/JenkinsfileBase#L360-L365 should be updated. Customized SDK URL only set when SDK_RESOURCE is customized. That is as long as SDK_RESOURCE != "customized" ( except (params.SDK_RESOURCE == 'nightly' && params.CUSTOMIZED_SDK_URL)) we'd like to set
And then the check for |
Thank you for the clarification.
On Fri, 15 Oct 2021 at 9:41 PM, sophia-guo ***@***.***> wrote:
The logic is a little bit different as now we also allow users to provide
a base artifactory URL (URL before the build number). For this issue we can
update jenkinsfileBase only. No need to update get.sh anymore.
For jenkinsfileBase the Line360-L365
https://github.com/adoptium/aqa-tests/blob/master/buildenv/jenkins/JenkinsfileBase#L360-L365
should be updated.
Customized SDK URL only set when SDK_RESOURCE is customized. That is as
long as SDK_RESOURCE != "customized" ( except (params.SDK_RESOURCE ==
'nightly' && params.CUSTOMIZED_SDK_URL)) we'd like to set CUSTOMIZED_SDK_URL_OPTION
= "".
if (params.SDK_RESOURCE == 'nightly' && params.CUSTOMIZED_SDK_URL) {
CUSTOMIZED_SDK_URL_OPTION = "-c '${params.CUSTOMIZED_SDK_URL}'"
} else if (params.SDK_RESOURCE != 'customized') {
CUSTOMIZED_SDK_URL_OPTION = ""
} else if (params.CUSTOMIZED_SDK_URL) {
CUSTOMIZED_SDK_URL_OPTION = "-c '${params.CUSTOMIZED_SDK_URL}'"
} else {
error("For customized sdk resource, please provide the sdk url as CUSTOMIZED_SDK_URL")
}
And then the check for !params.CUSTOMIZED_SDK_URL in
https://github.com/adoptium/aqa-tests/blob/master/buildenv/jenkins/JenkinsfileBase#L373
can also be removed.
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
<#2097 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AHMKITNLKGBD5BPIFAS4AOTUHCGZHANCNFSM4USF7ACA>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
--
Nneamaka Chalokwu
|
Hello Sophia,
Please kindly review my pull request on this issue, and share with me
your feedback.
Thank you.
On Sat, 16 Oct 2021 at 9:20 AM, Nneamaka Chalokwu ***@***.***>
wrote:
Thank you for the clarification.
On Fri, 15 Oct 2021 at 9:41 PM, sophia-guo ***@***.***>
wrote:
> The logic is a little bit different as now we also allow users to provide
> a base artifactory URL (URL before the build number). For this issue we can
> update jenkinsfileBase only. No need to update get.sh anymore.
>
> For jenkinsfileBase the Line360-L365
> https://github.com/adoptium/aqa-tests/blob/master/buildenv/jenkins/JenkinsfileBase#L360-L365
> should be updated.
>
> Customized SDK URL only set when SDK_RESOURCE is customized. That is as
> long as SDK_RESOURCE != "customized" ( except (params.SDK_RESOURCE ==
> 'nightly' && params.CUSTOMIZED_SDK_URL)) we'd like to set CUSTOMIZED_SDK_URL_OPTION
> = "".
>
> if (params.SDK_RESOURCE == 'nightly' && params.CUSTOMIZED_SDK_URL) {
> CUSTOMIZED_SDK_URL_OPTION = "-c '${params.CUSTOMIZED_SDK_URL}'"
> } else if (params.SDK_RESOURCE != 'customized') {
> CUSTOMIZED_SDK_URL_OPTION = ""
> } else if (params.CUSTOMIZED_SDK_URL) {
> CUSTOMIZED_SDK_URL_OPTION = "-c '${params.CUSTOMIZED_SDK_URL}'"
> } else {
> error("For customized sdk resource, please provide the sdk url as CUSTOMIZED_SDK_URL")
> }
>
> And then the check for !params.CUSTOMIZED_SDK_URL in
> https://github.com/adoptium/aqa-tests/blob/master/buildenv/jenkins/JenkinsfileBase#L373
> can also be removed.
>
> —
> You are receiving this because you were assigned.
> Reply to this email directly, view it on GitHub
> <#2097 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AHMKITNLKGBD5BPIFAS4AOTUHCGZHANCNFSM4USF7ACA>
> .
> Triage notifications on the go with GitHub Mobile for iOS
> <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
> or Android
> <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
>
>
--
Nneamaka Chalokwu
--
Nneamaka Chalokwu
|
Please note that our scenario has changed. We also have the following case where: |
Okay, thank you. Does this mean the code needs to be updated? If so, where
exactly.
On Mon, 18 Oct 2021 at 2:09 PM, Lan Xia ***@***.***> wrote:
Please note that our scenario has changed. We also have the following case
where:
SDK_RESOURCE=nightly
CUSTOMIZED_SDK_URL=<base URL from artifactory>
In this case, our script will try to find the latest URL link.
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
<#2097 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AHMKITKSEEVBTHA2TEVW3RDUHQMCFANCNFSM4USF7ACA>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
--
Nneamaka Chalokwu
|
yes, the changes or suggestion in #2097 (comment) has included the scenario @abigailsleek I didn't find your changes, did you create a PR? |
Okay, thank you.
Yes I already created a pull request for this repository because I made
changes to the testJobTemplate file. I’ll share the link to my commit on
this issue so you can review it.
3af6c7e
On Mon, 18 Oct 2021 at 3:37 PM, sophia-guo ***@***.***> wrote:
yes, the changes or suggestion in #2097 (comment)
<#2097 (comment)>
has included the scenario SDK_RESOURCE=nightly CUSTOMIZED_SDK_URL=<base
URL from artifactory>
@abigailsleek <https://github.com/abigailsleek> I didn't find your
changes, did you create a PR?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#2097 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AHMKITI76ON23BXJGAWH3S3UHQWKFANCNFSM4USF7ACA>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
--
Nneamaka Chalokwu
|
Thanks @abigailsleek . Could you please create one PR per issue? |
Sure, I will do that.
On Mon, 18 Oct 2021 at 4:49 PM, Lan Xia ***@***.***> wrote:
Thanks @abigailsleek <https://github.com/abigailsleek> . Could you please
create one PR per issue?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#2097 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AHMKITOBIGUY4VGUNC47VVLUHQ6YNANCNFSM4USF7ACA>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
--
Nneamaka Chalokwu
|
Hi, I tried creating another PR but it didn't work because it’s on the same
branch. Should I create another branch or I should pull request on one of
the other branches?
On Mon, 18 Oct 2021 at 4:49 PM, Lan Xia ***@***.***> wrote:
Thanks @abigailsleek <https://github.com/abigailsleek> . Could you please
create one PR per issue?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#2097 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AHMKITOBIGUY4VGUNC47VVLUHQ6YNANCNFSM4USF7ACA>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
--
Nneamaka Chalokwu
|
I typically use 1 branch per issue (where each issue gets is separate PR to resolve it). That way, I can start each branch freshly synched with the main branch and it contains no other clutter or content from other PRs. (see 3 minute recording describing this practice for guidance). |
Thank you for this information.
On Sat, 23 Oct 2021 at 4:25 PM, Shelley Lambert ***@***.***> wrote:
I typically use 1 branch per issue (where each issue gets is separate PR
to resolve it). That way, I can start each branch freshly synched with the
main branch and it contains no other clutter. (see 3 minute recording
<https://drive.google.com/file/d/1yTcXaA8vHgHMkkuDONKeDCEufgZJO-TJ/view?usp=sharing>
describing this practice for guidance).
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#2097 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AHMKITPPEDHU5SDNWTTIUE3UILHW3ANCNFSM4USF7ACA>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
--
Nneamaka Chalokwu
|
Hi Sophia, here is the link to my pull request. Kindly review. Thank you.
#3099
On Sat, 23 Oct 2021 at 5:50 PM, Nneamaka Chalokwu ***@***.***>
wrote:
Thank you for this information.
On Sat, 23 Oct 2021 at 4:25 PM, Shelley Lambert ***@***.***>
wrote:
> I typically use 1 branch per issue (where each issue gets is separate PR
> to resolve it). That way, I can start each branch freshly synched with the
> main branch and it contains no other clutter. (see 3 minute recording
> <https://drive.google.com/file/d/1yTcXaA8vHgHMkkuDONKeDCEufgZJO-TJ/view?usp=sharing>
> describing this practice for guidance).
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <#2097 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AHMKITPPEDHU5SDNWTTIUE3UILHW3ANCNFSM4USF7ACA>
> .
> Triage notifications on the go with GitHub Mobile for iOS
> <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
> or Android
> <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
>
>
--
Nneamaka Chalokwu
--
Nneamaka Chalokwu
|
Hi there, I am wondering if I could take this one? It would be much appreciated! |
Checkout: Yee Lin Date: Jan 21st, 2022 Relate issue: (adoptium#2097) adoptium#2097
Yes, it is a good first issue. |
@smlambert can you assign it to @julian55455 ? |
@llxia Has the mismatch been done #2097 (comment) ? |
No, it is a good first issue. |
@llxia , it's a good first issue under https://github.com/ibmruntimes/ci-jenkins-pipelines? Seems I can't even have the permission to see issues. Is it open to all people or only to ibmers? |
I do not see the issue tap in that repo as well. Maybe we can open the issue in aqa-tests instead. |
Hi @llxia, Is this issue still open? I would like to work on it. |
I think @julian55455 is on it already? I do not have permission on this repo to assign her, maybe @smlambert or @llxia can help |
@julian55455 I assigned this issue to you. Thanks |
@smlambert should this issue still be open? |
In the grinder setting it says Customized SDK URL, only set when SDK_RESOURCE customized. However if the user accidentally set both CUSTOMIZED_SDK_URL and SDK_RESOURCE ( non-customized) the system will take CUSTOMIZED_SDK_URL and ignore the SDK_RESOURCE's setting.
Senario:
Solution:
Enhance the check condition(https://github.com/adoptium/aqa-tests/blob/master/get.sh#L180) with
if "$SDK_RESOURCE" == "customized"
in two places.example:
https://ci.adoptopenjdk.net/view/work-in-progress/job/grinder_sandbox/162/console
The text was updated successfully, but these errors were encountered: