search

concourse / concourse-pipeline-resource

!!! use the `set_pipeline` step instead !!!
https://concourse-ci.org/jobs.html#schema.step.set-pipeline-step.set_pipeline
MIT License
76 stars 42 forks source link

Not deploying minor version change as latest version #63

Closed siyuantan closed 4 years ago

siyuantan commented 4 years ago

Not deploying the latest version from artifactory after successfully fetching the latest version

Bug Report

Pipeline is unable to detect and deploy minor version change as latest version from artifactory. This is due to version number increment from X.X.99 > X.X.100 > X.X.101

Steps to Reproduce

After pipeline successfully run tests, version is up from X.X.99 to X.X.100. Pipeline deploys version X.X.99 on server and showing X.X.99 as latest version on pipeline while X.X.100 is placed at the bottom of the list of version as an older version. I had to disable every old version (X.X.99...) and only enabling the latest version (X.X.100) to deploy the latest version.

Note: Screen capture illustrates the issue with X.X.101 instead of X.X.100 concourse version issue-1-edited concourse version issue-2-edited

Expected Results

It should detect X.X.100 as the latest version and place it right at the top instead of X.X.99 as latest and placed X.X.100 as old version

Actual Results

Pipeline still deploys version X.X.99 on server and showing X.X.99 as latest version on pipeline while X.X.100 is placed at the bottom of the list of version as an older version.

Additional Context

N.A.

Version Info

xtremerui commented 4 years ago

Are you sure about the resource type of the resource xxxx-artifactory is this concourse-pipeline i.e.

resource_types:
- name: concourse-pipeline
  type: docker-image
  source:
    repository: concourse/concourse-pipeline-resource

While I am checking here the check response of this resource type is version: md5 not what you shown version: semver

xtremerui commented 4 years ago

Closing this as the issue is from a different resource.