Closed prateekiiest closed 6 years ago
Sorry for the late update. Had to search for proper docs to use jenkins-rest
.
is the way we can work around this.
@prateekiiest would it be OK with you and seem fair if I only looked at this again when the red above is gone and it passes the build?
sure no problem with that
@vorburger Travis fails due to trailing whitespace. I have been trying to fix that since yesterday :P But can't find if there's any whitespace.
While I fix that , let me know how you would want to pass the job name and the password.
Travis fails due to trailing whitespace. I have been trying to fix that since yesterday :P But can't find if there's any whitespace.
it clearly says where here:
[INFO] There are 3 errors reported by Checkstyle 8.4 with odl_checks.xml ruleset.
[ERROR] src/main/java/org/opendaylight/bot/jenkins/Client.java:[20] (regexp) RegexpSingleline: Line has trailing spaces.
[ERROR] src/main/java/org/opendaylight/bot/jenkins/Client.java:[23] (regexp) RegexpSingleline: Line has trailing spaces.
[ERROR] src/main/java/org/opendaylight/bot/jenkins/Client.java:[31] (regexp) RegexpSingleline: Line has trailing spaces.
in each of these lines, you simply have empty lines which are not just LF but space-space-space-LF.
While I fix that , let me know how you would want to pass the job name and the password.
how you would want to pass the job name and the password.
as per this earlier comment, add the job name and the password to bot/src/main/java/org/opendaylight/bot/BotConfiguration.java and pass it through to here
@prateekiiest I just wanted to make sure that you had understood that you do not have to push all of these individual mini micro commits re. Checkstyle and wait for Travis builds - what everyone really does it just try it out locally, first simply by running ./mvnw clean package
. That's much easier and gives a faster turn around. Just thought that you may not be aware of this.
Oh!, my bad. I didn't know about it that we can do it locally too :smile: Thanks again.
@prateekiiest I'm guessing you'll close/abandon this, based on #21 ?
I guess I can work on this by updating the branch with the new code. Or should I open a fresh PR?
I am closing this. I am opening a new PR for this
issue #8