OpenNCP - Continuous Integration

10 Sep 2015 

Estimated - 13:00 to 14:00 CEST

Performed - 13:00 to 13:35 CEST

AGENDA

a) Follow up release management activities

...

PARTICIPANTS

Today's Meeting Participants:

...

• Release Management: https://openncp.atlassian.net/wiki/x/OQCp
  • Maintaining legacy branches (aka the 1.1.n vs. 2.x shootout):https://openncp.atlassian.net/wiki/x/HoDD
  • Release Plan and Actions: https://openncp.atlassian.net/wiki/x/XQAYAw
    
    
• OpenNCP Releases:https://openncp.atlassian.net/wiki/x/GoAmAg
  
• OpenNCP Release Notes:https://openncp.atlassian.net/wiki/x/C4BIAQ
  • 2.2.0 Release Changelog and Notes:https://openncp.atlassian.net/wiki/x/EgFPAw
    
    
• Version Management:https://openncp.atlassian.net/wiki/x/CQB9
  
  
• Continuous Integration Workflow:https://openncp.atlassian.net/wiki/x/F4BL
• Integration of CI Environment With Gazelle Services: https://openncp.atlassian.net/wiki/x/MIDh

MEETING NOTES

a) Jenkins to Bamboo

• Studying to move from Jenkins to Bamboo - this is very "green" at this point
• Estimated to shut the service CI Environment from iUZ - 30th - End of September
• Isabel: is this date compliant with the timetable?

Jerome:

S:

• • We installed one version of JENKINS.
  • Kostas and Marcello - ask to confirm what is required
  • Jenkins is up but not accessible from outside - asked DIGIT to configure this - complicated because JENKINS is not "supported" by EC
  • If we have a problem, do you think you can export a VM to ensure we have a backup? Is it complicated?
  • Isabel Cruz: I would prefer to have the services alive for another month and have a live service to ensure the service keeps avilable. I prefer to make this compromise: service available until END OF OCTOBER.
    • JeromeS: End of next week I can be able to tell if the iUZ environment will be needed or not.
    • Isabel Cruz: iUZ will keep the services alive. No need to wait for any confirmation.
    • Michelemichele.foucart: Maybe it would be interesting to organize an external test as soon as Jerome is ready and with feedback from DIGIT. When would this feasible?
    • Jerome: 
    • Michele: use it for a new release.
    • Kostas Karkaletsiscould S and michele.foucart: perhaps ask Kostas Karkaletsis as member of tech committee and current Release Manager if he could validate if the JENKINS is OK.
      • Rui Alves (Unlicensed): PT was willing to test as well. We should also go to the TECH COMMITTEE as suggested by Michele michele.foucart, or Kostas as Karkaletsis as a Release Manager.
      • Timeline
        Time
        • S:
        depends
        •  depends - planning: we plan to have it ready (at least the acceptance for being available from outside)
        • before end of next week we will have more info.

  JeromeS: Specific users in the iUZ environment?

  • • Isabel don't have the info right now.

  ...

  • • S proposed to send an e-mail to iUZ to check this.

  S: 

  • If I progress on the server and be available outside: I would provide a user for PT...
  • Michelemichele.foucart and Rui Alves (Unlicensed): We could adress this in the BiWeekly Meeting and if needed, schedule a next meeting on that week (21-25th Sept).
  • About S: About the Migration from JENKINS to BAMBOO... Plugin used in Jenkins doesn't exist in Bamboo.
    •  Rui Alves (Unlicensed) and S: Address this question in the BiWeekly Meeting to get help from the community: Plug-in used in Jenkins .

   

   

   

  a) Follow up release management activities

  •  Licinio Kustra Mano: Next release (maybe by the end of July, beginning of August) will be handled by the Alexandre Santos and Joao Cunha supervised by Kostas Karkaletsis, and observed by S
  •  Kostas Karkaletsis: Will work to enhance the topic description taking in consideration the most challenging tasks to be done during the process;

  ...

  Meeting notes:

  Joao Cunha: A new version of OpenNCP (2.3.0) was planned end of July. It will have to be postponed due to problems encountered with LARM solution.
  

  b) Progress monitoring of CI migration

  Meeting notes:

  michele.foucart:

  1. Feedback received from iuz, end of Jenkins hosting : end of September.
  2. Migration of Jenkins to Bamboo @EC: Acceptance ready end of August; production ready end of October.
  3. 2 fallback solutions have been envisaged:
  • Hosting Jenkins on a local environment @EC (but not accessibke from the oustide, as emergency situation): environment is ready
    • Jerôme is currently installing Jenkins, based on the last image of Jenkins from the USB stick, using the old jobs directories.
      • Jerôme received from Isabel info with Jenkins plug in allowing to access to the iuz Jenkins remotely. But it does not work that way.
        • Mail sent to Isabel on 31/07 with alternative solutions using FTP transfer 
  • Hosting Jenkings at the data center of EC DIGIT, accessible from outside of the EC
    • Because we request external access, we are entering an exception procedure. With the holiday perod, the person in charge is not available, so the process is longer than usual. Estimate to have environment ready: 2 weeks 
    • 2 additional weeks are foreseen to install Jenkins which leads us to end of August.

  ACTIONS NEEDED

  Today's meeting actions:

  ...

  DEVELOP

                  DEVELOP-epSOS.Audit.Manager

                  DEVELOP-epSOS.Automatic.Data.Collector

                  DEVELOP-epSOS.CDADisplayTool

                  DEVELOP-epSOS.Configuration.Manager

                  DEVELOP-epSOS.Data.Model

                  DEVELOP-epSOS.Default.Policy.Manager

                  DEVELOP-epSOS.OpenATNA

                  DEVELOP-epSOS.PT

                  DEVELOP-epSOS.PT.ClientSide

                  DEVELOP-epSOS.PT.ServerSide

                  DEVELOP-epSOS.SAML.Assertion.Validator

                  DEVELOP-epSOS.Security.Manager

                  DEVELOP-epSOS.STORK.Plugin

                  DEVELOP-epSOS.Transformation.Manager

                  DEVELOP-epSOS.TRC-STS

                  DEVELOP-epSOS.TRC-STS.Client

                  DEVELOP-epSOS.TSAM

                  DEVELOP-epSOS.TSAMSync

                  DEVELOP-epSOS.Utilities

                  DEVELOP-OpenNCP.Portal

                  DEVELOP-TSLSync

   

  RELEASE.X.X.X

                  RELEASE.2.0.3-.TRC-STS

                  RELEASE.2.0.3-epSOS.Audit.Manager

                  RELEASE.2.0.3-epSOS.PT

                  RELEASE.2.0.3-epSOS.PT.ClientSide

                  RELEASE.2.0.3-epSOS.PT.ServerSide

                  RELEASE.2.0.3-epSOS.SAML.Assertion.Validator

                  RELEASE.2.0.3-epSOS.Transformation.Manager

                  RELEASE.2.0.3-OpenNCP.Portal

                  RELEASE.2.0.3-TSLSync

                  RELEASE.2.2.0-epSOS.Utilities

   

                  STATIC ANALYSIS

                  StaticAnalisys_-_epSOS.STORK.Plugin

                  StaticAnalysis_-_epSOS.Data.Model

                  StaticAnalysis_-_epSOS.Protocol.Terminators

                  StaticAnalysis_-_epSOS.Utilities

   

                  TESTING

                  TESTING-epSOS.PT.ClientSide

                  TESTING-epSOS.PT.ServerSide

   

  TRILLIUM

                  TRILLIUM_-_CDA_DISPLAY_TOOL

                  TRILLIUM_-_OpenNCP_Portal

                  TRILLIUM_-_PT_(Bug-Fixing)

                  TRILLIUM_-_PT_ADDITIONAL_LIBS_(KP_CLIENTS)

                  TRILLIUM_-_PT_XCA_CLIENT_(KP_CLIENTS)

                  TRILLIUM_-_PT_XCPD_CLIENT_(KP_CLIENTS)

                  TRILLIUM_-_SECURITY_UTILS

                  TRILLIUM_-_TRILLIUM.CONNECTOR.EU-US

   

  TRILLIUM-DEPLOY

                  NCP-IT_-_CLIENT

                  NCP-IT_-_SERVER_(MOCK_CONNECTOR)

                  TRILLIUM-GW_-_CLIENT

                  TRILLIUM-GW_-_SERVER_(MOCK_CONNECTOR)

  ...

  NEXT MEETING:

  •  Rui Alves (Unlicensed) and michele.foucart: adress this in the BiWeekly Meeting and if needed, schedule a next meeting on that week (21-25th Sept).

  ...

   

  ACTIONS NEEDED:

  •  
    

  ...