Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[JENKINS-26100] Change buildEnvVars to take Run #102

Merged
merged 5 commits into from
May 19, 2017

Conversation

abayer
Copy link
Member

@abayer abayer commented May 1, 2017

JENKINS-26100

FYI, I had some weird test failures locally when I ran mvn clean install but couldn't reproduce when running, say, mvn clean install -Dtest=PipelineTest so I'm not sure if they're environmental or what, so...hey, why not, here's a PR.

cc @reviewbybees

@abayer abayer requested a review from jglick May 1, 2017 20:36
Copy link
Member

@jglick jglick left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

OK except for requested buildEnvVars rename.

pom.xml Outdated
<no-test-jar>false</no-test-jar>
<scm-api-plugin.version>2.0.8</scm-api-plugin.version>
<scm-api-plugin.version>2.1.0</scm-api-plugin.version>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

java.level → 8

pom.xml Outdated
@@ -14,9 +14,10 @@
<url>http://wiki.jenkins-ci.org/display/JENKINS/Mercurial+Plugin</url>

<properties>
<jenkins.version>1.642.3</jenkins.version>
<jenkins-core.version>2.58-20170502.192524-8</jenkins-core.version> <!-- TODO: Switch to release once https://github.com/jenkinsci/jenkins/pull/2730 is merged and released -->
<jenkins-war.version>2.58-20170502.192544-8</jenkins-war.version> <!-- TODO: Switch to release once https://github.com/jenkinsci/jenkins/pull/2730 is merged and released -->
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

2.61

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

2.60 I meant.

@ghost
Copy link

ghost commented May 18, 2017

This pull request originates from a CloudBees employee. At CloudBees, we require that all pull requests be reviewed by other CloudBees employees before we seek to have the change accepted. If you want to learn more about our process please see this explanation.

buildEnvironment(build, env);
}

public void buildEnvironment(Run<?,?> build, Map<String, String> env) {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same as for SVN plugin. It is better to reference the incoming method in the Core API.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Isn't that literally what I just did here?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not sure WDYM. I was talking about Javadoc and TODO comment

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah, yeah, doing so.

@@ -16,7 +16,7 @@
<properties>
<jenkins.version>1.642.3</jenkins.version>
<no-test-jar>false</no-test-jar>
<scm-api-plugin.version>2.0.8</scm-api-plugin.version>
<scm-api-plugin.version>2.1.0</scm-api-plugin.version>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I doubt it is required, but it won't hurt

Copy link
Member

@jglick jglick left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just please leave behind a comment reminding the maintainer (me) to delete the old overload and mark the new overload an @Override when updating to 2.60+.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants