Skip to content
Permalink
Browse files

JENKINS-10831 maven submodule build fails doing mkdir on master.

Remove the shadow copy of buildOn from MavenBuild.java and move the setter to
AbstractBuild to allow MavenModuleSetBuild.java to continue to set the
build node.

Originally-Committed-As: 67262e455f818bf693d1bd7a5987c9268b29c52e
  • Loading branch information
oldelvet authored and kohsuke committed Aug 28, 2011
1 parent 0aea1c0 commit 61cac17925d494606476920c9fa31cd26d1a835e
Showing with 0 additions and 27 deletions.
  1. +0 −27 src/main/java/hudson/maven/MavenBuild.java
@@ -95,13 +95,6 @@
* @since 1.98.
*/
private List<ExecutedMojo> executedMojos;

/**
* Name of the slave this project was built on.
* Null or "" if built by the master. (null happens when we read old record that didn't have this information.)
* @since 1.394
*/
private String builtOn;

public MavenBuild(MavenModule job) throws IOException {
super(job);
@@ -293,26 +286,6 @@ public MavenModule getParent() {// don't know why, but javac wants this
return super.getParent();
}

/**
* @see hudson.model.AbstractBuild#getBuiltOn()
* @since 1.394
*/
public Node getBuiltOn() {
if(builtOn==null || builtOn.equals(""))
return Jenkins.getInstance();
else
return Jenkins.getInstance().getNode(builtOn);
}

/**
* @param builtOn
* @since 1.394
*/
public void setBuiltOnStr( String builtOn )
{
this.builtOn = builtOn;
}

/**
* Runs Maven and builds the project.
*/

0 comments on commit 61cac17

Please sign in to comment.
You can’t perform that action at this time.