Skip to content

Feature toggle the Properties API (and tab)#6887

Merged
ketan merged 1 commit intogocd:masterfrom
ketan:remove-properties
Sep 6, 2019
Merged

Feature toggle the Properties API (and tab)#6887
ketan merged 1 commit intogocd:masterfrom
ketan:remove-properties

Conversation

@ketan
Copy link
Copy Markdown
Member

@ketan ketan commented Sep 5, 2019

  • Disables the "Properties" tab on the job detail page
  • Disable all "GET" API calls for properties.

POST is still supported, for now, but will be removed in a couple of
releases. Additionally, the <property/> tag is rarely used. This is
used to extract metrics from XML reports (via XPATH) and publish them
using the API. Support for <property/> tag will be removed in a couple
of releases as well.

The properties API provides the ability for GoCD to store arbitrary
key-value-pair data associated with each build. The intent of this API
(at the time of developing this) was to be able to store arbitrary
metrics (like test count, coverage%, warning count, et.al.) and be
able to track progress of these metrics over time.

Fast forward to 2019, there are (much) better tools available that can
do just this.

@ketan ketan added this to the Release 19.8.0 milestone Sep 5, 2019
ketan added a commit to ketan/api.go.cd that referenced this pull request Sep 5, 2019
@ketan
Copy link
Copy Markdown
Member Author

ketan commented Sep 6, 2019

Rebasing and merging. The current VSM is here

- Disables the "Properties" tab on the job detail page
- Disable all "GET" API calls for properties.

POST is still supported, for now, but will be removed in a couple of
releases. Additionally, the `<property/>` tag is rarely used. This is
used to extract metrics from XML reports (via XPATH) and publish them
using the API. Support for `<property/>` tag will be removed in a couple
of releases as well.

The properties API provides the ability for GoCD to store arbitrary
key-value-pair data associated with each build. The intent of this API
(at the time of developing this) was to be able to store arbitrary
metrics (like test count, coverage%, warning count, et.al.) and be
able to track progress of these metrics over time.

Fast forward to 2019, there are (much) better tools available that can
do just this.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants