Uploaded image for project: 'Bamboo Data Center'
  1. Bamboo Data Center
  2. BAM-13532

Bamboo artifacts do not respect symlinks

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Answered
    • Icon: Low Low
    • None
    • 5.0
    • Artifacts
    • None

      We use 2 stages in our plan. Each creates it's own artifact. The first one runs it's tasks and creates an artifact once it has finished successfully. This artifact is then used by the second plan (as Artifact dependency).

      The first Stage's plan definition uses the copy pattern "htdocs/" (which is the same as "htdocs/**" in ant, which means "htdocs recursively"). This does not copy those "dead" symlinks. They are just missing when we have a look into that build-dir of the second stage.
      Symlinks which resolve OK in build environment are also not exported as symlinks, but instead as files, containing the symlink's destination file's content, which also is not OK, since it alters what is exported as artifact, also.

      Symlinks should be respected when building the artifacts as any normal files are. And not (silently) skipped.

            [BAM-13532] Bamboo artifacts do not respect symlinks

            Axel Pardemann added a comment -

            Artifacts sharing is really buggy as it is. Relying on "use an archive format" to pass the artifacts is a really hacky way of doing this (which does solve every issue I state below however).

            In addition to symlinks being effectively destroyed by Bamboo artifacts sharing, there is also empty folders and for god sake's: permissions...

            I get that the there may be other pressing matters to develop/fix, but this unfinished behavior makes me look at other solutions (sad because I wanted the whole ecosystem Bitbucket-Jira-Confluence-Bamboo wired toghether).

            Axel Pardemann added a comment - Artifacts sharing is really buggy as it is. Relying on "use an archive format" to pass the artifacts is a really hacky way of doing this (which does solve every issue I state below however). In addition to symlinks being effectively destroyed by Bamboo artifacts sharing, there is also empty folders and for god sake's: permissions... I get that the there may be other pressing matters to develop/fix, but this unfinished behavior makes me look at other solutions (sad because I wanted the whole ecosystem Bitbucket-Jira-Confluence-Bamboo wired toghether).

            Michael Nicholson added a comment -

            I just ran into this. One does not expect these kind of silly limitations these days. Handling symlinks is something that has been around for decades.

            Michael Nicholson added a comment - I just ran into this. One does not expect these kind of silly limitations these days. Handling symlinks is something that has been around for decades.

            James Dumay added a comment -

            Hi there,

            Thanks for reporting. Unfortunately this is a known limitation with artifact sharing that I do not believe we will change in the near future.

            As a work around, it use an archive format that supports symlink preservation (such as tar) to capture all the files and artifact pass the archive itself to other jobs.

            Thanks
            James Dumay
            Product Manager

            James Dumay added a comment - Hi there, Thanks for reporting. Unfortunately this is a known limitation with artifact sharing that I do not believe we will change in the near future. As a work around, it use an archive format that supports symlink preservation (such as tar) to capture all the files and artifact pass the archive itself to other jobs. Thanks James Dumay Product Manager

              Unassigned Unassigned
              38d677b83562 SysOps AIJKO
              Affected customers:
              0 This affects my team
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: