Concourse Notes: Difference between revisions

From Federal Burro of Information
Jump to navigationJump to search
(Created page with "== cool resources == <pre> - name: registry-image type: registry-image source: repository: concourse/registry-image-resource tag: "1.6.0" username: teamsre password: ((dockerhub.token)) - name: helm type: registry-image source: repository: typositoire/concourse-helm3-resource tag: v1.24.2 username: teamsre password: ((dockerhub.token)) - name: bitbucket-build-status type: registry-image sour...")
 
No edit summary
 
(One intermediate revision by the same user not shown)
Line 34: Line 34:
       password: ((dockerhub.token))
       password: ((dockerhub.token))
</pre>
</pre>
== fun with instances ==
set a pipe instance?
fly -t ciserver sp -p mypipeline  -c ci/concourse/pipelines/release.yaml --instance-var stage-release=1.98.1
destroy a pipeline?
fly -t ciserver destroy-pipeline -p mypipeline/staging-release:1.98.1
points of note:
* "sp" same as "set-pipeline"
* "dp" same as "destroy-pipeline"
* instance-var command line option in set-pipeline becomes <piplinename>/variable:value in destroy pipeline.
== examinig activity ==
fly -t alias builds

Latest revision as of 18:54, 4 June 2024

cool resources

  - name: registry-image
    type: registry-image
    source:
      repository: concourse/registry-image-resource
      tag: "1.6.0"
      username: teamsre
      password: ((dockerhub.token))

  - name: helm
    type: registry-image
    source:
      repository: typositoire/concourse-helm3-resource
      tag: v1.24.2
      username: teamsre
      password: ((dockerhub.token))

  - name: bitbucket-build-status
    type: registry-image
    source:
      repository: shyxormz/bitbucket-build-status-resource
      tag: v1.6.0
      username: teamsre
      password: ((dockerhub.token))

  - name: slack-notification
    type: registry-image
    source:
      repository: cfcommunity/slack-notification-resource
      tag: latest
      username: teamsre
      password: ((dockerhub.token))


fun with instances

set a pipe instance?

fly -t ciserver sp -p mypipeline  -c ci/concourse/pipelines/release.yaml --instance-var stage-release=1.98.1

destroy a pipeline?

fly -t ciserver destroy-pipeline -p mypipeline/staging-release:1.98.1

points of note:

  • "sp" same as "set-pipeline"
  • "dp" same as "destroy-pipeline"
  • instance-var command line option in set-pipeline becomes <piplinename>/variable:value in destroy pipeline.

examinig activity

fly -t alias builds