Jenkins KT Documentation: Ashwini More
- Ashwini More
Development Plan
Sprint planning and release:
The sprints planned are mentioned in the Project:
DC: https://miniorange.atlassian.net/jira/software/projects/JA/boards/195/backlogHow to plan sprint, development, testing, and releases
Sprints are planned based on feature requirements and bug fixes identified/ reported by the customer. The tickets are created in backlog and a sprint is made in the project. Development and Testing are done by @Pranav Vinchurkar , Prijwal and Mahesh. Releases are done in Atlassian Marketplace by @Pranav Vinchurkar .What's the release frequency: The release frequency is as below:
Jenkins SAML SSO Free: in 2-3 months
Jenkins 2FA Free: in 2-3 months
Jenkins SAML SSO Premium: as per customer requirement or 3-4 months
Jenkins 2FA Premium: as per customer requirement or 3-4 months
What's going on in the Current Sprint:
The current sprint is completed already and we don't have a new one yet planned.
Parallel development which is in progress along with the current sprint
@Pranav Vinchurkar has all these details.
Future Roadmaps
User and Group management in 2FA Premium
2FA method advertisement in free 2FA plugins.
LDAP connection support in the SSO premium plugin
Security fixes mentioned in Jenkins community.
Customization
Cover all the customizations that are not in the marketplace version but deployed in the customer's environment (even on a test instance)
All customization has been released. checked in here: \Jenkins-apps\custom-work Each customization has a readme file which you can refer to.
Checkin code if not checked in yet, share details with the team
The code is checked in.
How are you planning to hand it to an existing team?
@Pranav Vinchurkar is already in the loop.
Customer
Cover all details of your customers.
MasterCard: Was using Jenkins Crowd connector previously. Now switched to Jenkins SAML SSO plugin to set up SSO with Crowd and Pull Users and Groups.
Tietoevry: Requested SSO support from Azure AD but needed group and user sync from the crowd. The provided plugin is checked in the custom work folder.
BestSecret: Require ignore case support for Login with email support.
InfoBlox: Added OTF group regex to extract group name from the incoming response. The code is checked in the custom work folder.
Cybereason: They are using the old Jenkins version which doesn't support the latest Mailer API versions. We have provided a custom plugin that has used older versions of the mailer API.
Other customers have been shared within the team.
How are you planning to delegate those customers to an existing team, who will be responsible for handling those customers?
@Pranav Vinchurkar will be working on these customers.
Marketing and Documentation
What's going on here
Current Documentation is released on the below platforms along with Marketplace listing for Jenkins SSO and Jenkins 2FA plugin
https://www.miniorange.com/atlassian/jenkins-single-sign-on
https://www.miniorange.com/atlassian/jenkins-two-factor-authentication-2fa-mfa/
What's a plan for the future
Improve SEO of the Jenkins plugin site pages.
Update Jenkins Settup guide
Streamline trial flow for premium plugins
Advertise OAuth and MFA support in SSO plugins.
Advertise common use cases as blogs.
Who will handle it?
Along with @Ananjan Mishra , @Pranav Vinchurkar https://miniorange.atlassian.net/people/team/b2e2af8f-7f67-4e7c-b966-b2884241e7a3 (@Ashwini More @Abhishek Jadhav @Nutan Patil @Shraddheya Athawale @Sneha Pawar) , prijwal and mahesh will be working on this
Additional revenue tracking and Tasks are mentioned in the below excel sheets:
Jenkins support plan calculator
https://docs.google.com/spreadsheets/d/1hLAshzMczub2mkf5my7kGpvyI_Y2mbq-zdqfmtHNMB0/edit?gid=0#gid=0
Jenkins dream team sheet