-
Notifications
You must be signed in to change notification settings - Fork 119
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
Conversation
There was a problem hiding this 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> |
There was a problem hiding this comment.
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 --> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
2.61
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
2.60 I meant.
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) { |
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
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?
There was a problem hiding this comment.
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
There was a problem hiding this comment.
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> |
There was a problem hiding this comment.
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
There was a problem hiding this 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+.
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