[JIRA] [git-plugin] (JENKINS-34878) jenkins failed to connect to Git repository
Title: Message Title Munira Presswala reopened an issue hi Mark , Reopening this issue , because i have asked you some questions ,and its not resolved the case . So Please assist me further . Thanks and Regards Munira Jenkins / JENKINS-34878 jenkins failed to connect to Git repository Change By: Munira Presswala Resolution: Not A Defect Status: Resolved Reopened Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-34878) jenkins failed to connect to Git repository
Title: Message Title Munira Presswala commented on JENKINS-34878 Re: jenkins failed to connect to Git repository Hi Mark , I have already check my JENKINS_HOME is correctly set . Could you Please suggest me , what should be ideal location of Git program. do Jenkins require Git to be installed Separately , As per my knowledge I didnt install Git previously , Git used to install in Jenkins automatically .So , why its not happening Now . could you Please suggest the above case. 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-34878) jenkins failed to connect to Git repository
Title: Message Title Munira Presswala commented on JENKINS-34878 Re: jenkins failed to connect to Git repository Hi Mark , Thank you for providing quick resolution . Could you Please help me in knowing what could be the correct reason behind getting this exception. Is that git plugin upgraded automatically or there is some change in Folder structure of Git . Also could you Please explain me , how Jenkins works when I push a small change to Git , Thanks for all your answers in advanced 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-changelog-plugin] (JENKINS-34886) Jenkins Git Error Invalid ID
Title: Message Title Mark Waite resolved as Not A Defect Since Nadine Sander says: I changed nothing in the jenkins! I found out that the error depends on the new gitlab update with the security updates.. Now i updated all Git Plugins, but the error still exists I think this is not related to Jenkins or the plugins at all. Nothing changed in Jenkins, something changed in gitlab, and the error happened. Jenkins / JENKINS-34886 Jenkins Git Error Invalid ID Change By: Mark Waite Status: Open Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] [git-plugin] (JENKINS-34811) Environment Variables not being created
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-34811 Environment Variables not being created Change By: Mark Waite Assignee: Mark Waite 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-34775) Broken jobs after upgrade to 1.651.2 security update
Title: Message Title Michael Haberler commented on JENKINS-34775 Re: Broken jobs after upgrade to 1.651.2 security update Thanks! using this in /etc/default/jenkins on debian jessie did the trick: JAVA_ARGS="-Djava.awt.headless=true -Dhudson.model.User.SECURITY_243_FULL_DEFENSE=false -Dhudson.model.ParametersAction.keepUndefinedParameters=true" I'd appreciate a hint on how to continue without this (somewhat sledgehammer) measure ? 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] [dashboard-view-plugin] (JENKINS-22016) TAP test results of matrix configuration project do not show in main project overview and dashboard
Title: Message Title Bruno P. Kinoshita resolved as Fixed Marking as fixed, scheduled for 1.25 release Jenkins / JENKINS-22016 TAP test results of matrix configuration project do not show in main project overview and dashboard Change By: Bruno P. Kinoshita 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] [dashboard-view-plugin] (JENKINS-22016) TAP test results of matrix configuration project do not show in main project overview and dashboard
Title: Message Title Bruno P. Kinoshita started work on JENKINS-22016 Change By: Bruno P. Kinoshita 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] [dashboard-view-plugin] (JENKINS-22016) TAP test results of matrix configuration project do not show in main project overview and dashboard
Title: Message Title Bruno P. Kinoshita commented on JENKINS-22016 Re: TAP test results of matrix configuration project do not show in main project overview and dashboard Evan Van Dyke's pull request has been merged. Marking as fixed. Can you confirm, please, Evan? If there's further work before we can mark it as fixed, feel free to re-open the issue. Once a release has been cut I will mark the issue as Resolved. Thanks. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [dashboard-view-plugin] (JENKINS-22016) TAP test results of matrix configuration project do not show in main project overview and dashboard
Title: Message Title Bruno P. Kinoshita assigned an issue to Bruno P. Kinoshita Jenkins / JENKINS-22016 TAP test results of matrix configuration project do not show in main project overview and dashboard Change By: Bruno P. Kinoshita Assignee: Peter Hayes Bruno P. Kinoshita 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] [dashboard-view-plugin] (JENKINS-22016) TAP test results of matrix configuration project do not show in main project overview and dashboard
Title: Message Title SCM/JIRA link daemon commented on JENKINS-22016 Re: TAP test results of matrix configuration project do not show in main project overview and dashboard Code changed in jenkins User: Evan Path: pom.xml src/main/java/org/tap4j/plugin/AbstractTapProjectAction.java src/main/java/org/tap4j/plugin/TapProjectAction.java http://jenkins-ci.org/commit/tap-plugin/f636de3b72aa41cfe654f659a3088215d4638b1d Log: JENKINS-22016: Enable test status rollup displays on the Dashboard 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] [dashboard-view-plugin] (JENKINS-22016) TAP test results of matrix configuration project do not show in main project overview and dashboard
Title: Message Title SCM/JIRA link daemon commented on JENKINS-22016 Re: TAP test results of matrix configuration project do not show in main project overview and dashboard Code changed in jenkins User: Evan Path: pom.xml src/main/java/org/tap4j/plugin/TapProjectAction.java http://jenkins-ci.org/commit/tap-plugin/712d3e3fb3d540fec91ca19fdc4fa16c5f5e5650 Log: JENKINS-22016: Create Graph for matrix summary page 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] [jiratestresultreporter-plugin] (JENKINS-34904) JiraTestResultReporter - Host name may not be null
Title: Message Title Owen Wood created an issue Jenkins / JENKINS-34904 JiraTestResultReporter - Host name may not be null Issue Type: Bug Assignee: Catalin Luta Components: jiratestresultreporter-plugin Created: 2016/May/18 2:47 AM Priority: Critical Reporter: Owen Wood Reproduced with latest version of plugin (2.0.1) on Jenkins 1.642x Add the plugin, go to Jenkins > Manage Jenkins > Configure System then hit save. Produces an angry butler, with the following stacktrace: Caused by: java.lang.IllegalArgumentException: Host name may not be null at org.apache.http.HttpHost.(HttpHost.java:79) at org.apache.http.impl.client.cache.CachingHttpAsyncClient.execute(CachingHttpAsyncClient.java:276) at com.atlassian.httpclient.apache.httpcomponents.SettableFuturePromiseHttpPromiseAsyncClient.execute(SettableFuturePromiseHttpPromiseAsyncClient.java:36) at com.atlassian.httpclient.apache.httpcomponents.DefaultHttpClient.doExecute(DefaultHttpClient.java:247) at com.atlassian.httpclient.apache.httpcomponents.DefaultHttpClient.execute(DefaultHttpClient.java:181) at com.atlassian.httpclient.apache.httpcomponents.DefaultRequest.get(DefaultRequest.java:47) at com.atlassian.jira.rest.client.internal.async.AbstractAsynchronousRestClient.getAndParse(AbstractAsynchronousRestClient.java:67) at org.jenkinsci.plugins.JiraTestResultReporter.restclientextensions.JiraRestClientExtension.getStatuses(JiraRestClientExtension.java:42) at
[JIRA] [ircbot-plugin] (JENKINS-34903) IRC plugin: custom post-build message
Title: Message Title
ozizka created an issue
Jenkins / JENKINS-34903
IRC plugin: custom post-build message
Issue Type:
Improvement
Assignee:
kutzi
Components:
ircbot-plugin
Created:
2016/May/18 12:57 AM
Priority:
Minor
Reporter:
ozizka
It would be very useful if the message could be customized like:
{{"$ {job.name}
run $ {build.number}
for $ {build.name}
- $ {build.result}
$ {build.result.tests.failed.count.asString}
$ {build.git.pr.url}
"}}
would result in
windup-pr-builder run #1656: for "PR #924: Fixed some mistaked in the ..." - FAILED 6 tests https://github.com/windup/windup/pull/925
Add Comment
[JIRA] [ircbot-plugin] (JENKINS-34902) IRC notification to contain builds name
Title: Message Title ozizka created an issue Jenkins / JENKINS-34902 IRC notification to contain builds name Issue Type: Improvement Assignee: kutzi Components: ircbot-plugin Created: 2016/May/18 12:43 AM Priority: Minor Reporter: ozizka The post-build step, IRC notification, allows 5 options of what to send to the channel. Ideally, this should be customizable in a String.format() way. But at least there should be an option to send a message containing the name of the build. Therefore: "Project windup-pr-builder build #1656: SUCCESS in 22 min: http://wonka.mw.lab.eng.bos.redhat.com/jenkins/job/windup-pr-builder/1656/" would become " Project windup-pr-builder build #1656: SUCCESS in 22 min: PR #924: Fixed some mistaked in the ...http://wonka.mw.lab.eng.bos.redhat.com/jenkins/job/windup-pr-builder/1656/" The main motivation is the combination with Github plugin, which sets the name of a build to the name of the pull request. In this case, without this name, the message is not much useful. Thanks for considering.
[JIRA] [openstack-cloud-plugin] (JENKINS-34899) Destroy slaves fail at end of job
Title: Message Title Thanh Ha commented on JENKINS-34899 Re: Destroy slaves fail at end of job I can confirm that this issue appears even if you only build 1 slave. 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] [parallel-test-executor-plugin] (JENKINS-34901) Continue parallel stage even if previous stage failed
Title: Message Title Ashudeep Budhiraja created an issue Jenkins / JENKINS-34901 Continue parallel stage even if previous stage failed Issue Type: New Feature Assignee: Sam Van Oort Components: parallel-test-executor-plugin, pipeline-stage-view-plugin, workflow-plugin Created: 2016/May/18 12:12 AM Priority: Major Reporter: Ashudeep Budhiraja Multiple parallel branches, parallel A parallel B parallel C Is there any option to continue to B, even if A fails Add Comment
[JIRA] [branch-api-plugin] (JENKINS-33106) CustomOrganizationFolderDescriptor does not work after a dynamic installation
Title: Message Title Patrick Wolf updated an issue Jenkins / JENKINS-33106 CustomOrganizationFolderDescriptor does not work after a dynamic installation Change By: Patrick Wolf Comment: [~shott85] reported today that this is still an issue. He had a fresh install and the GH Org item type did not display until he restarted. 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-34239) GitHub Organization Folder not available as a new item without a restart
Title: Message Title Patrick Wolf commented on JENKINS-34239 Re: GitHub Organization Folder not available as a new item without a restart David Schott reported today that this is still an issue. He had a fresh install and the GH Org item type did not display until he restarted. 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] [branch-api-plugin] (JENKINS-33106) CustomOrganizationFolderDescriptor does not work after a dynamic installation
Title: Message Title Patrick Wolf commented on JENKINS-33106 Re: CustomOrganizationFolderDescriptor does not work after a dynamic installation David Schott reported today that this is still an issue. He had a fresh install and the GH Org item type did not display until he restarted. 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] [naginator-plugin] (JENKINS-13791) naginator plugin NullPointerException on successful build
Title: Message Title Anil Arige commented on JENKINS-13791 Re: naginator plugin NullPointerException on successful build When is this update going to be available for install ? Will this resolve https://issues.jenkins-ci.org/browse/JENKINS-34900 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] [dashboard-view-plugin] (JENKINS-33952) "Test Statistics Grid" shows all in "0" and "0%" including total as 0 tests when build never passed
Title: Message Title Evan Van Dyke resolved as Fixed 2.9.8 Jenkins / JENKINS-33952 "Test Statistics Grid" shows all in "0" and "0%" including total as 0 tests when build never passed Change By: Evan Van Dyke Status: Reopened 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] [dashboard-view-plugin] (JENKINS-33952) "Test Statistics Grid" shows all in "0" and "0%" including total as 0 tests when build never passed
Title: Message Title Evan Van Dyke reopened an issue Jenkins / JENKINS-33952 "Test Statistics Grid" shows all in "0" and "0%" including total as 0 tests when build never passed Change By: Evan Van Dyke Resolution: Fixed Status: Closed Reopened Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [naginator-plugin] (JENKINS-34900) Naginator plugin throwing Null Pointer Exception
Title: Message Title Anil Arige created an issue Jenkins / JENKINS-34900 Naginator plugin throwing Null Pointer Exception Issue Type: Bug Assignee: Nicolas De Loof Components: naginator-plugin Created: 2016/May/17 11:39 PM Priority: Blocker Reporter: Anil Arige Jobs which are not configured with Naginator are also failed because of the below error. FATAL: null java.lang.NullPointerException at com.chikli.hudson.plugin.naginator.NaginatorListener.setUpEnvironment(NaginatorListener.java:94) at hudson.model.AbstractBuild$AbstractBuildExecution.createLauncher(AbstractBuild.java:587) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:491) at hudson.model.Run.execute(Run.java:1759) at hudson.maven.MavenBuild.run(MavenBuild.java:269) at hudson.model.ResourceController.execute(ResourceController.java:89) at hudson.model.Executor.run(Executor.java:240) Also Choice Parameter is not working after installing Naginator plugin. Add Comment
[JIRA] [git-plugin] (JENKINS-34811) Environment Variables not being created
Title: Message Title Daniel Beck commented on JENKINS-34811 Re: Environment Variables not being created This doesn't appear to actually be related to Git plugin, but GHPRB, i.e. JENKINS-34762 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] [jobconfighistory-plugin] (JENKINS-34861) Job Config History Plugin failing when comparing diff between config files
Title: Message Title Daniel Beck commented on JENKINS-34861 Re: Job Config History Plugin failing when comparing diff between config files Why is this labeled security-170? 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] [kubernetes-plugin] (JENKINS-34897) Slaves cannot connect
Title: Message Title Jordan Lin closed an issue as Not A Defect Jenkins / JENKINS-34897 Slaves cannot connect Change By: Jordan Lin Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [openstack-cloud-plugin] (JENKINS-34899) Destroy slaves fail at end of job
Title: Message Title
Thanh Ha created an issue
Jenkins / JENKINS-34899
Destroy slaves fail at end of job
Issue Type:
Bug
Assignee:
Oliver Gondža
Components:
openstack-cloud-plugin
Created:
2016/May/17 11:17 PM
Environment:
Jenkins ver. 1.651.1 OpenStack Plugin: 2.6
Priority:
Critical
Reporter:
Thanh Ha
When creating a job that launches multiple slaves openstack plugin always fails to clean up the slaves after successfully destroying the 1st slave and throws the following error message:
FATAL: ActionResponse {success=false, fault=Instance 3a58a111-5c89-4a20-aadb-abd94a36b1f8 could not be found., code=404} jenkins.plugins.openstack.compute.internal.Openstack$ActionFailed: ActionResponse{success=false, fault=Instance 3a58a111-5c89-4a20-aadb-abd94a36b1f8 could not be found., code=404}
It appears that the 1st slave created actually successfully gets destroyed despite the error message above stating that it failed and then the job fails and does not continue to destroy the remaining slaves.
To reproduce:
1. create new freestyle job 2. configure openstack instance configuration 3. configure at least 2 instances to be launched as part of the job 4. run job
Ideally the
[JIRA] [dashboard-view-plugin] (JENKINS-33952) "Test Statistics Grid" shows all in "0" and "0%" including total as 0 tests when build never passed
Title: Message Title Evan Van Dyke closed an issue as Fixed Resolved in 2.9.8 Jenkins / JENKINS-33952 "Test Statistics Grid" shows all in "0" and "0%" including total as 0 tests when build never passed Change By: Evan Van Dyke 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] [dashboard-view-plugin] (JENKINS-33952) "Test Statistics Grid" shows all in "0" and "0%" including total as 0 tests when build never passed
Title: Message Title Evan Van Dyke assigned an issue to Evan Van Dyke Jenkins / JENKINS-33952 "Test Statistics Grid" shows all in "0" and "0%" including total as 0 tests when build never passed Change By: Evan Van Dyke Assignee: Peter Hayes Evan Van Dyke 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] [dashboard-view-plugin] (JENKINS-33952) "Test Statistics Grid" shows all in "0" and "0%" including total as 0 tests when build never passed
Title: Message Title Evan Van Dyke updated an issue Jenkins / JENKINS-33952 "Test Statistics Grid" shows all in "0" and "0%" including total as 0 tests when build never passed Change By: Evan Van Dyke Priority: Major Minor 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-34894) Jenkins github oAuth breaks UI in anonymous login
Title: Message Title Ronald Gundlach-Chmara edited a comment on JENKINS-34894 Re: Jenkins github oAuth breaks UI in anonymous login Disabling 243, as usggested suggested in a possibly related bug, did not fix.JENKINS_JAVA_OPTIONS="-Dhudson.model.User.SECURITY_243_FULL_DEFENSE=false" 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] [dashboard-view-plugin] (JENKINS-34804) dashboard Test Status Grid shows old / inactive configurations
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-34804 dashboard Test Status Grid shows old / inactive configurations Change By: SCM/JIRA link daemon 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] [dashboard-view-plugin] (JENKINS-12205) Test result trend not displayed in matrix project configuration top page
Title: Message Title SCM/JIRA link daemon commented on JENKINS-12205 Re: Test result trend not displayed in matrix project configuration top page Code changed in jenkins User: Willem Verstraeten Path: src/main/java/hudson/plugins/view/dashboard/test/TestUtil.java http://jenkins-ci.org/commit/dashboard-view-plugin/7effaedfb180af5a543895ad3edef7758fb856ff Log: Related to JENKINS-12205 : don't report test failures of inactive Matrix Configurations 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] [dashboard-view-plugin] (JENKINS-34804) dashboard Test Status Grid shows old / inactive configurations
Title: Message Title SCM/JIRA link daemon commented on JENKINS-34804 Re: dashboard Test Status Grid shows old / inactive configurations Code changed in jenkins User: evandy0 Path: src/main/java/hudson/plugins/view/dashboard/test/TestUtil.java http://jenkins-ci.org/commit/dashboard-view-plugin/e83aaf7fdce05efcc269a4d88365e991eddc5642 Log: Merge pull request #41 from willemv/master [FIXED JENKINS-34804] Don't report test failures of inactive Matrix Configurations Compare: https://github.com/jenkinsci/dashboard-view-plugin/compare/3cb3cba3eb8a...e83aaf7fdce0 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-34898) Parameter not resolved in image tag of plugin docker-custom-build-environment since 2.3
Title: Message Title hector CALDERON created an issue Jenkins / JENKINS-34898 Parameter not resolved in image tag of plugin docker-custom-build-environment since 2.3 Issue Type: Bug Assignee: Nicolas De Loof Attachments: docker.jenkins.png Components: docker-custom-build-environment-plugin Created: 2016/May/17 10:18 PM Environment: Running Jenkins 2.2-2.5 on Tomcat 8 and CentOS 7.2 Labels: regression Priority: Major Reporter: hector CALDERON The plugin is broken when the image to use contains a $ variable. It worked fine up to Jenkins ver 2.2 and is broken since 2.3. We can reproduce the problem by switching from 2.2 to any version above without modifying anything else.
[JIRA] [matrix-project-plugin] (JENKINS-34758) Parameters are not passed to child jobs in multi-configuration projects
Title: Message Title Andrew Bayer commented on JENKINS-34758 Re: Parameters are not passed to child jobs in multi-configuration projects So trying to look into fixing this - I guess it would make sense to have a child build-specific EnviromentContributor look at getAllParameters() in the child build, see which ones (a) aren't also in getParameters() for the child build and (b) are in the parent's getParameters(), and then add any that satisfy both criteria to the environment. Does that seem reasonable? 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] [kubernetes-plugin] (JENKINS-34897) Slaves cannot connect
Title: Message Title Jordan Lin commented on JENKINS-34897 Re: Slaves cannot connect Should note that I deployed this on a local kubernetes setup using (https://github.com/jenkinsci/kubernetes-plugin) Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-33546) Regression with build parameters in XML API
Title: Message Title Vivek Pandey resolved as Fixed Fixed in Jenkins 2.2 with integration of Stapler 1.243. Jenkins / JENKINS-33546 Regression with build parameters in XML API Change By: Vivek Pandey 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] [build-pipeline-plugin] (JENKINS-34724) No visible hyphen between displayed builds
Title: Message Title Nicholas Raymond commented on JENKINS-34724 Re: No visible hyphen between displayed builds Nico Falk what version of the Build Pipeline Plugin are you using? The last few updates (1.4.8+) contain changes to how the pipeline is presented. Currently, I'm running 1.4.9 in our environment and the breaks between the job pipeline executions are shown. 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] [kubernetes-plugin] (JENKINS-34897) Slaves cannot connect
Title: Message Title Jordan Lin updated an issue Jenkins / JENKINS-34897 Slaves cannot connect Change By: Jordan Lin When there are multiple jobs in queue, multiple executors are brought up but a majority of them die. So all the jobs in queue all run on one container. The containers that aren't brought up have the error of "This node is offline because Jenkins failed to launch the slave agent on it.". While reading the container logs of both master and slave, I found it out it's because the slave cannot connect to the master in some cases. Some slaves can connect but a majority of them die with ```SEVERE: Failed to connect to http://container-ip:8080/tcpSlaveAgentListener/: connect timed outjava.io.IOException: Failed to connect to http://container-ip:8080/tcpSlaveAgentListener/: connect timed out``` 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] [kubernetes-plugin] (JENKINS-34897) Slaves cannot connect
Title: Message Title Jordan Lin created an issue Jenkins / JENKINS-34897 Slaves cannot connect Issue Type: Bug Assignee: Carlos Sanchez Components: kubernetes-plugin Created: 2016/May/17 9:43 PM Environment: Jenkins build: 1.642.2 Kubernetes plugin: 0.6 Kubernetes: 1.2 The kubernetes plugin points to the internal jenkins master at http://containter-ip:8080 The container cap is at 10 The docker image deployed is jenkin/jnlp-slave Priority: Minor Reporter: Jordan Lin When there are multiple jobs in queue, multiple executors are brought up but a majority of them die. So all the jobs in queue all run on one container. The containers that aren't brought up have the error of "This node is offline because Jenkins failed to launch the slave agent on it.". While reading the container logs of both master and slave, I found it out it's because the slave cannot connect to the master in some cases. Some slaves can connect but a majority of them die with ``` SEVERE: Failed to connect to http://container-ip:8080/tcpSlaveAgentListener/: connect timed out java.io.IOException: Failed to connect to http://container-ip:8080/tcpSlaveAgentListener/: connect timed out ```
[JIRA] [core] (JENKINS-22949) If a QueueItemAuthenticator is configured but returns null, use ANONYMOUS not SYSTEM
Title: Message Title stephenconnolly updated an issue Jenkins / JENKINS-22949 If a QueueItemAuthenticator is configured but returns null, use ANONYMOUS not SYSTEM Since there is some confusion from people as to why this issue is now redundant. In Authorize Project Plugin 1.2.0 JENKINS-30574 implemented a feature that makes this request irrelevant as configuration can now enable this behaviour for instances that wish to opt-in, thereby removing the risk that would be inherent in implementing JENKINS-22949 Here is how to configure JENKINS-30574 to behave in this way: Change By: stephenconnolly Attachment: jenkins-22949-config.png Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you
[JIRA] [core] (JENKINS-22949) If a QueueItemAuthenticator is configured but returns null, use ANONYMOUS not SYSTEM
Title: Message Title stephenconnolly closed an issue as Won't Do Jenkins / JENKINS-22949 If a QueueItemAuthenticator is configured but returns null, use ANONYMOUS not SYSTEM Change By: stephenconnolly Status: Open Closed Resolution: Won't 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] [github-oauth-plugin] (JENKINS-34896) Not retrieving teams
Title: Message Title Felipe Santos created an issue Jenkins / JENKINS-34896 Not retrieving teams Issue Type: Bug Assignee: Sam Gleske Components: github-oauth-plugin Created: 2016/May/17 9:30 PM Environment: Jenkins 2.5 Github Authentication plugin 0.23 Priority: Minor Reporter: Felipe Santos Plugin is not retrieving items from github, or it is not setting on user Add Comment
[JIRA] [filesystem_scm-plugin] (JENKINS-34895) Multiple SCMs plugin doesn't save file system path
Title: Message Title Jonathan Phelps created an issue Jenkins / JENKINS-34895 Multiple SCMs plugin doesn't save file system path Issue Type: Bug Assignee: samngms Components: filesystem_scm-plugin, multiple-scms-plugin Created: 2016/May/17 8:32 PM Environment: Jenkins ver. 2.5 multiple-scms 0.6 filesystem_scm 1.20 Labels: multiple-scms Priority: Major Reporter: Jonathan Phelps I'm trying to build a simple job from scripts in a git repo and copy another file from the filesystem using the File System SCM and Multiple SCMs plugins. I can copy the file system directory by itself as the only SCM without Multiple SCMs configured. I can also checkout from git, but when I add the File System SCM under Multiple SCMs and configure the path I get this error in the console output log: FSSCM.checkout to /home/user/.jenkins/workspace/Projects/Build Test FATAL: Parameter 'directory' is not a directory Going back to re-configure the build, I find that the file system path is empty,
[JIRA] [github-oauth-plugin] (JENKINS-34894) Jenkins github oAuth breaks UI in anonymous login
Title: Message Title Ronald Gundlach-Chmara commented on JENKINS-34894 Re: Jenkins github oAuth breaks UI in anonymous login Disabling 243, as usggested in a possibly related bug, did not fix. JENKINS_JAVA_OPTIONS="-Dhudson.model.User.SECURITY_243_FULL_DEFENSE=false" 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-34894) Jenkins github oAuth breaks UI in anonymous login
Title: Message Title Ronald Gundlach-Chmara created an issue Jenkins / JENKINS-34894 Jenkins github oAuth breaks UI in anonymous login Issue Type: Bug Assignee: Sam Gleske Components: github-oauth-plugin Created: 2016/May/17 8:26 PM Environment: Jenkins 2.5, GitHub oAuth 0.23 Priority: Major Reporter: Ronald Gundlach-Chmara Seeing "java.lang.ClassCastException: org.acegisecurity.providers.anonymous.AnonymousAuthenticationToken cannot be cast to org.jenkinsci.plugins.GithubAuthenticationToken" errors on Jenkins 2.5, GitHub oAuth 0.23 with the user interface images (i.e. http://jenkins/static/0e8678ad/images/32x32/red.png ) when users are anonymous. Add Comment
[JIRA] [core] (JENKINS-34740) Many XHR requests fail under certain conditions when an underscore is present in the hostname
Title: Message Title Daniel Beck commented on JENKINS-34740 Re: Many XHR requests fail under certain conditions when an underscore is present in the hostname Peter Ntende Looks like outdated/mismatched plugins, may just take a Jenkins restart (or at worst an update of plugins) to fix. 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-folder-plugin] (JENKINS-34458) POST /github-webhook/ ignored if triggered within a minute
Title: Message Title Samuel Reed edited a comment on JENKINS-34458 Re: POST /github-webhook/ ignored if triggered within a minute I'm seeing the same issue on a pretty vanilla 2.x GitHub Organization project. If the pushes come too quickly (e.g. I push master & staging at the same time), only master is built because that hook came first and the second is ignored. Edit: Actually, this is probably getting confused with the GitHub Source Plugin and this issue: https://issues.jenkins-ci.org/browse/JENKINS-34727 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-folder-plugin] (JENKINS-34458) POST /github-webhook/ ignored if triggered within a minute
Title: Message Title Samuel Reed commented on JENKINS-34458 Re: POST /github-webhook/ ignored if triggered within a minute I'm seeing the same issue on a pretty vanilla 2.x GitHub Organization project. If the pushes come too quickly (e.g. I push master & staging at the same time), only master is built because that hook came first and the second is ignored. 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] [tfs-plugin] (JENKINS-33545) The SOAP endpoint could not be contacted (HTTP status: 302), new in 4.1.0.
Title: Message Title Matthew Sweeney commented on JENKINS-33545 Re: The SOAP endpoint could not be contacted (HTTP status: 302), new in 4.1.0. Same problem directly after upgrading to 4.1, downgrading to 4.0 is the current solution. 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] [gradle-jpi-plugin] (JENKINS-34874) Generated POM refers non-existing parent POM
Title: Message Title Fredrik Bruzelius edited a comment on JENKINS-34874 Re: Generated POM refers non-existing parent POM I have made a test build and publishToMavenLocal with Gradle using the patched plugin and the POM can now be resolved properly from the dependant (Maven-based) plugin.I also tried building using mismatching Core versions (using a more recent version in the API plugin), and that did not cause any resolution problems either.As far as I can tell, it seems to work as expected. 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] [gradle-jpi-plugin] (JENKINS-34874) Generated POM refers non-existing parent POM
Title: Message Title Fredrik Bruzelius commented on JENKINS-34874 Re: Generated POM refers non-existing parent POM I have made a test build and publishToMavenLocal using the patched plugin and the POM can now be resolved properly from the dependant plugin. I also tried building using mismatching Core versions (using a more recent version in the API plugin), and that did not cause any resolution problems either. As far as I can tell, it seems to work as expected. 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-34060) Unstable a build when DSL scripts pattern doesn't list any files
Title: Message Title Daniel Spilker commented on JENKINS-34060 Re: Unstable a build when DSL scripts pattern doesn't list any files Victor Martinez are you still working on a fix? 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] [scp-plugin] (JENKINS-34893) Promote from Build Artifacts
Title: Message Title Matthew Kruer created an issue Jenkins / JENKINS-34893 Promote from Build Artifacts Issue Type: Improvement Assignee: Andres Rodriguez Components: scp-plugin Created: 2016/May/17 7:24 PM Environment: Jenkins ver. 1.642.3 promoted builds plugin 2.26 Publish artifacts to SCP Repository (scp 1.8) Java ver. 1.7 Priority: Major Reporter: Matthew Kruer When used in conjunction with the "Promoted Builds Plugin" it would be very helpful to allow promotions from the "archived" location and not just the workspace. Build/Test/Promote Logic Flow Build Job #1, (no blocking) Archive Build Artifacts Build Job #1, triggers Test Job #1, Build Job #2 , (no blocking) Archive Build Artifacts On success of Test Job #1, using the "Promoted Builds" of the Build Job #1 SCP copies files from Build Job #2 (because its form the work space) Oops! So by the time the promotion occurs the workspace might have been wiped and rebuilt with a new Build Artifacts . This is important because some test may require a lot of time and we dont want to block up stream builds
[JIRA] [job-dsl-plugin] (JENKINS-34060) Unstable a build when DSL scripts pattern doesn't list any files
Title: Message Title Chris Hubbard commented on JENKINS-34060 Re: Unstable a build when DSL scripts pattern doesn't list any files We have a web application that generates DSL files from a database. When there are no entries in the database, then there won't be any groovy files. When a database entry is deleted (and the count goes to zero), the job should be deleted. With JENKINS-30541 , now the Job DSL job fails and the generated job doesn't get deleted. I would be fine with a checkbox to enable/disable this. I don't want a switch between "validate that at least one DSL was found" and "validate that all globs resulted in a DSL being found" since we can have cases where it is fine that there are no DSL files generated. 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] [lockable-resources-plugin] (JENKINS-34892) lock step in Pipeline should allow creation of implicit locks
Title: Message Title Patrick Wolf created an issue Jenkins / JENKINS-34892 lock step in Pipeline should allow creation of implicit locks Issue Type: Story Assignee: Jesse Glick Components: lockable-resources-plugin, workflow-plugin Created: 2016/May/17 6:59 PM Priority: Minor Reporter: Patrick Wolf When using a lock step in a Pipeline it is possible to name a globally defined resource and lock it. However, in order to use lock to institute concurrency within a job, Pipeline would need to create an implicit (ephemeral) resource that prevents other jobs from entering the defined lock step. There has been some discussion about how this would be implemented to avoid name collisions among different jobs. Add Comment
[JIRA] [job-dsl-plugin] (JENKINS-33861) Support Unity3d plugin
Title: Message Title
Daniel Spilker resolved as Fixed
This is supported by the automatically generated DSL:
job('example') {
steps {
unity3dBuilder {
unity3dName('unity-5.2.1')
unstableReturnCodes('2,3')
argLine('-batchmode')
}
}
}
Jenkins / JENKINS-33861
Support Unity3d plugin
Change By:
Daniel Spilker
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
[JIRA] [job-dsl-plugin] (JENKINS-34817) Add job-dsl-plugin support for logstash plugin
Title: Message Title
Daniel Spilker resolved as Fixed
This is already supported by the automatically generated DSL:
job('example') {
wrappers {
logstashBuildWrapper()
}
}
Jenkins / JENKINS-34817
Add job-dsl-plugin support for logstash plugin
Change By:
Daniel Spilker
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] [jobconfighistory-plugin] (JENKINS-34861) Job Config History Plugin failing when comparing diff between config files
Title: Message Title Jonathan Strickland commented on JENKINS-34861 Re: Job Config History Plugin failing when comparing diff between config files Jochen A. Fürbacher Thanks for the update. Let me schedule an upgrade with my team; this was the first issue found with my search engine. After reading JENKINS 33289, it looks like the same. I'm ok with closure of this issue if Stefan Brausch is ok with 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] [logstash-plugin] (JENKINS-34891) java.lang.NoClassDefFoundError: com/michelin/cio/hudson/plugins/maskpasswords/MaskPasswordsOutputStream
Title: Message Title Daniel Spilker created an issue Jenkins / JENKINS-34891 java.lang.NoClassDefFoundError: com/michelin/cio/hudson/plugins/maskpasswords/MaskPasswordsOutputStream Issue Type: Bug Assignee: Unassigned Components: logstash-plugin Created: 2016/May/17 6:33 PM Environment: Jenkins 2.3 Logstask Plugin 1.2.0 Priority: Minor Reporter: Daniel Spilker When trying to safe a job config with "Send console log to Logstash" enabled, I get the following exception. It works after installing the mask-passwords plugin. The logstash plugin should declare a non-optional dependency to the mask-passwords plugin. javax.servlet.ServletException: java.lang.NoClassDefFoundError: com/michelin/cio/hudson/plugins/maskpasswords/MaskPasswordsOutputStream at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$5.doDispatch(MetaClass.java:233) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at
[JIRA] [job-dsl-plugin] (JENKINS-34810) Error in Job DSL if no files found
Title: Message Title Daniel Spilker closed an issue as Duplicate Jenkins / JENKINS-34810 Error in Job DSL if no files found Change By: Daniel Spilker Status: Open Closed Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-34890) Unable to push tags to remote GIT repo
Title: Message Title David MacPhail closed an issue as Not A Defect Jenkins / JENKINS-34890 Unable to push tags to remote GIT repo Change By: David MacPhail Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [buildgraph-view-plugin] (JENKINS-34803) Update to version 1.3 of build-graph-view plugin crashes Jenkins hard
Title: Message Title Goffredo Marocchi edited a comment on JENKINS-34803 Re: Update to version 1.3 of build-graph-view plugin crashes Jenkins hard This error occurs on Jenkins 2.5 too, but with a different stack trace. I have tried all other plugins I have updated this week one by one and this update is the one consistently reproducing this issue on two machines. 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] [buildgraph-view-plugin] (JENKINS-34803) Update to version 1.3 of build-graph-view plugin crashes Jenkins hard
Title: Message Title Goffredo Marocchi updated an issue Jenkins / JENKINS-34803 Update to version 1.3 of build-graph-view plugin crashes Jenkins hard This error occurs on Jenkins 2.5 too, but with a different stack trace. Change By: Goffredo Marocchi Attachment: upload.png Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-28492) The server rejected the connection: *** is already connected to this master. Rejecting this connection.
Title: Message Title mark mann commented on JENKINS-28492 Re: The server rejected the connection: *** is already connected to this master. Rejecting this connection. windows 2008R2 master and slaves master on Jenkins ver. 1.651.1 Java JRE is mixture of 8u60, 8u77, 8u91 I have >200 slaves and started seeing some of my "controller" slaves not wanting to start their jenkins slaves, especially when the slave has been reinstalled (as a refresh) the sample below is from a fresh slave, on 8u91. try to start the windows service hosting the slave and it stops immediately with the following log trace. May 17, 2016 5:45:58 PM hudson.remoting.jnlp.Main createEngine INFO: Setting up slave: ComputerA May 17, 2016 5:45:58 PM hudson.remoting.jnlp.Main$CuiListener INFO: Jenkins agent is running in headless mode. May 17, 2016 5:45:58 PM hudson.remoting.jnlp.Main$CuiListener status INFO: Locating server among http://10.20.1.181:8080/jenkins/, http://jenkins:8080/jenkins/ May 17, 2016 5:45:58 PM hudson.remoting.jnlp.Main$CuiListener status INFO: Handshaking May 17, 2016 5:45:58 PM hudson.remoting.jnlp.Main$CuiListener status INFO: Connecting to 10.20.1.181:55945 May 17, 2016 5:45:58 PM hudson.remoting.jnlp.Main$CuiListener status INFO: Trying protocol: JNLP2-connect May 17, 2016 5:45:58 PM hudson.remoting.jnlp.Main$CuiListener status INFO: Server didn't understand the protocol: ComputerA is already connected to this master. Rejecting this connection. May 17, 2016 5:45:58 PM hudson.remoting.jnlp.Main$CuiListener status INFO: Connecting to 10.20.1.181:55945 May 17, 2016 5:45:58 PM hudson.remoting.jnlp.Main$CuiListener status INFO: Trying protocol: JNLP-connect May 17, 2016 5:45:58 PM hudson.remoting.jnlp.Main$CuiListener status INFO: Server didn't understand the protocol: ComputerA is already connected to this master. Rejecting this connection. May 17, 2016 5:45:58 PM hudson.remoting.jnlp.Main$CuiListener status INFO: Connecting to 10.20.1.181:55945 May 17, 2016 5:45:58 PM hudson.remoting.jnlp.Main$CuiListener error SEVERE: The server rejected the connection: None of the protocols were accepted java.lang.Exception: The server rejected the connection: None of the protocols were accepted at hudson.remoting.Engine.onConnectionRejected(Engine.java:297) at hudson.remoting.Engine.run(Engine.java:268) i've set the slave to "disconnected" on the master and then restart the service. sometimes it might then stay up, but not for long!! Add Comment This
[JIRA] [active-directory-plugin] (JENKINS-34426) Changing project-based settings for AD-Groups shows error
Title: Message Title Billy Foss commented on JENKINS-34426 Re: Changing project-based settings for AD-Groups shows error I am seeing this issue with the LTS stream as well. Jenkins ver. 1.651.2 AD Plugin 1.45 Configuration is xxx xxx xxx RECURSIVE false Existing users can still login, but new users cannot. New users are also shown as invalid on the Global Security page. — Failed to test the validity of the user name hudson.plugins.active_directory.CacheAuthenticationException: Authentication failed because there was a problem caching user ; nested exception is com.google.common.util.concurrent.UncheckedExecutionException: java.lang.IllegalStateException: Recursive load at hudson.plugins.active_directory.ActiveDirectoryUnixAuthenticationProvider.retrieveUser(ActiveDirectoryUnixAuthenticationProvider.java:340) at hudson.plugins.active_directory.ActiveDirectoryUnixAuthenticationProvider.retrieveUser(ActiveDirectoryUnixAuthenticationProvider.java:199) at hudson.plugins.active_directory.ActiveDirectoryUnixAuthenticationProvider.retrieveUser(ActiveDirectoryUnixAuthenticationProvider.java:141) at hudson.plugins.active_directory.AbstractActiveDirectoryAuthenticationProvider.loadUserByUsername(AbstractActiveDirectoryAuthenticationProvider.java:54) at hudson.plugins.active_directory.ActiveDirectorySecurityRealm.loadUserByUsername(ActiveDirectorySecurityRealm.java:731) at hudson.security.GlobalMatrixAuthorizationStrategy$DescriptorImpl.doCheckName_(GlobalMatrixAuthorizationStrategy.java:336) at hudson.security.GlobalMatrixAuthorizationStrategy$DescriptorImpl.doCheckName(GlobalMatrixAuthorizationStrategy.java:314) at sun.reflect.GeneratedMethodAccessor91.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:320) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:163) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:96) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:124) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$5.doDispatch(MetaClass.java:233) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:135) at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:59) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:132) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:126) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:49) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) at
[JIRA] [kubernetes-plugin] (JENKINS-34380) kubernetes plugin creates an unbounded number of Netty I/O threads
Title: Message Title Jordan Lin stopped work on JENKINS-34380 Change By: Jordan Lin Status: In Progress Open 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] [kubernetes-plugin] (JENKINS-34380) kubernetes plugin creates an unbounded number of Netty I/O threads
Title: Message Title Jordan Lin started work on JENKINS-34380 Change By: Jordan Lin 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] [hidden-parameter-plugin] (JENKINS-34875) Support of com.wangyin.parameter.WHideParameterDefinition in Jenkins CLI
Title: Message Title Oleg Nenashev commented on JENKINS-34875 Re: Support of com.wangyin.parameter.WHideParameterDefinition in Jenkins CLI Fixed the component, but it has no default assignee. Pinged the hosting requester in https://groups.google.com/forum/#!searchin/jenkinsci-dev/wy-scm/jenkinsci-dev/Vxu26M5O2Ms/Ni2Ffc99jC0J , but no guarantee there will be a response. If no, consider fixing the issue on you own and creating a PR. Then you will be able to request the plugin ownership transfer 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] [hidden-parameter-plugin] (JENKINS-34875) Support of com.wangyin.parameter.WHideParameterDefinition in Jenkins CLI
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-34875 Support of com.wangyin.parameter.WHideParameterDefinition in Jenkins CLI Change By: Oleg Nenashev Component/s: hidden-parameter-plugin Component/s: _unsorted 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] [hidden-parameter-plugin] (JENKINS-34875) Support of com.wangyin.parameter.WHideParameterDefinition in Jenkins CLI
Title: Message Title Oleg Nenashev assigned an issue to Unassigned Jenkins / JENKINS-34875 Support of com.wangyin.parameter.WHideParameterDefinition in Jenkins CLI Change By: Oleg Nenashev Assignee: 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] [remoting] (JENKINS-2374) Master-Slave Workspace Directory Structure Different
Title: Message Title
Mike Robinson commented on JENKINS-2374
Re: Master-Slave Workspace Directory Structure Different
Simple Problem Case: build script used by a job run requires full path to workspace. Simple enough to build as: {{$ {Jenkins_Root}
/jobs/$ {Job_Name}
/workspace}}
Now add a slave to do builds, all builds fail because path is no longer correct.
That this has been labeled Minor because it "...has no impact on the builds." is incorrect, it most assuredly has impact on 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] [core] (JENKINS-34854) Some properties missed in the introduction of SystemProperties
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-34854 Some properties missed in the introduction of SystemProperties Change By: Oleg Nenashev I believe During implementation of JENKINS-34755 the author only searched for System.getProperty and missed lines like Boolean.getBoolean and Integer.getInteger()Example here: https://github.com/jenkinsci/jenkins/blob/99f80a0b0b93a6d7c928d21849d96e0d642e5d1f/core/src/main/java/hudson/model/ParametersAction.java#L270 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-34854) Some properties missed in the introduction in SystemProperties
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-34854 Some properties missed in the introduction in SystemProperties Change By: Oleg Nenashev Summary: Some properties missed in the introduction of in SystemProperties 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-34854) Some properties missed in the introduction of SystemProperties
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-34854 Some properties missed in the introduction of SystemProperties Change By: Oleg Nenashev Labels: settings.xml war 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-34854) Some properties missed in the introduction of SystemProperties
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-34854 Some properties missed in the introduction of SystemProperties Change By: Oleg Nenashev Priority: Minor Major 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-34854) Some properties missed in the introduction of SystemProperties
Title: Message Title Oleg Nenashev commented on JENKINS-34854 Re: Some properties missed in the introduction of SystemProperties As an author, I agree that update of JENKINS-34755 to ALL properties was incomplete. Since it involves security fixes, I consider it as a major bug. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-34890) Unable to push tags to remote GIT repo
Title: Message Title David MacPhail created an issue Jenkins / JENKINS-34890 Unable to push tags to remote GIT repo Issue Type: Bug Assignee: Unassigned Components: git-plugin Created: 2016/May/17 5:18 PM Environment: Jenkins 1.651.1 Priority: Minor Reporter: David MacPhail When executing a Jenkins GIT build, the system cannot push tags to the remote repo and fails with the following error ERROR: Failed to push tag git_publish_label.15 to origin hudson.plugins.git.GitException: org.eclipse.jgit.api.errors.TransportException: http://tfs.tsl.telus.com/tfs/telus/BT-GIT/_git/Platform-SampleApplication: error occurred during unpacking on the remote end: error Operation is not valid due to the current state of the object. We are running Jenkins war 1.651.1 with Git Client 1.19.6, Git Plugin 2.4.4 and GIT Server Plugin 1.6 Hopefully I have included all required information. Please let me know if anything further required
[JIRA] [core] (JENKINS-34854) Some properties missed in the introduction of SystemProperties
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-34854 Some properties missed in the introduction of SystemProperties Change By: Oleg Nenashev I believe the author only searched for System.getProperty and missed lines like Boolean.getBoolean and Integer.getInteger() Example here: https://github.com/jenkinsci/jenkins/blob/99f80a0b0b93a6d7c928d21849d96e0d642e5d1f/core/src/main/java/hudson/model/ParametersAction.java#L270 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-34775) Broken jobs after upgrade to 1.651.2 security update
Title: Message Title Joseph Thibeault commented on JENKINS-34775 Re: Broken jobs after upgrade to 1.651.2 security update Thanks! That seems to have fixed it for now. I had to disable SECURITY-170 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] [pipeline-stage-view-plugin] (JENKINS-34212) Visualization shows stage failed when an exception is caught
Title: Message Title Jesse Glick commented on JENKINS-34212 Re: Visualization shows stage failed when an exception is caught This is clearly a bug, in that we are able to tell from the flow graph whether or not an error was caught within a stage. But there is also an RFE to allow the script to indicate that a stage should be considered “failed” in some sense despite having caught and handled the exception, and proceeded to the end of the build or subsequent stages. See JENKINS-26522. 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-34863) WebSphere Plugin Configure System Missing
Title: Message Title Bruce Coveny updated an issue Jenkins / JENKINS-34863 WebSphere Plugin Configure System Missing Change By: Bruce Coveny Since the upgrade to Jenkins 2.0 - 2.4 the configuration setup for the WAS Builder Plugin does not show up in the Manage Jenkins -> Configure System. In Jenkins 1.xxx you would go there to configure the server names.It looks like the information is stored in a file in the home directory by the name filename of com.michelin.cio.hudson.plugins.wasbuilder.WASInstallation.xml You can manually modify this file and the information will only show up if you restart the Jenkins instance. The configuration doesn't refresh if you reload the configuration from disk. Also if the password is different than another server you cannot create the password encryption manually. 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-34775) Broken jobs after upgrade to 1.651.2 security update
Title: Message Title Andrew Stiegmann commented on JENKINS-34775 Re: Broken jobs after upgrade to 1.651.2 security update You need to add it as part of your Java options. On CentOS 7 the file is /etc/sysconfig/jenkins and you need to set the following: JENKINS_JAVA_OPTIONS="-Dhudson.model.User.SECURITY_243_FULL_DEFENSE=false" or whatever works best for you. In my case I also had to disable the fix for SECURITY-170 since that was interfering with one of my plugins. 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] [view-job-filters-plugin] (JENKINS-30182) view-job-filters plugin, parameterized jobs filter, does not work. exceptions thrown from build filter (wrapper) column
Title: Message Title Carl Jokl commented on JENKINS-30182 Re: view-job-filters plugin, parameterized jobs filter, does not work. exceptions thrown from build filter (wrapper) column Having examined the source code to try and fix it myself, I have observed the following explanation for the behaviour. This can be used to filter Jobs where parameters are typically used on an individual run. When filtering at the Job level the behaviour based on the source code logic is: If "match against many previous builds" is set then the Job will match if any of those builds/runs had the specified parameter set. If "match against many previous builds" is not set the Job will match only if the latest build/run had the specified parameter set. The filter has the logic available to filter builds/runs that match the parameter. This would only work if the code using the filter is making use of the build/run filter logic. This seems to imply that the filter itself is working correctly when filtering at the Job level. This behaviour may not be intuitive without knowing why it behaves the way it does. As far as I understand, the problem is with code using the filter not filtering out just the runs with a given parameter set. As I am new to the Jenkins / plugin source code it would help to check my observations are reasonable. 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-34775) Broken jobs after upgrade to 1.651.2 security update
Title: Message Title Joseph Thibeault commented on JENKINS-34775 Re: Broken jobs after upgrade to 1.651.2 security update I'm having this issue as well. I'm struggling to find where I can disable that option though. Which file should I be looking in? 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-34369) NPE on PreBuildMerge.decorateRevisionToBuild
Title: Message Title Russell Gallop commented on JENKINS-34369 Re: NPE on PreBuildMerge.decorateRevisionToBuild I have seen this issue when using the git plugin to merge branches. Git needs to hit a merge conflict (or other error in merging maybe) to hit this problem. Without the pull request (git plugin 2.4.4) > git.exe merge --ff 4f7fc6bad3bc7778104b92950bfc1b3f5e1d3d9d # timeout=10 > git.exe config core.sparsecheckout # timeout=10 > git.exe checkout -f 4f7fc6bad3bc7778104b92950bfc1b3f5e1d3d9d FATAL: null java.lang.NullPointerException at hudson.plugins.git.extensions.impl.PreBuildMerge.decorateRevisionToBuild(PreBuildMerge.java:88) With the pull request applied on top of ce5479a42e74b45dd8b954776ad4220c9c0151bc the problem is reported better. > git.exe merge --ff 4f7fc6bad3bc7778104b92950bfc1b3f5e1d3d9d # timeout=10 > git.exe config core.sparsecheckout # timeout=10 > git.exe checkout -f 4f7fc6bad3bc7778104b92950bfc1b3f5e1d3d9d ERROR: Branch not suitable for integration as it does not merge cleanly: Could not merge AnyObjectId[4f7fc6bad3bc7778104b92950bfc1b3f5e1d3d9d] I think this should have a test case though. 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-changelog-plugin] (JENKINS-34886) Jenkins Git Error Invalid ID
Title: Message Title Paul Wellner Bou edited a comment on JENKINS-34886 Re: Jenkins Git Error Invalid ID [~nsd]: Are you able to reproduce this with an open repository, where we have access to, to reproduce this bug? Could you check if this error happens without using git-changelog-plugin at all? 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-changelog-plugin] (JENKINS-34886) Jenkins Git Error Invalid ID
Title: Message Title Paul Wellner Bou commented on JENKINS-34886 Re: Jenkins Git Error Invalid ID Nadine Sander: Are you able to reproduce this with an open repository, where we have access to, to reproduce this bug? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-34889) Build history alternating colors flip when filtering
Title: Message Title Steve Pokorski created an issue Jenkins / JENKINS-34889 Build history alternating colors flip when filtering Issue Type: Improvement Assignee: Unassigned Components: core Created: 2016/May/17 4:09 PM Environment: Jenkins LTS 1.651.2 ubuntu 12.04 precise x64 openJDK 7u65-2.5.1-4ubuntu1~0.12.04.2 Priority: Trivial Reporter: Steve Pokorski When initially loading or refreshing a job page, the build history alternating colors start with white on the filter textbox, then grey/white/grey/white for the builds. after using the filter box, or even clearing an already empty filter, the colors fip with the filter textbox having grey, and them white/grey/white/grey for the builds. obviously trivial issue; everything still works just fine, and the rows still have alternating colors. inspecting the page elements, this appears to be a fault in reconstructing the elements after using the filter. on initial page load, the table is constructed like: ...
[JIRA] [core] (JENKINS-34706) InstallationWizard: Layout overlaps on the narrow screen
Title: Message Title Manuel Jesús Recena Soto resolved as Duplicate Jenkins / JENKINS-34706 InstallationWizard: Layout overlaps on the narrow screen Change By: Manuel Jesús Recena Soto 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] [core] (JENKINS-34676) Outdated version of js-modules causes loading issues on JS module conflicts
Title: Message Title Manuel Jesús Recena Soto closed an issue as Duplicate Jenkins / JENKINS-34676 Outdated version of js-modules causes loading issues on JS module conflicts Change By: Manuel Jesús Recena Soto Status: Open Closed Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-34676) Outdated version of js-modules causes loading issues on JS module conflicts
Title: Message Title Manuel Jesús Recena Soto reopened an issue Jenkins / JENKINS-34676 Outdated version of js-modules causes loading issues on JS module conflicts Change By: Manuel Jesús Recena Soto Resolution: Duplicate Status: Closed Reopened Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-34826) Promoted builds do not receive parameter values defined at the job level
Title: Message Title Hidden Maverick edited a comment on JENKINS-34826 Re: Promoted builds do not receive parameter values defined at the job level I'm using a workaround similar to the accepted answer here: http://stackoverflow.com/questions/31082154/parameterize-the-approver-detail-in-promoted-build-plugin-in-jenkins#31116631This workaround uses the Copy Artifacts Artifact and EnvInject plugins to store the parameters at the job level and retrieve them at the promotion level. The job uses a native shell build task (Execute Windows Batch Command, Execute Shell, etc.) to store the parameters using the Java Properties format into a file in the workspace, with one parameter per line given in a name=value pair. A Copy An Archive The Artifacts post-build task (from the Copy Artifact plugin) is then used to copy the parameter file to the job as an artifact.The promotion will need an action to copy the artifact from the project, with $PROMOTED_JOB_NAME as the project name, $PROMOTED_NUMBER as the specific build number, and the filename of the parameter file as the artifact to copy. Finally, an Inject Environment Variables task (from the EnvInject plugin), with the filename of the parameter file specified, will make the parameters available as environment variables.The workaround requires a few extra steps, but has been working robustly for me in both Jenkins 1.651.1 and Jenkins 1.651.2. 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-34676) Outdated version of js-modules causes loading issues on JS module conflicts
Title: Message Title Manuel Jesús Recena Soto assigned an issue to Manuel Jesús Recena Soto Jenkins / JENKINS-34676 Outdated version of js-modules causes loading issues on JS module conflicts Change By: Manuel Jesús Recena Soto Assignee: Manuel Jesús Recena Soto Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-34676) Outdated version of js-modules causes loading issues on JS module conflicts
Title: Message Title Manuel Jesús Recena Soto stopped work on JENKINS-34676 Change By: Manuel Jesús Recena Soto Status: In Progress Open 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-34676) Outdated version of js-modules causes loading issues on JS module conflicts
Title: Message Title Oleg Nenashev assigned an issue to Unassigned Jenkins / JENKINS-34676 Outdated version of js-modules causes loading issues on JS module conflicts Change By: Oleg Nenashev Assignee: 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] [core] (JENKINS-34826) Promoted builds do not receive parameter values defined at the job level
Title: Message Title Hidden Maverick edited a comment on JENKINS-34826 Re: Promoted builds do not receive parameter values defined at the job level I'm using a workaround similar to the accepted answer here: http://stackoverflow.com/questions/31082154/parameterize-the-approver-detail-in-promoted-build-plugin-in-jenkins#31116631This workaround uses the Copy Artifacts and EnvInject plugins to store the parameters at the job level and retrieve them at the promotion level. The job uses a native shell build task (Execute Windows Batch Command, Execute Shell, etc.) to store the parameters using the Java Properties format into a file in the workspace, with one parameter per line given in a name=value pair. A Copy Artifacts post-build task is then used to copy the parameter file to the job as an artifact.The promotion will need an action to copy the artifact from the project, with $PROMOTED_JOB_NAME as the project name, $PROMOTED_NUMBER as the specific build number, and the filename of the parameter file as the artifact to copy. Finally, an Inject Environment Variables task (from the EnvInject plugin), with the filename of the parameter file specified, will make the parameters available as environment variables.The workaround requires a few extra steps, but has been working robustly for me in both Jenkins 1 . 651.1 and Jenkins 1.651.2. 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-34826) Promoted builds do not receive parameter values defined at the job level
Title: Message Title Hidden Maverick commented on JENKINS-34826 Re: Promoted builds do not receive parameter values defined at the job level I'm using a workaround similar to the accepted answer here: http://stackoverflow.com/questions/31082154/parameterize-the-approver-detail-in-promoted-build-plugin-in-jenkins#31116631 This workaround uses the Copy Artifacts and EnvInject plugins to store the parameters at the job level and retrieve them at the promotion level. The job uses a native shell build task (Execute Windows Batch Command, Execute Shell, etc.) to store the parameters using the Java Properties format into a file in the workspace, with one parameter per line given in a name=value pair. A Copy Artifacts post-build task is then used to copy the parameter file to the job as an artifact. The promotion will need an action to copy the artifact from the project, with $PROMOTED_JOB_NAME as the project name, $PROMOTED_NUMBER as the specific build number, and the filename of the parameter file as the artifact to copy. Finally, an Inject Environment Variables task (from the EnvInject plugin), with the filename of the parameter file specified, will make the parameters available as environment variables. The workaround requires a few extra steps, but has been working robustly for me. 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.
