Keeping unix execute permission on build artifacts

Answered

Hi All -

I'm having an issue where we have a build (Build A) that generates some artifacts that are needed by other builds.  The only problem is these artifacts need to have their unix execute bit preserved.  I've noticed when when I have a new build Build B that has Build A's artifacts as a dependency, the artifacts are extracted , but with no execute bit.  Is there any way around this?

Thanks,
Lester

3 comments
Comment actions Permalink

Hello,

  Could you please provide more details on the issue. What are your artifacts? How do you pack it to archive?
  Please provide more details.

  Thanks,
  KIR

0
Comment actions Permalink

I wanted to +1 this.

 

I have a build A that publishes a script lets say `scriptA.sh` which is checked in my VCS repository - with the executable bit set. Build A then publishes that artifact (no archiving).

 

Build B depends on Build A as an artifact dependency. `scriptA.sh` no longer has the executable bit set.

0
Comment actions Permalink

Hello,

We have the related ticket in our issue tracker: https://youtrack.jetbrains.com/issue/TW-4651. Please vote for it and try the workaround.

0

Please sign in to leave a comment.