Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Not A Defect
-
None
-
Windows Server 2008 R2
Jenkins 2.60.1 LTS
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
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?
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? 
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.
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. 
I cannot get why you think that is an issue of copyartifact.
Please clarify what the issue of copyartifact is.