PCM Development/Palladio Concall/Minutes 20180514

Participants

• Markus Frank
• Max Scheerer
• Sebastian Krach
• Stephan Seifermann
• Dominik Werle

Agenda

• Service release (Stephan)
  • Oxygen-based drop fixes PALLADIO-425 PALLADIO-428
  • Any other artifacts to be updated to Oxygen?
  • Version number 4.1.1 ?
• Status update
  • BWCloud (Max)
  • OAuth2 for authorization (Dominik)
  • Tycho builds (Stephan)
    • Workflow engine migrated [1]
    • Javadoc is still missing -> adjust existing ant task
• Organizing Github repositories/organizations (Stephan)
  • Usage of Wiki/Issues on Github
    • Problem: Multiple locations of issues for instance in Architectural Templates
    • Suggestion: Disable issues and wiki on Github and add README.md that refers to our wiki, JIRA, and the Jenkins build
  • Suggestions for moving projects from KIT-SDQ to MDSD-Tools
    • Ecore2Txt (framework for M2T transformations)
    • XAnnotations (helpers for writing Xtend code easier)
    • SDQ-Commons (helpers for EMF, Eclipse, and Java to be used with xtend)
    • Demo-Metamodels (typical toy examples)
• SimuLizar Developer Meeting
• Change of concall time (3pm) (Stephan)

Minutes

• Service Release:
  • No compatibility with Java 9. Fixed in nightly. Release as "subminor" release?
    • Light-weight solution: Only release product, since it is only a Eclipse problem.
    • Objections/known compatibility problems?
      • MF: Oxygen+PCM works. SDK: No specific problems w/ Java 9 and Eclipse (problem can be fixed by correctly parametrizing Eclipse)

• Status update
  • BWCloud (Max S.): Jenkins Slave / OpenStack
    • Jenkins Slave: connect via SSH to nodes
    • OpenStack: starts VMs on demand. VMs are "clean", installing JREs takes time. Can be automated. Plugin is not documented. StS: bwCloud pricing unclear. OpenStack is principaly interesting. On average builds are not long (5 minutes), if initialization takes longer, we gain nothing. Nightly builds could be supported by correctly setting the time for retaining sleeping VMs. Which builds can be grouped on the instanes? Group the builds by dependencies. Clone jobs, deploy them together and find out if the build process works, could be problematic for Buckminster based builds.
  • OAuth2 for authorization (Dominik)
    • move to next concall
  • Tycho builds (Stephan)
    • build migrated (Workflow engine), works in Tycho.
    • Javadoc is separate job, not yet ported. Has dependencies to buckminster artefacts (cached update sites, local target platforms, ...).

• Organizing Github repositories/organizations (Stephan)
  • Usage of Wiki/Issues on Github
    • GitHub-Issues/-Wiki is used for some projects (ATs)
    • MF: was (partially) discussed at the retreat. Forward from GitHub to Jira. Put link into GitHub, then issues are automatically added to the Jira. In one direction or the other. (GitHub->Jira, Jira->GitHub?). TODO: StS research
  • Suggestions for moving projects from KIT-SDQ to MDSD-Tools
    • Will be moved. Need to be maintained in MDSD-Tools, however. Needs new build server.

• Coding session / Architectural meeting
  • 08.06.2018. Start at 8:30 - 10:00 ?? TODO: Ask Steffen Becker.
  • Additional topics: Please add to Agenda for Coding Session page.

• Change of concall time (3pm) (Stephan)
  • TODO: per email