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

Artifact copier fails to copy any artifacts if a target directory is missing

    XMLWordPrintable

Details

    • Bug
    • Resolution: Fixed
    • High
    • 2.2
    • None
    • Artifacts
    • None
    • BEAC: 2.2-SNAPSHOT build 1104

    Description

      When the builder has completed and it is time for the artifact copier to run through each entry; if a directory is missing for an entry, artifacts that are found are not sent to the Bamboo server.

      For example, observe the following build configuration for artifacts:

      Running a build based of this configuration where the directory /tmp/jira does not exist causes the following to appear in the build logs:

      20-Jan-2009 17:58:57	Running post build plugin 'Artifact Copier'
      20-Jan-2009 17:58:57	Copying artifact JIRA Logs
      20-Jan-2009 17:58:57	Failed to execute plugin 'Artifact Copier' with error: /opt/lmwork/bamboo-agent/xml-data/build-dir/LABJIRA-CE52IX86DK15WL92MY50/../../../../../../tmp/jira not found.
      20-Jan-2009 17:58:57	Finalising the build...
      

      Then, when viewing the build artifacts, there are none:

      This is odd, as there are files that would have been picked up by the artifact copier:

      Orphaned Logs
      [root@CentOS5i386 labmanager]# find . -type f -name '*.log'
      ./spm/atlassian-jira.log
      ./spm/atlassian-jira-http-dump.log
      ./spm/atlassian-jira-http-access.log
      ./spm/atlassian-jira-soap-dump.log
      ./spm/atlassian-jira-soap-access.log
      
      WebSphere Logs
      [root@CentOS5i386 labmanager]# find /opt/bea/user_projects/domains/atlassian -type f -name '*.log*'
      /opt/bea/user_projects/domains/atlassian/servers/AdminServer/data/ldap/log/EmbeddedLDAPAccess.log
      /opt/bea/user_projects/domains/atlassian/servers/AdminServer/data/ldap/log/EmbeddedLDAP.log
      /opt/bea/user_projects/domains/atlassian/servers/AdminServer/logs/atlassian.log00001
      /opt/bea/user_projects/domains/atlassian/servers/AdminServer/logs/AdminServer.log00066
      /opt/bea/user_projects/domains/atlassian/servers/AdminServer/logs/atlassian.log
      /opt/bea/user_projects/domains/atlassian/servers/AdminServer/logs/AdminServer.log00070
      /opt/bea/user_projects/domains/atlassian/servers/AdminServer/logs/access.log
      /opt/bea/user_projects/domains/atlassian/servers/AdminServer/logs/AdminServer.log00071
      /opt/bea/user_projects/domains/atlassian/servers/AdminServer/logs/AdminServer.log00067
      /opt/bea/user_projects/domains/atlassian/servers/AdminServer/logs/access.log00001
      /opt/bea/user_projects/domains/atlassian/servers/AdminServer/logs/AdminServer.log00068
      /opt/bea/user_projects/domains/atlassian/servers/AdminServer/logs/AdminServer.log
      /opt/bea/user_projects/domains/atlassian/servers/AdminServer/logs/AdminServer.log00069
      /opt/bea/user_projects/domains/atlassian/servers/AdminServer/logs/AdminServer.log00072
      

      What I imagine happens, is that the artifact copier throws an exception, bailing out of the plugin; then no data is transferred back to the Bamboo server.

      Attachments

        Activity

          People

            mark@atlassian.com MarkC
            pdzwart PdZ (Inactive)
            Votes:
            1 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: