Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • E escet
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Graph
    • Compare
    • Locked Files
  • Issues 92
    • Issues 92
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
  • Merge requests 5
    • Merge requests 5
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Releases
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Eclipse ProjectsEclipse Projects
  • Eclipse ESCET (Supervisory Control Engineering Toolkit)
  • escet
  • Issues
  • #394
Closed
Open
Issue created Jul 04, 2022 by Dennis Hendriks@ddennisMaintainer

Automate updating the standard visible ESCET website

Currently, we deploy release websites to eclipse.org/escet/<release_version/*. And one of those gets set as the standard visible website at eclipse.org/escet/*. The steps are a bit involved, and manual. This could be automated. The Eclipse TRACE4CPS project has that in place.

Furthermore, with the changes in #386 (closed), the release-specific websites get links to the release-specific pages. It may be good to replace those by standard visible website URLs (thus taking out the version number) when a version-specific website is promoted to standard visible website. An automatic replacement could be done for this.

Assignee
Assign to
Time tracking

Copyright © Eclipse Foundation, Inc. All Rights Reserved.     Privacy Policy | Terms of Use | Copyright Agent