[JIRA] (JENKINS-58958) Use the same Jenkins workspace on a Change basis

[imann04@gmail.com (JIRA)]

isaac mann moved an issue

Jenkins / JENKINS-58958 Use the same Jenkins workspace on a Change basis Change By: isaac mann Project: Infrastructure Jenkins Key: INFRA JENKINS - 2215 58958 Workflow: classic default workflow JNJira + In-Review Component/s: gerrit-code-review-plugin Component/s: github Add Comment

This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

[imann04@gmail.com (JIRA)]

isaac mann assigned an issue to lucamilanesio

Jenkins / JENKINS-58958 Use the same Jenkins workspace on a Change basis

Change By: isaac mann Assignee: Daniel Beck lucamilanesio

Add Comment

[luca.milanesio@gmail.com (JIRA)]

Luca Domenico Milanesio commented on JENKINS-58958

Re: Use the same Jenkins workspace on a Change basis The behaviour you see is a consequence of how Gerrit stores patch-sets, which is different from the way GitHub (for example) stores PRs. Gerrit has a different ref for every patch-set, which results in a different build and workspace. GitHub, instead, uses the same ref (e.g. refs/pull/N/head) and thus has the same workspace.

Add Comment

This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)

[andreas@unjo.com (JIRA)]

Andreas Fritiofson commented on JENKINS-58958

Re: Use the same Jenkins workspace on a Change basis

How Gerrit internally stores and references Patchsets should be orthogonal to how we want to handle them in Jenkins/BlueOcean.

Add Comment

[luca.milanesio@gmail.com (JIRA)]

Luca Domenico Milanesio commented on JENKINS-58958

Re: Use the same Jenkins workspace on a Change basis

Generally speaking, yes. However, this plugin uses the multi-branch pipeline which has a 1:1 representation between a child job and a branch. Because the branch is different, then the job is different. Does that makes sense? For reusing cached results of past builds, have you looked at Bazel?

Add Comment