[JIRA] (JENKINS-51485) Warnings Plugin MSBuildParser does not handle hyphen or underscore in category
Title: Message Title John Case commented on JENKINS-51485 Re: Warnings Plugin MSBuildParser does not handle hyphen or underscore in category Ulli Hafner Thank you for merging the PR! What is the typical release process? When will I be able to update the warnings-plugin with this fix on my Jenkins server? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51485) Warnings Plugin MSBuildParser does not handle hyphen or underscore in category
Title: Message Title John Case commented on JENKINS-51485 Re: Warnings Plugin MSBuildParser does not handle hyphen or underscore in category Ulli Hafner This was auto assigned to you. If you aren't the right person to do this can you please pass it off to somebody else? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51485) Warnings Plugin MSBuildParser does not handle hyphen or underscore in category
Title: Message Title John Case commented on JENKINS-51485 Re: Warnings Plugin MSBuildParser does not handle hyphen or underscore in category Getting the tooling to create a pull request wasn't that difficult after all... PR Created: https://github.com/jenkinsci/warnings-plugin/pull/128 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51485) Warnings Plugin MSBuildParser does not handle hyphen or underscore in category
Title: Message Title
John Case updated an issue
Jenkins / JENKINS-51485
Warnings Plugin MSBuildParser does not handle hyphen or underscore in category
Change By:
John Case
The following output (from [sass - lint| [ https://github.com/sasstools/sass-lint]) ] is not properly handled by the MSBuild parser: {code:java}dist/search-list.component.scss(41,17): warning shorthand-values : Property `margin` should be written more concisely as `5px 0 0` instead of `5px 0 0 0`{code} After fiddling around with it, I was able to figure out that it is failing on the category value "shorthand-values"Currently, the regex only expects letters and numbers in that string, it does not match on hyphens.I think the regex should be expanded to handle hyphens (and underscores would be good too.)The change should be simple enough. Just modify the regex: {code:java}private static final String MS_BUILD_WARNING_PATTERN = "(?:^(?:.*)Command line warning ([A-Za-z0-9]+):\\s*(.*)\\s*\\[(.*)\\])|"+ ANT_TASK + "(?:(?:\\s*\\d+>)?(?:(?:(?:(.*)\\((\\d*)(?:,(\\d+))?.*\\)|.*LINK)\\s*:|(.*):)\\s*([A-z-_]*\\s?(?:[Nn]ote|[Ii]nfo|[Ww]arning|(?:fatal\\s*)?[Ee]rror))\\s*:?\\s*([A-Za-z0-9]+)\\s*:\\s(?:\\s*([A-Za-z0-9.]+)\\s*:)?\\s*(.*?)(?: \\[([^\\]]*)[/][^\\]]+\\])?"+ "|(.*)\\s*:.*error\\s*(LNK[0-9]+):\\s*(.*)))$";{code}with the following: {code:java}private static final String MS_BUILD_WARNING_PATTERN = "(?:^(?:.*)Command line warning ([A-Za-z0-9]+):\\s*(.*)\\s*\\[(.*)\\])|"+ ANT_TASK + "(?:(?:\\s*\\d+>)?(?:(?:(?:(.*)\\((\\d*)(?:,(\\d+))?.*\\)|.*LINK)\\s*:|(.*):)\\s*([A-z-_]*\\s?(?:[Nn]ote|[Ii]nfo|[Ww]arning|(?:fatal\\s*)?[Ee]rror))\\s*:?\\s*([A-Za-z0-9\\-_]+)\\s*:\\s(?:\\s*([A-Za-z0-9.]+)\\s*:)?\\s*(.*?)(?: \\[([^\\]]*)[/][^\\]]+\\])?"+ "|(.*)\\s*:.*error\\s*(LNK[0-9]+):\\s*(.*)))$";{code}I'd be happy to make a pull request in the [github repo|https://github.com/jenkinsci/warnings-plugin] but it would take me a bit to get the tooling on my workstation to write a test.
Add Comment
[JIRA] (JENKINS-51485) Warnings Plugin MSBuildParser does not handle hyphen or underscore in category
Title: Message Title
John Case updated an issue
Jenkins / JENKINS-51485
Warnings Plugin MSBuildParser does not handle hyphen or underscore in category
Change By:
John Case
The following output (from [sass lint|https://github.com/sasstools/sass-lint]) is not properly handled by the MSBuild parser: {code:java}dist/search-list.component.scss(41,17): warning shorthand-values : Property `margin` should be written more concisely as `5px 0 0` instead of `5px 0 0 0`{code} After fiddling around with it, I was able to figure out that it is failing on the category value "shorthand-values"Currently, the regex only expects letters and numbers in that string, it does not match on hyphens.I think the regex should be expanded to handle hyphens (and underscores would be good too.)The change should be simple enough. Just modify the regex: {code:java}private static final String MS_BUILD_WARNING_PATTERN = "(?:^(?:.*)Command line warning ([A-Za-z0-9]+):\\s*(.*)\\s*\\[(.*)\\])|"+ ANT_TASK + "(?:(?:\\s*\\d+>)?(?:(?:(?:(.*)\\((\\d*)(?:,(\\d+))?.*\\)|.*LINK)\\s*:|(.*):)\\s*([A-z-_]*\\s?(?:[Nn]ote|[Ii]nfo|[Ww]arning|(?:fatal\\s*)?[Ee]rror))\\s*:?\\s*([A-Za-z0-9]+)\\s*:\\s(?:\\s*([A-Za-z0-9.]+)\\s*:)?\\s*(.*?)(?: \\[([^\\]]*)[/][^\\]]+\\])?"+ "|(.*)\\s*:.*error\\s*(LNK[0-9]+):\\s*(.*)))$";{code}with the following: {code:java}private static final String MS_BUILD_WARNING_PATTERN = "(?:^(?:.*)Command line warning ([A-Za-z0-9]+):\\s*(.*)\\s*\\[(.*)\\])|"+ ANT_TASK + "(?:(?:\\s*\\d+>)?(?:(?:(?:(.*)\\((\\d*)(?:,(\\d+))?.*\\)|.*LINK)\\s*:|(.*):)\\s*([A-z-_]*\\s?(?:[Nn]ote|[Ii]nfo|[Ww]arning|(?:fatal\\s*)?[Ee]rror))\\s*:?\\s*([A-Za-z0-9\\-_]+)\\s*:\\s(?:\\s*([A-Za-z0-9.]+)\\s*:)?\\s*(.*?)(?: \\[([^\\]]*)[/][^\\]]+\\])?"+ "|(.*)\\s*:.*error\\s*(LNK[0-9]+):\\s*(.*)))$";{code}I'd be happy to make a pull request in the [github repo|https://github.com/jenkinsci/warnings-plugin] but it would take me a bit to get the tooling on my workstation to write a test.
Add Comment
[JIRA] (JENKINS-51485) Warnings Plugin MSBuildParser does not handle hyphen or underscore in category
Title: Message Title John Case created an issue Jenkins / JENKINS-51485 Warnings Plugin MSBuildParser does not handle hyphen or underscore in category Issue Type: Bug Assignee: Ulli Hafner Components: warnings-plugin Created: 2018-05-22 15:34 Priority: Minor Reporter: John Case The following output (from [sass-lint|https://github.com/sasstools/sass-lint)] is not properly handled by the MSBuild parser: dist/search-list.component.scss(41,17): warning shorthand-values : Property `margin` should be written more concisely as `5px 0 0` instead of `5px 0 0 0` After fiddling around with it, I was able to figure out that it is failing on the category value "shorthand-values" Currently, the regex only expects letters and numbers in that string, it does not match on hyphens. I think the regex should be expanded to handle hyphens (and underscores would be good too.) The change should be simple enough. Just modify the regex: private static final String MS_BUILD_WARNING_PATTERN = "(?:^(?:.*)Command line warning ([A-Za-z0-9]+):\\s*(.*)\\s*\\[(.*)\\])|" + ANT_TASK + "(?:(?:\\s*\\d+>)?(?:(?:(?:(.*)\\((\\d*)(?:,(\\d+))?.*\\)|.*LINK)\\s*:|(.*):)\\s*([A-z-_]*\\s?(?:[Nn]ote|[Ii]nfo|[Ww]arning|(?:fatal\\s*)?[Ee]rror))\\s*:?\\s*([A-Za-z0-9]+)\\s*:\\s(?:\\s*([A-Za-z0-9.]+)\\s*:)?\\s*(.*?)(?: \\[([^\\]]*)[/][^\\]]+\\])?" + "|(.*)\\s*:.*error\\s*(LNK[0-9]+):\\s*(.*)))$";
[JIRA] (JENKINS-50920) NPM registry credentials not correctly formatted
Title: Message Title John Case edited a comment on JENKINS-50920 Re: NPM registry credentials not correctly formatted e We are not using Artifactory. We are using [Verdaccio|http://www.verdaccio.org/] Publishing to it works manually with the authToken property as described in the issue. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50920) NPM registry credentials not correctly formatted
Title: Message Title John Case commented on JENKINS-50920 Re: NPM registry credentials not correctly formatted e are not using Artifactory. We are using Verdaccio Publishing to it works manually with the authToken property as described in the issue. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50920) NPM registry credentials not correctly formatted
Title: Message Title
John Case updated an issue
Jenkins / JENKINS-50920
NPM registry credentials not correctly formatted
Change By:
John Case
I am trying to use Jenkins to publish npm packages to a private npm repository. I use the config-file-provider plugin to create a new npm config file.Creating the config looks like this:!npmConfig.PNG!The credentials used in that config is a "username with password" credentials configured with the correct username/password for publishing to my repository. The publish part of my Jenkinsfile looks like:{code:java}nodejs(nodeJSInstallationName: "6.12.0", configId: "npm-publish-config") {lerna publish --conventional-commits --yes}{code} When I run the build I get the following error when it tries to publish: {noformat}need auth You need to authorize this machine using `npm adduser`{noformat} I did a little debugging. I was able to fine find the file it claims to have used as it's npm config:{code:java}@myScope:registry = http://my.private.registry/ //my.private.registry/:always-auth = true //my.private.registry/:username = jenkins //my.private.registry/:_password = <>{code}I have found no information online about the :username and :_password properties being supported by NPM. Everything I have found has said that the .npmrc config file should have an _authToken property like this:{code:java}@myScope:registry = http://my.private.registry/ //my.private.registry/:always-auth = true //my.private.registry/:_authToken="SECRET"{code}What am I doing wrong?
Add Comment
This
[JIRA] (JENKINS-50920) NPM registry credentials not correctly formatted
Title: Message Title
John Case created an issue
Jenkins / JENKINS-50920
NPM registry credentials not correctly formatted
Issue Type:
Bug
Assignee:
Dominik Bartholdi
Attachments:
npmConfig.PNG
Components:
config-file-provider-plugin, nodejs-plugin
Created:
2018-04-20 21:53
Priority:
Major
Reporter:
John Case
I am trying to use Jenkins to publish npm packages to a private npm repository. I use the config-file-provider plugin to create a new npm config file. Creating the config looks like this: The credentials used in that config is a "username with password" credentials configured with the correct username/password for publishing to my repository. The publish part of my Jenkinsfile looks like:
nodejs(nodeJSInstallationName: "6.12.0", configId: "npm-publish-config") {
lerna publish --conventional-commits --yes
}
When I run the build I get the following error when it tries to publish:
need auth You need to authorize this machine using `npm adduser`
I did a little debugging. I was able to fine the file it claims to have used as it's npm config:
