[JIRA] [git-client-plugin] (JENKINS-29604) git-client CLI implementation does not propogate username
Title: Message Title Mark Waite resolved as Fixed Fixed in git client plugin release after 1.18.0 for repositories which don't use submodules. Jenkins / JENKINS-29604 git-client CLI implementation does not propogate username Change By: Mark Waite 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] [git-client-plugin] (JENKINS-29604) git-client CLI implementation does not propogate username
Title: Message Title Jacob Keller commented on JENKINS-29604 Re: git-client CLI implementation does not propogate username I removed the .m2/repository, and am re-running the mvn clean install to see if this helps. 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-22855) SSH Credential's username isn't used.
Title: Message Title Mark Waite resolved as Fixed Fixed in the next git client plugin released after 1.18.0 Jenkins / JENKINS-22855 SSH Credential's username isn't used. Change By: Mark Waite 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] [git-client-plugin] (JENKINS-29604) git-client CLI implementation does not propogate username
Title: Message Title SCM/JIRA link daemon commented on JENKINS-29604 Re: git-client CLI implementation does not propogate username Code changed in jenkins User: Jacob Keller Path: src/main/java/org/jenkinsci/plugins/gitclient/CliGitAPIImpl.java http://jenkins-ci.org/commit/git-client-plugin/9953d3dbb3526aa014d0382b37d3ed4d43646f57 Log: git-client: store username as default user in credentials.username In case the http(s) url being used does not supply a username, set the default username for credentials in the gitconfig. This helps ensure that credentials which have usernames not matching the system username of the slave will work as expected for http(s) urls. JENKINS-29604 - git-client CLI implementation does not propogate username Signed-off-by: Jacob Keller 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-29604) git-client CLI implementation does not propogate username
Title: Message Title SCM/JIRA link daemon commented on JENKINS-29604 Re: git-client CLI implementation does not propogate username Code changed in jenkins User: Jacob Keller Path: src/main/java/org/jenkinsci/plugins/gitclient/CliGitAPIImpl.java http://jenkins-ci.org/commit/git-client-plugin/38a6fb0a602da63ffd160344ac1e98c8894b1f69 Log: git-client: use username in the GIT_SSH setup Teach the GIT_SSH script we create to pass "-l " so that a default user will be selected incase the URL does not encode the username. This is important, as otherwise the CLI implementation will default to the local username, which is probably incorrect. While users are able to work around this bug by specifying the correct user in the ssh url, they cannot do so for submodules. JENKINS-29604 - git-client CLI implementation does not propogate username Signed-off-by: Jacob Keller 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-29604) git-client CLI implementation does not propogate username
Title: Message Title SCM/JIRA link daemon commented on JENKINS-29604 Re: git-client CLI implementation does not propogate username Code changed in jenkins User: Mark Waite Path: src/main/java/org/jenkinsci/plugins/gitclient/CliGitAPIImpl.java http://jenkins-ci.org/commit/git-client-plugin/d582d1b0465ef0b651880da16c2e83474389a60f Log: Merge [Fix JENKINS-29604] from Jacob Keller 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-29604) git-client CLI implementation does not propogate username
Title: Message Title Mark Waite commented on JENKINS-29604 Re: git-client CLI implementation does not propogate username You should first get the tests running from a command line in your environment. Once you have that, I can send you some scripts I used to assemble my authentication test case data files. The authentication tests currently read data from a CSV file. That's nice and simple, but doesn't handle the many interesting authentication cases which exist. I'd really like the authentication tests to accept a better data format (JSON, for example) with more variation allowed so that one entry could be for an ssh URL, another for an https URL with user name and password provided, etc. 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-29604) git-client CLI implementation does not propogate username
Title: Message Title Jacob Keller commented on JENKINS-29604 Re: git-client CLI implementation does not propogate username Ok, I'll give this a try. How do I setup the special ssh-auth tests so that I can add some of the repositories I use for testing, that have multiple submodules. Regards, Jake 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-plugin] (JENKINS-22536) Date in changeset is in wrong format
Title: Message Title Mark Waite closed an issue as Fixed Jenkins / JENKINS-22536 Date in changeset is in wrong format Change By: Mark Waite 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] [git-plugin] (JENKINS-22536) Date in changeset is in wrong format
Title: Message Title Mark Waite resolved as Fixed Assuming this was fixed in git client plugin 1.18.0 and git plugin 2.4.0, released 18 July 2015 Jenkins / JENKINS-22536 Date in changeset is in wrong format Change By: Mark Waite 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] [git-client-plugin] (JENKINS-26026) Submodules not supported with JGit
Title: Message Title Mark Waite commented on JENKINS-26026 Re: Submodules not supported with JGit Yes, having more submodule tests would be a great help. One of the items listed as needed in the README is "Create submodule 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] [git-client-plugin] (JENKINS-29604) git-client CLI implementation does not propogate username
Title: Message Title Mark Waite commented on JENKINS-29604 Re: git-client CLI implementation does not propogate username I run tests from many different platforms using mvn clean install The tests assume you have http protocol access to the public internet. If you are connecting through an http or https proxy, then http_proxy needs to be set in your environment. 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-26026) Submodules not supported with JGit
Title: Message Title Jacob Keller commented on JENKINS-26026 Re: Submodules not supported with JGit Maybe providing more tests would help here? The git-client doesn't use these methods at all, and the git-plugin proper only uses the "updateSubmoduleUrls" and the comments here are completely dubious at best, considering that it is somehow attempting to "locate" where the refs are coming from which is something 100% foreign to git, and seems to be some scheme cooked up by whoever added this functionality in the first place. It certainly doesn't feel like a normal setup or feature. It's highly "magical" in that and it already claims to be only "heuristic" which seems fishy to me. I do not know what sort of tests would be there, and the methods already mention that they are "deprecated" It's understandable to not want to break any users, so having more tests for the standard behavior without the weird "hueristic" would be helpful. 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] [ssh-credentials-plugin] (JENKINS-20637) SSH Keys are only usable on master, not replicated on slaves
Title: Message Title Jacob Keller commented on JENKINS-20637 Re: SSH Keys are only usable on master, not replicated on slaves Yep this works just fine as long as you use proper credential setup. 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-29604) git-client CLI implementation does not propogate username
Title: Message Title Jacob Keller commented on JENKINS-29604 Re: git-client CLI implementation does not propogate username It actually does, but the git-plugin breaks, because it doesn't assign a default credentials, and the per-url doesn't work since the git-plugin doesn't provide that... I think we need to look up credentials based on the super project url instead, or provide 'submodule' credentials in the git-plugin. I worked around this by adding remotes that match the submodules for each submodule. This seemed to work, but I ran into another issue. Also, I can't for the life of me get the tests to run locally. What do I need to do that? just running "mvn" results in a spew of very bad behavior and no successful complete. I see the Jenkins running on the github pull request and it passes, but I would really like to run locally so I can start experimenting with more tests to add to the pull request. 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] [ssh-credentials-plugin] (JENKINS-20637) SSH Keys are only usable on master, not replicated on slaves
Title: Message Title Mark Waite commented on JENKINS-20637 Re: SSH Keys are only usable on master, not replicated on slaves I think this bug can be closed, since the git plugin and the git client plugin use the Jenkins credentials plugins with user name / password (all platforms), ssh private key without passphrase (all platforms), and ssh private key with passphrase (Unix platforms). 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-29604) git-client CLI implementation does not propogate username
Title: Message Title Mark Waite commented on JENKINS-29604 Re: git-client CLI implementation does not propogate username Thanks for the pull request. It allowed me to add two more authentication test cases that did not work prior to your pull request. I'm not ready to include the third commit from that pull request in the master branch, since it doesn't yet solve submodule authentication. 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] [p4-plugin] (JENKINS-24024) Opt-out of pulling changelist info for Build Changes
Title: Message Title Sam Alsam closed an issue as Fixed Jenkins / JENKINS-24024 Opt-out of pulling changelist info for Build Changes Change By: Sam Alsam 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] [git-client-plugin] (JENKINS-26026) Submodules not supported with JGit
Title: Message Title Mark Waite commented on JENKINS-26026 Re: Submodules not supported with JGit With 60,000+ installations of the git plugin and the git client plugin, I avoid changing existing behavior in areas which aren't well covered by automated tests, especially in an area as obscure (to me) as submodules. I made the mistake a few releases ago of making the client requirements more explicit, refusing to allow ancient git command line executables. The Red Hat 5 users had serious problems with the change. I had to revert it within a day or two of that mistake. 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-29634) a job was stuck with no possibility to abort when the underlying worker was edited
Title: Message Title Alexey Java created an issue Jenkins / JENKINS-29634 a job was stuck with no possibility to abort when the underlying worker was edited Issue Type: Bug Assignee: Unassigned Components: core Created: 25/Jul/15 3:44 AM Environment: Jenkins 1.580.3 Priority: Minor Reporter: Alexey Java I created a new slave/worker node in my Jenkins, then some job started running on it. then I edited the Jenkins node settings: changed its IP address and clicked save. I didn't check if there was something running on that node at the time... apparently there was. oh well.. I was hoping that worst case jenkins would just abort that job after some timeout and then reuse that new worker. also, there was "abort if stuck" setting on that job (coming from a jenkins plugin). but what happened was that even 2 days later the build job was still "running" and clicking "abort" had no effect. I tried clicking that red button many times - no effect. I had to restart the master jenkins instance for those jobs to finally stop. jenkins should gracefully handle situations when the slave/worker node disappears - like in this case when I
[JIRA] [openstack-cloud-plugin] (JENKINS-29633) jobs are not executed when not explicitly tied to a particular openstack group
Title: Message Title Alexey Java created an issue Jenkins / JENKINS-29633 jobs are not executed when not explicitly tied to a particular openstack group Issue Type: Bug Assignee: Marat Mavlyutov Components: openstack-cloud-plugin Created: 25/Jul/15 3:25 AM Priority: Major Reporter: Alexey Java environment: Jenkins master server with Openstack cloud plugin 1.8. openstack plugin is configured with 1 instance type - "openstack-medium". maximum number of openstack nodes of this type is set to 5. master server has 0 executors. no slave nodes are attached to master, so everything is expected to be executed on Openstack workers only. I have 10 build jobs that are not restricted where to run. now, I start a build job. I see in jenkins console that it creates and provisions a new VM. so far so good. the new VM is fully up and running with proper permissions and ssh access and ssh port open. all good. but the job is still in "waiting for available executor" state... then I see the plugin creates second worker... then it creates all 5 (up to max number of 5) jenkins workers. they are all fully functional, but not doing anything! the job is still "waiting for available executor". then I see in jenkins console "cleaning up openstack nodes"... after 3 minutes (the time I set as retention policy for those nodes) those workers are deleted from both Jenkins and openstack. and.. then openstack cloud starts creating new nodes again... all 5 of them. and they are not used again. and goes forever without any
[JIRA] [github-oauth-plugin] (JENKINS-17539) Swarm clients fail to connect if GitHub for authentication
Title: Message Title Sam Gleske resolved as Fixed Jenkins / JENKINS-17539 Swarm clients fail to connect if GitHub for authentication 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-17539) Swarm clients fail to connect if GitHub for authentication
Title: Message Title Sam Gleske commented on JENKINS-17539 Re: Swarm clients fail to connect if GitHub for authentication Great! Thanks for your follow up. I appreciate 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] [github-oauth-plugin] (JENKINS-27764) unable to discover private github email addresses
Title: Message Title Sam Gleske commented on JENKINS-27764 Re: unable to discover private github email addresses Jenkins plugin 0.22 has been released fixing this issue. I've also updated the wiki page to reflect the latest 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] [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 Jenkins plugin 0.22 has been released fixing this issue. I've also updated the wiki page to reflect the latest 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] [github-oauth-plugin] (JENKINS-20845) Private user memberships can't be used for authorization
Title: Message Title Sam Gleske resolved as Fixed Jenkins / JENKINS-20845 Private user memberships can't be used for authorization Change By: Sam Gleske Status: In Progress 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) Private user memberships can't be used for authorization
Title: Message Title Sam Gleske commented on JENKINS-20845 Re: Private user memberships can't be used for authorization Jenkins plugin 0.22 has been released fixing this issue. I've also updated the wiki page to reflect the latest 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] [git-plugin] (JENKINS-29631) Trigger notification broken for non-default refspecs when using parameterized branch
Title: Message Title Mark Waite commented on JENKINS-29631 Re: Trigger notification broken for non-default refspecs when using parameterized branch Thanks for the report and my apologies that 2.4.0 introduced a regression. I had high hopes to introduce no regressions with that release. The parameterized branch polling in 2.3.5 (and possibly before) would incorrectly poll the most recently used branch, instead of polling the branch named by the default value of the parameter. In your use case, were you relying on it to poll the most recently used branch? JENKINS-27352 was fixed in 2.4.0 to poll with the default value of the "branch to build" parameter. That fix may also have caused it to ignore the refspec's in the polling. JENKINS-17348 , JENKINS-27327 , and JENKINS-27351 were also fixed in 2.4.0 and might have had an impact. Any chance you'd be willing to construct a JUnit based test case in the code which would show the problem? 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] [artifactory-plugin] (JENKINS-17593) Artifactory Plugin Uses Incorrect Artifact Names
Title: Message Title Andrew McLaughlin commented on JENKINS-17593 Re: Artifactory Plugin Uses Incorrect Artifact Names Still happening as of July 2015 (1.601). Will check the latest release (1.621) and also try the Advanced Project OPtions to see if I can fix that way. Very annoying that it works differently than build/publish from my desktop. No other comments since 2013?!?! 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] [cpptest-plugin] (JENKINS-29088) Clicking on the “You can define the default values for the trend graph in a separate view.” for “Trend Graph” link results in HTTP ERROR 404.
Title: Message Title SCM/JIRA link daemon commented on JENKINS-29088 Re: Clicking on the “You can define the default values for the trend graph in a separate view.” for “Trend Graph” link results in HTTP ERROR 404. Code changed in jenkins User: Antonio Muñiz Path: src/main/resources/hudson/plugins/cpptest/CpptestPublisher/config.jelly http://jenkins-ci.org/commit/cpptest-plugin/75ab10c9d1e37816da38e45e68389c52744be987 Log: JENKINS-29088 Fix 404 on treds configuration link 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] [cpptest-plugin] (JENKINS-29088) Clicking on the “You can define the default values for the trend graph in a separate view.” for “Trend Graph” link results in HTTP ERROR 404.
Title: Message Title SCM/JIRA link daemon commented on JENKINS-29088 Re: Clicking on the “You can define the default values for the trend graph in a separate view.” for “Trend Graph” link results in HTTP ERROR 404. Code changed in jenkins User: Antonio Muñiz Path: pom.xml src/test/java/hudson/plugins/cpptest/functional/CpptestPublisherTest.java http://jenkins-ci.org/commit/cpptest-plugin/e1fe0fb234cf9e03fe26ed2341742eb4cda13ca0 Log: JENKINS-29088 Add 2 new tests: general publisher run inside a job + check that 404 is solved in trends link 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] [cpptest-plugin] (JENKINS-29088) Clicking on the “You can define the default values for the trend graph in a separate view.” for “Trend Graph” link results in HTTP ERROR 404.
Title: Message Title SCM/JIRA link daemon commented on JENKINS-29088 Re: Clicking on the “You can define the default values for the trend graph in a separate view.” for “Trend Graph” link results in HTTP ERROR 404. Code changed in jenkins User: Gregory Boissinot Path: pom.xml src/main/resources/hudson/plugins/cpptest/CpptestPublisher/config.jelly src/test/java/hudson/plugins/cpptest/functional/CpptestPublisherTest.java http://jenkins-ci.org/commit/cpptest-plugin/65d6348edb48fd973d8fe248aa53a9ef13d8becc Log: Merge pull request #9 from amuniz/trend-config-JENKINS-29088 JENKINS-29088 Fix 404 on trends configuration link Compare: https://github.com/jenkinsci/cpptest-plugin/compare/bca40df150bb...65d6348edb48 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] [other] (JENKINS-29632) Long text in "Configure" elements do not word wrap
Title: Message Title Scott Russell created an issue Jenkins / JENKINS-29632 Long text in "Configure" elements do not word wrap Issue Type: Bug Assignee: Unassigned Attachments: jenkins-css-form.PNG, jenkins-css-table.PNG, jenkins-footer.PNG, jenkins-header.PNG, jenkins-long-textbox.PNG Components: other Created: 24/Jul/15 9:42 PM Environment: Jenkins 1.619, Window 8.1, Ubuntu 12.04, Chrome, Firefox Labels: user-experience gui jenkins configuration Priority: Minor Reporter: Scott Russell On the configuration pages for various projects, when there is a large running paragraph of text (no returns), the text box will continue extending horizontally in the browser until there is a return/new
[JIRA] [extended-choice-parameter-plugin] (JENKINS-29539) NullPointerException on Matrix project
Title: Message Title Jaroslaw Niec commented on JENKINS-29539 Re: NullPointerException on Matrix project 0.50 added all this json kind of configuration and this requires new code that right now fails on latest Jenkins with matrix plugin. And it doesn't matter if previously it was working. I'm not sure but maybe author could implement a workaround so this json would still fail but at least old kind of configuration could work even with buggy matrix plugin. I think this would be the best solution till matrix plugin is fixed. Maybe even adding simple check if build != null could be this workaround. 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-plugin] (JENKINS-29631) Trigger notification broken for non-default refspecs when using parameterized branch
Title: Message Title
Jason Miller updated an issue
Jenkins / JENKINS-29631
Trigger notification broken for non-default refspecs when using parameterized branch
Change By:
Jason Miller
All of our projects have a BRANCH parameter with a default value that's used to fill in the git plugin's branch field.In addition, we have two refspecs for normal jobs - the regular all branches one and one to match tags. Pull request jobs point at Atlassian Stash pull requests ({code}+refs/pull-requests/*/from:refs/heads/origin/pr/*{code}).When Jenkins gets notified to poll for changes, it appears to outright ignore anything that wouldn't be matched by a default refspec - in this case, it won't match tags or pull requests since they aren't present in a standard fetch, despite explicitly setting the refspec. Worse, if both the default refspec and the tags refspec are listed, it won't trigger on *any* changes, reporting that nothing matches the configured refspec, not even master.This worked just fine in the prior version of the git plugin (2.3.5). I've reproduced the problem on both Jenkins 1.584 and 1.609.1. I've tried forcing re-clone and forcing polling with a workspace to no effect.It seems to have something to do with the parameterized branch, as using a concrete branch parameter seemed to make the issue go away.Example polling log for pull request:{ code noformat }[poll] Last Built Revision: Revision aba91cae473c7318a85b31f5271c95f4a8f7c0cc (origin/***) > git rev-parse --is-inside-work-tree # timeout=10Fetching changes from the remote Git repositories > git config remote.origin.url ssh://git@stash.***.com/GROUP/PROJECT.git # timeout=10Fetching upstream changes from ssh://git@stash.***.com/GROUP/PROJECT.git > git --version # timeout=10 > git -c core.askpass=true fetch --tags --progress ssh://git@stash.***.com/GROUP/PROJECT.git +refs/pull-requests/*/from:refs/heads/origin/pr/*Polling for changes inSeen branch in repository origin/**Seen branch in repository origin/**Seen branch in repository origin/**Seen branch in repository origin/masterSeen branch in repository origin/**Seen branch in repository origin/TAGSeen 6 remote branchesDone. Took 0.52 secNo changes{ code noformat }
Add Comment
[JIRA] [git-plugin] (JENKINS-29631) Trigger notification broken for non-default refspecs when using parameterized branch
Title: Message Title
Jason Miller updated an issue
Jenkins / JENKINS-29631
Trigger notification broken for non-default refspecs when using parameterized branch
Change By:
Jason Miller
All of our projects have a BRANCH parameter with a default value that's used to fill in the git plugin's branch field.In addition, we have two refspecs for normal jobs - the regular all branches one and one to match tags. Pull request jobs point at Atlassian Stash pull requests ({code}+refs/pull-requests/*/from:refs/heads/origin/pr/*{code}).When Jenkins gets notified to poll for changes, it appears to outright ignore anything that wouldn't be matched by a default refspec - in this case, it won't match tags or pull requests since they aren't present in a standard fetch, despite explicitly setting the refspec. Worse, if both the default refspec and the tags refspec are listed, it won't trigger on *any* changes, reporting that nothing matches the configured refspec, not even master.This worked just fine in the prior version of the git plugin (2.3.5). I've reproduced the problem on both Jenkins 1.584 and 1.609.1. I've tried forcing re-clone and forcing polling with a workspace to no effect. It seems to have something to do with the parameterized branch, as using a concrete branch parameter seemed to make the issue go away. Example polling log for pull request:{code}[poll] Last Built Revision: Revision aba91cae473c7318a85b31f5271c95f4a8f7c0cc (origin/***) > git rev-parse --is-inside-work-tree # timeout=10Fetching changes from the remote Git repositories > git config remote.origin.url ssh://git@stash.***.com/GROUP/PROJECT.git # timeout=10Fetching upstream changes from ssh://git@stash.***.com/GROUP/PROJECT.git > git --version # timeout=10 > git -c core.askpass=true fetch --tags --progress ssh://git@stash.***.com/GROUP/PROJECT.git +refs/pull-requests/*/from:refs/heads/origin/pr/*Polling for changes inSeen branch in repository origin/**Seen branch in repository origin/**Seen branch in repository origin/**Seen branch in repository origin/masterSeen branch in repository origin/**Seen branch in repository origin/TAGSeen 6 remote branchesDone. Took 0.52 secNo changes{code}
Add Comment
[JIRA] [git-plugin] (JENKINS-29631) Trigger notification broken for non-default refspecs when using parameterized branch
Title: Message Title Jason Miller created an issue Jenkins / JENKINS-29631 Trigger notification broken for non-default refspecs when using parameterized branch Issue Type: Bug Assignee: Nicolas De Loof Components: git-plugin Created: 24/Jul/15 8:56 PM Labels: git plugin Priority: Major Reporter: Jason Miller All of our projects have a BRANCH parameter with a default value that's used to fill in the git plugin's branch field. In addition, we have two refspecs for normal jobs - the regular all branches one and one to match tags. Pull request jobs point at Atlassian Stash pull requests ( +refs/pull-requests/*/from:refs/heads/origin/pr/* ). When Jenkins gets notified to poll for changes, it appears to outright ignore anything that wouldn't be matched by a default refspec - in this case, it won't match tags or pull requests since they aren't present in a standard fetch, despite explicitly setting the refspec. Worse, if both the default refspec and the tags refspec are listed, it won't trigger on any changes, reporting
[JIRA] [job-dsl-plugin] (JENKINS-29630) Add support for Authorize Project plugin
Title: Message Title Ian Tait updated an issue Jenkins / JENKINS-29630 Add support for Authorize Project plugin Change By: Ian Tait Issue Type: Bug New Feature 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] [job-dsl-plugin] (JENKINS-29630) Add support for Authorize Project plugin
Title: Message Title Ian Tait created an issue Jenkins / JENKINS-29630 Add support for Authorize Project plugin Issue Type: Bug Assignee: Daniel Spilker Components: job-dsl-plugin Created: 24/Jul/15 8:51 PM Priority: Minor Reporter: Ian Tait Any chance support will be added for the Authorize Project plugin any time soon? Thanks! Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e
[JIRA] [extended-choice-parameter-plugin] (JENKINS-29539) NullPointerException on Matrix project
Title: Message Title Jonathan Langevin commented on JENKINS-29539 Re: NullPointerException on Matrix project Jaroslaw Niec, so what is the extended choice param plugin doing differently in 0.50, that results in this error in conjunction with Matrix plugin? I'm not doubting that Matrix is at fault in some way, but the extended choice plugin 0.48 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] [job-dsl-plugin] (JENKINS-29629) Build Blocker support does not work as expected
Title: Message Title
Ian Tait created an issue
Jenkins / JENKINS-29629
Build Blocker support does not work as expected
Issue Type:
Bug
Assignee:
Daniel Spilker
Attachments:
$2454F42A972DAD54.jpg
Components:
job-dsl-plugin
Created:
24/Jul/15 8:37 PM
Priority:
Major
Reporter:
Ian Tait
I have a DSL Job that invoke two different DSL scripts, creating and queuing two different jobs to run. The first job (we'll call it Job1) must complete before the second job (we'll call it Job2) begins. To do this, I have chosen to use the Build Blocker plugin , which the Job DSL Plugin supposedly supports. However, when I add the "blockOn('Job1')" line to the second DSL script, it doesn't actually block the second job from running even though the first one is still running.
The image attached is the configuration of the second job that gets created. You can see the "blockOn()" line in the DSL script worked, however it needs further configuration abilities. By default, "disable queue checking" is selected, which basically ignores the blocking rules altogether, making the Build Blocker plugin useless through a DSL script.
[JIRA] [build-timeout-plugin] (JENKINS-29602) Abort wildly verbose job-runs
Title: Message Title Darrel Vuncannon commented on JENKINS-29602 Re: Abort wildly verbose job-runs I'll consider Logfilesizechecker Plugin. It troubles me some that it hasn't been widely adopted by the Jenkins community, judging by the low number of installations. I know build-timeout plugin already monitors writing to the console – that's in order to abort a build that seems stuck. Admittedly, my request would enhance the plugin from "timeout" to "build intervention". Thanks for pointing me to the other 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] [extended-choice-parameter-plugin] (JENKINS-29539) NullPointerException on Matrix project
Title: Message Title Jaroslaw Niec commented on JENKINS-29539 Re: NullPointerException on Matrix project I've debugged this issue and it could be caused by matrix project plugin. Matrix project plugin passed incorrect parameter and this plugin fails. I've raised new issue agains matrix project plugin https://issues.jenkins-ci.org/browse/JENKINS-29628 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] [matrix-project-plugin] (JENKINS-29628) createVariableResolver() is called with null as a parameter
Title: Message Title Jaroslaw Niec created an issue Jenkins / JENKINS-29628 createVariableResolver() is called with null as a parameter Issue Type: Bug Assignee: Kohsuke Kawaguchi Components: matrix-project-plugin Created: 24/Jul/15 8:19 PM Priority: Critical Reporter: Jaroslaw Niec createVariableResolver() method in FilterScript.java (97) is called with null as a parameter instead of build instance. final String value = pv.createVariableResolver(null).resolve(name); This is against specification http://javadoc.jenkins-ci.org/hudson/model/ParameterValue.html#createVariableResolver(hudson.model.AbstractBuild) where we can read that: build - The build for which this parameter is being used. Never null. This null is causing other plugins to fail. For example: https://issues.jenkins-ci.org/browse/JENKINS-29539 Add Comment
[JIRA] [docker-build-publish-plugin] (JENKINS-29627) JSONException: null object when interacting with Docker Hub Registry
Title: Message Title Matt McClean created an issue Jenkins / JENKINS-29627 JSONException: null object when interacting with Docker Hub Registry Issue Type: Bug Assignee: Carlos Sanchez Components: docker-build-publish-plugin Created: 24/Jul/15 7:56 PM Environment: Jenkins docker image running version. 1.609.1 Running Java version OpenJDK Runtime Environment 1.8.0_45-internal-b14 Running plugins: Docker Commons Plugin v1.1 Docker Build and Publish plugin v1.0 Labels: plugin Priority: Blocker Reporter: Matt McClean I am trying to build and publish a Docker image using the "docker-build-publish-plugin" module and getting the stack trace error below. I am using the Jenkins credential module to store the Docker Hub credentials. I am have configured the Docker build step with the default setting of the Docker Hub registry: https://index.docker.io/v1/ Started by an SCM ch
[JIRA] [testng-plugin] (JENKINS-20985) TestNG plugin should has a possibility to use thresholds for failed tests
Title: Message Title Chris Everling commented on JENKINS-20985 Re: TestNG plugin should has a possibility to use thresholds for failed tests During a company hackathon, a team of co-workers and myself worked on this ticket (as well as others). Here is the PR link: https://github.com/jenkinsci/testng-plugin-plugin/pull/20/files 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] [htmlpublisher-plugin] (JENKINS-29626) Binary compatibility loss in htmlpublisher-1.4
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-29626 Binary compatibility loss in htmlpublisher-1.4 Change By: SCM/JIRA link daemon Status: In Progress 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] [htmlpublisher-plugin] (JENKINS-29626) Binary compatibility loss in htmlpublisher-1.4
Title: Message Title SCM/JIRA link daemon commented on JENKINS-29626 Re: Binary compatibility loss in htmlpublisher-1.4 Code changed in jenkins User: Oleg Nenashev Path: src/main/java/htmlpublisher/HtmlPublisherTarget.java http://jenkins-ci.org/commit/htmlpublisher-plugin/99dde68428b021af356a69964431e4e33ff1c62d Log: [FIXED JENKINS-29626] - Restore the removed constructor, add Javadoc 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] [cobertura-plugin] (JENKINS-26823) With concurrent builds, Cobertura blocks later builds from finishing first
Title: Message Title chris meyers commented on JENKINS-26823 Re: With concurrent builds, Cobertura blocks later builds from finishing first I'm experience this as well 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] [htmlpublisher-plugin] (JENKINS-29626) Binary compatibility loss in htmlpublisher-1.4
Title: Message Title Oleg Nenashev created an issue Jenkins / JENKINS-29626 Binary compatibility loss in htmlpublisher-1.4 Issue Type: Bug Assignee: mcrooney Components: htmlpublisher-plugin Created: 24/Jul/15 7:18 PM Environment: htmlpublisher-1.4 Priority: Minor Reporter: Oleg Nenashev Caused by https://github.com/jenkinsci/htmlpublisher-plugin/commit/0e328854d2a625b550a5429b0e2c2233ffcd1d2c It may affect installations, which generate HTMLPublishers from Groovy scripts. Changing of a public constructor is dangerous. I'll create an issue & pull request Add Comment
[JIRA] [htmlpublisher-plugin] (JENKINS-29626) Binary compatibility loss in htmlpublisher-1.4
Title: Message Title Oleg Nenashev assigned an issue to Oleg Nenashev Jenkins / JENKINS-29626 Binary compatibility loss in htmlpublisher-1.4 Change By: Oleg Nenashev Assignee: mcrooney Oleg Nenashev 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] [htmlpublisher-plugin] (JENKINS-29626) Binary compatibility loss in htmlpublisher-1.4
Title: Message Title Oleg Nenashev started work on JENKINS-29626 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] [git-client-plugin] (JENKINS-26026) Submodules not supported with JGit
Title: Message Title Jacob Keller commented on JENKINS-26026 Re: Submodules not supported with JGit Note that JGit implementation (correctly) does not implement setupSubmoduleUrls and friends. These interfaces were ported over from the original git-plugin implementation for the CLI implementation. I think the correct thing to do is figure out how to avoid needing these, as it seems incredibly weird to attempt this weird "automatic" detection hueristic for the submodule URL.. I think that shouldn't be done at all by the git-client plugin, and probably shouldn't be done in the git-plugin proper either. That sort of magic is really weird, and after digging, I can't figure out what it was originally intended to do. 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-29604) git-client CLI implementation does not propogate username
Title: Message Title Jacob Keller commented on JENKINS-29604 Re: git-client CLI implementation does not propogate username Note. The linked pull request apparently only resolves one issue, as submodules do not seem to support the Credentials. The resolved issue is the case for SSH urls which don't provide the username. However, the underlying submodule issue is not resolved, as they don't appear to take git credentials correctly. 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-29604) git-client CLI implementation does not propogate username
Title: Message Title Jacob Keller commented on JENKINS-29604 Re: git-client CLI implementation does not propogate username See https://github.com/jenkinsci/git-client-plugin/pull/176 for a pull request that fixes the 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] [matrix-project-plugin] (JENKINS-29625) Matrix job updates don't see latest commit
Title: Message Title Matt Kulka created an issue Jenkins / JENKINS-29625 Matrix job updates don't see latest commit Issue Type: Bug Assignee: Kohsuke Kawaguchi Components: matrix-project-plugin Created: 24/Jul/15 5:41 PM Environment: awt.toolkit sun.awt.X11.XToolkit executable-war /usr/share/jenkins/jenkins.war file.encoding UTF-8 file.encoding.pkg sun.io file.separator / hudson.diyChunking true java.awt.graphicsenv sun.awt.X11GraphicsEnvironment java.awt.headless true java.awt.printerjob sun.print.PSPrinterJob java.class.path /usr/share/jenkins/jenkins.war java.class.version 51.0 java.endorsed.dirs /usr/lib/jvm/java-7-openjdk-amd64/jre/lib/endorsed java.ext.dirs /usr/lib/jvm/java-7-openjdk-amd64/jre/lib/ext:/usr/java/packages/lib/ext java.home /usr/lib/jvm/java-7-openjdk-amd64/jre java.io.tmpdir /tmp java.library.path /usr/java/packages/lib/amd64:/usr/lib/x86_64-linux-gnu/jni:/lib/x86_64-linux-gnu:/usr/lib/x86_64-linux-gnu:/usr/lib/jni:/lib:/usr/lib java.runtime.name OpenJDK Runtime Environment java.runtime.version 1.7.0_79-b14 java.specification.name Java Platform API Specification java.specification.vendor Oracle Corporation java.specification.version 1.7 java.vendor Oracle Corporation java.vendor.url http://java.oracle.com/ java.vendor.url.bug http://bugreport.sun.com/bugreport/ java.version 1.7.0_79 java.vm.info mixed mode java.vm.name OpenJDK 64-Bit Server VM java.vm.specification.name Java Virtual Machine Specification java.vm.specification.vendor Oracle Corporation java.vm.specification.version 1.7 java.vm.vendor Oracle Corporation java.vm.version 24.79-b02 jna.platform.library.path /usr/lib/x86_64-linux-gnu:/lib/x86_64-linux-gnu:/lib64:/usr/lib:/lib jnidispatch.path /tmp/jna--1712433994/jna227542207951697946.tmp line.separator mail.smtp.sendpartial true mail.smtps.sendpartial true os.arch amd64 os.name Linux os.version 3.16.0-39-generic path.separator : sun.arch.data.model 64 sun.boot.class.path /usr/lib/jvm/java-7-openjdk-amd64/jre/lib/resources.jar:/usr/lib/jvm/java-7-openjdk-amd64/jre/lib/rt.jar:/usr/lib/jvm/java-7-openjdk-amd64/jre/lib/sunrsasign.jar:/usr/lib/jvm/java-7-openjdk-amd64/jre/lib/jsse.jar:/usr/lib/jvm/java-7-openjdk-amd64/jre/lib/jce.jar:/usr/lib/jvm/java-7-openjdk-amd64/jre/lib/charsets.jar:/usr/lib/jvm/java-7-openjdk-amd64/jre/lib/rhino.jar:/usr/lib/jvm/jav
[JIRA] [maven-plugin] (JENKINS-23846) Jenkins Maven support doesn't handle version ranges in parent definitions
Title: Message Title Justin Wesley commented on JENKINS-23846 Re: Jenkins Maven support doesn't handle version ranges in parent definitions I am trying to build and I get maven-plugin\target\generated-sources\localizer\hudson\maven\Messages.java:[17,27] error: unmappable character for encoding UTF-8 from the generated classes. 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-29618) Suggested update fails to download resource
Title: Message Title Andrew Lamonica commented on JENKINS-29618 Re: Suggested update fails to download resource I'm having the same issue. I'm assuming there is a workaround or at least a way to get an older version. Anyone have any ideas? 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 Rusty Gerard closed an issue as Fixed Jenkins / JENKINS-29339 Pushing logs to redis using LogStash plugin is serialised Change By: Rusty Gerard 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] [logstash-plugin] (JENKINS-29202) logstash 1.1.0 tries to create a queue which already exists on ReddisMQ server - and fails
Title: Message Title Rusty Gerard closed an issue as Fixed Jenkins / JENKINS-29202 logstash 1.1.0 tries to create a queue which already exists on ReddisMQ server - and fails Change By: Rusty Gerard 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] [maven-plugin] (JENKINS-23846) Jenkins Maven support doesn't handle version ranges in parent definitions
Title: Message Title Christophe Lallement commented on JENKINS-23846 Re: Jenkins Maven support doesn't handle version ranges in parent definitions Hi I try to fork this plugins and update mvn dependencies but unfortunately it' s not a trivial task There is is lot of dependencies on "legacy" jenkins maven libs that are almost deprecated. C. 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] [cloudbees-disk-usage-simple-plugin] (JENKINS-29516) Track usage of `java.io.tmpdir`
Title: Message Title Arnaud Héritier commented on JENKINS-29516 Re: Track usage of `java.io.tmpdir` Pr done https://github.com/jenkinsci/cloudbees-disk-usage-simple/pull/3 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] [cloudbees-disk-usage-simple-plugin] (JENKINS-29516) Track usage of `java.io.tmpdir`
Title: Message Title Arnaud Héritier started work on JENKINS-29516 Change By: Arnaud Héritier 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] [git-client-plugin] (JENKINS-29604) git-client CLI implementation does not propogate username
Title: Message Title Jacob Keller updated an issue Jenkins / JENKINS-29604 git-client CLI implementation does not propogate username Change By: Jacob Keller Summary: git plugin submodule -client CLI implementation does not propogate credentials and username 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-29604) git-client CLI implementation does not propogate username
Title: Message Title Jacob Keller updated an issue Jenkins / JENKINS-29604 git-client CLI implementation does not propogate username Change By: Jacob Keller Component/s: git-client-plugin Component/s: git-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] [active-directory-plugin] (JENKINS-28576) WebSphere Crashes on Jenkins 1.612 and higher supporting Java 7 changes
Title: Message Title Bruce Coveny commented on JENKINS-28576 Re: WebSphere Crashes on Jenkins 1.612 and higher supporting Java 7 changes Removing the active directory settings made the server stable and not crash. It took some time to get the configuration setup for the LDAP plugin. We have successfully switched to the LDAP Plugin and the server is up and stable under JDK 1.7. 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-plugin] (JENKINS-12545) Jenkins should build all tracked branches that have changed when triggered by Github
Title: Message Title Stepan Mazurov commented on JENKINS-12545 Re: Jenkins should build all tracked branches that have changed when triggered by Github Mark Waite I effectively did same repro steps as you, with 2 changes: 1. I did not have any post-receive hooks set up, simply SCM poll every minute 2. The "origin" repo was on github Does it work correctly for you if you remove post-receive hook and simply poll? Kanstantsin Shautsou is there anything else I could do to help fix this? Its quite a big issue that I would love to resolve. Effectively all git-flow type workflows are affected. 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] [_test] (JENKINS-29624) Java heap space when using maven.plugin.surefire
Title: Message Title Oleg Nenashev commented on JENKINS-29624 Re: Java heap space when using maven.plugin.surefire I don't see a heap dump 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-plugin] (JENKINS-29604) git plugin submodule does not propogate credentials and username
Title: Message Title Jacob Keller assigned an issue to Jacob Keller Jenkins / JENKINS-29604 git plugin submodule does not propogate credentials and username Change By: Jacob Keller Assignee: Manoj Kumar Jacob Keller 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-plugin] (JENKINS-29604) git plugin submodule does not propogate credentials and username
Title: Message Title Jacob Keller commented on JENKINS-29604 Re: git plugin submodule does not propogate credentials and username I found the issue in the CLI Git client implementation. The code correctly sets up the SSH key file and an http passphrase, but does not correctly store the username and forward it. Thus, as long as the local username matches the remote username things work as expected, but in the case where local username does not match, it does not get correctly setup. I have prepared a pull request on git-client-plugin which I will submit shortly to resolve this. 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] [artifact-promotion-plugin] (JENKINS-29623) Add classifier support for ArtifactPromotionPlugin
Title: Message Title Mate Farkas commented on JENKINS-29623 Re: Add classifier support for ArtifactPromotionPlugin https://github.com/farkasmate/artifact-promotion-plugin/tree/feature/JENKINS-29623-Add_classifier_support_for_ArtifactPromotionPlugin 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] [xtrigger-plugin] (JENKINS-29610) Scheduling skipped when there is no restriction for label
Title: Message Title Oliver Gondža assigned an issue to Oliver Gondža Jenkins / JENKINS-29610 Scheduling skipped when there is no restriction for label Change By: Oliver Gondža Assignee: Gregory Boissinot Oliver Gondža 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] [_test] (JENKINS-29624) Java heap space when using maven.plugin.surefire
Title: Message Title fadi hussein updated an issue Jenkins / JENKINS-29624 Java heap space when using maven.plugin.surefire Change By: fadi hussein the error that appear in consolejava.lang.OutOfMemoryError: Java heap space2015-07-24 18:11:16.330 Dumping heap to /temp/dump.hprof ...2015-07-24 18:11:19.200 Heap dump file created [473449760 bytes in 2.848 secs]2015-07-24 18:11:19.202 Exception in thread "ThreadedStreamConsumer" java.lang.OutOfMemoryError: Java heap space2015-07-24 18:11:19.202 at java.util.Arrays.copyOf(Arrays.java:2367)2015-07-24 18:11:19.202 at java.lang.AbstractStringBuilder.expandCapacity(AbstractStringBuilder.java:130)2015-07-24 18:11:19.202 at java.lang.AbstractStringBuilder.ensureCapacityInternal(AbstractStringBuilder.java:114)2015-07-24 18:11:19.202 at java.lang.AbstractStringBuilder.append(AbstractStringBuilder.java:415)2015-07-24 18:11:19.202 at java.lang.StringBuilder.append(StringBuilder.java:132)2015-07-24 18:11:19.202 at org.apache.maven.plugin.surefire.report.TestSetRunListener.getAsString(TestSetRunListener.java:223)2015-07-24 18:11:19.202 at org.apache.maven.plugin.surefire.report.TestSetRunListener.wrap(TestSetRunListener.java:230)2015-07-24 18:11:19.202 at org.apache.maven.plugin.surefire.report.TestSetRunListener.testSucceeded(TestSetRunListener.java:161)2015-07-24 18:11:19.202 at org.apache.maven.plugin.surefire.booterclient.output.ForkClient.consumeLine(ForkClient.java:100)2015-07-24 18:11:19.202 at org.apache.maven.plugin.surefire.booterclient.output.ThreadedStreamConsumer$Pumper.run(ThreadedStreamConsumer.java:67)2015-07-24 18:11:19.202 at java.lang.Thread.run(Thread.java:745)2015-07-24 18:11:19.203 2015-07-24 18:11:19.203 Results :attached hep heap dump Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [_test] (JENKINS-29624) Java heap space when using maven.plugin.surefire
Title: Message Title fadi hussein created an issue Jenkins / JENKINS-29624 Java heap space when using maven.plugin.surefire Issue Type: Bug Assignee: Oleg Nenashev Components: _test Created: 24/Jul/15 5:06 PM Priority: Blocker Reporter: fadi hussein the error that appear in console java.lang.OutOfMemoryError: Java heap space 2015-07-24 18:11:16.330 Dumping heap to /temp/dump.hprof ... 2015-07-24 18:11:19.200 Heap dump file created [473449760 bytes in 2.848 secs] 2015-07-24 18:11:19.202 Exception in thread "ThreadedStreamConsumer" java.lang.OutOfMemoryError: Java heap space 2015-07-24 18:11:19.202 at java.util.Arrays.copyOf(Arrays.java:2367) 2015-07-24 18:11:19.202 at java.lang.AbstractStringBuilder.expandCapacity(AbstractStringBuilder.java:130) 2015-07-24 18:11:19.202 at java.lang.AbstractStringBuilder.ensureCapacityInternal(AbstractStringBuilder.java:114) 2015-07-24 18:11:19.202 at java.lang.AbstractStringBuilder.append(AbstractStringBuilder.java:415) 2015-07-24 18:11:19.202 at java.lang.StringBuilder.append(StringBuilder.java:132) 2015-07-24 18:11:19.202 at org.apache.maven.plugin.surefire.report.TestSetRunListener.getAsString(TestSetRunListener.java:223) 2015-07-24 18:11:19.202 at org.apache.maven.plugin.surefire.report.TestSetRunListener.wrap(TestSetRunListener.java:230) 2015-07-24 18:11:19.202 at org.apache.maven.plugin.surefire.report.TestSetRunListener.testSucceeded(TestSetRunListener.java:161) 2015-07-24 18:11:19.202 at org.apache.maven.plugin.surefire.booterclient.output.ForkClient.consumeLine(ForkClient.java:100) 2015-07-24 18:11:19.202 at org.apache.maven.plugin.surefire.booterclient.output.ThreadedStreamConsumer$Pumper.run(ThreadedStreamConsumer.java:67
[JIRA] [github-oauth-plugin] (JENKINS-17539) Swarm clients fail to connect if GitHub for authentication
Title: Message Title
Stepan Mazurov edited a comment on JENKINS-17539
Re: Swarm clients fail to connect if GitHub for authentication
{quote}Stepan Mazurov how are you connecting with the swarm plugin? Are you using the GitHub personal access token?{quote}Yes.{quote}Another thing you could try is just setting se-jenkins as an admin.{quote}This indeed did work, but was too permissive for my taste. {quote}Also, contributions are welcome for slave users setting.{quote}I took a look at the code, and to implement it in a way I want (add a field to specify slave users to commiter strategy settings), it appears it would require to modify a lot of code as it would be another discrete strategy permission . I do not feel like the added convince over Matrix strategy is worth the tech debt of adding such functionality. I can now confirm that, with matrix strategy (or commiter strategy with bot account having admin access), a dedicated github "bot" account with a _personal access token_ allows slaves to correctly connect, register themselves and execute tasks. I believe this issue can be considered resolved.
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-17539) Swarm clients fail to connect if GitHub for authentication
Title: Message Title Stepan Mazurov commented on JENKINS-17539 Re: Swarm clients fail to connect if GitHub for authentication Stepan Mazurov how are you connecting with the swarm plugin? Are you using the GitHub personal access token? Yes. Another thing you could try is just setting se-jenkins as an admin. This indeed did work, but was too permissive for my taste. Also, contributions are welcome for slave users setting. I took a look at the code, and to implement it in a way I want (add a field to specify slave users to commiter strategy settings), it appears it would require to modify a lot of code as it would be another discrete strategy. I do not feel like the added convince over Matrix strategy is worth the tech debt of adding such functionality. I can now confirm that, with matrix strategy (or commiter strategy with bot account having admin access), a dedicated github "bot" account with a personal access token allows slaves to correctly connect, register themselves and execute tasks. I believe this issue can be considered resolved. 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] [artifact-promotion-plugin] (JENKINS-29623) Add classifier support for ArtifactPromotionPlugin
Title: Message Title Mate Farkas created an issue Jenkins / JENKINS-29623 Add classifier support for ArtifactPromotionPlugin Issue Type: New Feature Assignee: Mate Farkas Components: artifact-promotion-plugin Created: 24/Jul/15 4:51 PM Environment: Jenkins: 1.595 Nexus OSS: 2.11.3-01 Priority: Minor Reporter: Mate Farkas The ArtifactPromotionPlugin currently only supports promoting of the primary artifact. To handle secondary artifacts the 'classifier' coordinate needs to be specified. Add Comment
[JIRA] [maven-plugin] (JENKINS-29622) Maven S3 Wagon support
Title: Message Title martino tu updated an issue Jenkins / JENKINS-29622 Maven S3 Wagon support Change By: martino tu Hi all,First I want to thanks you for the amazing work you are doing!I have an improvment request, can we add S3 support to maven-plug in?There is already a wagon for it at : https://github.com/jcaddel/maven-s3-wagonand I belieave is just a matther of adding this extencion in to your plugin.With this we could use the Jenkins artifact publisher with an s3:// I tried already to use a s3 from Jenkins and RedeployPublisher but with the following error:ERROR: Failed to deploy artifacts/metadata: Cannot access s3://my.repo.com/maven2 with type default using the available connector factories: WagonRepositoryConnectorFactoryThanks guys for your help,Martino 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] [maven-plugin] (JENKINS-29622) Maven S3 Wagon support
Title: Message Title martino tu created an issue Jenkins / JENKINS-29622 Maven S3 Wagon support Issue Type: Improvement Assignee: Unassigned Components: maven-plugin Created: 24/Jul/15 4:42 PM Priority: Minor Reporter: martino tu Hi all, First I want to thanks you for the amazing work you are doing! I have an improvment request, can we add S3 support to maven-plug in? There is already a wagon for it at https://github.com/jcaddel/maven-s3-wagon and I belieave is just a matther of adding this extencion in to your plugin. With this we could use the artifact publisher with an s3:// I tried already but with the following error: ERROR: Failed to deploy artifacts/metadata: Cannot access s3://my.repo.com/maven2 with type default using the available connector factories: WagonRepositoryConnectorFactory Thanks guys for your help, Martino
[JIRA] [envinject-plugin] (JENKINS-29415) Injecting Environment variable failing after 1.609.1 LTS upgrade
Title: Message Title Vinoth Kumar Pandian updated an issue Jenkins / JENKINS-29415 Injecting Environment variable failing after 1.609.1 LTS upgrade Because of this issue, were forced to use last LTS version 1.596. And few projects requires upgrade to 1.609 or later. So we are stuck in between, please help to get rid of this issue Change By: Vinoth Kumar Pandian Priority: Minor Major After upgrading Jenkins to the latest LTS version 1.609.1, Jenkins fails to inject environment variables by Groovy script failed with below error. [EnvInject] - [ERROR] - [EnvInject] - [ERROR] - Problems occurs on injecting env vars as a build wrap: null 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+u
[JIRA] [maven-plugin] (JENKINS-27372) Failed to getClass for org.apache.maven.plugin.source.SourceJarMojo
Title: Message Title Charles Chan commented on JENKINS-27372 Re: Failed to getClass for org.apache.maven.plugin.source.SourceJarMojo I agree with Alexander Kriegisch. If this is a issue with the Maven project plugin, I would like it to be fixed as well. There are too many Maven projects out there to update manually. Also, for people who pays attention to these things, warning message are a red flag and may indicate a potential 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] [docker-custom-build-environment-plugin] (JENKINS-29410) Compatibility with Sonar plugin (and possibly other auto installed software)
Title: Message Title Michael Süß commented on JENKINS-29410 Re: Compatibility with Sonar plugin (and possibly other auto installed software) It is not really practical to have separate images for all different combinations of build tools, package managers and runtime environments. We currently have several hundred build jobs of different projects on our build environment, that have different requirements on particular tool versions. We want to use the auto-installer of Jenkins where possible and only have job or project specific images on special cases (there will still be a couple of them). Our main intention of using this plugin is to provide an isolated build environment for each build job and still be able to solve the issue of providing project specific environment adjustments on our build nodes. Therefore I would like to see a higher priority on 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] [maven-plugin] (JENKINS-23846) Jenkins Maven support doesn't handle version ranges in parent definitions
Title: Message Title Justin Wesley updated an issue Jenkins / JENKINS-23846 Jenkins Maven support doesn't handle version ranges in parent definitions Change By: Justin Wesley Priority: Minor Critical 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-29409) Add shared Ivy cache
Title: Message Title Michael Süß commented on JENKINS-29409 Re: Add shared Ivy cache The same applies for Maven, NPM, Rubygems and so on 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-29621) EnvInject Plugin is only working to a limited extent in combination with the docker build environment
Title: Message Title Michael Süß created an issue Jenkins / JENKINS-29621 EnvInject Plugin is only working to a limited extent in combination with the docker build environment Issue Type: Bug Assignee: Nicolas De Loof Components: docker-custom-build-environment-plugin Created: 24/Jul/15 3:33 PM Priority: Major Reporter: Michael Süß When using the env inject plugin, only those properties are injected that are specified before the scm checkout. Properties that are set after the scm checkout aren't available during the build execution within the docker container. Add Comment
[JIRA] [workflow-plugin] (JENKINS-29346) Input approval should only be granted to users with job build permission
Title: Message Title Jesse Glick resolved as Duplicate Not exactly a duplicate, but an implementation of JENKINS-27134 would cover it, so marking it that way. Jenkins / JENKINS-29346 Input approval should only be granted to users with job build permission Change By: Jesse Glick Status: Open Resolved 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] [script-security-plugin] (JENKINS-29541) workflow scripts can't use String.substring(int,int)
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-29541 workflow scripts can't use String.substring(int,int) Change By: Jesse Glick Component/s: workflow-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] [script-security-plugin] (JENKINS-29541) workflow scripts can't use String.substring(int,int)
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-29541 workflow scripts can't use String.substring(int,int) Change By: Jesse Glick Labels: workflow 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-plugin] (JENKINS-29604) git plugin submodule does not propogate credentials and username
Title: Message Title Jacob Keller edited a comment on JENKINS-29604 Re: git plugin submodule does not propogate credentials and username Is there something special I need to do for credentials that is git specific? I'm already using the Jenkins credentials for the ssh keys. It propogates the SSH key itself just fine, but I don't think the username gets propagated... Edit: this occurs with submodules specifically, as I am able to pass user@ to the ssh URL when I format it ie:ssh://user@host:port/path/to/repoRegards,Jake 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-plugin] (JENKINS-29604) git plugin submodule does not propogate credentials and username
Title: Message Title Jacob Keller commented on JENKINS-29604 Re: git plugin submodule does not propogate credentials and username Is there something special I need to do for credentials that is git specific? I'm already using the Jenkins credentials for the ssh keys. It propogates the SSH key itself just fine, but I don't think the username gets propagated... 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-pipeline-plugin] (JENKINS-29620) Incompatible with latest jQuery plugin
Title: Message Title Clayton O'Neill created an issue Jenkins / JENKINS-29620 Incompatible with latest jQuery plugin Issue Type: Bug Assignee: Unassigned Components: build-pipeline-plugin Created: 24/Jul/15 3:18 PM Environment: Jenkins ver. 1.609.1 LTS Priority: Minor Reporter: Clayton O'Neill Upgrading the jquery plugin from 1.7.2-1 to 1.11.2-0 broke the "Run" and console window buttons. Downgrading restored that functionality. Add Comment
[JIRA] [docker-custom-build-environment-plugin] (JENKINS-29619) Option to expose container ports via port mapping
Title: Message Title Michael Süß created an issue Jenkins / JENKINS-29619 Option to expose container ports via port mapping Issue Type: New Feature Assignee: Nicolas De Loof Components: docker-custom-build-environment-plugin Created: 24/Jul/15 2:39 PM Priority: Minor Reporter: Michael Süß For integration testing, it might be necessary for the tested system to be reachable by an external process (for example to receive asynchronous responses). Therefore it should be possible to map ports that are exposed by the container to a specific host port. At the moment I don't know of a specific need, but I'm quite sure, that this case will occur (we are hosting a centralized build environment for a couple of projects within our company) Add Comment
[JIRA] [build-token-root-plugin] (JENKINS-22849) Send 201 (Created) response with a Location header pointing to the queue item once job submitted
Title: Message Title Jesse Glick started work on JENKINS-22849 Change By: Jesse Glick 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] [build-token-root-plugin] (JENKINS-22849) Send 201 (Created) response with a Location header pointing to the queue item once job submitted
Title: Message Title Jesse Glick assigned an issue to Yoann Dubreuil Jenkins / JENKINS-22849 Send 201 (Created) response with a Location header pointing to the queue item once job submitted Change By: Jesse Glick Assignee: Jesse Glick Yoann Dubreuil 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-29615) Return queue item location of scheduled build
Title: Message Title Jesse Glick resolved as Duplicate Jenkins / JENKINS-29615 Return queue item location of scheduled build Change By: Jesse Glick Status: Open Resolved 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] [multijob-plugin] (JENKINS-25675) Provide environment variables like Parameterized Trigger Plugin
Title: Message Title Sebastian Schuberth commented on JENKINS-25675 Re: Provide environment variables like Parameterized Trigger Plugin Well, we'd need to have these variables per phase, so that the job containing the multijob build step can know which builds were triggered in the phase jobs in order to be able to copy artifacts form these builds. 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] [workflow-plugin] (JENKINS-29571) Unreadable data after renaming a Workflow job
Title: Message Title SCM/JIRA link daemon commented on JENKINS-29571 Re: Unreadable data after renaming a Workflow job Code changed in jenkins User: Jesse Glick Path: CHANGES.md aggregator/src/test/java/org/jenkinsci/plugins/workflow/WorkflowRunTest.java api/src/main/java/org/jenkinsci/plugins/workflow/flow/FlowExecution.java cps/src/main/java/org/jenkinsci/plugins/workflow/cps/CpsFlowExecution.java cps/src/test/java/org/jenkinsci/plugins/workflow/cps/CpsFlowDefinition2Test.java job/src/main/java/org/jenkinsci/plugins/workflow/job/WorkflowRun.java http://jenkins-ci.org/commit/workflow-plugin/a007b88c1fe653ac9fb900bf41bfbeffd9808d8c Log: Merge pull request #157 from jglick/rename-JENKINS-29571 JENKINS-29571 Handle build records after rename Compare: https://github.com/jenkinsci/workflow-plugin/compare/06d82c91d88f...a007b88c1fe6 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] [workflow-plugin] (JENKINS-29571) Unreadable data after renaming a Workflow job
Title: Message Title SCM/JIRA link daemon commented on JENKINS-29571 Re: Unreadable data after renaming a Workflow job Code changed in jenkins User: Jesse Glick Path: CHANGES.md aggregator/src/test/java/org/jenkinsci/plugins/workflow/WorkflowRunTest.java api/src/main/java/org/jenkinsci/plugins/workflow/flow/FlowExecution.java cps/src/main/java/org/jenkinsci/plugins/workflow/cps/CpsFlowExecution.java cps/src/test/java/org/jenkinsci/plugins/workflow/cps/CpsFlowDefinition2Test.java job/src/main/java/org/jenkinsci/plugins/workflow/job/WorkflowRun.java http://jenkins-ci.org/commit/workflow-plugin/b7014e66b8b064794efea6c78f35160c5250cc2e Log: [FIXED JENKINS-29571] Make CpsFlowExecution.owner transient (JENKINS-27704) to avoid problems after renames/moves. 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] [workflow-plugin] (JENKINS-27704) Clean up build record storage
Title: Message Title SCM/JIRA link daemon commented on JENKINS-27704 Re: Clean up build record storage Code changed in jenkins User: Jesse Glick Path: CHANGES.md aggregator/src/test/java/org/jenkinsci/plugins/workflow/WorkflowRunTest.java api/src/main/java/org/jenkinsci/plugins/workflow/flow/FlowExecution.java cps/src/main/java/org/jenkinsci/plugins/workflow/cps/CpsFlowExecution.java cps/src/test/java/org/jenkinsci/plugins/workflow/cps/CpsFlowDefinition2Test.java job/src/main/java/org/jenkinsci/plugins/workflow/job/WorkflowRun.java http://jenkins-ci.org/commit/workflow-plugin/b7014e66b8b064794efea6c78f35160c5250cc2e Log: [FIXED JENKINS-29571] Make CpsFlowExecution.owner transient (JENKINS-27704) to avoid problems after renames/moves. 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] [workflow-plugin] (JENKINS-29571) Unreadable data after renaming a Workflow job
Title: Message Title SCM/JIRA link daemon commented on JENKINS-29571 Re: Unreadable data after renaming a Workflow job Code changed in jenkins User: Jesse Glick Path: aggregator/src/test/java/org/jenkinsci/plugins/workflow/WorkflowRunTest.java http://jenkins-ci.org/commit/workflow-plugin/9d087ca7fcb3e6f186d3f44f289bae8861dedad7 Log: JENKINS-29571 reproduced in test and confirmed to depend on part of JENKINS-27704. 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.
