Skip to content

SKETCH: add step for getting properties#943

Open
eaaltonen wants to merge 1 commit into
jfrog:masterfrom
eaaltonen:getproperties
Open

SKETCH: add step for getting properties#943
eaaltonen wants to merge 1 commit into
jfrog:masterfrom
eaaltonen:getproperties

Conversation

@eaaltonen

Copy link
Copy Markdown

Add a groovy script step to fetch custom properties from Artifactory.

NOTE: this is functional, but not suitable to be integrated directly. Some of the changes should be made to https://github.com/jfrog/build-info instead. This PR shows how to serve our use case of accessing our custom metadata and is here to solicit discussion on the API.

This provides Artifactory users with access to their additional metadata associated with artifacts stored in Artifactory, and allows pipelines to make decisions based on that metadata.

This is called roughly as:

artifactory = newArtifactoryServer( ARGS )
def props = artifactoryGetProps(
    server: artifactory,
    relativePath: "PATH/TO/ARTIFACT"
    propertyKeys: ['PROPA', 'PROPB']
)

Add a groovy script step to fetch custom properties from Artifactory.

This provides Artifactory users with access to their additional
metadata associated with artifacts stored in Artifactory, and allows
pipelines to make decisions based on that metadata.

This is called roughly as:
```
artifactory = newArtifactoryServer( ARGS )
def props = artifactoryGetProps(
    server: artifactory,
    relativePath: "PATH/TO/ARTIFACT"
    propertyKeys: ['PROPA', 'PROPB']
)
```

Signed-off-by: Eero Aaltonen <eero.aaltonen@vaisala.com>
@github-actions

github-actions Bot commented Jun 19, 2024

Copy link
Copy Markdown

CLA Assistant Lite bot All contributors have signed the CLA ✍️ ✅

@eaaltonen

Copy link
Copy Markdown
Author

I have read the CLA Document and I hereby sign the CLA

@eyalbe4

eyalbe4 commented Jun 19, 2024

Copy link
Copy Markdown

@eaaltonen,
Thank you for your contribution. We are not promoting new features for this plugin. We strongly recommend users switch to the newer JFrog Jenkins Plugin, which offers significantly more features and functionality than this plugin, including the new functionality proposed by this PR. Both plugins can be used side-by-side within the same jobs.

@eaaltonen

Copy link
Copy Markdown
Author

@eyalbe4: there is an issue that is preventing us from switching to the JFrog Jenkins plugin at this point. I've opened an issue via another channel.

If I split the parts from this PR that belong to build-info to a separate PR, would you be open to accepting them while the other issue is resolved?

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.

2 participants