Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SKETCH: add step for getting properties #943

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

eaaltonen
Copy link

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>
Copy link

github-actions bot commented Jun 19, 2024

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

@eaaltonen
Copy link
Author

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

@eyalbe4
Copy link

eyalbe4 commented Jun 19, 2024

@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
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.

None yet

2 participants