[JIRA] [subversion-plugin] (JENKINS-29340) E200015: ISVNAuthentication provider did not provide credentials
Title: Message Title Manuel Jesús Recena Soto commented on JENKINS-29340 Re: E200015: ISVNAuthentication provider did not provide credentials Ricardo García Fernández, I've reproduced the bug. Thanks so much. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [subversion-plugin] (JENKINS-29340) E200015: ISVNAuthentication provider did not provide credentials
Title: Message Title Ricardo García Fernández commented on JENKINS-29340 Re: E200015: ISVNAuthentication provider did not provide credentials Screencast I've recorded another screencast with the error: https://drive.google.com/file/d/0B-JHYZKBisF1bF9KTHVMdG8yRXc/view?usp=sharing Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [subversion-plugin] (JENKINS-22922) Subversion : environment variables work only partially (got broken in 2.3 or prior, after 1.44)
Title: Message Title Manuel Jesús Recena Soto commented on JENKINS-22922 Re: Subversion : environment variables work only partially (got broken in 2.3 or prior, after 1.44) Ralf Mühle, you should use the variables in the way: https://hostname/svn/$REPO/trunk Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [subversion-plugin] (JENKINS-22922) Subversion : environment variables work only partially (got broken in 2.3 or prior, after 1.44)
Title: Message Title Manuel Jesús Recena Soto edited a comment on JENKINS-22922 Re: Subversion : environment variables work only partially (got broken in 2.3 or prior, after 1.44) [~ralf_muehle], it seems we have a very similar (maybe the same) bug here: https://issues.jenkins-ci.org/browse/JENKINS-29340Please, review these two comments: [first ]( | https://issues.jenkins-ci.org/browse/JENKINS-29340?focusedCommentId=232041&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-232041 ) ] and [second ]( | https://issues.jenkins-ci.org/secure/EditComment!default.jspa?id=163807&commentId=232045 ) ] . The last includes a screencast. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [subversion-plugin] (JENKINS-22922) Subversion : environment variables work only partially (got broken in 2.3 or prior, after 1.44)
Title: Message Title Manuel Jesús Recena Soto started work on JENKINS-22922 Change By: Manuel Jesús Recena Soto Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [subversion-plugin] (JENKINS-22922) Subversion : environment variables work only partially (got broken in 2.3 or prior, after 1.44)
Title: Message Title Manuel Jesús Recena Soto commented on JENKINS-22922 Re: Subversion : environment variables work only partially (got broken in 2.3 or prior, after 1.44) Ralf Mühle, it seems we have a very similar (maybe the same) bug here: https://issues.jenkins-ci.org/browse/JENKINS-29340 Please, review these two comments: [first](https://issues.jenkins-ci.org/browse/JENKINS-29340?focusedCommentId=232041&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-232041) and [second](https://issues.jenkins-ci.org/secure/EditComment!default.jspa?id=163807&commentId=232045). The last includes a screencast. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [subversion-plugin] (JENKINS-29340) E200015: ISVNAuthentication provider did not provide credentials
Title: Message Title Ricardo García Fernández commented on JENKINS-29340 Re: E200015: ISVNAuthentication provider did not provide credentials Manuel Jesús Recena Soto thanks for the screencast, but the problem appears when the jobs tries to check if there's any update in the scm repository 'via' scmPollLog: http://jenkinsurl/job/JENKINS-29340/scmPollLog/ Here if you use an environment variable into scm url this section fails and you can't check if there are any updates in repository. Thanks! Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-29336) loadStatistics API not accessible
Title: Message Title Stefan Bisplinghoff updated an issue Jenkins / JENKINS-29336 loadStatistics API not accessible Change By: Stefan Bisplinghoff Summary: loadStatistics API not accessible Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-29376) Label expression help is missing in recent Jenkins versions
Title: Message Title Oliver Gondža created an issue Jenkins / JENKINS-29376 Label _expression_ help is missing in recent Jenkins versions Issue Type: Bug Assignee: Unassigned Components: core Created: 13/Jul/15 5:54 AM Priority: Minor Reporter: Oliver Gondža Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message
[JIRA] [job-dsl-plugin] (JENKINS-29375) Add method to configure childCustomWorkspace in MatrixJob
Title: Message Title Aleksandar Odorovic created an issue Jenkins / JENKINS-29375 Add method to configure childCustomWorkspace in MatrixJob Issue Type: New Feature Assignee: Aleksandar Odorovic Components: job-dsl-plugin Created: 13/Jul/15 5:51 AM Priority: Minor Reporter: Aleksandar Odorovic Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because y
[JIRA] [subversion-plugin] (JENKINS-22922) Subversion : environment variables work only partially (got broken in 2.3 or prior, after 1.44)
Title: Message Title
Ralf Mühle edited a comment on JENKINS-22922
Re: Subversion : environment variables work only partially (got broken in 2.3 or prior, after 1.44)
Yes, Bug exists in SVN Plugin 2.5.1 and Jenkins 1.619Location 'http:///$ \ {RELEASE_BRANCH \ }/' does not exist
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
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] [subversion-plugin] (JENKINS-22922) Subversion : environment variables work only partially (got broken in 2.3 or prior, after 1.44)
Title: Message Title
Ralf Mühle commented on JENKINS-22922
Re: Subversion : environment variables work only partially (got broken in 2.3 or prior, after 1.44)
Yes, Bug exists in SVN Plugin 2.5.1 and Jenkins 1.619
Location 'http:///$ {RELEASE_BRANCH}
/' does not exist
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
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] [pretested-integration-plugin] (JENKINS-28640) Quotationmarks in commit message leads to merge failure (Praqma case 13083)
Title: Message Title SCM/JIRA link daemon commented on JENKINS-28640 Re: Quotationmarks in commit message leads to merge failure (Praqma case 13083) Code changed in jenkins User: Bue Petersen Path: pom.xml src/main/java/org/jenkinsci/plugins/pretestedintegration/scm/git/AccumulatedCommitStrategy.java src/main/java/org/jenkinsci/plugins/pretestedintegration/scm/git/GitBridge.java src/test/java/org/jenkinsci/plugins/pretestedintegration/integration/scm/git/CommitMessagesWithDoubleQuotes.java src/test/java/org/jenkinsci/plugins/pretestedintegration/integration/scm/git/CommitMessagesWithSpecialChars.java src/test/java/org/jenkinsci/plugins/pretestedintegration/integration/scm/git/CustomIntegrationBranch.java src/test/java/org/jenkinsci/plugins/pretestedintegration/integration/scm/git/StaticGitRepositoryTestBase.java src/test/java/org/jenkinsci/plugins/pretestedintegration/integration/scm/git/TestUtilsFactory.java src/test/resources/JENKINS-28640.md src/test/resources/JENKINS-28640.zip src/test/resources/commitMessagesWithDoubleQuotesSingleQuotesMade.md src/test/resources/commitMessagesWithDoubleQuotesSingleQuotesMade_linux-repo_description.log src/test/resources/commitMessagesWithDoubleQuotesSingleQuotesMade_linux.sh src/test/resources/commitMessagesWithDoubleQuotesSingleQuotesMade_linux.zip src/test/resources/commitMessagesWithDoubleQuotesSingleQuotesMade_windows-repo_description.log src/test/resources/commitMessagesWithDoubleQuotesSingleQuotesMade_windows.bat src/test/resources/commitMessagesWithDoubleQuotesSingleQuotesMade_windows.zip http://jenkins-ci.org/commit/pretested-integration-plugin/a48f690943cb79034717e495706c6428c7e710e4 Log: JENKINS-28640: Quotation marks in commit msg: Only related to the accumulated strategy. Temporary fix for the bug with quotation marks in the commit message leading to merge failure because of not properly escaped and formatted command line arguments. Fix is temporary replacing " (quotation marks) with ' (plings). The squashed strategy is not affected, as the git command automatically generated the commit message, where as the plugin creates a look-a-like squash message, slightly modified, is using accumulated strategy. Other improvements: fixed hard-coded dependency on the maven-hpi-plugin in the pom file, new version works now cleaned few tests from wrong comments, and not clearly formatted error messages if the tests failed renamed test suite for commit message prolems related to quotation marks to special chars test suite shared a useful method from one test suite through test utils class that can pretty print console output from the job to use for verification in the tests.
[JIRA] [pretested-integration-plugin] (JENKINS-28640) Quotationmarks in commit message leads to merge failure (Praqma case 13083)
Title: Message Title SCM/JIRA link daemon commented on JENKINS-28640 Re: Quotationmarks in commit message leads to merge failure (Praqma case 13083) Code changed in jenkins User: Bue Petersen Path: src/test/java/org/jenkinsci/plugins/pretestedintegration/integration/scm/git/CommitMessagesWithSpecialChars.java src/test/java/org/jenkinsci/plugins/pretestedintegration/integration/scm/git/CommitMessagesWithSpecialCharsIT.java src/test/java/org/jenkinsci/plugins/pretestedintegration/integration/scm/git/CustomIntegrationBranch.java src/test/java/org/jenkinsci/plugins/pretestedintegration/integration/scm/git/CustomIntegrationBranchIT.java src/test/java/org/jenkinsci/plugins/pretestedintegration/integration/scm/git/DoNotAllowMasterBranchAsReadyBranch.java src/test/java/org/jenkinsci/plugins/pretestedintegration/integration/scm/git/DoNotAllowMasterBranchAsReadyBranchIT.java src/test/java/org/jenkinsci/plugins/pretestedintegration/integration/scm/git/UseAuthorOfLastCommit.java src/test/java/org/jenkinsci/plugins/pretestedintegration/integration/scm/git/UseAuthorOfLastCommitIT.java http://jenkins-ci.org/commit/pretested-integration-plugin/349570612582f04199683850676cad203b4d8fb9 Log: JENKINS-28640: Quotation marks - enabled tests: Not all tests have automatically been executed before. Fixing the filenames to include all tests. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [pretested-integration-plugin] (JENKINS-29369) Accumulated commit message is locale and launguage dependent (Praqma case 13296)
Title: Message Title SCM/JIRA link daemon commented on JENKINS-29369 Re: Accumulated commit message is locale and launguage dependent (Praqma case 13296) Code changed in jenkins User: Bue Petersen Path: README.md src/main/java/org/jenkinsci/plugins/pretestedintegration/scm/git/AccumulatedCommitStrategy.java src/main/java/org/jenkinsci/plugins/pretestedintegration/scm/git/GetAllCommitsFromBranchCallback.java src/main/java/org/jenkinsci/plugins/pretestedintegration/scm/git/SquashCommitStrategy.java src/test/java/org/jenkinsci/plugins/pretestedintegration/integration/scm/git/BuildResultValidator.java src/test/java/org/jenkinsci/plugins/pretestedintegration/integration/scm/git/CommitMessagesWithSpecialCharsIT.java src/test/java/org/jenkinsci/plugins/pretestedintegration/integration/scm/git/CustomIntegrationBranchIT.java src/test/java/org/jenkinsci/plugins/pretestedintegration/integration/scm/git/StaticGitRepositoryTestBase.java src/test/java/org/jenkinsci/plugins/pretestedintegration/integration/scm/git/TestUtilsFactory.java http://jenkins-ci.org/commit/pretested-integration-plugin/9b4e052022bb618a4d85c7852a5ac76d5391d89e Log: JENKINS-29369 Fix locale dependent accumulated msg The accumulated commit message is now using english locale when formatting date and time. The commit message is generated by the plugin and formatted to look like the squash commit message except for the header line. Tests have been improved to include detailed commit message asserts and extend to include few more tests for squashed also. Each test now verifies that the formatting of dates are correct for the tests regarding special charecters and custom integration branch (those were the newer tests we added so the follow a better design). Other improvements and refactoring: removed un-used code in squash commit strategy removed debug print of squash commit strategy to build console add debug printing of exception during integration to the build console fixed minor bug in test utils regarding printing console which is null test base class for static git repos extended to print out cleaning repos and temp files Compare: https://github.com/jenkinsci/pretested-integration-plugin/compare/cbd24a9b1b9a...9b4e052022bb Add Comment
[JIRA] [git-client-plugin] (JENKINS-20393) Git plugin 2.0 JGit implementation does not publish merge result
Title: Message Title Mark Waite commented on JENKINS-20393 Re: Git plugin 2.0 JGit implementation does not publish merge result An initial idea for the test is evolving as PushTest.java. It is currently missing tests for branches other than master and for branch names which contain embedded slashes. I'm confident there are many other relevant cases which it is missing. Could you review it and provide your feedback on GitHub? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-10696) Problem with libpam4j after 1.420
Title: Message Title Dan Kasak reopened an issue I'm seeing this issue also. I'm new to Jenkins, and have triggered this issue by installing a plugin and bouncing the service. The version of Ubuntu being used is out of my control. I've unpacked the jenkins.war file, and went to manually add libpam4j-1.4.jar ( which a java dev here told me would work ) to the WEB-INF/lib folder, but saw that this war file already includes libpam4j-1.8.jar. I would greatly appreciate it if someone could tell me how to resolve this issue ... Jenkins / JENKINS-10696 Problem with libpam4j after 1.420 Change By: Dan Kasak Resolution: Cannot Reproduce Status: Resolved Reopened Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receivi
[JIRA] [core] (JENKINS-29368) WARNING: invalid gitTool selection Default
Title: Message Title Mark Waite resolved as Not A Defect While the message is surprising, this is a message the plugin has reported for a very long time. Jenkins / JENKINS-29368 WARNING: invalid gitTool selection Default Change By: Mark Waite Status: Open Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [awseb-deployment-plugin] (JENKINS-29374) S3 request format does not conform to Non-US regions
Title: Message Title Michal Krupa created an issue Jenkins / JENKINS-29374 S3 request format does not conform to Non-US regions Issue Type: Bug Assignee: Michal Krupa Components: awseb-deployment-plugin Created: 13/Jul/15 12:46 AM Environment: Jenkins ver. 1.614 Windows Server AWSEB Plugin ver. 0.3 Labels: plugin windows Priority: Minor Reporter: Michal Krupa java.lang.RuntimeException: com.amazonaws.services.s3.model.AmazonS3Exception: Status Code: 301, AWS Service: Amazon S3, AWS Request ID: FFC11C51CF485478, AWS Error Code: PermanentRedirect, AWS Error Message: The bucket you are attempting to access must be addressed using the specified endpoint. Please send all future requests to this endpoint., S3 Extended Request ID: RkHqHGuiRN2SmQQMwem4elgLyM6VGvnuDicN9y81n7oYIV9y8gxTqrmfDkrI+cVSw77QE6TsDc0= at br.com.ingenieux.jenkins.plugins.awsebdeployment.AWSEBDeploymentBuilder.perform(AWSEBDeploymentBuilder.java:211) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.j
[JIRA] [github-oauth-plugin] (JENKINS-29373) Port github-oauth unit tests from Java 6 to Java 7
Title: Message Title Sam Gleske commented on JENKINS-29373 Re: Port github-oauth unit tests from Java 6 to Java 7 Contributions are welcome! I do not actively develop this plugin. I only maintain pull requests and releases. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [github-oauth-plugin] (JENKINS-29373) Port github-oauth unit tests from Java 6 to Java 7
Title: Message Title Sam Gleske created an issue Jenkins / JENKINS-29373 Port github-oauth unit tests from Java 6 to Java 7 Issue Type: Improvement Assignee: Sam Gleske Components: github-oauth-plugin Created: 12/Jul/15 11:59 PM Priority: Minor Reporter: Sam Gleske Support for Java 6 is being completely dropped according to the Jenkins CI blog. Additionally, Maven 3.3+ only supports Java 1.7+. Maven 3.3 requires JDK 1.7 or above to execute - it still allows you to build against 1.3 and other JDK versions by Using Toolchains Therefore, it is imperative that the GitHub OAuth plugin be ported to Java 7 and even Java 8. Otherwise, it will likely not be maintainable as time progresses. Add Comment
[JIRA] [ircbot-plugin] (JENKINS-28175) config change deadlock Jenkins when pircx.shutdown() is invoked
Title: Message Title Leon Blakey commented on JENKINS-28175 Re: config change deadlock Jenkins when pircx.shutdown() is invoked Hi, I'm the PircBotX developer. Can someone please check if this is still an issue on PircBotX 2.1-SNAPSHOT? There have been several changes since then that should fix this. I'd like to verify this works before I do the final release. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [git-client-plugin] (JENKINS-26748) Git plugin sometimes reports Could not checkout null with start point
Title: Message Title Nathan Neulinger commented on JENKINS-26748 Re: Git plugin sometimes reports Could not checkout null with start point We're seeing this problem (likely due to some dev teams frequently force pushing). Trying the binaries you listed in comment above. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-29372) Help text for "Label expression" does not appear
Title: Message Title Dave Bacher created an issue Jenkins / JENKINS-29372 Help text for "Label _expression_" does not appear Issue Type: Bug Assignee: Unassigned Components: core Created: 12/Jul/15 8:50 PM Environment: Jenkins 1.609.1 Priority: Minor Reporter: Dave Bacher Previous versions of Jenkins show a help button for the "Label _expression_" field under "Restrict where this job can run" in the job configuration page. With Jenkins 1.609.1, I no longer see this help button or text on the job configuration page. The text itself does appear to be present under http://jenkins/descriptor/hudson.model.FreeStyleProject/help/assignedLabelString, but it's not linked on the job configuration page.
[JIRA] [authentication-tokens-plugin] (JENKINS-29370) Add ability to filter TokenSources by external conditions
Title: Message Title Oleg Nenashev created an issue Jenkins / JENKINS-29370 Add ability to filter TokenSources by external conditions Issue Type: New Feature Assignee: Oleg Nenashev Components: authentication-tokens-plugin Created: 12/Jul/15 8:21 PM Priority: Minor Reporter: Oleg Nenashev I've got into the situation, when there're several extensions of AuthenticationTokenSource matching the same credentials class. In such case I would like to be able to filter proposed sources by an external matcher. Example: user/password authorization with different connection types (basic, digest, etc.) Add Comment
[JIRA] [authentication-tokens-plugin] (JENKINS-29370) Add ability to filter TokenSources by external conditions
Title: Message Title Oleg Nenashev started work on JENKINS-29370 Change By: Oleg Nenashev Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [pretested-integration-plugin] (JENKINS-29371) Empty commit can't be squashed (Praqma case 13298)
Title: Message Title Bue Petersen updated an issue Jenkins / JENKINS-29371 Empty commit can't be squashed (Praqma case 13298) Change By: Bue Petersen Summary: Empty commit can't be squashed (Praqma case 13298) Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [pretested-integration-plugin] (JENKINS-29371) Empty commit can't be squashed
Title: Message Title Bue Petersen created an issue Jenkins / JENKINS-29371 Empty commit can't be squashed Issue Type: Bug Assignee: Praqma Support Components: pretested-integration-plugin Created: 12/Jul/15 8:29 PM Priority: Trivial Reporter: Bue Petersen Squash commit commands fails if only one commit, that is empty, is tried to be integrated. Squash will do a fast-forward. Not sure if this really is something we should handle, or it is a git problem. Squash shouldn't allow fast-forward according to docs. Example on git commands $ git init emptyCommitTest Initialized empty Git repository in /home/user/gitlab-repos/github/pretested-integration-plugin/src/test/resources/emptyCommitTest/.git/ $ cd emptyCommitTest/ $ date > date.log $ git add date.log $ git commit -m "initial commit" [master (root-commit) 01f7627] initial commit 1 file changed, 1 insertion create mode 100644 date.log $ git checkout -b dev Switched to a new branch 'dev' $ git commit -m "empty commit" --allow-empty [dev be7178f] empty commit $ git checkout master Switched to branch 'master' $ git merge --squash dev Updating 01f7627..be7178f Fast-forward Squash commit – not updating HEAD *The fast-forward is a problem, as the plugin do squash as a two-step process to allow settings author*: Example:
[JIRA] [job-dsl-plugin] (JENKINS-27050) Parameterized seed job is automatically triggered after change
Title: Message Title Vladimir Sitnikov commented on JENKINS-27050 Re: Parameterized seed job is automatically triggered after change Christoph Burgmer, can you please give a hint how you did debug the source of the trigger? I'm running into the same "Template has changed", however I see no obvious reason for those triggers. If only I had a job name that causes those triggers. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [build-token-root-plugin] (JENKINS-29256) Build-Token-Plugin: build option
Title: Message Title David Harris commented on JENKINS-29256 Re: Build-Token-Plugin: build option Hi Daniel, That was the issue! My other instances didn't have security enabled. Thanks for the pointer. Cheers, David Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [build-token-root-plugin] (JENKINS-29256) Build-Token-Plugin: build option
Title: Message Title David Harris closed an issue as Not A Defect Jenkins / JENKINS-29256 Build-Token-Plugin: build option Change By: David Harris Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [pretested-integration-plugin] (JENKINS-29369) Accumulated commit message is locale and launguage dependent (Praqma case 13296)
Title: Message Title
Bue Petersen edited a comment on JENKINS-29369
Re: Accumulated commit message is locale and launguage dependent (Praqma case 13296)
Example on danish formatted date strings:{ {{ code} Accumulated commit of the following from branch 'origin/ready/myDevelopmentBranch':commit c1449e075f528974c63eef81109d0632eaada0c7Author: Praqma Support Date: on jun 3 14:03:46 2015 +0200Added a second line from myDevelopmentBranch in test commit log file.commit 70353ce6771866f29c38b4460b3f74f9024f8ce2Author: Praqma Support Date: on jun 3 14:03:45 2015 +0200Added line from myDevelopmentBranch in test commit log file. {code } }}
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
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] [pretested-integration-plugin] (JENKINS-29369) Accumulated commit message is locale and launguage dependent (Praqma case 13296)
Title: Message Title Bue Petersen commented on JENKINS-29369 Re: Accumulated commit message is locale and launguage dependent (Praqma case 13296) Example on danish formatted date strings: Accumulated commit of the following from branch 'origin/ready/myDevelopmentBranch': commit c1449e075f528974c63eef81109d0632eaada0c7 Author: Praqma Support Date: on jun 3 14:03:46 2015 +0200 Added a second line from myDevelopmentBranch in test commit log file. commit 70353ce6771866f29c38b4460b3f74f9024f8ce2 Author: Praqma Support Date: on jun 3 14:03:45 2015 +0200 Added line from myDevelopmentBranch in test commit log file. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [pretested-integration-plugin] (JENKINS-29369) Accumulated commit message is locale and launguage dependent (Praqma case 13296)
Title: Message Title
Bue Petersen edited a comment on JENKINS-29369
Re: Accumulated commit message is locale and launguage dependent (Praqma case 13296)
Example on danish formatted date strings: {{{ Accumulated commit of the following from branch 'origin/ready/myDevelopmentBranch':commit c1449e075f528974c63eef81109d0632eaada0c7Author: Praqma Support Date: on jun 3 14:03:46 2015 +0200Added a second line from myDevelopmentBranch in test commit log file.commit 70353ce6771866f29c38b4460b3f74f9024f8ce2Author: Praqma Support Date: on jun 3 14:03:45 2015 +0200Added line from myDevelopmentBranch in test commit log file. }}}
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
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] [pretested-integration-plugin] (JENKINS-29369) Accumulated commit message is locale and launguage dependent (Praqma case 13296)
Title: Message Title Bue Petersen updated an issue Jenkins / JENKINS-29369 Accumulated commit message is locale and launguage dependent (Praqma case 13296) Change By: Bue Petersen Summary: Accumulated commit message is locale and launguage dependent (Praqma case 13296) Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [gitlab-hook-plugin] (JENKINS-29283) Allow cloning job trees when creating job via gitlab web hook
Title: Message Title Vladimir Sitnikov commented on JENKINS-29283 Re: Allow cloning job trees when creating job via gitlab web hook Finally I ended up with the following setup: 1) "seed job" calls "jobcopy plugin" to create jobs as required and schedules the proper job for execution 2) gitlab-hook triggers only "seed job" no matter which branch is triggered In that setup, gitlab-hook still does not work out-of-the-box since it tries to trigger all the jobs (see JENKINS-29317). Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [gerrit-trigger-plugin] (JENKINS-28168) gerrit-trigger used cpu 100%
Title: Message Title Vladimir Sitnikov commented on JENKINS-28168 Re: gerrit-trigger used cpu 100% This is a JDK bug: https://bugs.openjdk.java.net/browse/JDK-8028627 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [pretested-integration-plugin] (JENKINS-29369) Accumulated commit message is locale and launguage dependent
Title: Message Title Bue Petersen created an issue Jenkins / JENKINS-29369 Accumulated commit message is locale and launguage dependent Issue Type: Bug Assignee: Praqma Support Components: pretested-integration-plugin Created: 12/Jul/15 6:25 PM Priority: Major Reporter: Bue Petersen The generated accumulated commit message is language and git configuration independent. This gives unstable test results, as well as users can not always be sure that they get the expected accumulated commit message if build slaves have different language and locale settings. Currently best found solution is to enforce english locale settings in the accumulated commit message. Currently there is none, thus it is build environment dependent. It does not affect the squash commit message, as this is generated by Git and seems to have defaults that matches english. Add Comment
[JIRA] [subversion-plugin] (JENKINS-18414) Jenkins Subversion plugin checkouts in something NON-UTF-8
Title: Message Title Manuel Jesús Recena Soto resolved as Cannot Reproduce Jenkins / JENKINS-18414 Jenkins Subversion plugin checkouts in something NON-UTF-8 Change By: Manuel Jesús Recena Soto Status: Open Resolved Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [subversion-plugin] (JENKINS-18414) Jenkins Subversion plugin checkouts in something NON-UTF-8
Title: Message Title Manuel Jesús Recena Soto assigned an issue to Manuel Jesús Recena Soto Jenkins / JENKINS-18414 Jenkins Subversion plugin checkouts in something NON-UTF-8 Change By: Manuel Jesús Recena Soto Assignee: Manuel Jesús Recena Soto Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [subversion-plugin] (JENKINS-29293) Repositories set as external are not triggered if they are in the list of jobs after the main repository
Title: Message Title Manuel Jesús Recena Soto edited a comment on JENKINS-29293 Re: Repositories set as external are not triggered if they are in the list of jobs after the main repository [~balteanu_marius], What subversion workspace version are you using? Here you can find the configuration form: [^JENKINS-29293.png] Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [subversion-plugin] (JENKINS-29293) Repositories set as external are not triggered if they are in the list of jobs after the main repository
Title: Message Title Manuel Jesús Recena Soto edited a comment on JENKINS-29293 Re: Repositories set as external are not triggered if they are in the list of jobs after the main repository [~balteanu_marius], What subversion workspace version are you using? Here you can find the configuration form: [^JENKINS-29293.png] Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [subversion-plugin] (JENKINS-29293) Repositories set as external are not triggered if they are in the list of jobs after the main repository
Title: Message Title Manuel Jesús Recena Soto edited a comment on JENKINS-29293 Re: Repositories set as external are not triggered if they are in the list of jobs after the main repository [~balteanu_marius], What subversion workspace version are you using? Here you can find the configuration form: [^JENKINS-29293.png] Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [subversion-plugin] (JENKINS-29293) Repositories set as external are not triggered if they are in the list of jobs after the main repository
Title: Message Title Manuel Jesús Recena Soto updated an issue Jenkins / JENKINS-29293 Repositories set as external are not triggered if they are in the list of jobs after the main repository Change By: Manuel Jesús Recena Soto Attachment: JENKINS-29293.png Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [subversion-plugin] (JENKINS-29293) Repositories set as external are not triggered if they are in the list of jobs after the main repository
Title: Message Title Manuel Jesús Recena Soto edited a comment on JENKINS-29293 Re: Repositories set as external are not triggered if they are in the list of jobs after the main repository [~balteanu_marius], What subversion workspace version are you using? Here you can find the configuration form: ! [^ JENKINS-29293.png |thumbnail! ] Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [subversion-plugin] (JENKINS-29293) Repositories set as external are not triggered if they are in the list of jobs after the main repository
Title: Message Title Manuel Jesús Recena Soto edited a comment on JENKINS-29293 Re: Repositories set as external are not triggered if they are in the list of jobs after the main repository [~balteanu_marius], What subversion workspace version are you using? Here you can find the configuration form: [^ ! JENKINS-29293.png ] |thumbnail! Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [subversion-plugin] (JENKINS-29293) Repositories set as external are not triggered if they are in the list of jobs after the main repository
Title: Message Title Manuel Jesús Recena Soto updated an issue Jenkins / JENKINS-29293 Repositories set as external are not triggered if they are in the list of jobs after the main repository Change By: Manuel Jesús Recena Soto Attachment: JENKINS-29293.png Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [subversion-plugin] (JENKINS-29293) Repositories set as external are not triggered if they are in the list of jobs after the main repository
Title: Message Title Manuel Jesús Recena Soto edited a comment on JENKINS-29293 Re: Repositories set as external are not triggered if they are in the list of jobs after the main repository [~balteanu_marius], What subversion workspace version are you using? Here you can find the configuration form: [^JENKINS-29293.png] Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [subversion-plugin] (JENKINS-29293) Repositories set as external are not triggered if they are in the list of jobs after the main repository
Title: Message Title Manuel Jesús Recena Soto commented on JENKINS-29293 Re: Repositories set as external are not triggered if they are in the list of jobs after the main repository Marius Balteanu, What subversion workspace version are you using? Here you can find the configuration form: Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [subversion-plugin] (JENKINS-29293) Repositories set as external are not triggered if they are in the list of jobs after the main repository
Title: Message Title Manuel Jesús Recena Soto started work on JENKINS-29293 Change By: Manuel Jesús Recena Soto Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [subversion-plugin] (JENKINS-29293) Repositories set as external are not triggered if they are in the list of jobs after the main repository
Title: Message Title Manuel Jesús Recena Soto assigned an issue to Manuel Jesús Recena Soto Jenkins / JENKINS-29293 Repositories set as external are not triggered if they are in the list of jobs after the main repository Change By: Manuel Jesús Recena Soto Assignee: Manuel Jesús Recena Soto Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [subversion-plugin] (JENKINS-26158) Active Directory authentication for Subversion plugin fails
Title: Message Title Manuel Jesús Recena Soto commented on JENKINS-26158 Re: Active Directory authentication for Subversion plugin fails Steven Christou, What do you think if we resolve this ticket as duplicated? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [subversion-plugin] (JENKINS-29352) SVN Polling does not accept system variable in repo URL
Title: Message Title Manuel Jesús Recena Soto commented on JENKINS-29352 Re: SVN Polling does not accept system variable in repo URL Ryan Hochstetler, Could you try "Wipe Out Current Workspace" and build again? Access to Jenkins Select your job Press on Workspace (left menu) Press on Wipe Out Current Workspace Press on Build Now Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [subversion-plugin] (JENKINS-29352) SVN Polling does not accept system variable in repo URL
Title: Message Title Manuel Jesús Recena Soto edited a comment on JENKINS-29352 Re: SVN Polling does not accept system variable in repo URL [~ryanhos], Could you try "_Wipe Out Current Workspace_" and build again?# Access to Jenkins# Select your job# Press on _Workspace_ (left menu)# Press on _Wipe Out Current Workspace_# Press on _Build Now_ What version of Subversion Plugin are you using? 2.5 or 2.5.1? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [subversion-plugin] (JENKINS-29352) SVN Polling does not accept system variable in repo URL
Title: Message Title Manuel Jesús Recena Soto started work on JENKINS-29352 Change By: Manuel Jesús Recena Soto Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [subversion-plugin] (JENKINS-29352) SVN Polling does not accept system variable in repo URL
Title: Message Title Manuel Jesús Recena Soto assigned an issue to Manuel Jesús Recena Soto Jenkins / JENKINS-29352 SVN Polling does not accept system variable in repo URL Change By: Manuel Jesús Recena Soto Assignee: Vincent Latombe Manuel Jesús Recena Soto Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [subversion-plugin] (JENKINS-28749) Incorrect local modification being identified when svn:keywords are used on 1.8
Title: Message Title Manuel Jesús Recena Soto commented on JENKINS-28749 Re: Incorrect local modification being identified when svn:keywords are used on 1.8 dan russell I could not reproduce the bug. I followed this steps: Configure Jenkins to work with subversion workspace version 1.8 Add a freestyle project Configure a subversion repository protected Configure a credentials for this repository Build the project Environment: Jenkins 1.613 + Subversion Plugin 2.5.1 This repository had files using SVN Keyword Substitution (svn:keywords) Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [github-oauth-plugin] (JENKINS-23324) GitHub OAuth 0.17 requires private access to all repositories
Title: Message Title Sam Gleske commented on JENKINS-23324 Re: GitHub OAuth 0.17 requires private access to all repositories Fixed in release 0.21. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [github-oauth-plugin] (JENKINS-16350) "logout" link doesn't work
Title: Message Title Sam Gleske commented on JENKINS-16350 Re: "logout" link doesn't work With the GitHub authorization strategy anonymous read includes reading projects. We'd have to modify the behavior so anonymous can read overall but not actually allow read on any folders or projects. Contributions are welcome! Someone could create a pull request to fix this. I don't actively develop this plugin. I only maintain pull requests and releases. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [github-oauth-plugin] (JENKINS-25809) Issue when using embeddable-build-status
Title: Message Title Sam Gleske resolved as Fixed Fixed in release 0.21.1. Jenkins / JENKINS-25809 Issue when using embeddable-build-status Change By: Sam Gleske Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [github-oauth-plugin] (JENKINS-27118) Exception due to https://api.github.com/repos///collaborators not found
Title: Message Title Sam Gleske resolved as Fixed Fixed in 0.21 with configurable scopes. Jenkins / JENKINS-27118 Exception due to https://api.github.com/repos///collaborators not found Change By: Sam Gleske Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [github-oauth-plugin] (JENKINS-20845) Github Authorization Settings, users in "Participant in Organization" not given READ
Title: Message Title Sam Gleske resolved as Fixed Fixed in 0.21 with configurable scopes. Jenkins / JENKINS-20845 Github Authorization Settings, users in "Participant in Organization" not given READ Change By: Sam Gleske Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [subversion-plugin] (JENKINS-28749) Incorrect local modification being identified when svn:keywords are used on 1.8
Title: Message Title Manuel Jesús Recena Soto commented on JENKINS-28749 Re: Incorrect local modification being identified when svn:keywords are used on 1.8 dan russell Could you provide a step by step process in order to reproduce the bug? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [subversion-plugin] (JENKINS-21679) After update to 2.0 all jobs lost Subversion urls and it's not able to select Subversion at config (Source Code Management)
Title: Message Title Manuel Jesús Recena Soto edited a comment on JENKINS-21679 Re: After update to 2.0 all jobs lost Subversion urls and it's not able to select Subversion at config (Source Code Management) [~danielbeck] Yes but I was waiting for feedback from [~ andreas. podskalsky]. If I don't receive nothing in few day, I'll close this ticket. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [subversion-plugin] (JENKINS-29340) E200015: ISVNAuthentication provider did not provide credentials
Title: Message Title Manuel Jesús Recena Soto edited a comment on JENKINS-29340 Re: E200015: ISVNAuthentication provider did not provide credentials [~ricardogarfe], I've recorded a screencast showing the process: https://goo.gl/Xi8Q6f In order to So that I can continue working on go ahead with this bug, I need more detailed information. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [subversion-plugin] (JENKINS-29340) E200015: ISVNAuthentication provider did not provide credentials
Title: Message Title Manuel Jesús Recena Soto commented on JENKINS-29340 Re: E200015: ISVNAuthentication provider did not provide credentials Ricardo García Fernández, I've recorded a screencast showing the process: https://goo.gl/Xi8Q6f In order to I can continue working on this bug, I need more detailed information. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [subversion-plugin] (JENKINS-29340) E200015: ISVNAuthentication provider did not provide credentials
Title: Message Title Manuel Jesús Recena Soto commented on JENKINS-29340 Re: E200015: ISVNAuthentication provider did not provide credentials Ricardo García Fernández, I've also tried using a slave node. Everything works fine. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-29367) Unable to use label expression to restrict execution on more than one label
Title: Message Title
Dominique Brice edited a comment on JENKINS-29367
Re: Unable to use label _expression_ to restrict execution on more than one label
Hello SorinYour issue is not linked to the [label-linked-jobs-plugin|https://wiki.jenkins-ci.org/display/JENKINS/Label+Linked+Jobs+Plugin] so I changed its component to "core". Label functionality is provided by the core engine of Jenkins.This being said I didn't find either documentation of the available expressions, although I know where to look in the code ([there|https://github.com/jenkinsci/jenkins/blob/master/core/src/main/grammar/labelExpr.g] and [there|https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/model/labels/LabelExpression.java]).The available operators are:* {{&&}} logical and. Both labels must be present on the node to execute the job.* {{||}} logical or. At least one of the labels must be present on the node to execute the job* {{!}} logical not. The label must not be present on the node to execute the job* {{->}} implies operator. If your condition is a -> b, then if label a is present on the node, b must also be present to run the job. If a is not defined, there's no requirement on b* {{<\->}} 'equivalent' operator. If your condition is a <-> b, then either both or nore of the two labels must be defined on the node to run the job. If only a or only b is defined on the node, the job won't be run on it. If you can provide additional details and screenshots of what you're trying to achieve I'll be happy to help.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
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] [core] (JENKINS-29367) Unable to use label expression to restrict execution on more than one label
Title: Message Title
Dominique Brice edited a comment on JENKINS-29367
Re: Unable to use label _expression_ to restrict execution on more than one label
Hello SorinYour issue is not linked to the [label-linked-jobs-plugin|https://wiki.jenkins-ci.org/display/JENKINS/Label+Linked+Jobs+Plugin] so I changed its component to "core". Label functionality is provided by the core engine of Jenkins.This being said I didn't find either documentation of the available expressions, although I know where to look in the code ([there|https://github.com/jenkinsci/jenkins/blob/master/core/src/main/grammar/labelExpr.g] and [there|https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/model/labels/LabelExpression.java]).The available operators are:* {{&&}} , logical and. Both labels must be present on the node to execute the job.* {{||}} , logical or. At least one of the labels must be present on the node to execute the job* {{!}} , logical not. The label must not be present on the node to execute the job* {{->}} , implies operator. If your condition is a -> b, then if label a is present on the node, b must also be present to run the job. If a is not defined, there's no requirement on b* {{<\->}} , 'equivalent' operator. If your condition is a <-> b, then either both or nore of the two labels must be defined on the node to run the job. If only a or only b is defined on the node, the job won't be run on it.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
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] [core] (JENKINS-29367) Unable to use label expression to restrict execution on more than one label
Title: Message Title
Dominique Brice edited a comment on JENKINS-29367
Re: Unable to use label _expression_ to restrict execution on more than one label
Hello SorinYour issue is not linked to the [ label-linked-jobs-plugin |https://wiki.jenkins-ci.org/display/JENKINS/Label+Linked+Jobs+Plugin] so I changed its component to "core". Label functionality is provided by the core engine of Jenkins.This being said I didn't find either documentation of the available expressions, although I know where to look in the code ([there|https://github.com/jenkinsci/jenkins/blob/master/core/src/main/grammar/labelExpr.g] and [there|https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/model/labels/LabelExpression.java]).The available operators are:* {{&&}}, logical and. Both labels must be present on the node to execute the job.* {{||}}, logical or. At least one of the labels must be present on the node to execute the job* {{!}}, logical not. The label must not be present on the node to execute the job* {{->}}, implies operator. If your condition is a -> b, then if label a is present on the node, b must also be present to run the job. If a is not defined, there's no requirement on b* {{<\->}}, 'equivalent' operator. If your condition is a <-> b, then either both or nore of the two labels must be defined on the node to run the job. If only a or only b is defined on the node, the job won't be run on it.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
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] [core] (JENKINS-29367) Unable to use label expression to restrict execution on more than one label
Title: Message Title Dominique Brice commented on JENKINS-29367 Re: Unable to use label _expression_ to restrict execution on more than one label Hello Sorin Your issue is not linked to the label-linked-jobs-plugin so I changed its component to "core". Label functionality is provided by the core engine of Jenkins. This being said I didn't find either documentation of the available expressions, although I know where to look in the code (there and there). The available operators are: &&, logical and. Both labels must be present on the node to execute the job. ||, logical or. At least one of the labels must be present on the node to execute the job !, logical not. The label must not be present on the node to execute the job ->, implies operator. If your condition is a -> b, then if label a is present on the node, b must also be present to run the job. If a is not defined, there's no requirement on b <->, 'equivalent' operator. If your condition is a <-> b, then either both or nore of the two labels must be defined on the node to run the job. If only a or only b is defined on the node, the job won't be run on it. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenk
[JIRA] [core] (JENKINS-29367) Unable to use label expression to restrict execution on more than one label
Title: Message Title Dominique Brice updated an issue Jenkins / JENKINS-29367 Unable to use label _expression_ to restrict execution on more than one label Change By: Dominique Brice Component/s: core Component/s: label-linked-jobs-plugin Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-29368) WARNING: invalid gitTool selection Default
Title: Message Title Gaurav Chhabra created an issue Jenkins / JENKINS-29368 WARNING: invalid gitTool selection Default Issue Type: Bug Assignee: Nicolas De Loof Components: core, git-plugin Created: 12/Jul/15 1:36 PM Environment: Jenkins 1.614 Git plugin 2.3.5 Server version: Apache Tomcat/7.0.2 Server built: Aug 4 2010 12:23:47 Server number: 7.0.2.0 OS Name: Linux OS Version: 3.14.20-20.44.amzn1.x86_64 Architecture: amd64 JVM Version: 1.8.0_45-b14 JVM Vendor: Oracle Corporation Labels: Jenkins Git Git-plugin Priority: Minor Reporter: Gaurav Chhabra I'm running Jenkins in Tomcat container. On startup, i see the following message in catalina.out: ... ... Jul 12, 2015 4:55:14 PM org.springframework.beans.factory.support.DefaultListableBeanFactory preInstantiateSingletons INFO: Pre-instantiating singletons in org.springframework.beans.factory.support.DefaultListableBeanFactory@558f7e2a: defining beans [filter,legacy]; root of factory hierarchy Jul 12, 2015 4:55:19 PM hudson.WebAppMain$3 run INFO: Jenkins is fully up and running Jul 12, 2015 4:56:00 P
[JIRA] [label-linked-jobs-plugin] (JENKINS-29367) Unable to use label expression to restrict execution on more than one label
Title: Message Title Sorin Sbarnea created an issue Jenkins / JENKINS-29367 Unable to use label _expression_ to restrict execution on more than one label Issue Type: Bug Assignee: Dominique Brice Components: label-linked-jobs-plugin Created: 12/Jul/15 12:27 PM Priority: Minor Reporter: Sorin Sbarnea Somehow I am unable to find a way to introduce more than a label in label expresison field of the job configuration. I tried any combination and it seems impossible to write something else than just a single label. I don't know if that's just because I do not know the magic syntax but also the help text is completly missing to tell which kind of syntax you can put inside. In my case I wanted A && B kind of condition. Even if that's only lack of knowledge this bug is still valid because the help-text does not contain any example. Add Comment
[JIRA] [subversion-plugin] (JENKINS-22922) Subversion : environment variables work only partially (got broken in 2.3 or prior, after 1.44)
Title: Message Title Manuel Jesús Recena Soto commented on JENKINS-22922 Re: Subversion : environment variables work only partially (got broken in 2.3 or prior, after 1.44) Pawel Defee, Hi. Could you try if this bug is present on Subversion Plugin 2.5.1 (latest release)? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [subversion-plugin] (JENKINS-22922) Subversion : environment variables work only partially (got broken in 2.3 or prior, after 1.44)
Title: Message Title Manuel Jesús Recena Soto assigned an issue to Manuel Jesús Recena Soto Jenkins / JENKINS-22922 Subversion : environment variables work only partially (got broken in 2.3 or prior, after 1.44) Change By: Manuel Jesús Recena Soto Assignee: Manuel Jesús Recena Soto Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [subversion-plugin] (JENKINS-29340) E200015: ISVNAuthentication provider did not provide credentials
Title: Message Title
Manuel Jesús Recena Soto edited a comment on JENKINS-29340
Re: E200015: ISVNAuthentication provider did not provide credentials
[~ricardogarfe] I could not reproduce it.I used the same environment: Jenkins 1.613, Subversion Plugin (2.5.1) and EnvInject Plugin 1.91.3 and I followed the steps described above. The result:{noformat}Lanzada por el usuario anonymous[EnvInject] - Loading node environment variables.[EnvInject] - Preparing an environment for the build.[EnvInject] - Keeping Jenkins system variables.[EnvInject] - Keeping Jenkins build variables.[EnvInject] - Injecting as environment variables the properties content REPO=jenkins-26318[EnvInject] - Variables injected successfully.[EnvInject] - Injecting contributions.Ejecutando.en el espacio de trabajo /Users/recena/Documents/workspace-luna-cb/subversion-plugin/work/workspace/JENKINS-29308Checking out a fresh workspace because there's no workspace at /Users/recena/Documents/workspace-luna-cb/subversion-plugin/work/workspace/JENKINS-29308Cleaning local Directory .Checking out https://subversion.assembla.com/svn/jenkins-26318/trunk at revision '2015-07-12T12:55:34.653 +0200'A srcA src/testA src/test/javaA src/test/java/comA src/test/java/com/cloudbeesA src/test/java/com/cloudbees/manticoreA src/test/java/com/cloudbees/manticore/AppTest.javaA src/mainA src/main/javaA src/main/java/comA src/main/java/com/cloudbeesA src/main/java/com/cloudbees/manticoreA src/main/java/com/cloudbees/manticore/App.javaA pom.xmlA logparser-rules.txtAt revision 12Finished: SUCCESS{noformat}I think it would be interesting to improve the repository validation and avoid this message: [^JENKINS-29308.png]
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
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] [subversion-plugin] (JENKINS-29340) E200015: ISVNAuthentication provider did not provide credentials
Title: Message Title Manuel Jesús Recena Soto updated an issue Jenkins / JENKINS-29340 E200015: ISVNAuthentication provider did not provide credentials Change By: Manuel Jesús Recena Soto Attachment: JENKINS-29308.png Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [subversion-plugin] (JENKINS-29340) E200015: ISVNAuthentication provider did not provide credentials
Title: Message Title Manuel Jesús Recena Soto commented on JENKINS-29340 Re: E200015: ISVNAuthentication provider did not provide credentials Ricardo García Fernández I could not reproduce it. I used the same environment: Jenkins 1.613, Subversion Plugin (2.5.1) and EnvInject Plugin 1.91.3 and I followed the steps described above. The result: Lanzada por el usuario anonymous [EnvInject] - Loading node environment variables. [EnvInject] - Preparing an environment for the build. [EnvInject] - Keeping Jenkins system variables. [EnvInject] - Keeping Jenkins build variables. [EnvInject] - Injecting as environment variables the properties content REPO=jenkins-26318 [EnvInject] - Variables injected successfully. [EnvInject] - Injecting contributions. Ejecutando.en el espacio de trabajo /Users/recena/Documents/workspace-luna-cb/subversion-plugin/work/workspace/JENKINS-29308 Checking out a fresh workspace because there's no workspace at /Users/recena/Documents/workspace-luna-cb/subversion-plugin/work/workspace/JENKINS-29308 Cleaning local Directory . Checking out https://subversion.assembla.com/svn/jenkins-26318/trunk at revision '2015-07-12T12:55:34.653 +0200' A src A src/test A src/test/java A src/test/java/com A src/test/java/com/cloudbees A src/test/java/com/cloudbees/manticore A src/test/java/com/cloudbees/manticore/AppTest.java A src/main A src/main/java A src/main/java/com A src/main/java/com/cloudbees A src/main/java/com/cloudbees/manticore A src/main/java/com/cloudbees/manticore/App.java A pom.xml A logparser-rules.txt At revision 12 Finished: SUCCESS I think it would be interesting to improve the repository validation and avoid this message: Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [ssh2easy-plugin] (JENKINS-29364) In Jenkins Update Center , There are display two the same duplicated items for this plugin - SSH2 Easy Plugin V1.3 .
Title: Message Title Jerry Cai resolved as Fixed Root Cause : It is rename (ID : ssh2easy ) to another with suffix -plugin (new ID : ssh2easy-plugin) and release again by the author of this plugin . Resolved : Now remove the ssh2easy-plugin from update center , just leave ssh2easy only available . To Users: 1. If you has already install the ssh2easy-plugin , You can find the SSH2 Easy Plugin still there in available for installation , I suggest you uninstalled SSH2 Easy Plugin and re-install from available for installation tab again . Then it will keep update in future . Sorry for this changes with this issue . Jenkins / JENKINS-29364 In Jenkins Update Center , There are display two the same duplicated items for this plugin - SSH2 Easy Plugin V1.3 . Change By: Jerry Cai Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [subversion-plugin] (JENKINS-29340) E200015: ISVNAuthentication provider did not provide credentials
Title: Message Title Manuel Jesús Recena Soto updated an issue Jenkins / JENKINS-29340 E200015: ISVNAuthentication provider did not provide credentials Change By: Manuel Jesús Recena Soto Labels: svn parameters url Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [ssh2easy-plugin] (JENKINS-29364) In Jenkins Update Center , There are display two the same duplicated items for this plugin - SSH2 Easy Plugin V1.3 .
Title: Message Title Jerry Cai updated an issue Jenkins / JENKINS-29364 In Jenkins Update Center , There are display two the same duplicated items for this plugin - SSH2 Easy Plugin V1.3 . Change By: Jerry Cai Issue Phenomenon Description : In Jenkins Update Center , There are display two the same duplicated items for this plugin - SSH2 Easy Plugin V1.3 . Root Cause :It is rename (ID : ssh2easy ) to another with suffix -plugin (new ID : ssh2easy-plugin) and release again by the author of this plugin . Resolved :Now remove the ssh2easy-plugin from update center , just leave ssh2easy only available .To Users:1. If you has already install the ssh2easy-plugin , You can find the SSH2 Easy Plugin still there in available for installation , I suggest you uninstalled SSH2 Easy Plugin and re-install from available for installation tab again . Then it will keep update in future . Sorry for this changes with this issue . Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [ssh2easy-plugin] (JENKINS-29365) In Jenkins Update Center , There are display two the same duplicated items for this plugin - SSH2 Easy Plugin V1.3 .
Title: Message Title Jerry Cai closed an issue as Duplicate Jenkins / JENKINS-29365 In Jenkins Update Center , There are display two the same duplicated items for this plugin - SSH2 Easy Plugin V1.3 . Change By: Jerry Cai Status: Open Closed Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [proc-cleaner-plugin] (JENKINS-29366) add documentation
Title: Message Title Dominik Bartholdi created an issue Jenkins / JENKINS-29366 add documentation Issue Type: Bug Assignee: Oliver Gondža Components: proc-cleaner-plugin Created: 12/Jul/15 10:39 AM Priority: Major Reporter: Dominik Bartholdi please add some documentation to the wiki, users have no idea what this plugin is all about. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [docker-custom-build-environment-plugin] (JENKINS-29081) Add ability for this plugin to communicate with the docker daemon using a java-based client
Title: Message Title Nicolas De Loof commented on JENKINS-29081 Re: Add ability for this plugin to communicate with the docker daemon using a java-based client docker-custom-build-environment-plugin do communicate from build slave with a local docker daemon so it can bind mount workspace, so it doesn't make much sense to run on a node that does not have docker executable available. For a containerized environment, you can download and install docker client using docker-commons 1.1 auto-installer Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [docker-custom-build-environment-plugin] (JENKINS-28989) support registry credentials
Title: Message Title Nicolas De Loof closed an issue as Fixed Jenkins / JENKINS-28989 support registry credentials Change By: Nicolas De Loof Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [subversion-plugin] (JENKINS-29340) E200015: ISVNAuthentication provider did not provide credentials
Title: Message Title Manuel Jesús Recena Soto commented on JENKINS-29340 Re: E200015: ISVNAuthentication provider did not provide credentials Ricardo García Fernández, I'm trying to reproduce the bug. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [subversion-plugin] (JENKINS-29340) E200015: ISVNAuthentication provider did not provide credentials
Title: Message Title Manuel Jesús Recena Soto started work on JENKINS-29340 Change By: Manuel Jesús Recena Soto Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [subversion-plugin] (JENKINS-21679) After update to 2.0 all jobs lost Subversion urls and it's not able to select Subversion at config (Source Code Management)
Title: Message Title Manuel Jesús Recena Soto commented on JENKINS-21679 Re: After update to 2.0 all jobs lost Subversion urls and it's not able to select Subversion at config (Source Code Management) Daniel Beck Yes but I was waiting for feedback from [~andreas.podskalsky]. If I don't receive nothing in few day, I'll close this ticket. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [subversion-plugin] (JENKINS-21679) After update to 2.0 all jobs lost Subversion urls and it's not able to select Subversion at config (Source Code Management)
Title: Message Title Manuel Jesús Recena Soto updated an issue Jenkins / JENKINS-21679 After update to 2.0 all jobs lost Subversion urls and it's not able to select Subversion at config (Source Code Management) Change By: Manuel Jesús Recena Soto Labels: subversion Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [subversion-plugin] (JENKINS-29340) E200015: ISVNAuthentication provider did not provide credentials
Title: Message Title Manuel Jesús Recena Soto commented on JENKINS-29340 Re: E200015: ISVNAuthentication provider did not provide credentials Daniel Beck Thanks for the advice. Is there any reason why that PR has not been merged? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-27189) In IE11, name of running job extends into main dashboard area
Title: Message Title Tom FENNELLY commented on JENKINS-27189 Re: In IE11, name of running job extends into main dashboard area Hi David. Sorry to hear you are having issues. Sadly, IE always continues to be a source of problems. Jenkins inserts zero-width-space characters (u8203) in long strings of text. This is not working for David's IE11 setup under some particular scenario. You could look at the source (select the test and do "view element source" in the browser) and see if these characters are getting inserted, or not. Daniel (Daniel Beck), sounds like you have found a situation where your modern.ie breaks? Maybe we can do a screenshare? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [logstash-plugin] (JENKINS-29339) Pushing logs to redis using LogStash plugin is serialised
Title: Message Title Giulio Eulisse commented on JENKINS-29339 Re: Pushing logs to redis using LogStash plugin is serialised Post build. buildwrapper seems fine. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [logstash-plugin] (JENKINS-29339) Pushing logs to redis using LogStash plugin is serialised
Title: Message Title Giulio Eulisse commented on JENKINS-29339 Re: Pushing logs to redis using LogStash plugin is serialised I am using the latest released version. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [role-strategy-plugin] (JENKINS-29333) role-based security: edit existing role
Title: Message Title Waldek M closed an issue as Not A Defect Not an issue. Jenkins / JENKINS-29333 role-based security: edit existing role Change By: Waldek M Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [github-oauth-plugin] (JENKINS-23324) GitHub OAuth 0.17 requires private access to all repositories
Title: Message Title Paul Blundell commented on JENKINS-23324 Re: GitHub OAuth 0.17 requires private access to all repositories woohoo Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [role-strategy-plugin] (JENKINS-29333) role-based security: edit existing role
Title: Message Title Waldek M commented on JENKINS-29333 Re: role-based security: edit existing role Ouch! "The field doesn't look editable" is my only defence. Thanks a lot! Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [ssh2easy-plugin] (JENKINS-29365) In Jenkins Update Center , There are display two the same duplicated items for this plugin - SSH2 Easy Plugin V1.3 .
Title: Message Title Jerry Cai created an issue Jenkins / JENKINS-29365 In Jenkins Update Center , There are display two the same duplicated items for this plugin - SSH2 Easy Plugin V1.3 . Issue Type: Bug Assignee: Jerry Cai Components: ssh2easy-plugin Created: 12/Jul/15 7:17 AM Labels: ssh2easy-plugin plugin jenkins Priority: Minor Reporter: Jerry Cai Issue Phenomenon : In Jenkins Update Center , There are display two the same duplicated items for this plugin - SSH2 Easy Plugin V1.3 . Root Cause : It is rename (ID : ssh2easy ) to another with suffix -plugin (new ID : ssh2easy-plugin) and release again by the author of this plugin . Resolved : Now remove the ssh2easy-plugin from update center , just leave ssh2easy only available . To Users: 1. If you has already install the ssh2easy-plugin , You can find the SSH2 Easy Plugin still there in available for installation , I suggest you uninstalled SSH2 Easy Plugin and re-install from available for installation tab again . Then it will keep update in future . Sorry for this changes with this issue .
[JIRA] [ssh2easy-plugin] (JENKINS-29364) In Jenkins Update Center , There are display two the same duplicated items for this plugin - SSH2 Easy Plugin V1.3 .
Title: Message Title Jerry Cai created an issue Jenkins / JENKINS-29364 In Jenkins Update Center , There are display two the same duplicated items for this plugin - SSH2 Easy Plugin V1.3 . Issue Type: Bug Assignee: Jerry Cai Components: ssh2easy-plugin Created: 12/Jul/15 7:16 AM Labels: ssh2easy-plugin plugin jenkins Priority: Minor Reporter: Jerry Cai Issue Phenomenon : In Jenkins Update Center , There are display two the same duplicated items for this plugin - SSH2 Easy Plugin V1.3 . Root Cause : It is rename (ID : ssh2easy ) to another with suffix -plugin (new ID : ssh2easy-plugin) and release again by the author of this plugin . Resolved : Now remove the ssh2easy-plugin from update center , just leave ssh2easy only available . To Users: 1. If you has already install the ssh2easy-plugin , You can find the SSH2 Easy Plugin still there in available for installation , I suggest you uninstalled SSH2 Easy Plugin and re-install from available for installation tab again . Then it will keep update in future . Sorry for this changes with this issue .
