Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-48216

"Keep the build logs of dependencies" doesn't work in all cases

    Details

    • Type: Bug
    • Status: Resolved (View Workflow)
    • Priority: Major
    • Resolution: Not A Defect
    • Component/s: copyartifact-plugin
    • Labels:
      None
    • Environment:
      Windows Server 2008 R2
      Jenkins 2.60.1 LTS
    • Similar Issues:

      Description

      I've configured a Build-Job which copies artifacts from multiple other jobs and assembles a bundle.

      The build-step "Copy artifacts from another project" is used - Fingerprint Artifacts is enabled at every of those steps.
      At Job Notifications => Advanced Keep the build logs of dependencies is also enabled.

      I'd like to trigger this downstream-Build manually.... but if I disable ALL Build Triggers and trigger manually a Build via Build now, no Builds in Upstream-Builds are locked. So the build logs of the dependencies will be discarded according to Log-Rotation-Setting. (Keep the build logs of dependencies does not work here properly in my opinion)

      If I enable Build after other projects are built and enter the Upstream Jobs there, then some "padlock"-Icons appear in the Upstream-Builds.... regardless if the downstream-job was triggered manually or via an upstream-build.

        Attachments

          Activity

          Hide
          ikedam ikedam added a comment -

          I cannot get why you think that is an issue of copyartifact.
          Please clarify what the issue of copyartifact is.

          Show
          ikedam ikedam added a comment - I cannot get why you think that is an issue of copyartifact. Please clarify what the issue of copyartifact is.
          Hide
          coyote_de Dieter G. added a comment -

          Will "Copy Artifact" cause a true upstream/downstream-relationship between builds?

          Does it also if I manually trigger a build which copies artifacts from other builds?

          Show
          coyote_de Dieter G. added a comment - Will "Copy Artifact" cause a true upstream/downstream-relationship between builds? Does it also if I manually trigger a build which copies artifacts from other builds?
          Hide
          ikedam ikedam added a comment -

          "Keep logs ..." checks only dependencies of downstream projects.
          That means you need to define triggers for the downstream projects.
          https://github.com/jenkinsci/jenkins/blob/jenkins-2.73/core/src/main/java/hudson/model/AbstractBuild.java#L1042

          > Will "Copy Artifact" cause a true upstream/downstream-relationship between builds?
          >
          > Does it also if I manually trigger a build which copies artifacts from other builds?

          Yes.
          Rlationships between builds are always recorded as fingerprints.
          Unfortunately "Keep logs..." checks only when there're project-level relationships.

          Show
          ikedam ikedam added a comment - "Keep logs ..." checks only dependencies of downstream projects. That means you need to define triggers for the downstream projects. https://github.com/jenkinsci/jenkins/blob/jenkins-2.73/core/src/main/java/hudson/model/AbstractBuild.java#L1042 > Will "Copy Artifact" cause a true upstream/downstream-relationship between builds? > > Does it also if I manually trigger a build which copies artifacts from other builds? Yes. Rlationships between builds are always recorded as fingerprints. Unfortunately "Keep logs..." checks only when there're project-level relationships.

            People

            • Assignee:
              coyote_de Dieter G.
              Reporter:
              coyote_de Dieter G.
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: