profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/stig/events. GitMemory does not store any data, but only uses NGINX to cache data for a period of time. The idea behind GitMemory is simply to give users a better reading experience.
Stig Brautaset stig @circleci @sbjson Berwick-upon-Tweed, Northumberland, UK https://www.brautaset.org Father, husband, feminist, guitarist.

SBJson/SBJson 3771

This framework implements a strict JSON parser and generator in Objective-C.

stig/ox-jira.el 97

Org-mode export backend for JIRA markup

stig/ob-applescript.el 18

AppleScript integration for Org Babel

stig/couchobjc 16

Objective-C CouchDB framework

stig/dotfiles 10

My Emacs config

SBJson/ChunkedDelivery 7

An example of using SBJson 4's chunked delivery

SBJson/DisplayPretty 6

Example of reflowing JSON for OS X

stig/pac 4

My first game: a Pacman clone (what else?)

stig/AlphaBeta 3

A stab at generalised AlphaBeta search for Objective-C

Pull request review commentcircleci/circleci-docs

[CIRCLE-38345] Add docs for scheduled pipeline

+---+layout: classic-docs+title: "Scheduled Pipelines"+description: "Docs page on using Scheduled Pipeline"+version:+- Cloud+---++Schedule Pipelines allow users to trigger pipelines periodically based on a schedule.++Since the scheduled run is based on pipelines, scheduled pipelines have all the features that come with using pipelines:++- Can control the actor that's associated with the pipeline, which can enable the use of restricted contexts+- Can use dynamic config via setup workflows+- Can modify the schedule without having to change the config.yml+- Can interact with auto-cancelling of pipelines+- Can specify pipeline parameters associated with a schedule++CircleCI has APIs that allows users to create, view, edit, and delete Scheduled Pipelines.++**Note**: *At this time, the UI for Scheduled Pipelines is not available. It will become available soon.++## Getting started with scheduled pipelines in CircleCI+{: #getting-started-with-scheduled-pipelines-in-circleci }++### Start from scratch+{: #start-from-scratch }+If your project has no scheduled workflows and would like to try out scheduled pipelines:++- Have your CCI token ready or create a new one following [these steps](https://circleci.com/docs/2.0/managing-api-tokens/)+- Create a new schedule using the new Pipelines Schedule API, for example:++```+curl --location --request POST 'https://circleci.com/api/v2/project/<project-slug>/schedule' \+--header 'circle-token: <your-cci-token>' \+--header 'Content-Type: application/json' \+--data-raw '{+    "name": "my schedule name",+    "description": "some description",+    "attribution-actor": "system",+    "parameters": {+      "branch": "main"+      <additional pipeline parameters can be added here>+    },+    "timetable": {+        "per_hour": 3,+        "hours_of_day": [1,15],+        "days_of_week": ["MON", "WED"]+    }+}'+```++- Check out the `schedule` section under the [open-api docs](https://circleci.com/docs/api/v2/) for additional information++### Migrating from scheduled workflows to scheduled pipelines+{: #migrating-from-scheduled-workflows-to-scheduled-pipelines }++Currently, using Scheduled Workflows has numerous shortcomings. Some of them are listed below:++- Cannot control the actor, so scheduled workflows can't use restricted contexts+- Cannot control the interaction with auto-cancelling of pipelines+- Cannot use scheduled workflow together with dynamic config without hakcy workarounds+- Cannot change or cancel scheduled workflows on a branch without triggering a pipeline+- Cannot kick off test runs for scheduled workflows without changing the schedule+- Cannot restrict scheduled workflows from PR branches if you want the workflow to run on webhooks

I would put this in a sub-section, "why migrate?". It gets in the way for people who know they need to migrate, but want to link to that section for reference.

h42zhu

comment created time in 13 hours

Pull request review commentcircleci/circleci-docs

[CIRCLE-38345] Add docs for scheduled pipeline

+---+layout: classic-docs+title: "Scheduled Pipelines"+description: "Docs page on using Scheduled Pipeline"+version:+- Cloud+---++Schedule Pipelines allow users to trigger pipelines periodically based on a schedule.++Since the scheduled run is based on pipelines, scheduled pipelines have all the features that come with using pipelines:++- Can control the actor that's associated with the pipeline, which can enable the use of restricted contexts+- Can use dynamic config via setup workflows+- Can modify the schedule without having to change the config.yml+- Can interact with auto-cancelling of pipelines

I don't think we expose opt-in/opt-out of auto-cancelling for pipelines via scheduled pipelines, yet?

h42zhu

comment created time in 13 hours

PullRequestReviewEvent
PullRequestReviewEvent
PullRequestReviewEvent

Pull request review commentcircleci/circleci-docs

[CIRCLE-38345] Add docs for scheduled pipeline

+---+layout: classic-docs+title: "Scheduled Pipeline"+description: "Docs page on using Scheduled Pipeline"+version:+- Cloud+---++Currently, using Scheduled Workflows has numerous shortcomings for customers. Some of them are listed below:++- Cannot control the actor, so scheduled workflows can't use restricted contexts+- Cannot control the interaction with auto-cancelling of pipelines+- Cannot use scheduled workflow together with dynamic config without hakcy workarounds+- Cannot change or cancel scheduled workflows on a branch without triggering a pipeline+- Cannot kick off test runs for scheduled workflows without changing the schedule+- Cannot restrict scheduled workflows from PR branches if you want the workflow to run on webhooks++CircleCI has introduced a few new APIs that allows users to create, view, edit, and delete Scheduled Pipelines.++**Note**: *At this time, the UI for Scheduled Pipelines is not available. It will become available soon.++## Getting started with scheduled pipelines in CircleCI+{: #getting-started-with-scheduled-pipelines-in-circleci }++### Start from scratch+{: #start-from-scratch }+If your project has no scheduled workflows and would like to try out scheduled pipelines:++- Have your CCI token ready or create a new one following [these steps](https://circleci.com/docs/2.0/managing-api-tokens/)+- Create a new schedule using the new Pipeline Schedules API, for example:++```+curl --location --request POST 'https://circleci.com/api/v2/project/<project-slug>/schedule' \+--header 'circle-token: <your-cci-token>' \+--header 'Content-Type: application/json' \+--data-raw '{+    "name": "my schedule name",+    "description": "some description",+    "attribution-actor": "system",+    "parameters": {+      "branch": "master"+      <additional pipeline parameters can be added here>+    },+    "timetable": {+        "per_hour": 3,+        "hours_of_day": [1,15],+        "days_of_week": ["MON", "WED"]+    }+}'+```++- Check out the [open-api docs](https://circleci.com/docs/api/v2/) for additional information++### Migrating from scheduled workflows to scheduled pipelines+{: #migrating-from-scheduled-workflows-to-scheduled-pipelines }+- Find the scheduled trigger in your project's .circleci/config.yml+    - For example, it might look like this one:++```+daily-run-workflow:+  triggers:+    - schedule:+        # Every day, 0421Z.+        cron: "21 4 * * *"+        filters:+          branches:+            only:+              - master
              - main
h42zhu

comment created time in 2 days

Pull request review commentcircleci/circleci-docs

[CIRCLE-38345] Add docs for scheduled pipeline

+---+layout: classic-docs+title: "Scheduled Pipeline"+description: "Docs page on using Scheduled Pipeline"+version:+- Cloud+---++Currently, using Scheduled Workflows has numerous shortcomings for customers. Some of them are listed below:++- Cannot control the actor, so scheduled workflows can't use restricted contexts+- Cannot control the interaction with auto-cancelling of pipelines+- Cannot use scheduled workflow together with dynamic config without hakcy workarounds+- Cannot change or cancel scheduled workflows on a branch without triggering a pipeline+- Cannot kick off test runs for scheduled workflows without changing the schedule+- Cannot restrict scheduled workflows from PR branches if you want the workflow to run on webhooks++CircleCI has introduced a few new APIs that allows users to create, view, edit, and delete Scheduled Pipelines.++**Note**: *At this time, the UI for Scheduled Pipelines is not available. It will become available soon.++## Getting started with scheduled pipelines in CircleCI+{: #getting-started-with-scheduled-pipelines-in-circleci }++### Start from scratch+{: #start-from-scratch }+If your project has no scheduled workflows and would like to try out scheduled pipelines:++- Have your CCI token ready or create a new one following [these steps](https://circleci.com/docs/2.0/managing-api-tokens/)+- Create a new schedule using the new Pipeline Schedules API, for example:
- Create a new schedule using the Pipeline Schedules API, for example:
h42zhu

comment created time in 2 days

Pull request review commentcircleci/circleci-docs

[CIRCLE-38345] Add docs for scheduled pipeline

+---+layout: classic-docs+title: "Scheduled Pipeline"+description: "Docs page on using Scheduled Pipeline"+version:+- Cloud+---++Currently, using Scheduled Workflows has numerous shortcomings for customers. Some of them are listed below:++- Cannot control the actor, so scheduled workflows can't use restricted contexts+- Cannot control the interaction with auto-cancelling of pipelines+- Cannot use scheduled workflow together with dynamic config without hakcy workarounds+- Cannot change or cancel scheduled workflows on a branch without triggering a pipeline+- Cannot kick off test runs for scheduled workflows without changing the schedule+- Cannot restrict scheduled workflows from PR branches if you want the workflow to run on webhooks++CircleCI has introduced a few new APIs that allows users to create, view, edit, and delete Scheduled Pipelines.++**Note**: *At this time, the UI for Scheduled Pipelines is not available. It will become available soon.++## Getting started with scheduled pipelines in CircleCI+{: #getting-started-with-scheduled-pipelines-in-circleci }++### Start from scratch+{: #start-from-scratch }+If your project has no scheduled workflows and would like to try out scheduled pipelines:++- Have your CCI token ready or create a new one following [these steps](https://circleci.com/docs/2.0/managing-api-tokens/)+- Create a new schedule using the new Pipeline Schedules API, for example:++```+curl --location --request POST 'https://circleci.com/api/v2/project/<project-slug>/schedule' \+--header 'circle-token: <your-cci-token>' \+--header 'Content-Type: application/json' \+--data-raw '{+    "name": "my schedule name",+    "description": "some description",+    "attribution-actor": "system",+    "parameters": {+      "branch": "master"+      <additional pipeline parameters can be added here>+    },+    "timetable": {+        "per_hour": 3,+        "hours_of_day": [1,15],+        "days_of_week": ["MON", "WED"]+    }+}'+```++- Check out the [open-api docs](https://circleci.com/docs/api/v2/) for additional information++### Migrating from scheduled workflows to scheduled pipelines+{: #migrating-from-scheduled-workflows-to-scheduled-pipelines }+- Find the scheduled trigger in your project's .circleci/config.yml+    - For example, it might look like this one:++```+daily-run-workflow:+  triggers:+    - schedule:+        # Every day, 0421Z.+        cron: "21 4 * * *"+        filters:+          branches:+            only:+              - master+  jobs:+    - test+    - build+```++- Interpret the frequency your trigger needs to run from the cron expression+- Use the same step from `Starting from scratch` section above to create the schedule+- In the circleci config file, remove the `triggers` section so that it looks like a normal workflow++```+daily-run-workflow:+  jobs:+    - test+    - build+```++- Add workflows filtering. As scheduled pipeline is essentially a triggered pipeline, it will run every workflow in the config.+    - One way to implement workflows filtering is by using the pipeline values, for example:++```+daily-run-workflow:+  when:+    and:+      - equal: [ schedule, << pipeline.trigger_source >> ]+      - equal: [ "my schedule name", << pipeline.schedule.name >> ]

~ Are both necessary here? Is there a chance that you get a schedule name without it being a schedule?

h42zhu

comment created time in 2 days

Pull request review commentcircleci/circleci-docs

[CIRCLE-38345] Add docs for scheduled pipeline

+---+layout: classic-docs+title: "Scheduled Pipeline"+description: "Docs page on using Scheduled Pipeline"+version:+- Cloud+---++Currently, using Scheduled Workflows has numerous shortcomings for customers. Some of them are listed below:++- Cannot control the actor, so scheduled workflows can't use restricted contexts+- Cannot control the interaction with auto-cancelling of pipelines+- Cannot use scheduled workflow together with dynamic config without hakcy workarounds+- Cannot change or cancel scheduled workflows on a branch without triggering a pipeline+- Cannot kick off test runs for scheduled workflows without changing the schedule+- Cannot restrict scheduled workflows from PR branches if you want the workflow to run on webhooks++CircleCI has introduced a few new APIs that allows users to create, view, edit, and delete Scheduled Pipelines.++**Note**: *At this time, the UI for Scheduled Pipelines is not available. It will become available soon.++## Getting started with scheduled pipelines in CircleCI+{: #getting-started-with-scheduled-pipelines-in-circleci }++### Start from scratch+{: #start-from-scratch }+If your project has no scheduled workflows and would like to try out scheduled pipelines:++- Have your CCI token ready or create a new one following [these steps](https://circleci.com/docs/2.0/managing-api-tokens/)+- Create a new schedule using the new Pipeline Schedules API, for example:++```+curl --location --request POST 'https://circleci.com/api/v2/project/<project-slug>/schedule' \+--header 'circle-token: <your-cci-token>' \+--header 'Content-Type: application/json' \+--data-raw '{+    "name": "my schedule name",+    "description": "some description",+    "attribution-actor": "system",+    "parameters": {+      "branch": "master"

Let's not use master branch in examples please!

      "branch": "main"
h42zhu

comment created time in 2 days

Pull request review commentcircleci/circleci-docs

[CIRCLE-38345] Add docs for scheduled pipeline

+---+layout: classic-docs+title: "Scheduled Pipeline"

I would recommend using the plural, here and throughout the document. (And also in the file name.)

title: "Scheduled Pipelines"
h42zhu

comment created time in 2 days

PullRequestReviewEvent

Pull request review commentcircleci/circleci-docs

[CIRCLE-38345] Add docs for scheduled pipeline

+---+layout: classic-docs+title: "Scheduled Pipeline"+description: "Docs page on using Scheduled Pipeline"+version:+- Cloud+---++Currently, using Scheduled Workflows has numerous shortcomings for customers. Some of them are listed below:

I recommend leading with what Scheduled Pipelines is, and what benefits they bring, rather than listing problems with Scheduled Workflows here at the top. Those issues are irrelevant to someone who has never used scheduled workflows. Though it would make sense in a later section to explain why you should migrate.

h42zhu

comment created time in 2 days

Pull request review commentcircleci/circleci-docs

[CIRCLE-38345] Add docs for scheduled pipeline

+---+layout: classic-docs+title: "Scheduled Pipeline"+description: "Docs page on using Scheduled Pipeline"+version:+- Cloud+---++Currently, using Scheduled Workflows has numerous shortcomings for customers. Some of them are listed below:++- Cannot control the actor, so scheduled workflows can't use restricted contexts+- Cannot control the interaction with auto-cancelling of pipelines+- Cannot use scheduled workflow together with dynamic config without hakcy workarounds+- Cannot change or cancel scheduled workflows on a branch without triggering a pipeline+- Cannot kick off test runs for scheduled workflows without changing the schedule+- Cannot restrict scheduled workflows from PR branches if you want the workflow to run on webhooks++CircleCI has introduced a few new APIs that allows users to create, view, edit, and delete Scheduled Pipelines.
CircleCI has APIs that allows users to create, view, edit, and delete Scheduled Pipelines.
h42zhu

comment created time in 2 days

PullRequestReviewEvent

push eventstig/www.brautaset.org

Stig Brautaset

commit sha 6a4c732fc5c54d30fec83f892d7d3c0d1d237828

Hopefully fix the RSS-only item re-appearing in the feed

view details

push time in 8 days

push eventstig/www.brautaset.org

Stig Brautaset

commit sha 3aabff4746ffc0622362b18f081576d24bc8db83

Remove 11th item in RSS feed

view details

push time in 8 days

push eventstig/www.brautaset.org

Stig Brautaset

commit sha 7ca9e318652adf634c51e5a4eb6270d22940f9a5

fix RSS feed title

view details

push time in 9 days

push eventstig/dotfiles

Stig Brautaset

commit sha 3f539b086b44346a833de1e75bde49947ec96b2a

brew: drop MeetingBar; Fantastical has similar functionality

view details

push time in 10 days

push eventstig/dotfiles

Stig Brautaset

commit sha a1d65917d1bc30cfd3d48bf9ba38f782d7aa5b90

emacs: clock in for daily notes

view details

push time in 10 days

push eventstig/www.brautaset.org

Stig Brautaset

commit sha f75de838364cbf17e0d4c823f6120f30697bbd63

new post: Reviewing The Scout Mindset

view details

push time in 14 days

delete branch stig/www.brautaset.org

delete branch : scout-mindset

delete time in 14 days

push eventstig/www.brautaset.org

Stig Brautaset

commit sha b579e82eb9eed0bcb5df190b6f346d64940484c0

typo and grammar fixes

view details

push time in 14 days

push eventstig/www.brautaset.org

Stig Brautaset

commit sha 41b7a4202503d4a3d7236f32975ac1531fe32eb8

fixup! new post: Reviewing The Scout Mindset

view details

push time in 14 days

push eventstig/www.brautaset.org

Stig Brautaset

commit sha d205f4fdd77d046342b39995b9bf80d9f1c08aae

fixup! fixup! fixup! fixup! new post: Reviewing The Scout Mindset

view details

push time in 14 days

push eventstig/www.brautaset.org

Stig Brautaset

commit sha 6fe975a1c3e45fd09080542d4aaebe4c1b71f0f8

fixup! fixup! fixup! new post: Reviewing The Scout Mindset

view details

push time in 14 days

push eventstig/www.brautaset.org

Stig Brautaset

commit sha e061dcb6d099d5c661dc63d77f261804f9befbf9

fixup! fixup! new post: Reviewing The Scout Mindset

view details

push time in 14 days

push eventstig/www.brautaset.org

Stig Brautaset

commit sha 88bcfac32ed0b9c41f89016e16f11a90f6c822c1

fixup! fixup! new post: Reviewing The Scout Mindset

view details

push time in 14 days

push eventstig/www.brautaset.org

Stig Brautaset

commit sha 21777f229e1a3bc902f9305605e2c3f942cf3fcf

fixup! new post: Reviewing The Scout Mindset

view details

push time in 14 days

Pull request review commentcircleci/circleci-docs

fix: command bash script for create_concatenated_package_lock

 commands:     steps:       - run:           name: Combine package-lock.json files to single file-          command: npx lerna la -a | awk -F packages '{printf "\"packages%s/package-lock.json\" ", $2}' | xargs cat > << parameters.filename >>+          command: cat $(ls packages/*/package-lock.json) > << parameters.filename >>

This is untested, but I think the ls is unnecessary? How about:

          command: cat packages/*/package-lock.json > << parameters.filename >>
dok

comment created time in 15 days

PullRequestReviewEvent