Skip to content

Conversation

@peter277
Copy link

@peter277 peter277 commented Jul 19, 2025

Add support for optional attach parameter to disable artifact attachment

fixes #620

Checklist

  • Make sure there is a GitHub issue filed
    for the change (usually before you start working on it). Trivial changes like typos do not
    require a GitHub issue. Your pull request should address just this issue, without
    pulling in other changes.
  • Each commit in the pull request should have a meaningful subject line and body.
  • Format the pull request title like [#<num>] - Fixes bug in ApproximateQuantiles,
    where you replace #<num> with the appropriate GitHub issue. Best practice
    is to use the GitHub issue title in the pull request title and in the first line of the
    commit message.
  • Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
  • Run mvn clean verify to make sure basic checks pass. A more thorough check will
    be performed on your pull request automatically.
  • You have run the integration tests successfully (mvn -Prun-its clean verify).

If your pull request is about ~20 lines of code you don't need to sign an
Individual Contributor License Agreement if you are unsure
please ask on the developers list.

To make clear that you license your contribution under
the Apache License Version 2.0, January 2004
you have to acknowledge this by using the following check-box.

Copy link
Member

@slawekjaranowski slawekjaranowski left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

simple test will be appreciated

@peter277 peter277 force-pushed the add-attach-option branch from 99500d0 to 26dfd96 Compare July 19, 2025 08:55
… attaching output artifacts when attach parameter set to false
@peter277
Copy link
Author

simple test will be appreciated

I have added a new integration test attach_skip to this pull request to test the new parameter's behaviour. Would appreciate your review.

@peter277
Copy link
Author

Hi Team - just checking in to see if there’s anything I can do to help move this PR forward? Happy to make adjustments if needed.

CC: @slawekjaranowski, @bmarwell

@peter277
Copy link
Author

Thanks @bmarwell for the review - I have incorporated your suggested changes into the branch.

Copy link
Contributor

@bmarwell bmarwell left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd remove the last if-else, but works for me.


try {
File target = new File( basedir, "target" )
if ( !target.exists() || !target.isDirectory() ) {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we can simply use a groovy assert

https://groovy-lang.org/semantics.html#_power_assertion

but it is not a blocker for it

@peter277
Copy link
Author

Hi Team - just checking in to see if there’s anything else needed before this PR can be merged? Do I need to sign an individual contributor license agreement, given that the change only adds a flag?

Was hoping there might be a release in the near future including this change so that I could start using it.

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.

Add support for optional attach parameter to disable artifact attachment

3 participants