You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@daffodil.apache.org by "Steve Lawrence (Jira)" <ji...@apache.org> on 2021/12/19 18:58:00 UTC

[jira] [Resolved] (DAFFODIL-2595) Create podman/docker container for maintaining daffodil-site

     [ https://issues.apache.org/jira/browse/DAFFODIL-2595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Steve Lawrence resolved DAFFODIL-2595.
--------------------------------------
    Fix Version/s: 3.3.0
       Resolution: Fixed

Fixed in commit 456ee18b44ea3ef76a97425c59310e0f42889503 in the daffodil-site repo

> Create podman/docker container for maintaining daffodil-site
> ------------------------------------------------------------
>
>                 Key: DAFFODIL-2595
>                 URL: https://issues.apache.org/jira/browse/DAFFODIL-2595
>             Project: Daffodil
>          Issue Type: Improvement
>          Components: Infrastructure
>            Reporter: Mike Beckerle
>            Assignee: Steve Lawrence
>            Priority: Major
>             Fix For: 3.3.0
>
>
> It takes hours to get ruby, rubygems, jekyll, etc. all working again when you haven't used it in a while.
> Many people use this infrastructure only for maintaining the daffodil-site content, which only changes occasionally. 
> Various platform upgrades and security updates on a developer workstations break this stuff. 
> A podman/docker container with a known good configuration of these ruby and jekyll tools would massively smooth the release process. 



--
This message was sent by Atlassian Jira
(v8.20.1#820001)