Date   

Upcoming Event: Cupids Scrum - This squad works on issues related to installing, packaging, launching Zowe including SMP/E PTF and APAR delivery. - Wed, 12/04/2019 1:00pm-1:30pm #cal-reminder

zowe-dev@lists.openmainframeproject.org Calendar <zowe-dev@...>
 

Reminder: Cupids Scrum - This squad works on issues related to installing, packaging, launching Zowe including SMP/E PTF and APAR delivery.

When: Wednesday, 4 December 2019, 1:00pm to 1:30pm, (GMT+00:00) UTC

Where:https://zoom.us/my/zowe.onboarding

View Event

Organizer: Joe Winchester winchest@... +447749965423

Description: Cupids Scrum - This squad works on issues related to installing, packaging, launching Zowe including SMP/E PTF and APAR delivery.  
https://github.com/zowe/zowe-install-packaging#workspaces/community-5c93e02fa70b456d35b8f0ed/board?repos=145870120,151615191,155383451,144619729,144599701,144592776


Re: [MARKETING] Follow up to Membership Inquiry with the Open Mainframe Project

John Mertic
 

Adding +zowe-dev@... to help here.

Thank you,

John Mertic
Director of Program Management - Linux Foundation
ASWF, ODPi, and Open Mainframe Project
Schedule time with me at https://calendly.com/jmertic



On Tue, Dec 3, 2019 at 2:59 PM Mai, Don <don.mai@...> wrote:

I am doing initial research into Zowe and was wondering if there is a list of APIs, with their description, of the APIs available with the base installation.

 

From: John Mertic <jmertic@...>
Sent: Tuesday, December 03, 2019 2:42 PM
To: Mai, Don <don.mai@...>
Subject: [MARKETING] Follow up to Membership Inquiry with the Open Mainframe Project

 

Hi Don,

Thank you for your interest in the Open Mainframe Project. In response to your membership inquiry, here are links to both a deck providing an overview of the membership and governance structure of the Open Mainframe Project, as well as the membership application and charter.

The Open Mainframe Project provides a unique opportunity for both business and academia alike to engage with Linux on the Mainframe. There are numerous opportunities to participate from both a business and technical level. I’d be happy to schedule time to walk through the project with you if you have more questions.

Feel free to reach out to me through the contact information below with any questions you might have.

Thanks!

John Mertic
Senior Program Manager - Linux Foundation
jmertic@...
+1 234-738-4571


///

You are receiving this email because you have expressed interest in the Open Mainframe Project. To no longer receive these emails, please https://www2.thelinuxfoundation.org/unsubscribe/u/6342/455f31ceff99aed37f35bed6d6e1d726b0fd203c8d423242c4903d3cc832955d/1005594729.

Open Mainframe Project

One Letterman Drive Building D
Suite D4700
San Francisco, CA 94129

Image removed by sender.


Re: [zowe-user] NOMINATIONS RESULT: ZLC Voting seat

Sean Grady
 

Absolutely. Congratulations Joe!

Sean Grady

Software Architect

Rocket Software

77 Fourth Avenue • Waltham, MA, 02451-1466 • USA

t: +1 781 684 2022 • e: sgrady@... • w: www.rocketsoftware.com



From: zowe-user@... <zowe-user@...> on behalf of John Mertic via Lists.Openmainframeproject.Org <jmertic=linuxfoundation.org@...>
Sent: Tuesday, December 3, 2019 11:11 AM
To: zowe-zlc@... <zowe-zlc@...>; zowe-dev@... <zowe-dev@...>; zowe-user@... <zowe-user@...>
Cc: Joe Winchester <winchest@...>
Subject: [zowe-user] NOMINATIONS RESULT: ZLC Voting seat
 
EXTERNAL EMAIL




Zowe Community,

The ZLC Voting Seat nominations have closed with only Joe Winchester receiving a nomination. As such, he is automatically elected to that seat - congratulations Joe!

Thank you everyone for your participation.

John Mertic
Director of Program Management - Linux Foundation
ASWF, ODPi, and Open Mainframe Project
jmertic@...
+1 234-738-4571
Schedule time with me at https://calendly.com/jmertic

================================
Rocket Software, Inc. and subsidiaries ■ 77 Fourth Avenue, Waltham MA 02451 ■ Main Office Toll Free Number: +1 855.577.4323
Contact Customer Support: https://my.rocketsoftware.com/RocketCommunity/RCEmailSupport
Unsubscribe from Marketing Messages/Manage Your Subscription Preferences - http://www.rocketsoftware.com/manage-your-email-preferences
Privacy Policy - http://www.rocketsoftware.com/company/legal/privacy-policy
================================

This communication and any attachments may contain confidential information of Rocket Software, Inc. All unauthorized use, disclosure or distribution is prohibited. If you are not the intended recipient, please notify Rocket Software immediately and destroy all copies of this communication. Thank you.


NOMINATIONS RESULT: ZLC Voting seat

John Mertic
 

Zowe Community,

The ZLC Voting Seat nominations have closed with only Joe Winchester receiving a nomination. As such, he is automatically elected to that seat - congratulations Joe!

Thank you everyone for your participation.

John Mertic
Director of Program Management - Linux Foundation
ASWF, ODPi, and Open Mainframe Project
jmertic@...
+1 234-738-4571
Schedule time with me at https://calendly.com/jmertic


Cancelled Event: CI/CD Squad Scrum (https://zoom.us/my/zowe.cicd) - Tuesday, 3 December 2019 #cal-cancelled

zowe-dev@lists.openmainframeproject.org Calendar <zowe-dev@...>
 

Cancelled: CI/CD Squad Scrum (https://zoom.us/my/zowe.cicd)

This event has been cancelled.

When:
Tuesday, 3 December 2019
11:00am to 12:00pm
(UTC-05:00) America/New York

Where:
https://zoom.us/my/zowe.cicd

Organizer: kocsis@...

Description:
CI/CD Squad Scrum (https://zoom.us/my/zowe.cicd)


Upcoming Event: Zowe ZLC meeting - Wed, 12/04/2019 9:00am-10:00am #cal-reminder

zowe-dev@lists.openmainframeproject.org Calendar <zowe-dev@...>
 

Reminder: Zowe ZLC meeting

When: Wednesday, 4 December 2019, 9:00am to 10:00am, (GMT-05:00) America/New York

Where:https://zoom.us/j/935375531

View Event

Organizer: matt@... +1-919-656-0564

Description:

Join from PC, Mac, Linux, iOS or Android: https://zoom.us/j/935375531

Or iPhone one-tap : US: +16699006833,,935375531# or +16465588656,,935375531# Or Telephone: Dial(for higher quality, dial a number based on your current location): US: +1 669 900 6833 or +1 646 558 8656 or +1 877 369 0926 (Toll Free) or +1 855 880 1246 (Toll Free) Meeting ID: 935 375 531 International numbers available: https://zoom.us/u/b1u8uCXIn


Cupids Scrum - Install/Package/SMP-E/PTF/Componentize - Mon, 12/02/2019 #cal-notice

zowe-dev@lists.openmainframeproject.org Calendar <noreply@...>
 

Cupids Scrum - Install/Package/SMP-E/PTF/Componentize

When:
Monday, 2 December 2019
2:30pm to 3:00pm
(GMT+00:00) UTC

Where:
https://zoom.us/my/zowe.onboarding

Organizer:
winchest@... +447749965423

Description:
Cupids Scrum - This squad works on issues related to installing, packaging, launching Zowe including SMP/E PTF and APAR delivery.  
https://github.com/zowe/zowe-install-packaging#workspaces/community-5c93e02fa70b456d35b8f0ed/board?repos=145870120,151615191,155383451,144619729,144599701,144592776


Cupids Scrum - This squad works on issues related to installing, packaging, launching Zowe including SMP/E PTF and APAR delivery. - Fri, 11/29/2019 #cal-notice

zowe-dev@lists.openmainframeproject.org Calendar <noreply@...>
 

Cupids Scrum - This squad works on issues related to installing, packaging, launching Zowe including SMP/E PTF and APAR delivery.

When:
Friday, 29 November 2019
3:00pm to 3:30pm
(GMT+00:00) UTC

Where:
https://zoom.us/my/zowe.onboarding

Organizer:
winchest@... +447749965423

Description:
Cupids Scrum - This squad works on issues related to installing, packaging, launching Zowe including SMP/E PTF and APAR delivery.  
https://github.com/zowe/zowe-install-packaging#workspaces/community-5c93e02fa70b456d35b8f0ed/board?repos=145870120,151615191,155383451,144619729,144599701,144592776


Upcoming Event: CI/CD Squad Scrum (https://zoom.us/my/zowe.cicd) - Thu, 11/28/2019 11:00am-11:30am #cal-reminder

zowe-dev@lists.openmainframeproject.org Calendar <zowe-dev@...>
 

Reminder: CI/CD Squad Scrum (https://zoom.us/my/zowe.cicd)

When: Thursday, 28 November 2019, 11:00am to 11:30am, (GMT-05:00) America/New York

Where:https://zoom.us/my/zowe.cicd

View Event

Organizer: kocsis@...

Description: CI/CD Squad Scrum (https://zoom.us/my/zowe.cicd)


Upcoming Event: Zowe Development / Release Weekly Checkpoint (https://zoom.us/my/zowe.cicd) - Thu, 11/28/2019 10:00am-11:00am #cal-reminder

zowe-dev@lists.openmainframeproject.org Calendar <zowe-dev@...>
 

Reminder: Zowe Development / Release Weekly Checkpoint (https://zoom.us/my/zowe.cicd)

When: Thursday, 28 November 2019, 10:00am to 11:00am, (GMT-05:00) America/New York

Where:https://zoom.us/my/zowe.cicd

View Event

Organizer: kocsis@...

Description: Meeting Call-in: https://zoom.us/my/zowe.cicd
Meeting minutes and Agenda: https://github.com/zowe/community/tree/master/Project%20Management/Meeting%20Minutes%20and%20Agenda


Zowe Architecture Call (https://zoom.us/my/zowe.cicd) - Wed, 11/27/2019 #cal-notice

zowe-dev@lists.openmainframeproject.org Calendar <noreply@...>
 

Zowe Architecture Call (https://zoom.us/my/zowe.cicd)

When:
Wednesday, 27 November 2019
12:00pm to 1:00pm
(GMT-05:00) America/New York

Where:
https://zoom.us/my/zowe.cicd

Organizer:
kocsis@...

Description:

Zowe Architecture Callin Information:
https://zoom.us/my/zowe.cicd

Agenda:
- Add the topics you wish to discuss (along with date) to the agenda
https://wiki.zowe.org/display/ZOWE/Architecture+Call+Topics


Upcoming Event: Zowe Architecture Call (https://zoom.us/my/zowe.cicd) - Wed, 11/27/2019 12:00pm-1:00pm #cal-reminder

zowe-dev@lists.openmainframeproject.org Calendar <zowe-dev@...>
 

Reminder: Zowe Architecture Call (https://zoom.us/my/zowe.cicd)

When: Wednesday, 27 November 2019, 12:00pm to 1:00pm, (GMT-05:00) America/New York

Where:https://zoom.us/my/zowe.cicd

View Event

Organizer: kocsis@...

Description:

Zowe Architecture Callin Information:
https://zoom.us/my/zowe.cicd

Agenda:
- Add the topics you wish to discuss (along with date) to the agenda
https://wiki.zowe.org/display/ZOWE/Architecture+Call+Topics


Zowe ZLC meeting - Wed, 11/27/2019 #cal-notice

zowe-dev@lists.openmainframeproject.org Calendar <noreply@...>
 

Zowe ZLC meeting

When:
Wednesday, 27 November 2019
9:00am to 10:00am
(GMT-05:00) America/New York

Where:
https://zoom.us/j/935375531

Organizer:
matt@... +1-919-656-0564

Description:

Join from PC, Mac, Linux, iOS or Android: https://zoom.us/j/935375531

Or iPhone one-tap : US: +16699006833,,935375531# or +16465588656,,935375531# Or Telephone: Dial(for higher quality, dial a number based on your current location): US: +1 669 900 6833 or +1 646 558 8656 or +1 877 369 0926 (Toll Free) or +1 855 880 1246 (Toll Free) Meeting ID: 935 375 531 International numbers available: https://zoom.us/u/b1u8uCXIn


Upcoming Event: Zowe ZLC meeting - Wed, 11/27/2019 9:00am-10:00am #cal-reminder

zowe-dev@lists.openmainframeproject.org Calendar <zowe-dev@...>
 

Reminder: Zowe ZLC meeting

When: Wednesday, 27 November 2019, 9:00am to 10:00am, (GMT-05:00) America/New York

Where:https://zoom.us/j/935375531

View Event

Organizer: matt@... +1-919-656-0564

Description:

Join from PC, Mac, Linux, iOS or Android: https://zoom.us/j/935375531

Or iPhone one-tap : US: +16699006833,,935375531# or +16465588656,,935375531# Or Telephone: Dial(for higher quality, dial a number based on your current location): US: +1 669 900 6833 or +1 646 558 8656 or +1 877 369 0926 (Toll Free) or +1 855 880 1246 (Toll Free) Meeting ID: 935 375 531 International numbers available: https://zoom.us/u/b1u8uCXIn


Cupids Scrum - This squad works on issues related to installing, packaging, launching Zowe including SMP/E PTF and APAR delivery. - Wed, 11/27/2019 #cal-notice

zowe-dev@lists.openmainframeproject.org Calendar <noreply@...>
 

Cupids Scrum - This squad works on issues related to installing, packaging, launching Zowe including SMP/E PTF and APAR delivery.

When:
Wednesday, 27 November 2019
1:00pm to 1:30pm
(GMT+00:00) UTC

Where:
https://zoom.us/my/zowe.onboarding

Organizer:
winchest@... +447749965423

Description:
Cupids Scrum - This squad works on issues related to installing, packaging, launching Zowe including SMP/E PTF and APAR delivery.  
https://github.com/zowe/zowe-install-packaging#workspaces/community-5c93e02fa70b456d35b8f0ed/board?repos=145870120,151615191,155383451,144619729,144599701,144592776


Upcoming Event: Zowe ZLC meeting - Wed, 11/27/2019 9:00am-10:00am #cal-reminder

zowe-dev@lists.openmainframeproject.org Calendar <zowe-dev@...>
 

Reminder: Zowe ZLC meeting

When: Wednesday, 27 November 2019, 9:00am to 10:00am, (GMT-05:00) America/New York

Where:https://zoom.us/j/935375531

View Event

Organizer: matt@... +1-919-656-0564

Description:

Join from PC, Mac, Linux, iOS or Android: https://zoom.us/j/935375531

Or iPhone one-tap : US: +16699006833,,935375531# or +16465588656,,935375531# Or Telephone: Dial(for higher quality, dial a number based on your current location): US: +1 669 900 6833 or +1 646 558 8656 or +1 877 369 0926 (Toll Free) or +1 855 880 1246 (Toll Free) Meeting ID: 935 375 531 International numbers available: https://zoom.us/u/b1u8uCXIn


Upcoming Event: Cupids Scrum - This squad works on issues related to installing, packaging, launching Zowe including SMP/E PTF and APAR delivery. - Wed, 11/27/2019 1:00pm-1:30pm #cal-reminder

zowe-dev@lists.openmainframeproject.org Calendar <zowe-dev@...>
 

Reminder: Cupids Scrum - This squad works on issues related to installing, packaging, launching Zowe including SMP/E PTF and APAR delivery.

When: Wednesday, 27 November 2019, 1:00pm to 1:30pm, (GMT+00:00) UTC

Where:https://zoom.us/my/zowe.onboarding

View Event

Organizer: Joe Winchester winchest@... +447749965423

Description: Cupids Scrum - This squad works on issues related to installing, packaging, launching Zowe including SMP/E PTF and APAR delivery.  
https://github.com/zowe/zowe-install-packaging#workspaces/community-5c93e02fa70b456d35b8f0ed/board?repos=145870120,151615191,155383451,144619729,144599701,144592776


Re: Expiring project Giza dot org domain

Jack-Tiefeng Jia
 

Thanks a lot Dan for the explanations and the Artifactory token.
 
I attached a screenshot about the "Build with Parameters" option for Jenkins Pipeline. For a parameterized pipeline, we have this option to run the same code/pipeline but different input. In the screenshot, you can see, without changing github code, we can test any Zowe build and on any server. If we don't have this permission, we have to create a git commit and hardcode what zowe build to test and trigger the build. Since the test could be just one time run, the commit is useless for the code base. So if we can have the Build with Parameters permission, it's really convenient for the team, and avoid to create dummy commits.
 
 
And one more background is almost all our builds can be run as many times as user like. It won't create conflict in the Artifactory.
 
But we do have one build we wish it could be restricted, which is promote-publish build. We wish this build can only is started by CI/CD squad.
 
Thanks,
 
Jack (T.) Jia
Software Developer
IBM Z Management Software
IBM Systems

Phone: 1-905-413-3195
IBM

8200 Warden Ave
Markham, ON L6G 1C7
Canada
 
 

----- Original message -----
From: "Daniel Pono Takamori" <dtakamori@...>
Sent by: zowe-dev@...
To: Jack-Tiefeng Jia <Jack-Tiefeng.Jia@...>, zowe-dev@...
Cc: Andrew Grimberg <agrimberg@...>, John Mertic <jmertic@...>
Subject: [EXTERNAL] Re: [zowe-dev] Expiring project Giza dot org domain
Date: Mon, Nov 25, 2019 4:56 PM
 
Hey Jack and Team,
First note is about permission for starting/ editing jobs: 
Unfortunately on the production Jenkins we do not allow triggering of arbitrary jobs from the UI (or API as you noted). However, on jenkins.zowe.org/sandbox Jack and Mark are in a group that allows them to start jobs at will (without the dance of posting 'retry' or 'recheck' [0] in the comments on a Github PR). This group can be added to by filing a ticket on support.linuxfoundation.org [1].  Is this an integral part of the workflow _after_ jobs are merged somewhere?  (currently we don't allow that permission on the production Jenkins instances, but could look into options if this is a necessary feature).
Since you are one of the first projects using Pipelines, our usual workflow of using `jenkins-job-builder` [2] will need to be looked at and reconsidered to fit your needs.
Secondly, I'm going to rebuild the Jenkins builder nodes with the containers already in them to reduce the bandwidth/ time overhead of pulling them in.  We can update them when new containers are released, but in the meantime if you are building them from the same underlying bits, it'll drastically reduce the time spent fetching new layers.
Thirdly, I've responded on the ticket about the Artifactory token.
 
I apologize for not being more a part of the CI discussions; I've joined the zowe-dev list to track updates and feel free to reach out for how we can better help you in this process!
 
-Daniel Pono Takamori on behalf of LF CI/ Release Engineering
 
 
On Fri, Nov 22, 2019 at 11:36 AM Jack-Tiefeng Jia <Jack-Tiefeng.Jia@...> wrote:
John, for sure. Currently when we test the Jenkins Library, which is a gradle build, the test starts with gradle test command, it will try to test several functionalities in the library. It's generally integration tests since when the code runs under Jenkins, it may behave differently when we run under JRE. Jenkins pipeline workflow plugin will convert the code into CPS https://github.com/cloudbees/groovy-cps/blob/master/doc/cps-basics.md.
 
For each major functionality, we will create a test Jenkins job on-the-fly with Jenkinsfile, and/or start the build with different parameters. The job could be a simple Pipeline, or a Multibranch Pipeline depends on the feature the test case is testing. For multibranch pipeline, we will also trigger a scan job to find the branches.
 
With current LF Jenkins setup, we don't have these permissions:
- create a job on-the-fly (or through Jenkins API)
- start a scan on Multibranch Pipeline job (or through Jenkins API)
- start a job on Jenkins (or through Jenkins API)
- start a job with parameters on Jenkins (or through Jenkins API)
- delete the temporary test job when the test is done
 
So we have to figure other ways to perform the tests.
 
For the permission of starting a job with parameters on Jenkins, we do rely a lot on this with our own Jenkins. Few scenarios like:
- start a smoke test on any build we produced,
- or start a smoke test on a different testing server.
- parameters to decide if/how we want to release.
 
For all the permission limitations, I believe we can have workarounds, just not ideal. Like we have to create dummy branches/commits to the github to trigger a build. The dummy commits eventually will end up to many merging conflicts, which is minor but have to deal with. To create workaround on testing Jenkins Library, we will need to change a lot on the way how we start our test.
 
FYI, another workaround we have already added is building in docker containers. The Jenkins has docker support VM agent, but the agent is not reusable. We can start the container with the build, but every build it will need to download the base build image again.  For example, https://jenkins.zowe.org/job/zowe-docs-site/job/users%252Fjack%252Flf-jenkins/6/execution/node/8/log/. Currently the base image is 1.24G, which create extra overhead to the build and server traffic. We may be able to try to make the base image slightly smaller, but I think with JDK8 and node.js v8 or v12 pre-installed, it will be still about 600M to 900M.
 
Hope this explains the issues we are having.
 
Thanks,
 
Jack (T.) Jia
Software Developer
IBM Z Management Software
IBM Systems

Phone: 1-905-413-3195
IBM

8200 Warden Ave
Markham, ON L6G 1C7
Canada
 
 
----- Original message -----
From: "John Mertic" <jmertic@...>
Sent by: zowe-dev@...
To: zowe-dev@..., Andrew Grimberg <agrimberg@...>, Daniel Pono Takamori <dtakamori@...>
Cc:
Subject: [EXTERNAL] Re: [zowe-dev] Expiring project Giza dot org domain
Date: Fri, Nov 22, 2019 11:34 AM
 
Hey Jack!
 
Adding +Andrew Grimberg and +Daniel Pono Takamori to this thread...
 
I will keep investigating the possibilities of migrating everything to LF Jenkins. One difficulty we have is the "Jenkins Library" build which will fail on LF Jenkins due to the permission limitation we have. Will see what we can do. The tests for Jenkins Library code is suggested because if it fails, it may indicate every other builds using that branch will fail. The test has to be performed against a real Jenkins server, not a virtual JVM environment because Jenkins handles Groovy scripts differently. The way of testing Jenkins Library is it will try to create a job through Jenkins API and start the build and check result, which is against the permission scheme we have on LF Jenkins.
 
Can you elaborate on the permissions issues? I thought we had built the environment to align with the existing practices, but wondering if something changed from discovery to implementation.
 
Thanks!
 
John

 

 

 
 


Re: Expiring project Giza dot org domain

Jack-Tiefeng Jia
 

Thanks a lot Dan for the explanations and the Artifactory token.
 
I attached a screenshot about the "Build with Parameters" option for Jenkins Pipeline. For a parameterized pipeline, we have this option to run the same code/pipeline but different input. In the screenshot, you can see, without changing github code, we can test any Zowe build and on any server. If we don't have this permission, we have to create a git commit and hardcode what zowe build to test and trigger the build. Since the test could be just one time run, the commit is useless for the code base. So if we can have the Build with Parameters permission, it's really convenient for the team, and avoid to create dummy commits.
 
 
And one more background is almost all our builds can be run as many times as user like. It won't create conflict in the Artifactory.
 
But we do have one build we wish it could be restricted, which is promote-publish build. We wish this build can only is started by CI/CD squad.
 
 
Regards,
 
Jack (T.) Jia
Software Developer
IBM Z Management Software
IBM Systems

Phone: 1-905-413-3195
IBM

8200 Warden Ave
Markham, ON L6G 1C7
Canada
 
 

----- Original message -----
From: "Daniel Pono Takamori" <dtakamori@...>
Sent by: zowe-dev@...
To: Jack-Tiefeng Jia <Jack-Tiefeng.Jia@...>, zowe-dev@...
Cc: Andrew Grimberg <agrimberg@...>, John Mertic <jmertic@...>
Subject: [EXTERNAL] Re: [zowe-dev] Expiring project Giza dot org domain
Date: Mon, Nov 25, 2019 4:56 PM
 
Hey Jack and Team,
First note is about permission for starting/ editing jobs: 
Unfortunately on the production Jenkins we do not allow triggering of arbitrary jobs from the UI (or API as you noted). However, on jenkins.zowe.org/sandbox Jack and Mark are in a group that allows them to start jobs at will (without the dance of posting 'retry' or 'recheck' [0] in the comments on a Github PR). This group can be added to by filing a ticket on support.linuxfoundation.org [1].  Is this an integral part of the workflow _after_ jobs are merged somewhere?  (currently we don't allow that permission on the production Jenkins instances, but could look into options if this is a necessary feature).
Since you are one of the first projects using Pipelines, our usual workflow of using `jenkins-job-builder` [2] will need to be looked at and reconsidered to fit your needs.
Secondly, I'm going to rebuild the Jenkins builder nodes with the containers already in them to reduce the bandwidth/ time overhead of pulling them in.  We can update them when new containers are released, but in the meantime if you are building them from the same underlying bits, it'll drastically reduce the time spent fetching new layers.
Thirdly, I've responded on the ticket about the Artifactory token.
 
I apologize for not being more a part of the CI discussions; I've joined the zowe-dev list to track updates and feel free to reach out for how we can better help you in this process!
 
-Daniel Pono Takamori on behalf of LF CI/ Release Engineering
 
 
On Fri, Nov 22, 2019 at 11:36 AM Jack-Tiefeng Jia <Jack-Tiefeng.Jia@...> wrote:
John, for sure. Currently when we test the Jenkins Library, which is a gradle build, the test starts with gradle test command, it will try to test several functionalities in the library. It's generally integration tests since when the code runs under Jenkins, it may behave differently when we run under JRE. Jenkins pipeline workflow plugin will convert the code into CPS https://github.com/cloudbees/groovy-cps/blob/master/doc/cps-basics.md.
 
For each major functionality, we will create a test Jenkins job on-the-fly with Jenkinsfile, and/or start the build with different parameters. The job could be a simple Pipeline, or a Multibranch Pipeline depends on the feature the test case is testing. For multibranch pipeline, we will also trigger a scan job to find the branches.
 
With current LF Jenkins setup, we don't have these permissions:
- create a job on-the-fly (or through Jenkins API)
- start a scan on Multibranch Pipeline job (or through Jenkins API)
- start a job on Jenkins (or through Jenkins API)
- start a job with parameters on Jenkins (or through Jenkins API)
- delete the temporary test job when the test is done
 
So we have to figure other ways to perform the tests.
 
For the permission of starting a job with parameters on Jenkins, we do rely a lot on this with our own Jenkins. Few scenarios like:
- start a smoke test on any build we produced,
- or start a smoke test on a different testing server.
- parameters to decide if/how we want to release.
 
For all the permission limitations, I believe we can have workarounds, just not ideal. Like we have to create dummy branches/commits to the github to trigger a build. The dummy commits eventually will end up to many merging conflicts, which is minor but have to deal with. To create workaround on testing Jenkins Library, we will need to change a lot on the way how we start our test.
 
FYI, another workaround we have already added is building in docker containers. The Jenkins has docker support VM agent, but the agent is not reusable. We can start the container with the build, but every build it will need to download the base build image again.  For example, https://jenkins.zowe.org/job/zowe-docs-site/job/users%252Fjack%252Flf-jenkins/6/execution/node/8/log/. Currently the base image is 1.24G, which create extra overhead to the build and server traffic. We may be able to try to make the base image slightly smaller, but I think with JDK8 and node.js v8 or v12 pre-installed, it will be still about 600M to 900M.
 
Hope this explains the issues we are having.
 
Thanks,
 
Jack (T.) Jia
Software Developer
IBM Z Management Software
IBM Systems

Phone: 1-905-413-3195
IBM

8200 Warden Ave
Markham, ON L6G 1C7
Canada
 
 
----- Original message -----
From: "John Mertic" <jmertic@...>
Sent by: zowe-dev@...
To: zowe-dev@..., Andrew Grimberg <agrimberg@...>, Daniel Pono Takamori <dtakamori@...>
Cc:
Subject: [EXTERNAL] Re: [zowe-dev] Expiring project Giza dot org domain
Date: Fri, Nov 22, 2019 11:34 AM
 
Hey Jack!
 
Adding +Andrew Grimberg and +Daniel Pono Takamori to this thread...
 
I will keep investigating the possibilities of migrating everything to LF Jenkins. One difficulty we have is the "Jenkins Library" build which will fail on LF Jenkins due to the permission limitation we have. Will see what we can do. The tests for Jenkins Library code is suggested because if it fails, it may indicate every other builds using that branch will fail. The test has to be performed against a real Jenkins server, not a virtual JVM environment because Jenkins handles Groovy scripts differently. The way of testing Jenkins Library is it will try to create a job through Jenkins API and start the build and check result, which is against the permission scheme we have on LF Jenkins.
 
Can you elaborate on the permissions issues? I thought we had built the environment to align with the existing practices, but wondering if something changed from discovery to implementation.
 
Thanks!
 
John

 

 

 
 


Re: Zowe code

John Mertic
 

Hi Tom!

Adding the +zowe-dev@... list for more context here. I'll also send you a note separately around the Zowe Conformance Program in case you wish to participate.

Thank you,

John Mertic
Director of Program Management - Linux Foundation
ASWF, ODPi, and Open Mainframe Project
Schedule time with me at https://calendly.com/jmertic



On Mon, Nov 25, 2019 at 4:27 PM Tom Williamson <tom@...> wrote:

Hello,

 

I am looking at adding code in our products to support Zowe.

 

In the doc it says: These resources are usually represented in the form of JSON or XML documents. The preferred documentation type in Zowe™ is in the JSON format.

 

Does this mean that zowe can handle data in XML format or does it require JSON?

 

I have a general Alexa interface working.  We will do a demo at the next Share.

 

Thanks

Tom

 

 

 

2701 - 2720 of 3845