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

Add supporting S3 tags #294

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

Conversation

gilgameshfreedom
Copy link

The PR is adding supporting of S3 tags - https://docs.aws.amazon.com/AmazonS3/latest/userguide/object-tagging.html

Like S3 Metadata, S3 Tags is an optional list of key-values pairs which can be applied per object.

In our use-case with the s3-plugin + MinIO and we use special lifecycle polices which delete only the objects with a specific tag assigned.

To be able to test the plugin locally I had also to increase the version of jenkins to 2.414.3.

* The key of the user tag pair to tag an upload with.
* Can contain macros.
*/
public String key;

Check warning

Code scanning / Jenkins Security Scan

Jenkins: Plaintext password storage Warning

Field should be reviewed whether it stores a password and is serialized to disk: key
Copy link
Member

Choose a reason for hiding this comment

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

Can this field contains confidential information?
From what I understand, no, so security alert is not true.

@gilgameshfreedom
Copy link
Author

Hi,

it looks like something happened yesterday with https://ci.jenkins.io/ and that's why the build for Windows was stuck. How should I retrigger the build? Just by changing the commit's message?

@gilgameshfreedom
Copy link
Author

@alecharp could you please have a look?

Copy link
Member

@alecharp alecharp left a comment

Choose a reason for hiding this comment

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

I'm wondering if you could check what happens when you try to upload a file with this changeset but with the old configuration in. Basically, using the default branch code, configure a job to to an upload to s3, then using this changeset run the job without touching the configuration.

pom.xml Outdated Show resolved Hide resolved
* The key of the user tag pair to tag an upload with.
* Can contain macros.
*/
public String key;
Copy link
Member

Choose a reason for hiding this comment

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

Can this field contains confidential information?
From what I understand, no, so security alert is not true.

@gilgameshfreedom
Copy link
Author

So I've run a Jenkins instance with s3-plugin pointed to the master branch, created two Freestyle project both using s3updoad and s3copy with gzip and without gzip, run them a few times. After that I've re-run Jenkins with s3-plugin pointed to my branch, run the projects a few times again - no problems have been observed.

@gilgameshfreedom
Copy link
Author

Hi @alecharp

Anything else should I do regarding the PR?

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