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

Allow managed non-file task properties to be registered as outputs #9190

Open
aalmiray opened this issue Apr 22, 2019 · 6 comments
Open

Allow managed non-file task properties to be registered as outputs #9190

aalmiray opened this issue Apr 22, 2019 · 6 comments
Labels
a:feature A new functionality in:configuration-model lazy api, domain object container

Comments

@aalmiray
Copy link
Contributor

Expected Behavior

Scalar properties such as Property<String> can be cached as outputs using an @Output annotation.

Current Behavior

Only file based properties (files & directories) can be cached with @OutputFile, @OutputDirectory, @OutputFiles, @OutputDirectories.

Context

A task takes Property<String> as inputs, issues a REST call, and returns a resource id. The resource id will always be the same given identical inputs. Current workaround is to store the resource id in a file that uses the given inputs as a key (hashing values together for example). However this pollutes the build directory with manually crafted files.

@aalmiray aalmiray added the a:feature A new functionality label Apr 22, 2019
@aalmiray aalmiray changed the title Allow managed non-file properties to be registered as outputs Allow managed non-file task properties to be registered as outputs Apr 22, 2019
@lptr
Copy link
Member

lptr commented Apr 23, 2019

If we do this, we should make @Input work with Provider<? extends FileSystemLocation> inputs, too. Doing so would simplify the input/output annotation API, as we could retire all the @InputFile, @InputFiles, @InputDirectory, @OutputFile, @OutputFiles, @OutputDirectory, @OutputDirectories annotations for Provider-style inputs and outputs.

@stale
Copy link

stale bot commented Sep 10, 2020

This issue has been automatically marked as stale because it has not had recent activity. Given the limited bandwidth of the team, it will be automatically closed if no further activity occurs. If you're interested in how we try to keep the backlog in a healthy state, please read our blog post on how we refine our backlog. If you feel this is something you could contribute, please have a look at our Contributor Guide. Thank you for your contribution.

@stale stale bot added the stale label Sep 10, 2020
@aalmiray
Copy link
Contributor Author

Ping

@stale stale bot removed the stale label Sep 10, 2020
@stale
Copy link

stale bot commented Sep 10, 2021

This issue has been automatically marked as stale because it has not had recent activity. Given the limited bandwidth of the team, it will be automatically closed if no further activity occurs. If you're interested in how we try to keep the backlog in a healthy state, please read our blog post on how we refine our backlog. If you feel this is something you could contribute, please have a look at our Contributor Guide. Thank you for your contribution.

@stale stale bot added the stale label Sep 10, 2021
@aalmiray
Copy link
Contributor Author

Ping

@stale stale bot removed the stale label Sep 11, 2021
@lptr
Copy link
Member

lptr commented Sep 13, 2021

This is still on the drawing board, but no immediate plans to deliver it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
a:feature A new functionality in:configuration-model lazy api, domain object container
Projects
None yet
Development

No branches or pull requests

3 participants