New Toolchain for Embedded Development
Project Challenge
Within four months:
- Set up a first official release for Jira and Confluence (with MS SQL) within a new toolchain.
- Create a user and role concept for the new toolchain and implement it for Jira and Confluence.
- Install this new toolchain behind a proxy (IIS) to give external partners secure access to the tools.
- Install and configure Crowd with Jira and Confluence to implement user and group management and Single Sign-on.
- Develop and deliver trainings.
- Optimise the existing Jenkins environment.
Solution Provided
- Set up a project plan and imported it into Jira.
- Atlassian Jira and Confluence installed and configured on a Windows server test environment with connection to a MS SQL database.
- Configured Jira and Confluence to run behind the companies IIS proxy to provide secure public internet access for the tools.
- Installed and configured Crowd for a central user and group management.
- Set up Crowd, Jira and Confluence for single sign-on.
- Developed a user and role concept and implemented this in Crowd, Jira and Confluence.
- Developed a way to have Confluence space templates and created a standard space template.
- Set-up of test scenarios and coordinated testing of Jira and Confluence and configuration on the test environment.
- Migrated the test environment into a new production environment with the latest Jira and Confluence production data within six hours.
- Set up a Sonatype demo and installed and tested a Nexus server.
- Jenkins analysis, optimisation proposal and plan with cost estimations.
- Full documentation of requirements, analysis, installation, configuration and architecture in a Confluence space.
Project Challenge
- Time limit of four months
- New toolchain
- Set-up for Jira and Confluence
- Secure tool access for externals
- Training
- Jenkins optimisation
Value Delivered
- Proper production environment
- Single sign-on
- Public access for externals
- Virtual URLs for all tools
Value Delivered
- Running production environment with Jira and Confluence with no rework or claims.
- Easier user and role access according to a concept with single sign-on.
- Standard Confluence structure with a Confluence space template.
- Less travel, as external partners can access Jira and Confluence from their home location.
- Easy to remember and systematic virtual URLs for all tools with https protocol mapped by IIS.
- A list of improvement suggestions for Jenkins (including Nexus) with cost estimations as a decision base.
Contact
Questions?
We would be happy to call you back!