-
Notifications
You must be signed in to change notification settings - Fork 31
[MINVOKER-296] Warn-log the case of incomplete name-description #97
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
[MINVOKER-296] Warn-log the case of incomplete name-description #97
Conversation
d6c7cd2 to
2e1ebef
Compare
|
please create jira issue for it |
|
It's seems I'm not following my own description/intention from the JIRA. Have to check it. |
|
a9ce77e to
d0bfae0
Compare
|
At the end please squash commits and add issue to commit subject |
d0bfae0 to
b6092a5
Compare
Incomplete = only one of name-description is provided
b6092a5 to
90fec67
Compare
|
@slawekjaranowski - squashed. |
|
Just out of curiosity of the failures on cloudbees - as I don't know where the jenkins pipeline source is stored and if it's publicly available at all. (If it is I'd be happy to learn its location.) The master - green one: while the failing build for this PR: So it seems that checkout of the project was not successful, however the build (next step I presume) was started regardless? |
|
@olamy what happens here ... why some of check are green and some are red |
Oh I see, it's from here: maven-invoker-plugin/Jenkinsfile Line 20 in 0ab1c94
+ above. Thanks! |
|
Resolve #543 |
No description provided.