Thanks Lionel. I'll take a peek at it, but our current direction is to piggyback on similar pipeline functionality our installation is already using for all the other platforms as much as possible. Your solution appears to be a very nice implementation, from what I have read, but doesn't address the needed processes to promote code, packages, etc from development stage through to Production.
_____________________________________________________________________________________________________ Dave Jousma AVP | Manager, Systems Engineering Fifth Third Bank | 1830 East Paris Ave, SE | MD RSCB2H | Grand Rapids, MI 49546 616.653.8429 | fax: 616.653.2717 -----Original Message----- From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of Lionel B Dyck Sent: Wednesday, November 20, 2019 5:01 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Mainframe DEVOPS **CAUTION EXTERNAL EMAIL** **DO NOT open attachments or click on links from unknown senders or unexpected emails** There is now a tool that will let your mainframe developers who are currently very productive using ISPF to interface to git. Check out https://protect2.fireeye.com/url?k=23e2235b-7fbed754-23e209c3-0cc47a33347c-0ba6f4518c1b7c75&u=https://zigi.rocks/ for more info. The V1R1 is about to be released into the wild - a release candidate is current available for the brave. This update addresses many of the issues in the original v1r0 release. Why use ISPF to interface to git: 1. Many developers are very comfortable and thus very productive using ISPF tools. 2. There have been many extensions to ISPF edit, in house developed, cbttape, and vendor, that extend ISPF Edit significantly to improve productivity. 3. The younger developers, who may already know about git, will find it familiar while remaining on the mainframe 4. The more seasoned developers will not have to spend time learning a new development interface and can continue to produce Zigi - the Z ISPF Git Interface Lionel B. Dyck <sdg>< Website: https://protect2.fireeye.com/url?k=98b27cf5-c4ee88fa-98b2566d-0cc47a33347c-e71e673d8eea16a2&u=http://www.lbdsoftware.com/ "Worry more about your character than your reputation. Character is what you are, reputation merely what others think you are." - John Wooden -----Original Message----- From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of Jousma, David Sent: Wednesday, November 20, 2019 3:06 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Mainframe DEVOPS All, We are evaluating moving from standard green screen application development to using the new tooling including iDZ-> GIT -> IBM DBB, ->Jenkins -> Urban Code Deploy, etc. Working on a mini POC in the sandbox, and am having a hard time finding z/OS security requirements for running the Jenkins slave as mainframe Unix user, and what it really needs access to. I'm still learning this territory, but my impression is the Jenkins server (off platflorm) communicates with the Jenkins slave on the MF and is a pipeline control tool, and issues GIT, IBM DBB build commands, and that the intention that it does that work on behalf of others, which could be an individual developer, or could be the userid of the "change management process", etc. I'm hoping that there are some shops out there already doing this, and would interested in sharing some information off-list? Thanks, Dave ____________________________________________________________________________ _________________________ Dave Jousma AVP | Manager, Systems Engineering [cid:image003.png@01D4F915.C9E34050] Fifth Third Bank | 1830 East Paris Ave, SE | MD RSCB2H | Grand Rapids, MI 49546 616.653.8429 | fax: 616.653.2717 This e-mail transmission contains information that is confidential and may be privileged. It is intended only for the addressee(s) named above. If you receive this e-mail in error, please do not read, copy or disseminate it in any manner. If you are not the intended recipient, any disclosure, copying, distribution or use of the contents of this information is prohibited. Please reply to the message immediately by informing the sender that the message was misdirected. After replying, please erase it from your computer system. Your assistance in correcting this error is appreciated. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu <mailto:lists...@listserv.ua.edu> with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN **CAUTION EXTERNAL EMAIL** **DO NOT open attachments or click on links from unknown senders or unexpected emails** This e-mail transmission contains information that is confidential and may be privileged. It is intended only for the addressee(s) named above. If you receive this e-mail in error, please do not read, copy or disseminate it in any manner. If you are not the intended recipient, any disclosure, copying, distribution or use of the contents of this information is prohibited. Please reply to the message immediately by informing the sender that the message was misdirected. After replying, please erase it from your computer system. Your assistance in correcting this error is appreciated. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
