Not downloading the newest files

[codesuki]

I have a pipeline similar to ci.concourse.ci.
After creating a RC version it builds the source, uploads to github release, builds helm charts and merges with github release binaries, uploads both charts and binaries -> deploys.

When I just rebuild the charts and upload them to the github release the deploy step always deploys the old charts. When I download the charts manually from github to check, they are actually the correct, new charts.

Is there any cache for resources in concourse? Maybe something is wrong with my pipeline. Not sure.

    serial: true
    plan:
      - aggregate:
          - get: source
            passed: [rc]
            trigger: true
          - get: version
            passed: [rc]
            trigger: true
      - aggregate:
          - task: build

 - name: build-charts
    serial: true
    plan:
      - aggregate:
          - get: source
            passed: [build]
            trigger: true
          - get: charts
            trigger: true
          - get: version
            passed: [build]
            trigger: true
          - get: rc
            passed: [build]
            trigger: true
      - task: build-charts
      - put: github-release
...

  - name: deploy-rc
    serial: true
    interruptible: true
    plan:
      - aggregate:
          - get: source
            passed: [build-charts]
          - get: version
            passed: [build-charts]
            trigger: true
          - get: config
            passed: [config-smoke-test]
            trigger: true
          - get: rc
            passed: [build-charts]
            trigger: true
            params:
              globs:
                - '*-chart.tgz'
    - deploy

[emcniece]

Is your release resource checking for draft releases?

I'm working through a problem right now where my draft releases are told to deliver the code for the release, but the actual code obtained by the resource is from the previous release and not the release that triggered the action.

My guess is that the resource can't find the archive on the draft resource, so it gets the most recent archive instead.

- name: draft-pre-release
  type: github-release
  source:
    owner: me
    repository: my-app
    access_token: ((github-token))
    drafts: true
    release: false
    pre_release: true

[cagiti]

Looking at the code snippet above, it seems that you’re passing the same version between your jobs, so I wouldn’t expect the built artefact from the build job in the deploy job. Remove passed from the resource in the deploy job.

[mook-as]

I am seeing a similar issue (with current github-release-resource), but can't quite tell if it is the same one.

When calculating the timestamp, we only look at the published and created times for the release, and ignore any asset time stamps. This means that, for example, if a release is created (as a draft), then assets are uploaded in a separate task, that will never be reflected in the resource. Even though the in step would get different data, as far as concourse is concerned the metadata (from check) is the same and therefore it doesn't need to redo the in.

[taylorsilva]

Stale issue.

[jamie-pate]

I worked around this by having 2 resources.. with a delay job between them..

• release-metadata just downloads the timestamp
• then a delay task checks the timestamp and delays until after 30 min from the timestamp.. to make sure the assets are uploaded properly...
• then release resource downloads the files I need with a glob filter

      - get: godot-release-meta
        # maybe switch to every version if we aren't getting them all?
        version: latest
        trigger: true
        params:
          globs:
            - xxxxnothingxxxx
      - task: delay
        config:
          platform: linux
          image_resource:
            type: registry-image
            source:
              repository: debian
              tag: bookworm
          run:
            path: sh
            args:
              - -ceux
              # wait for all asset files to be uploaded...
              # it seems like they create the release, then the build files come ~ 10..20 min later...
              # release at 3:15, SHA512-SUMS.txt at 3:32
              - |
                ts="$(TZ=utc date -d "$(cat timestamp)" +%s)"
                now="$(date +%s)"
                delay=$(( 60 * 30 ))  # 30 minutes to give some margin for slow builds
                remaining=$(( $delay - ($now - $ts) ))
                if [ $remaining -gt 0 ]; then
                  sleep $remaining
                fi
            dir: godot-release-meta
          inputs:
            - name: godot-release-meta
      - get: godot-release
        version: latest
        params:
          globs:
            - Godot_v*_linux.x86_64.zip
            # grab the export templates, ignoring the mono templates
            - Godot_v*!(mono)_export_templates.tpz

resources:
  - &godot-release
    name: godot-release-meta
    type: github-release
    source:
      owner: godotengine
      repository: godot-builds
      access_token: ((github_access_token.token))
      release: true
      pre_release: true
      tag_filter: ((tag_filter))
      order_by: time
      # this doesn't work since godot doesn't follow semver:
      # semver_constraint: '>= ((min_godot_version))'
  - <<: *godot-release
    name: godot-release