github.com-drone-plugins-gi.../.drone.yml

kind: pipeline
type: vm
name: default

platform:
  os: linux
  arch: amd64
pool:
  use: ubuntu

steps:
- name: build
  image: golang:1.19
  commands:
  - go test ./...
  - sh scripts/build.sh

- name: publish (dry run)
  image: plugins/docker
  pull: if-not-exists
  settings:
    dry_run: true
    repo: plugins/github-actions
    dockerfile: docker/Dockerfile.linux.amd64
    tags:
    - latest

- name: publish
  image: plugins/docker
  pull: if-not-exists
  settings:
    repo: plugins/github-actions
    auto_tag: true
    dockerfile: docker/Dockerfile.linux.amd64
    username:
      from_secret: docker_username
    password:
      from_secret: docker_password
  when:
    event:
    - tag
added yml 2021-09-27 07:31:36 +02:00			`kind: pipeline`
(maint) move to harness.drone.io 2022-12-07 15:42:15 +01:00			`type: vm`
added yml 2021-09-27 07:31:36 +02:00			`name: default`

(maint) move to harness.drone.io 2022-12-07 15:42:15 +01:00			`platform:`
			`os: linux`
			`arch: amd64`
			`pool:`
			`use: ubuntu`

added yml 2021-09-27 07:31:36 +02:00			`steps:`
			`- name: build`
(maint) move to harness.drone.io 2022-12-07 15:42:15 +01:00			`image: golang:1.19`
added yml 2021-09-27 07:31:36 +02:00			`commands:`
			`- go test ./...`
			`- sh scripts/build.sh`

update act to v0.2.34 this also required updating the action image to node16 this is a potentially breaking change, so I don't think we want this plugin image to be tagged 'latest' if/when this change is merged to main I have also updated the drone pipeline to only publish the image on tag events, so if we give a proper tag (maybe 2.0.0) this updated plugin image will be available as plugins/github-actions:2 which will not break existing pipelines pulling latest 2022-12-22 19:24:48 +01:00			`- name: publish (dry run)`
			`image: plugins/docker`
			`pull: if-not-exists`
			`settings:`
			`dry_run: true`
			`repo: plugins/github-actions`
			`dockerfile: docker/Dockerfile.linux.amd64`
remove auto tag from dry run step 2022-12-22 19:33:29 +01:00			`tags:`
			`- latest`
update act to v0.2.34 this also required updating the action image to node16 this is a potentially breaking change, so I don't think we want this plugin image to be tagged 'latest' if/when this change is merged to main I have also updated the drone pipeline to only publish the image on tag events, so if we give a proper tag (maybe 2.0.0) this updated plugin image will be available as plugins/github-actions:2 which will not break existing pipelines pulling latest 2022-12-22 19:24:48 +01:00
added yml 2021-09-27 07:31:36 +02:00			`- name: publish`
			`image: plugins/docker`
			`pull: if-not-exists`
			`settings:`
			`repo: plugins/github-actions`
			`auto_tag: true`
			`dockerfile: docker/Dockerfile.linux.amd64`
			`username:`
			`from_secret: docker_username`
			`password:`
update act to v0.2.34 this also required updating the action image to node16 this is a potentially breaking change, so I don't think we want this plugin image to be tagged 'latest' if/when this change is merged to main I have also updated the drone pipeline to only publish the image on tag events, so if we give a proper tag (maybe 2.0.0) this updated plugin image will be available as plugins/github-actions:2 which will not break existing pipelines pulling latest 2022-12-22 19:24:48 +01:00			`from_secret: docker_password`
			`when:`
			`event:`
remove auto tag from dry run step 2022-12-22 19:33:29 +01:00			`- tag`