Jira (PDB-4379) Automate Manual Repo Maintenance Tasks

[Austin Blatt (Jira)]

Austin Blatt updated an issue

PuppetDB / PDB-4379 Automate Manual Repo Maintenance Tasks Change By: Austin Blatt Summary: PuppetDB CI Improvements Automate Manual Repo Maintenance Tasks Add Comment

This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)

[Austin Blatt (Jira)]

Austin Blatt updated an issue

PuppetDB / PDB-4379 Automate Manual Repo Maintenance Tasks Change By: Austin Blatt

PuppetDB now auto There are automate - promotes into PE able tasks that we currently perform manually for releases and general keeping-the-lights- on merges to FOSS maintenance of the two PuppetDB Git repos. They all have context switching and cognitive-overhead costs , but there's still more the worst of these are the ones like creating merge-ups in the process of maintaining our LTS branch(es). This requires a few minutes of work to do w create the merge-up, then 20-30 minutes of tests running, followed by a few more minutes to commit the merge-up . r If you can fill that interim period with something productive, the cost is relatively low, but if the cost of context switching is high enough that can easily become a task that "costs" 40 minutes . t improving our CI pipelines. PDB-4520 is different that the other 3

Add Comment

[Austin Blatt (Jira)]

Austin Blatt updated an issue

PuppetDB / PDB-4379 Automate Manual Repo Maintenance Tasks Change By: Austin Blatt

There are automate-able tasks that we currently perform manually for releases and general keeping-the-lights-on maintenance of the two PuppetDB Git repos. They all have context switching and cognitive-overhead costs, but the worst of these are the ones like creating merge-ups in the process of maintaining our LTS branch(es). This requires a few minutes of work to create the merge-up, then 20-30 minutes of tests running, followed by a few more minutes to commit the merge-up. If you can fill that interim period with something productive, the cost is relatively low, but if the cost of context switching is high enough that can easily become a task that "costs" 40 minutes. PDB-4520 is different that the other 3 4 tickets, it's just wrong behaviour that could result in us merging broken code.

Add Comment

[Austin Blatt (Jira)]

Austin Blatt updated an issue

PuppetDB / PDB-4379 Automate Manual Repo Maintenance Tasks Change By: Austin Blatt

There are automate-able tasks that we currently perform manually for releases and general keeping-the-lights-on maintenance of the two PuppetDB Git repos. They all have context switching and cognitive-overhead costs, but the worst of these are the ones like creating merge-ups in the process of maintaining our LTS branch(es). This requires a few minutes of work to create the merge-up, then 20-30 minutes of tests running, followed by a few more minutes to commit the merge-up. If you can fill that interim period with something productive, the cost is relatively low, but if the cost of context switching is high enough that can easily become a task that "costs" 40 minutes.

PDB-4520 is different that than the other 4 tickets, it's just wrong behaviour that could result in us merging broken code.

Add Comment

[David Piekny (Jira)]

David Piekny updated an issue

PuppetDB / PDB-4379 Automate Manual Repo Maintenance Tasks

Change By: David Piekny Epic Status: To Do Done

Add Comment

This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d)