[JIRA] [scm-sync-configuration-plugin] (JENKINS-25786) Renaming Job Causes a poisoned commitQueue
Title: Message Title Christoph Obexer commented on JENKINS-25786 Re: Renaming Job Causes a poisoned commitQueue David Cullen Have you tried to just git commit the changes that are already in the scm-sync-configuration/checkoutConfiguration directory? modifying jobs with spaces always causes this for me and just committing manually fixes it 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.
[JIRA] [maven-plugin] (JENKINS-24832) Failed maven builds using -T are showing up as Aborted
Title: Message Title Yoram Michaeli commented on JENKINS-24832 Re: Failed maven builds using -T are showing up as Aborted As a workaround, until this is fixed, you can use a groovy post-build script that changes the status of the build from ABORTED to FAILED in case it finds the error in the log. See a post I've wrote about it: http://www.tikalk.com/devops/JenkinsJobStatusChange 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] [packaging] (JENKINS-33285) Old jenkins versions are not listed in Debian repository Packages.gz
Title: Message Title Heikki Hokkanen created an issue Jenkins / JENKINS-33285 Old jenkins versions are not listed in Debian repository Packages.gz Issue Type: Bug Assignee: Kohsuke Kawaguchi Components: packaging Created: 03/Mar/16 6:28 AM Priority: Major Reporter: Heikki Hokkanen The Red Hat repository contains all jenkins versions: curl http://pkg.jenkins-ci.org/redhat/repodata/filelists.xml.gz |gunzip However, the Debian mirror contains only the latest one: curl http://pkg.jenkins-ci.org/debian/binary/Packages |gunzip It would be really nice to be able to install a specific version of jenkins using the official distro repositories.
[JIRA] [build-flow-plugin] (JENKINS-33235) post groovy script throws Null Exception
Title: Message Title Gautham Rathina kumar commented on JENKINS-33235 Re: post groovy script throws Null Exception i dont think so because i tested some code taken from GITHUB it also throws the same type of exception 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] [configurationslicing-plugin] (JENKINS-30775) Please add support for the "Abort build if stuck" fields of Build-timeout plugin
Title: Message Title mdonohue commented on JENKINS-30775 Re: Please add support for the "Abort build if stuck" fields of Build-timeout plugin Yes, there is now an object hierarchy around the BuildTimeOutStrategy, which doesn't lend itself well to a simple string representation. Using a JSON or XML format may work though. We can serialize the strategy object to JSON, then use the databinding mechanism to read it back in from the slice configuration. I don't think this use-case was intended with Jenkins though, so it might hit some rough spots. 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] [configurationslicing-plugin] (JENKINS-9478) NullPointerException while submitting config slicer logrotationbuilds or logrotationdays
Title: Message Title mdonohue commented on JENKINS-9478 Re: NullPointerException while submitting config slicer logrotationbuilds or logrotationdays ok. thanks. I tried it just now with 1.580.1, and both slicers worked fine - # builds and days to keep. I'm inclined to close this as cannot reproduce, unless more information is provided. 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] [copyartifact-plugin] (JENKINS-33257) Misleading warning "Unable to find project" in "Permission to Copy Artifact - Projects to allow copy artifacts"
Title: Message Title Rick Liu updated an issue Jenkins / JENKINS-33257 Misleading warning "Unable to find project" in "Permission to Copy Artifact - Projects to allow copy artifacts" Jenkins System Information Change By: Rick Liu Attachment: System Information [Jenkins].htm 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] [copyartifact-plugin] (JENKINS-33257) Misleading warning "Unable to find project" in "Permission to Copy Artifact - Projects to allow copy artifacts"
Title: Message Title Rick Liu updated an issue Jenkins / JENKINS-33257 Misleading warning "Unable to find project" in "Permission to Copy Artifact - Projects to allow copy artifacts" The list of installed plugins and versions. Change By: Rick Liu Attachment: Update Center - installed plugins [Jenkins].html 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] [testng-plugin] (JENKINS-33284) TestNG report plugin cannot show complex object parameters clearly in test method
Title: Message Title maggie cq updated an issue Jenkins / JENKINS-33284 TestNG report plugin cannot show complex object parameters clearly in test method Change By: maggie cq Now testng report plugin can support to show the simple object parameters such as string or int etc, but when pass a complex parameter to the test method, for example, pass a an array parameter, then it will not show well in the testng report in Jenkins. It is just a suggestion. It will be better if this plugin can show the same with what the testng integrated report look likes. Screenshot is attached. 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] [testng-plugin] (JENKINS-33284) TestNG report plugin cannot show complex object parameters clearly in test method
Title: Message Title maggie cq created an issue Jenkins / JENKINS-33284 TestNG report plugin cannot show complex object parameters clearly in test method Issue Type: Improvement Assignee: dante briones Attachments: parameter_test_method.jpg Components: testng-plugin Created: 03/Mar/16 3:55 AM Labels: plugins Priority: Minor Reporter: maggie cq Now testng report plugin can support to show the simple object parameters such as string or int etc, but when pass a complex parameter to the test method, for example, pass a array parameter, then it will not show well in the testng report in Jenkins. It is just a suggestion. It will be better if this plugin can show the same with what the testng integrated report look likes. Screenshot is attached.
[JIRA] [copyartifact-plugin] (JENKINS-33257) Misleading warning "Unable to find project" in "Permission to Copy Artifact - Projects to allow copy artifacts"
Title: Message Title Rick Liu commented on JENKINS-33257 Re: Misleading warning "Unable to find project" in "Permission to Copy Artifact - Projects to allow copy artifacts" My downstream job is a freestyle project, but my upstream job is a multi-configuration matrix project. I'm not sure if that would make any differences. From Step 1~4 looks the same as mine, 4. Create a folder "FOLDER" 5. Create a freestyle project "DOWNSTREAM_PROJECT" in "FOLDER" 6. Create a multi-configuration matrix project "UPSTREAM_PROJECT" in "FOLDER" 7. In the configuration page of "UPSTREAM_PROJECT", check "Permission to Copy Artifact" 8. Put "DOWNSTREAM_PROJECT" to "projects to allow copy artifacts" Mine can't do the auto-completion. I'll also attach the list of current installed plugin and versions. 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] [packer-plugin] (JENKINS-33283) Packer plugin doesn't clean AWS resource when job is canceled
Title: Message Title Xueshan Feng created an issue Jenkins / JENKINS-33283 Packer plugin doesn't clean AWS resource when job is canceled Issue Type: Bug Assignee: Unassigned Components: packer-plugin Created: 03/Mar/16 3:46 AM Environment: Jenkins docker version: 1.642.2 Packer plugin version: 1.2 Priority: Minor Reporter: Xueshan Feng Canceling (Ctl-C) a Packer build that is not running as Jenkins plugin cleanup temporary resources. When a packer build job in Jenkins is canceled, it doesn't clean up temporary resources created - AWS keypairs, security groups, EC2 etc. One has to manually delete these resources. It would be nice to cleanup these automatically. Add Comment
[JIRA] [windows-slaves-plugin] (JENKINS-33282) Jenkins windows slave restarted our production server after a few hours
Title: Message Title Davis Liu updated an issue Jenkins / JENKINS-33282 Jenkins windows slave restarted our production server after a few hours Change By: Davis Liu Attachment: jenkins-slave.err.zip 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] [windows-slaves-plugin] (JENKINS-33282) Jenkins windows slave restarted our production server after a few hours
Title: Message Title Davis Liu updated an issue Jenkins / JENKINS-33282 Jenkins windows slave restarted our production server after a few hours Change By: Davis Liu Attachment: jenkins-slave.err.zip Attachment: image003.jpg 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] [label-linked-jobs-plugin] (JENKINS-32445) Make Label Linked Jobs plugin compatible with Jenkins Clouds definition
Title: Message Title Dominique Brice edited a comment on JENKINS-32445 Re: Make Label Linked Jobs plugin compatible with Jenkins Clouds definition I added two things that are visible:* on the labels dashboard, if there is at least one cloud defined in the Jenkins instance, each label has an indication to give the number of clouds which can provision it (see screenshot)* on the labels linked jobs, cloud(s) able to provision each label listed (atomic or composite) is/are listed (see screenshot)Provisioning clouds are also taken into account to determine the list of orphaned jobs on the dashboard. A snapshot plugin version is available [there|http://repo.jenkins-ci.org/snapshots/org/jenkins-ci/plugins/label-linked-jobs/5.0.1-SNAPSHOT/]. 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] [label-linked-jobs-plugin] (JENKINS-32445) Make Label Linked Jobs plugin compatible with Jenkins Clouds definition
Title: Message Title Dominique Brice edited a comment on JENKINS-32445 Re: Make Label Linked Jobs plugin compatible with Jenkins Clouds definition I added two things that are visible:* on the labels dashboard, if there is at least one cloud defined in the Jenkins instance, each label has an indication to give the number of clouds which can provision it (see screenshot)* on the labels linked jobs, cloud(s) able to provision each label listed (atomic or composite) is/are listed (see screenshot)Provisioning clouds are also taken into account to determine the list of orphaned jobs on the dashboard.A snapshot plugin version with this new feature is available [there|http://repo.jenkins-ci.org/snapshots/org/jenkins-ci/plugins/label-linked-jobs/5.0.1-SNAPSHOT/]. 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] [test1] (TEST-88) A test issue
Title: Message Title James Dumay created an issue test / TEST-88 A test issue Issue Type: Bug Assignee: Kohsuke Kawaguchi Components: test1 Created: 03/Mar/16 2:10 AM Labels: cloudbees Priority: Minor Reporter: James Dumay Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [test1] (TEST-87) A test issue
Title: Message Title James Dumay created an issue test / TEST-87 A test issue Issue Type: Bug Assignee: Kohsuke Kawaguchi Components: test1 Created: 03/Mar/16 2:09 AM Labels: cloudbees Priority: Minor Reporter: James Dumay Just testing an integration Add Comment
[JIRA] [github-oauth-plugin] (JENKINS-33258) Error on every Jenkins page: java.lang.RuntimeException: java.io.IOException: Server returned HTTP response code: 401 for URL: https://api.github.com/user
Title: Message Title Sam Gleske commented on JENKINS-33258 Re: Error on every Jenkins page: java.lang.RuntimeException: java.io.IOException: Server returned HTTP response code: 401 for URL: https://api.github.com/user Also, what changes to JENKINS_HOME did you 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-33258) Error on every Jenkins page: java.lang.RuntimeException: java.io.IOException: Server returned HTTP response code: 401 for URL: https://api.github.com/user
Title: Message Title Sam Gleske commented on JENKINS-33258 Re: Error on every Jenkins page: java.lang.RuntimeException: java.io.IOException: Server returned HTTP response code: 401 for URL: https://api.github.com/user What plugin versions are you using for: Icon Shim plugin Matrix authorization plugin Cloudbees folders plugin There was a recent release of those three plugins (an unfortunate staggered release) which threw authorization out of whack. Their versions should be: cloudbees-folder 5.2.2 icon-shim 2.0.3 matrix-auth 1.3.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] [label-linked-jobs-plugin] (JENKINS-32445) Make Label Linked Jobs plugin compatible with Jenkins Clouds definition
Title: Message Title Dominique Brice commented on JENKINS-32445 Re: Make Label Linked Jobs plugin compatible with Jenkins Clouds definition I added two things that are visible: on the labels dashboard, if there is at least one cloud defined in the Jenkins instance, each label has an indication to give the number of clouds which can provision it (see screenshot) on the labels linked jobs, cloud(s) able to provision each label listed (atomic or composite) is/are listed (see screenshot) Provisioning clouds are also taken into account to determine the list of orphaned jobs 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] [label-linked-jobs-plugin] (JENKINS-32445) Make Label Linked Jobs plugin compatible with Jenkins Clouds definition
Title: Message Title Dominique Brice updated an issue Jenkins / JENKINS-32445 Make Label Linked Jobs plugin compatible with Jenkins Clouds definition Change By: Dominique Brice Attachment: LabelLinkedJobs.png Attachment: Dashboard.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-33246) It is unclear that the items with ** are dependencies during plugin install on 2.0
Title: Message Title Christopher Orr commented on JENKINS-33246 Re: It is unclear that the items with ** are dependencies during plugin install on 2.0 I agree — I certainly found the dependency popup to be unnecessary. 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-33246) It is unclear that the items with ** are dependencies during plugin install on 2.0
Title: Message Title Christopher Orr edited a comment on JENKINS-33246 Re: It is unclear that the items with ** are dependencies during plugin install on 2.0 I agree — I certainly found the dependency popup tooltop to be unnecessary. 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] [copyartifact-plugin] (JENKINS-33257) Misleading warning "Unable to find project" in "Permission to Copy Artifact - Projects to allow copy artifacts"
Title: Message Title ikedam commented on JENKINS-33257 Re: Misleading warning "Unable to find project" in "Permission to Copy Artifact - Projects to allow copy artifacts" It sounds like a bug rather than a misleading behavior. Project names are expected to be treated relatively. But I can't reproduce the problem in my environment. Would you tell more detailed steps to reproduce the problem? Steps I tried (with Jenkins 1.642.1, cloudbees folder 5.1, copysrtifact 1.37) Lauch a newly installed Jenkins 1.642.1. Download and install Cloudbees Folder 5.1. It is not the latest and you can't get it from Manage Pkugins. Go to Manage Jenkins>Manage Pkugins and install Copyartifact 1.37. Create a folder "FOLDERNAME". Create a freestyle project "DOWNSTREAM_PROJECT_NAME" in FOLDERNAME. In the configuration page of DOWNSTREAM_PROJECT_NAME, check "Permission to Copy Artifact" Put DOWNSTREAM_PROJECT_NAME to "projects to allow copy artifacts" It can be input with the auto-completion. Result: No warnings are displayed. Add Comment
[JIRA] [analysis-core-plugin] (JENKINS-33210) EOFException when using Static Analysis Collector
Title: Message Title Ulli Hafner commented on JENKINS-33210 Re: EOFException when using Static Analysis Collector Ok, I tried to create a stripped down version of the config with a minimum of settings: http://pastebin.com/CPrEnxgQ Can you check if the error occurs here too? Then I can use it for a test on Ubuntu and Tomcat... Does the problem occur without using Tomcat? 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] [scm-sync-configuration-plugin] (JENKINS-25786) Renaming Job Causes a poisoned commitQueue
Title: Message Title David Cullen commented on JENKINS-25786 Re: Renaming Job Causes a poisoned commitQueue I use Gitlab, and I have to fix this by Uninstalling the "SCM Sync Configuration Plugin" Restarting Jenkins sudo su - tomcat7 pushd .jenkins rm -fr scm-sync-configuration* Restarting Jenkins Renaming the repository on GitLab Creating a new repository on GitLab with the original name Re-installing the "SCM Sync Configuration Plugin" Configure the "SCM Sync Configuration Plugin" pushd scm-sync-configuration/checkoutConfiguration git remote add scm-sync-configuration-old git fetch scm-sync-configuration-old git merge scm-sync-configuration-old/master git remote remove scm-sync-configuration-old git branch --unset-upstream There is a mix of GitLab operations and shell commands and obviously I am using tomcat to run Jenkins. However, this might work for someone else, so I am putting the information here. Doing all of that preserves the history that I would normally lose. I wish there was a way to use Jenkins security to only allow copying repositories and block renaming.
[JIRA] [extensible-choice-parameter-plugin] (JENKINS-33254) Promoting Builds fail with: FATAL: Illegal choice:
Title: Message Title ikedam commented on JENKINS-33254 Re: Promoting Builds fail with: FATAL: Illegal choice: I have ever seen this situation, which turned out caused for broken and inconsistent configurations originally caused for JENKINS-27505 . JENKINS-27505 is an issue of Jenkins core, and fixed with Jenkins 1.639. It happens with a following case: You put an empty value on the top of choices. You select the empty value for the default value. (not with the "") You trigger the project automatically (like with SCM polling, or parameterized-trigger plugin). It happens in this way: When you open the system configuration page, the top empty value is removed for JENKINS-27505 . It can be removed from the configuration unintentionally when you save the system configuration. The project tries to launch with the empty value as it's configured as the default value. Throws an exception as the value isn't listed in choices. If it is your case: How to fix: Visit the system configuration page and add the empty value again. How to prevent reproduction: A. upgrade your Jenkins to the latest one. I recommend you to install a LTS version. B. add an empty choice to a place other than the topmost. You can list the same value twice. C. Make the parameter editable. It prevents exceptions even for values not listed in choices. . Add
[JIRA] [tfs-plugin] (JENKINS-33280) TFS Plugin 4.0.0 returning null for remote changesets
Title: Message Title
Mahitha Chalasani updated an issue
Jenkins / JENKINS-33280
TFS Plugin 4.0.0 returning null for remote changesets
Change By:
Mahitha Chalasani
TFS Plugin 4.0.0 gives and error while querying for the changeset. I get the same error for all projects built from this machine. Verified that TFS SDK for Java is installed with the plugin and also TEE CLC, though its marked as not required for the 4.0 version. The project is developed in XCode and stored in TFS using the git-tf plugin for Mac OSX. {code:java} created by Team Build Querying for remote changeset at '$/x/_git/' as of 'D2016-03-02T18:51:31Z'...Query returned no result!FATAL: nulljava.lang.NullPointerException at hudson.plugins.tfs.model.Project.extractChangesetNumber(Project.java:194) at hudson.plugins.tfs.model.Project.getRemoteChangesetVersion(Project.java:189) at hudson.plugins.tfs.model.Project.getRemoteChangesetVersion(Project.java:205) at hudson.plugins.tfs.TeamFoundationServerScm.recordWorkspaceChangesetVersion(TeamFoundationServerScm.java:262) at hudson.plugins.tfs.TeamFoundationServerScm.checkout(TeamFoundationServerScm.java:211) at hudson.model.AbstractProject.checkout(AbstractProject.java:1276) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:607) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:529) at hudson.model.Run.execute(Run.java:1738) at hudson.matrix.MatrixBuild.run(MatrixBuild.java:306) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:410)Finished: FAILURE {code}
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [tfs-plugin] (JENKINS-33280) TFS Plugin 4.0.0 returning null for remote changesets
Title: Message Title Mahitha Chalasani updated an issue Jenkins / JENKINS-33280 TFS Plugin 4.0.0 returning null for remote changesets Change By: Mahitha Chalasani TFS Plugin 4.0.0 gives and error while querying for the changeset. I get the same error for all projects built from this machine. Verified that TFS SDK for Java is installed with the plugin and also TEE CLC, though its marked as not required for the 4.0 version. The project is developed in XCode and stored in TFS using the git-tf plugin for Mac OSX. created by Team Build Querying for remote changeset at '$/x/_git/' as of 'D2016-03-02T18:51:31Z'...Query returned no result!FATAL: nulljava.lang.NullPointerException at hudson.plugins.tfs.model.Project.extractChangesetNumber(Project.java:194) at hudson.plugins.tfs.model.Project.getRemoteChangesetVersion(Project.java:189) at hudson.plugins.tfs.model.Project.getRemoteChangesetVersion(Project.java:205) at hudson.plugins.tfs.TeamFoundationServerScm.recordWorkspaceChangesetVersion(TeamFoundationServerScm.java:262) at hudson.plugins.tfs.TeamFoundationServerScm.checkout(TeamFoundationServerScm.java:211) at hudson.model.AbstractProject.checkout(AbstractProject.java:1276) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:607) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:529) at hudson.model.Run.execute(Run.java:1738) at hudson.matrix.MatrixBuild.run(MatrixBuild.java:306) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:410)Finished: FAILURE Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [ldap-plugin] (JENKINS-18961) LDAP plugin does not support nested groups
Title: Message Title Abhimanyu Bishnoi commented on JENKINS-18961 Re: LDAP plugin does not support nested groups Has there been any update on this issue? I have Jenkins 1.636 and i still see this exact issue. Please let me know how can this be fixed. I used LDAP plugin and our company use Oracle not Active Directory. 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] [tfs-plugin] (JENKINS-33280) TFS Plugin 4.0.0 returning null for remote changesets
Title: Message Title Mahitha Chalasani stopped work on JENKINS-33280 Change By: Mahitha Chalasani 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] [tfs-plugin] (JENKINS-33280) TFS Plugin 4.0.0 returning null for remote changesets
Title: Message Title Mahitha Chalasani started work on JENKINS-33280 Change By: Mahitha Chalasani 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] [tfs-plugin] (JENKINS-33280) TFS Plugin 4.0.0 returning null for remote changesets
Title: Message Title Mahitha Chalasani updated an issue Jenkins / JENKINS-33280 TFS Plugin 4.0.0 returning null for remote changesets Change By: Mahitha Chalasani Priority: Major Critical Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [tfs-plugin] (JENKINS-33280) TFS Plugin 4.0.0 returning null for remote changesets
Title: Message Title Mahitha Chalasani updated an issue Jenkins / JENKINS-33280 TFS Plugin 4.0.0 returning null for remote changesets Change By: Mahitha Chalasani Environment: TFS-Plugin 4.0.0, Team Foundation Server 2013, Jenkins 1.6. 33 38 , JRE 1.8, Mac OSX 10.11.3 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [shiningpanda-plugin] (JENKINS-16176) ShiningPanda PATH update uses wrong separator on Windows
Title: Message Title
Colin Bennett commented on JENKINS-16176
Re: ShiningPanda PATH update uses wrong separator on Windows
Here's a possible way to use Python itself for a cross-platform PATH workaround hack. Call this script with the name of the command to run with a corrected PATH:
python -c "import os; import sys; import subprocess; env=os.environ.copy(); badsep = {':': ';', ';': ':'}[os.pathsep]; env['PATH'] = env['PATH'].replace(badsep, os.pathsep); subprocess.call(sys.argv[1:], env=env)" python --version
# Replace "python --version" with any other command to run
This can be run on either Windows cmd.exe or a bash shell on Windows or Linux.
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-33281) Release Jenkins 2.0
Title: Message Title R. Tyler Croy created an issue Jenkins / JENKINS-33281 Release Jenkins 2.0 Issue Type: Task Assignee: Daniel Beck Components: core Created: 02/Mar/16 10:48 PM Labels: 2.0 Priority: Minor Reporter: R. Tyler Croy This is just a place-holder ticket to use to reference 2.0 Launch Marketing activities and other 2.0 release related tasks. I'm assigning to Daniel Beck since he is the 2.0 release manager to the best of my knowledge right now Add Comment
[JIRA] [core] (JENKINS-33246) It is unclear that the items with ** are dependencies during plugin install on 2.0
Title: Message Title Ulli Hafner commented on JENKINS-33246 Re: It is unclear that the items with ** are dependencies during plugin install on 2.0 I would rather not show the dependencies in the new dialog: the dialog is especially for new users, they might get confused if there are now a lot of additional things that are going to be installed. (It's ok in the old dialog). I also would recommend to remove the dependencies tooltip in the selection dialog (or use an explicit action to show the dependencies). 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-29762) Make inclusion of build and environment variables configurable
Title: Message Title gabe cee commented on JENKINS-29762 Re: Make inclusion of build and environment variables configurable Looks like we are getting some other community requests as well, this pull-request submitted to the github repository is trying to fix a similar issue with excluding variables: https://github.com/jenkinsci/logstash-plugin/pull/11 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-32567) Downgrade “termination trace” warnings in Jenkins logs
Title: Message Title Andrew Barber commented on JENKINS-32567 Re: Downgrade “termination trace” warnings in Jenkins logs Backed up to 1.642.1 from 1.642.2 and memory leak is gone. With 1.642.2 the leak doesn't show in the java console or in the monitor plugin. I only see it in the memory usage from the top command. Resident memory grows until the machine eventually runs out of physical and swap memory. Using java 1.7.0_79 on centos 5.9. 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] [shiningpanda-plugin] (JENKINS-16176) ShiningPanda PATH update uses wrong separator on Windows
Title: Message Title Colin Bennett commented on JENKINS-16176 Re: ShiningPanda PATH update uses wrong separator on Windows Look at this very similar bug JENKINS-14515 , especially this code change that uses toComputer(): 8b09f8bbff45...6f337351a745: -EnvVars vars = new EnvVars(); +EnvVars vars = node.toComputer().getEnvironment(); 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-32502) Upgrade HipChat Publisher to Support HipChat Plugin Version >= 1.x
Title: Message Title Ben Middleton commented on JENKINS-32502 Re: Upgrade HipChat Publisher to Support HipChat Plugin Version >= 1.x Ryan Erato I've submitted a PR to support this here: https://github.com/jenkinsci/job-dsl-plugin/pull/766 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] [shiningpanda-plugin] (JENKINS-16176) ShiningPanda PATH update uses wrong separator on Windows
Title: Message Title Colin Bennett commented on JENKINS-16176 Re: ShiningPanda PATH update uses wrong separator on Windows Weird – I am seeing an incorrect path in the converse way – there are semicolons getting inserted into the Linux slave's PATH. I have a Windows master and Linux slave. The PATH variable is set like this /usr/lib/jvm/java-7-openjdk-amd64/bin:/var/jenkins/workspace/testproject;/var/jenkins/shiningpanda/jobs/ef9d92b6/virtualenvs/4a2c09ff/bin;/var/jenkins/bin:/var/jenkins/bin/cmake-3.5.0-rc2-Linux-x86_64/bin:/usr/local/bin:/usr/bin:/bin 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-33280) TFS Plugin 4.0.0 returning null for remote changesets
Title: Message Title Mahitha Chalasani updated an issue Jenkins / JENKINS-33280 TFS Plugin 4.0.0 returning null for remote changesets Change By: Mahitha Chalasani Environment: TFS-Plugin 4.0.0, Team Foundation Server 2013, Jenkins 1.6.33, JRE 1.8, Mac OSX 10.11.3 TFS Plugin 4.0.0 gives and error while querying for the changeset. I get the same error for all projects built from Mac OSX 10 this machine . 11.3. Verified that TFS SDK is installed with the plugin and also TEE CLC, though its marked as not required for the 4.0 version. The project is developed in XCode and stored in TFS using the git-tf plugin for Mac OSX. created by Team Build Querying for remote changeset at '$/x/_git/' as of 'D2016-03-02T18:51:31Z'...Query returned no result!FATAL: nulljava.lang.NullPointerException at hudson.plugins.tfs.model.Project.extractChangesetNumber(Project.java:194) at hudson.plugins.tfs.model.Project.getRemoteChangesetVersion(Project.java:189) at hudson.plugins.tfs.model.Project.getRemoteChangesetVersion(Project.java:205) at hudson.plugins.tfs.TeamFoundationServerScm.recordWorkspaceChangesetVersion(TeamFoundationServerScm.java:262) at hudson.plugins.tfs.TeamFoundationServerScm.checkout(TeamFoundationServerScm.java:211) at hudson.model.AbstractProject.checkout(AbstractProject.java:1276) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:607) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:529) at hudson.model.Run.execute(Run.java:1738) at hudson.matrix.MatrixBuild.run(MatrixBuild.java:306) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:410)Finished: FAILURE Add Comment
[JIRA] [tfs-plugin] (JENKINS-33280) TFS Plugin 4.0.0 returning null for remote changesets
Title: Message Title Mahitha Chalasani created an issue Jenkins / JENKINS-33280 TFS Plugin 4.0.0 returning null for remote changesets Issue Type: Bug Assignee: redsolo Components: tfs-plugin Created: 02/Mar/16 10:12 PM Environment: TFS-Plugin 4.0.0, Team Foundation Server 2013, Priority: Major Reporter: Mahitha Chalasani TFS Plugin 4.0.0 gives and error while querying for the changeset. I get the same error for all projects built from Mac OSX 10.11.3. Verified that TFS SDK is installed with the plugin and also TEE CLC, though its marked as not required for the 4.0 version. The project is developed in XCode and stored in TFS using the git-tf plugin for Mac OSX. created by Team Build Querying for remote changeset at '$/x/_git/' as of 'D2016-03-02T18:51:31Z'... Query returned no result! FATAL: null java.lang.NullPointerException at hudson.plugins.tfs.model.Project.extractChangesetNumber(Project.java:194) at hudson.plugins.tfs.model.Project.getRemoteChangesetVersion(Project.java:189) at hudson.plugins.tfs.model.Project.getRemoteChangesetVersion(Project.java:205) at hudson.plugins.tfs.TeamFoundationServerScm.recordWorkspaceChangesetVersion(TeamFoundationServerScm.java:262) at hudson.plugins.tfs.TeamFoundationServerScm.checkout(TeamFoundationServerScm.java:211) at hudson.model.AbstractProject.checkout(AbstractProject.java:1276) at
[JIRA] [poll-mailbox-trigger-plugin] (JENKINS-32966) Poll mail box plugin is not able to read the mail box of office365 but able to connect
Title: Message Title Nick Grealy closed an issue as Fixed Not a problem, thanks for the feedback! Jenkins / JENKINS-32966 Poll mail box plugin is not able to read the mail box of office365 but able to connect Change By: Nick Grealy 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] [docker-build-publish-plugin] (JENKINS-33278) Expecting 64-char full image ID
Title: Message Title
Martin Achtman updated an issue
Jenkins / JENKINS-33278
Expecting 64-char full image ID
Change By:
Martin Achtman
After upgrading docker-engine from 1.9.1 to 1.10.2 we encountered the same Docker ID problem as in issue [https://issues.jenkins-ci.org/browse/JENKINS-32792] even tough we've upgraded docker-commons to version 1.3.1:Output from docker inspect:{code:java} # $ docker inspect mybuild --type=image --format='{{json .Id }}' 598d0def97f1 [{ " Id" sha256 : 598d0def97f180366008bcddbf0a4ed5267b35d0a876c0f867fc38c7adb041e3 " 444009eaa9716873d0c57add83e1df3639181faca9edd8797cd120cc7eed7309", "Created": "2016-03-02T15:02:13.051405584Z", "Path": "/bin/tini",{code:java} Error msg: {code:java} Status: Image is up to date for mongo:latest ---> 598d0def97f1Successfully built 598d0def97f1[database] $ docker inspect 598d0def97f1ERROR: Build step failed with exceptionjava.lang.IllegalArgumentException: Expecting 64-char full image ID, but got at org.jenkinsci.plugins.docker.commons.fingerprint.DockerFingerprints.getFingerprintHash(DockerFingerprints.java:71) at org.jenkinsci.plugins.docker.commons.fingerprint.DockerFingerprints.forDockerInstance(DockerFingerprints.java:147) at org.jenkinsci.plugins.docker.commons.fingerprint.DockerFingerprints.forImage(DockerFingerprints.java:114) at org.jenkinsci.plugins.docker.commons.fingerprint.DockerFingerprints.forImage(DockerFingerprints.java:99) at org.jenkinsci.plugins.docker.commons.fingerprint.DockerFingerprints.addFromFacet(DockerFingerprints.java:259) at com.cloudbees.dockerpublish.DockerBuilder$Perform.processFingerprints(DockerBuilder.java:490) at com.cloudbees.dockerpublish.DockerBuilder$Perform.buildAndTag(DockerBuilder.java:364) at com.cloudbees.dockerpublish.DockerBuilder$Perform.exec(DockerBuilder.java:294) at com.cloudbees.dockerpublish.DockerBuilder$Perform.access$100(DockerBuilder.java:274) at com.cloudbees.dockerpublish.DockerBuilder.perform(DockerBuilder.java:245) at org.jenkinsci.plugins.conditionalbuildstep.BuilderChain.perform(BuilderChain.java:71) at org.jenkins_ci.plugins.run_condition.BuildStepRunner$2.run(BuildStepRunner.java:110) at org.jenkins_ci.plugins.run_condition.BuildStepRunner$Fail.conditionalRun(BuildStepRunner.java:154) at org.jenkins_ci.plugins.run_condition.BuildStepRunner.perform(BuildStepRunner.java:105) at org.jenkinsci.plugins.conditionalbuildstep.ConditionalBuilder.perform(ConditionalBuilder.java:133) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:782) at hudson.model.Build$BuildExecution.build(Build.java:205) at hudson.model.Build$BuildExecution.doRun(Build.java:162) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:534) at hudson.model.Run.execute(Run.java:1738) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:410){code}
[JIRA] [matrix-auth-plugin] (JENKINS-9774) Enabling "Project Matrix Authorization Strategy" without checking any permissions causes config.xml parsing to fail
Title: Message Title Raghavendra Tallam commented on JENKINS-9774 Re: Enabling "Project Matrix Authorization Strategy" without checking any permissions causes config.xml parsing to fail I faced the same issue. I tried to Update the Plugin along with Some other Plugins uninstalls. So, I Deleted the DISABLED files in Plugins Folder and Restarted my Jenkins Instance. Jenkins Loaded like a Charm.. 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-33258) Error on every Jenkins page: java.lang.RuntimeException: java.io.IOException: Server returned HTTP response code: 401 for URL: https://api.github.com/user
Title: Message Title Leandro Lucarella commented on JENKINS-33258 Re: Error on every Jenkins page: java.lang.RuntimeException: java.io.IOException: Server returned HTTP response code: 401 for URL: https://api.github.com/user It looks like there's a browser component on this issue, it works fine on a private window and a browser restart fixed it. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [github-branch-source-plugin] (JENKINS-33256) Re-enable GitHub PR support for public repos
Title: Message Title Manuel Jesús Recena Soto commented on JENKINS-33256 Re: Re-enable GitHub PR support for public repos Andrew Bayer My initial proposal was to consider both private and public repos. In fact, thus is in 1.2. Anyway I'm sure we can find a better solutions. Thanks for your feedback. 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-32567) Downgrade “termination trace” warnings in Jenkins logs
Title: Message Title Andrew Barber commented on JENKINS-32567 Re: Downgrade “termination trace” warnings in Jenkins logs We experienced a memory leak after upgrading to a version with this patch. We had been seeing ~600MB daily log file size with these warnings present, but after the change we see unbounded growth in the memory footprint of java. Has anyone else noticed this? It might not be evident if the warning wasn't happening that often. 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] [js-modules] (JENKINS-32319) Republish all NPM packages into a "jenkins-cd" NPM scope
Title: Message Title
Tom FENNELLY updated an issue
Jenkins / JENKINS-32319
Republish all NPM packages into a "jenkins-cd" NPM scope
Change By:
Tom FENNELLY
(this isn't anything to do with "core" component, but nothing else is appropriate either)I already subscribed to capture the [jenkins-cd|https://www.npmjs.com/org/jenkins-cd] organisation on the central registry ("jenkins-ci" was not available because of a username of the same).At the moment, all packages are published under my account (tfennelly), which is not what we want. This will allow me and others to publish packages under a community owned scope via this org. h1. TODO* js-modules (done)* js-builder (done)* js-test (done)* js-samples* js-libs
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] [js-modules] (JENKINS-32319) Republish all NPM packages into a "jenkins-cd" NPM scope
Title: Message Title Tom FENNELLY commented on JENKINS-32319 Re: Republish all NPM packages into a "jenkins-cd" NPM scope I've done this for the following modules: js-modules js-builder js-test 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] [extensible-choice-parameter-plugin] (JENKINS-33254) Promoting Builds fail with: FATAL: Illegal choice:
Title: Message Title Stephen Nichols commented on JENKINS-33254 Re: Promoting Builds fail with: FATAL: Illegal choice: Oleg, Thanks for looking into it. config.xml is now attached. 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] [extensible-choice-parameter-plugin] (JENKINS-33254) Promoting Builds fail with: FATAL: Illegal choice:
Title: Message Title Stephen Nichols updated an issue Jenkins / JENKINS-33254 Promoting Builds fail with: FATAL: Illegal choice: Change By: Stephen Nichols Attachment: config.xml 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-branch-source-plugin] (JENKINS-33256) Re-enable GitHub PR support for public repos
Title: Message Title Andrew Bayer commented on JENKINS-33256 Re: Re-enable GitHub PR support for public repos And fwiw, I like the idea of being able to say "just use the Jenkinsfile from the target branch" without worrying about who the author is in most cases. Obviously, for PRs with legit changes to the Jenkinsfile, that's a bit different, but the majority of use cases, etc. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [github-branch-source-plugin] (JENKINS-33256) Re-enable GitHub PR support for public repos
Title: Message Title Andrew Bayer commented on JENKINS-33256 Re: Re-enable GitHub PR support for public repos Nah, it's definitely a bug, albeit one introduced for good reasons. =) Putting aside github.com public repo use cases, GitHub Enterprise behind-the-firewall use cases are basically all now broken, and "public" behind-the-firewall repos are basically equivalent to github.com private repos, so they shouldn't be restricted, IMO. 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] [conditional-buildstep-plugin] (JENKINS-33264) Please make this plugin available in the post-build action
Title: Message Title Lior Goikhburg commented on JENKINS-33264 Re: Please make this plugin available in the post-build action Thanks Dominik Bartholdi , the flexible publish plugin + any buildstep suit my needs perfectly! 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] [bitbucket-build-status-notifier-plugin] (JENKINS-33276) Build status is not being set for commit in bitbucket
Title: Message Title
Lior Goikhburg edited a comment on JENKINS-33276
Re: Build status is not being set for commit in bitbucket
Hey [~amansilla] I figured out what's causing this.I have a global variable (that I inject before SCM) configured in the repo name url such as: {noformat} Repository URL: g...@bitbucket.org:my_team/${PROJECT}.git{noformat}I guess that the plugin cannot expand that variable and proceeds to notify the repo by {noformat}my_team/${PROJECT}{noformat} name.When I change the variable to a real repo name - the plugin works like a charm.
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-33184) JobDSL plugin requires build-publisher plugin to use discardOldBuilds
Title: Message Title Benjamin van den Berg commented on JENKINS-33184 Re: JobDSL plugin requires build-publisher plugin to use discardOldBuilds Yes, the logRotator is what I should be using instead. Many 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] [job-dsl-plugin] (JENKINS-33184) JobDSL plugin requires build-publisher plugin to use discardOldBuilds
Title: Message Title Benjamin van den Berg closed an issue as Not A Defect See comments. I should have been using the logRotator top-level component from the DSL. Jenkins / JENKINS-33184 JobDSL plugin requires build-publisher plugin to use discardOldBuilds Change By: Benjamin van den Berg Status: Resolved Closed Assignee: Daniel Spilker Benjamin van den Berg 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] [bitbucket-build-status-notifier-plugin] (JENKINS-33276) Build status is not being set for commit in bitbucket
Title: Message Title
Lior Goikhburg edited a comment on JENKINS-33276
Re: Build status is not being set for commit in bitbucket
Hey [~amansilla] I figured out what's causing this.I have a global variable (that I inject before SCM) in the repo name such as: {noformat}g...@bitbucket.org:my_team/${PROJECT}.git{noformat}I guess that the plugin cannot expand that variable and proceeds to notify the repo by {noformat}my_team/${PROJECT}{noformat} repo name .When I change the variable to a real repo name - the plugin works like a charm.
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] [throttle-concurrent-builds-plugin] (JENKINS-33279) Concurrent builds in queue cause jenkins to use 300+%CPU
Title: Message Title Marek Włodarczyk created an issue Jenkins / JENKINS-33279 Concurrent builds in queue cause jenkins to use 300+%CPU Issue Type: Bug Assignee: Oleg Nenashev Components: throttle-concurrent-builds-plugin Created: 02/Mar/16 5:12 PM Environment: Ubuntu 14.04 amd64 javaThrottle Concurrent Builds Plug-in 1.8.4 Jenkins ver. 1.625.2 Java(TM) SE Runtime Environment (build 1.8.0_66-b17) Priority: Minor Reporter: Marek Włodarczyk Hi, while there are regular builds in queue jenkins uses around 10-20% CPU, but when there are builds blocked by throttle concurrent builds plugin, then CPU goes to 200-400% and website is very slow. System Properties Name ↓ Value awt.toolkit sun.awt.X11.XToolkit executable-war /usr/share/jenkins/jenkins.war file.encoding UTF-8 file.encoding.pkg sun.io file.separator / hudson.diyChunking true java.awt.graphicsenv sun.awt.X11GraphicsEnvironment java.awt.headless true java.awt.printerjob sun.print.PSPrinterJob java.class.path /usr/share/jenkins/jenkins.war java.class.version 52.0 java.endorsed.dirs /usr/lib/jvm/java-8-oracle/jre/lib/endorsed java.ext.dirs /usr/lib/jvm/java-8-oracle/jre/lib/ext:/usr/java/packages/lib/ext java.home /usr/lib/jvm/java-8-oracle/jre java.io.tmpdir /tmp java.library.path /usr/java/packages/lib/amd64:/usr/lib64:/lib64:/lib:/usr/lib
[JIRA] [bitbucket-build-status-notifier-plugin] (JENKINS-33276) Build status is not being set for commit in bitbucket
Title: Message Title
Lior Goikhburg commented on JENKINS-33276
Re: Build status is not being set for commit in bitbucket
Hey Antonio Mansilla I figured out what's causing this. I have a global variable (that I inject before SCM) in the repo name such as: g...@bitbucket.org:my_team/$ {PROJECT}.git. I guess that the plugin cannot expand that variable and proceeds to notify the repo by my_team/${PROJECT}
repo. When I change the variable to a real repo name - the plugin works like a charm.
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] [bitbucket-build-status-notifier-plugin] (JENKINS-33276) Build status is not being set for commit in bitbucket
Title: Message Title
Lior Goikhburg edited a comment on JENKINS-33276
Re: Build status is not being set for commit in bitbucket
Hey [~amansilla] I figured out what's causing this.I have a global variable (that I inject before SCM) in the repo name such as: {noformat} g...@bitbucket.org:my_team/${PROJECT}.git . {noformat} I guess that the plugin cannot expand that variable and proceeds to notify the repo by {noformat} my_team/${PROJECT} {noformat} repo.When I change the variable to a real repo name - the plugin works like a charm.
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] [bitbucket-build-status-notifier-plugin] (JENKINS-33276) Build status is not being set for commit in bitbucket
Title: Message Title Lior Goikhburg commented on JENKINS-33276 Re: Build status is not being set for commit in bitbucket The job name is "test". Regarding fixing the code myself, well, that has a very low chance of success considering me not knowing Java 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-branch-source-plugin] (JENKINS-33272) GitHub-specific SCMFileSystem
Title: Message Title Manuel Jesús Recena Soto edited a comment on JENKINS-33272 Re: GitHub-specific SCMFileSystem [~jglick] My english failed, I'm sorry. I understand the issue. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [github-branch-source-plugin] (JENKINS-33272) GitHub-specific SCMFileSystem
Title: Message Title Manuel Jesús Recena Soto commented on JENKINS-33272 Re: GitHub-specific SCMFileSystem Jesse Glick My english failed, I'm sorry. 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-branch-source-plugin] (JENKINS-33272) GitHub-specific SCMFileSystem
Title: Message Title Manuel Jesús Recena Soto commented on JENKINS-33272 Re: GitHub-specific SCMFileSystem Jesse Glick I don't understand this issue. Currently we are using GitHub API to detect if Jenkinsfile exists in a branch or in a pull request. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-30749) Jenkins should be secure out of the box by default
Title: Message Title Keith Zantow updated an issue Jenkins / JENKINS-30749 Jenkins should be secure out of the box by default Change By: Keith Zantow The default setup is of jenkins should be secure out-of-the-box and the admin must change it to be insecure if they desire.* Things like listen on localhost only (for http/https/ssh/cli etc)* ship with jenkins own security realm by default without allow users to sign up and a single admin user pre-defined.* Force password expiry on the local user database (to ensure the password is changed at first login)* Local user database should be able to support locking accounts (to prevent brute force attacks) See also: [Design|https://docs.google.com/document/d/1kD3xVoarOaHPEs1yi1VaES12Ksca_NKRNYA3MDsdu_k] 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] [stashnotifier-plugin] (JENKINS-32817) stashnotifier-plugin credentials are broken
Title: Message Title Stuart Beard commented on JENKINS-32817 Re: stashnotifier-plugin credentials are broken Experiencing the same issue on a Ubuntu instance. Other plugins on the 'Configure System' page are able to select credentials from a drop down 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] [stashnotifier-plugin] (JENKINS-32817) stashnotifier-plugin credentials are broken
Title: Message Title Stuart Beard updated an issue Jenkins / JENKINS-32817 stashnotifier-plugin credentials are broken Change By: Stuart Beard Environment: Windows, Java7 or Java8 , Ubuntu 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] [bitbucket-build-status-notifier-plugin] (JENKINS-33276) Build status is not being set for commit in bitbucket
Title: Message Title Antonio Mansilla commented on JENKINS-33276 Re: Build status is not being set for commit in bitbucket Hi Lior Goikhburg I just remembered some guy had a similar issue because long job names. Can you please report the job name you are having this issue with? Thx 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-build-publish-plugin] (JENKINS-33278) Expecting 64-char full image ID
Title: Message Title
Martin Achtman created an issue
Jenkins / JENKINS-33278
Expecting 64-char full image ID
Issue Type:
Bug
Assignee:
Carlos Sanchez
Components:
docker-build-publish-plugin
Created:
02/Mar/16 4:27 PM
Environment:
Jenkins: 1.642.2 docker-commons: 1.3.1 docker-build-publish: 1.2 OS: debian jessie 8.3 docker-engine 1.10.2 docker-compose 1.5.2
Labels:
plugin
Priority:
Major
Reporter:
Martin Achtman
After upgrading docker-engine from 1.9.1 to 1.10.2 we encountered the same Docker ID problem as in issue https://issues.jenkins-ci.org/browse/JENKINS-32792 even tough we've upgraded docker-commons to version 1.3.1: Output from docker inspect:
#docker inspect mybuild --type=image --format='{{json }}'
[
{
"Id": "444009eaa9716873d0c57add83e1df3639181faca9edd8797cd120cc7eed7309",
"Created": "2016-03-02T15:02:13.051405584Z",
"Path": "/bin/tini",
{code:java}
Error msg:
[JIRA] [git-server-plugin] (JENKINS-25264) Scriptler add script fails with java.io.IOException: failed to update git repo
Title: Message Title Sagayaraj David commented on JENKINS-25264 Re: Scriptler add script fails with java.io.IOException: failed to update git repo After adding a new scriptler script, we get the errr 'failed to update git repo', however the JENKINS_HOME/scripler/scripts and scriptler.xml are updated with the file. Not sure what is causing the issue. Please prioritize and 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] [git-server-plugin] (JENKINS-25264) Scriptler add script fails with java.io.IOException: failed to update git repo
Title: Message Title Sagayaraj David commented on JENKINS-25264 Re: Scriptler add script fails with java.io.IOException: failed to update git repo Yes. This error is available on GIT server 1.6 as well. java.io.IOException: failed to update git repo at org.jenkinsci.plugins.scriptler.ScriptlerManagement.commitFileToGitRepo(ScriptlerManagement.java:299) at org.jenkinsci.plugins.scriptler.ScriptlerManagement.saveScriptAndForward(ScriptlerManagement.java:274) at org.jenkinsci.plugins.scriptler.ScriptlerManagement.doScriptAdd(ScriptlerManagement.java:249) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) I tried to test it with fresh installation without any jobs in place. In which scriptler - new script addition was working good. However with having old data in JENKINS_HOME, the error continues to come. Dont have any clue from the error log 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] [ivy-plugin] (JENKINS-33277) ivy plugin triggers build although module does not longer exist (whith this name)
Title: Message Title
Christian Bitschnau updated an issue
Jenkins / JENKINS-33277
ivy plugin triggers build although module does not longer exist (whith this name)
Change By:
Christian Bitschnau
One ivy-build job can build multiple ivy modules that are located in one git repository:{ { noformat} repository/├── Module A/│ ├── src/...│ ├── build.xml│ └── ivy.xml├── Module B/│ ├── src/...│ ├── build.xml│ └── ivy.xml├── Module C/│ ├── src/...│ ├── build.xml│ └── ivy.xml└── ... {noformat } } If one of the modules is removed from resp. renamed in the repository, the ivy plugin continues to trigger builds. These builds fail with "FATAL: Unable to find build script at...", as the module does not exist any more (at this location).Current workaround: delete the module directory under $JENKINS_HOME$/jobs//modules/ and restarting jenkins resp. "Reload Configuration from Disk"
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] [ivy-plugin] (JENKINS-33224) mask-passwords plugin does not mask in ivy-project's modules
Title: Message Title
Christian Bitschnau updated an issue
Jenkins / JENKINS-33224
mask-passwords plugin does not mask in ivy-project's modules
Change By:
Christian Bitschnau
When I build a project (Ivy-project), that contains multiple ivy-modules, with the following settings:{ { noformat} Ivy xml files: */ivy.xml...Ant BuilderProperties: deploytarget.user.pwd=${artifactory_jenkins_pwd} # injected by mask-passwords (global password)...x Incremental build - only build changed modulesx Build modules as separate jobs...BuildEnvironmentx Mask passwords (and enable global passwords) {noformat } } the passwords are not masked in the buildlog. They are shown in plain text in the line of the Ant-call.When I have multiple Jobs, that build the modules directly, the passwords are masked 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] [multijob-plugin] (JENKINS-31527) multijob plugin throws NPE
Title: Message Title James Femia commented on JENKINS-31527 Re: multijob plugin throws NPE I also encounter this issue in 1.20 and 1.18 when using the "Build only if SCM changes" option on a phase job, if the job referenced by that phase job is already 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] [ivy-plugin] (JENKINS-33277) ivy plugin triggers build although module does not longer exist (whith this name)
Title: Message Title
Christian Bitschnau updated an issue
Jenkins / JENKINS-33277
ivy plugin triggers build although module does not longer exist (whith this name)
Change By:
Christian Bitschnau
One ivy-build job can build multiple ivy modules that are located in one git repository: {{ repository/├── Module A/│ ├── src/...│ ├── build.xml│ └── ivy.xml├── Module B/│ ├── src/...│ ├── build.xml│ └── ivy.xml├── Module C/│ ├── src/...│ ├── build.xml│ └── ivy.xml└── ... }} If one of the modules is removed from resp. renamed in the repository, the ivy plugin continues to trigger builds. These builds fail with "FATAL: Unable to find build script at...", as the module does not exist any more (at this location).Current workaround: delete the module directory under $JENKINS_HOME$/jobs//modules/ and restarting jenkins resp. "Reload Configuration from Disk"
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] [ivy-plugin] (JENKINS-33277) ivy plugin triggers build although module does not longer exist (whith this name)
Title: Message Title Christian Bitschnau created an issue Jenkins / JENKINS-33277 ivy plugin triggers build although module does not longer exist (whith this name) Issue Type: Bug Assignee: Timothy Bingaman Components: ivy-plugin Created: 02/Mar/16 4:01 PM Environment: Jenkins (1.642.1), mask-passwords (2.8), ivy (1.26) Labels: ivy trigger Priority: Major Reporter: Christian Bitschnau One ivy-build job can build multiple ivy modules that are located in one git repository: repository/ ├── Module A/ │ ├── src/... │ ├── build.xml │ └── ivy.xml ├── Module B/ │ ├── src/... │ ├── build.xml │ └── ivy.xml ├── Module C/ │ ├── src/... │ ├── build.xml │ └── ivy.xml └── ... If one of the modules is removed from resp. renamed in the repository, the ivy plugin continues to trigger builds. These builds fail with "FATAL: Unable to find build script at...", as the module does not exist any more (at this location). Current workaround: delete
[JIRA] [core] (JENKINS-24352) Unneccessary line breaks in JUnit test results table since 1.576
Title: Message Title Keith Zantow closed an issue as Fixed Jenkins / JENKINS-24352 Unneccessary line breaks in JUnit test results table since 1.576 Change By: Keith Zantow Status: In Progress 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] [branch-api-plugin] (JENKINS-33106) CustomOrganizationFolderDescriptor does not work after a dynamic installation
Title: Message Title Patrick Wolf assigned an issue to Manuel Jesús Recena Soto Jenkins / JENKINS-33106 CustomOrganizationFolderDescriptor does not work after a dynamic installation Change By: Patrick Wolf 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] [bitbucket-build-status-notifier-plugin] (JENKINS-33276) Build status is not being set for commit in bitbucket
Title: Message Title Antonio Mansilla commented on JENKINS-33276 Re: Build status is not being set for commit in bitbucket Hi Lior Goikhburg, first thank you for reporting the issue. Currently I don't have too much time to take a look to this, so maybe you could clone the repository, deep into the code and try identify what is exactly the problem, that'd be fine at first. 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] [jira-plugin] (JENKINS-32560) jira-plugin generating message in the wrong ticket
Title: Message Title David Brown commented on JENKINS-32560 Re: jira-plugin generating message in the wrong ticket We are seeing two different formats to the message. A valid message has multiple lines including the JIRA reference, commit comments and changeset details. Incorrect (misleading) messages contain a single line “SUCCESS: Integrated in PROJECT #BuildNum”. The following image shows a good followed by a bad message as seen on a single JIRA ticket: We are using Jenkins version 1.598, JIRA Version v6.3.15 and JIRA plugin version 1.38. Can someone please confirm whether this is a known issue? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jira-plugin] (JENKINS-32560) jira-plugin generating message in the wrong ticket
Title: Message Title David Brown updated an issue Jenkins / JENKINS-32560 jira-plugin generating message in the wrong ticket Change By: David Brown Attachment: screenshot-1.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] [jira-plugin] (JENKINS-32560) jira-plugin generating message in the wrong ticket
Title: Message Title David Brown commented on JENKINS-32560 Re: jira-plugin generating message in the wrong ticket Thank you for your update, Alexei Znamensky. 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-branch-source-plugin] (JENKINS-33256) Re-enable GitHub PR support for public repos
Title: Message Title Manuel Jesús Recena Soto commented on JENKINS-33256 Re: Re-enable GitHub PR support for public repos I don't think this is a 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] [bitbucket-build-status-notifier-plugin] (JENKINS-33276) Build status is not being set for commit in bitbucket
Title: Message Title Lior Goikhburg commented on JENKINS-33276 Re: Build status is not being set for commit in bitbucket Key and Secret credentials are accepted without error in job configuration 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] [bitbucket-build-status-notifier-plugin] (JENKINS-33276) Build status is not being set for commit in bitbucket
Title: Message Title Lior Goikhburg commented on JENKINS-33276 Re: Build status is not being set for commit in bitbucket Bitbucket account and Jenkins was configured according to documentation. Anything I can do to help troubleshoot this issue ? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [bitbucket-build-status-notifier-plugin] (JENKINS-33276) Build status is not being set for commit in bitbucket
Title: Message Title Antonio Mansilla updated an issue Jenkins / JENKINS-33276 Build status is not being set for commit in bitbucket Change By: Antonio Mansilla Issue Type: New Feature 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] [bitbucket-build-status-notifier-plugin] (JENKINS-33276) Build status is not being set for commit in bitbucket
Title: Message Title Lior Goikhburg created an issue Jenkins / JENKINS-33276 Build status is not being set for commit in bitbucket Issue Type: New Feature Assignee: Antonio Mansilla Components: bitbucket-build-status-notifier-plugin Created: 02/Mar/16 3:32 PM Priority: Major Reporter: Lior Goikhburg The plugin doesn't set the status: According to the job log - everything is fine: Sending build status INPROGRESS for commit 915809121478ace3d92e52bbb2769f03f26cbfa9 to BitBucket is done! Sending build status SUCCESSFUL for commit 915809121478ace3d92e52bbb2769f03f26cbfa9 to BitBucket is done! Plugin log: Mar 02, 2016 6:23:46 PM INFO org.jenkinsci.plugins.bitbucket.BitbucketBuildStatusNotifier prebuild Bitbucket notify on start Mar 02, 2016 6:23:46 PM INFO org.jenkinsci.plugins.bitbucket.BitbucketBuildStatusNotifier notifyBuildStatus This response was received: Mar 02, 2016 6:23:47 PM INFO org.jenkinsci.plugins.bitbucket.BitbucketBuildStatusNotifier prebuild Bitbucket notify on start succeeded Mar 02, 2016 6:23:47 PM INFO org.jenkinsci.plugins.bitbucket.BitbucketBuildStatusNotifier perform Bitbucket notify on finish Mar 02, 2016 6:23:47 PM INFO org.jenkinsci.plugins.bitbucket.BitbucketBuildStatusNotifier notifyBuildStatus This response was
[JIRA] [core] (JENKINS-22051) build.xml not created after successful build
Title: Message Title Daniel Beck commented on JENKINS-22051 Re: build.xml not created after successful build The current UI does no longer allow you to disable plugins that are a dependency of other plugins, so that should take care of most of the problems due to exceptions as in the initial post. 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-22051) build.xml not created after successful build
Title: Message Title Paul Bakker edited a comment on JENKINS-22051 Re: build.xml not created after successful build For example some references to cases that involve builds getting lost: JENKINS-17265, JENKINS-15156 and JENKINS-11938 (all closed as not reproducible) Just google for "jenkins build lost" and you see how common a problem this is.I had the same thing happening, started comparing builds that did remain and didn't remain after a restart and saw that the onces that remained had a build.xml in the build directory and the other ones didn't.That triggered me to search on that and found this case. I looked at my setup and indeed the Maven Integration plugin was disabled. Once enabled again the build.xml is written again 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-22051) build.xml not created after successful build
Title: Message Title Paul Bakker commented on JENKINS-22051 Re: build.xml not created after successful build For example some references to cases that involve builds getting lost: JENKINS-17265 , JENKINS-15156 and JENKINS-11938 Just google for "jenkins build lost" and you see how common a problem this is. I had the same thing happening, started comparing builds that did remain and didn't remain after a restart and saw that the onces that remained had a build.xml in the build directory and the other ones didn't. That triggered me to search on that and found this case. I looked at my setup and indeed the Maven Integration plugin was disabled. Once enabled again the build.xml is written again 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-33275) Job DSL integration with ComputedFolder
Title: Message Title Jesse Glick created an issue Jenkins / JENKINS-33275 Job DSL integration with ComputedFolder Issue Type: New Feature Assignee: Daniel Spilker Components: job-dsl-plugin Created: 02/Mar/16 2:55 PM Labels: multibranch Priority: Major Reporter: Jesse Glick ComputedFolder in the cloudbees-folder plugin defines a folder whose children are computed by some process. Currently it is used only for organization folders, but it would be natural to integrate it with the Job DSL plugin: the definition of the folder would include the DSL script (or a link to its location), and the script would have some way of expressing the enumeration of child items. Folder recomputation would rerun the script, on demand or on a schedule. Child items would be view-only. Add Comment
[JIRA] [branch-api-plugin] (JENKINS-33274) "Base build" link for first build of branch project
Title: Message Title Jesse Glick created an issue Jenkins / JENKINS-33274 "Base build" link for first build of branch project Issue Type: Improvement Assignee: stephenconnolly Components: branch-api-plugin Created: 02/Mar/16 2:51 PM Labels: api Priority: Major Reporter: Jesse Glick The first build of a branch project should have a UI link like Previous Build but pointing to the build on the project corresponding to the base branch (such as master for Git) which its SCM revision links to. Should use SCMSource.parentHeads; major SCM plugins needs to implement this API. When present, the base build should be used as a baseline for determining the SCM changelog, so that a user can see the changes made in the SCM commit initiating a branch. An API should also be introduced to core so that plugins such as junit can use this backlink rather than previousBuild for purposes of comparing test results; the same could be true of static analysis, code coverage, etc. Merely changing Run.getPreviousBuild to return a build from another Job is unsafe; many plugins may assume that the Job pairs match, or that getNextBuild is the inverse operation, etc. Perhaps we need an API addition to Run such as /** * Gets
[JIRA] [workflow-plugin] (JENKINS-33273) Optimize Jenkinsfile loading and branch detection
Title: Message Title Jesse Glick created an issue Jenkins / JENKINS-33273 Optimize Jenkinsfile loading and branch detection Issue Type: Improvement Assignee: Jesse Glick Components: workflow-plugin Created: 02/Mar/16 2:38 PM Labels: multibranch api Priority: Major Reporter: Jesse Glick Currently if use the Git branch source, your repository gets cloned three times: Once to determine the head revision of the branch. Once to load Jenkinsfile. Once when you checkout scm as part of your build. (Normally once. Could be multiple times, or even zero.) This could be a performance issue for large repositories. What we would rather do in the second step is use SCMFileSystem to locate Jenkinsfile. Unfortunately this is not currently implemented in any of the current scm-api clients (git, subversion, mercurial,
[JIRA] [github-branch-source-plugin] (JENKINS-33272) GitHub-specific SCMFileSystem
Title: Message Title Jesse Glick created an issue Jenkins / JENKINS-33272 GitHub-specific SCMFileSystem Issue Type: Improvement Assignee: Jesse Glick Components: github-branch-source-plugin Created: 02/Mar/16 2:34 PM Priority: Major Reporter: Jesse Glick While there is no general solution for Git, in the case of GitHub we may be able to use this. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [github-branch-source-plugin] (JENKINS-33256) Re-enable GitHub PR support for public repos
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-33256 Re-enable GitHub PR support for public repos Change By: Jesse Glick Labels: api security workflow Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
