[JIRA] [promoted-builds-plugin] (JENKINS-31151) scm-sync-configuration does not track promotions/config.xml
Title: Message Title aeschbacher created an issue Jenkins / JENKINS-31151 scm-sync-configuration does not track promotions/config.xml Issue Type: Bug Assignee: Oleg Nenashev Components: promoted-builds-plugin, scm-sync-configuration-plugin Created: 25/Oct/15 11:45 AM Environment: scm-sync-configuration-plugin version 0.0.8 Priority: Major Reporter: aeschbacher When the plugin 'promoted-build' is installed, the files jobs//promotions//config.xml shall be archived This is currently not done Add Comment
[JIRA] [promoted-builds-plugin] (JENKINS-31151) scm-sync-configuration does not track promotions/config.xml
Title: Message Title aeschbacher updated an issue Jenkins / JENKINS-31151 scm-sync-configuration does not track promotions/config.xml Change By: aeschbacher When the plugin 'promoted-build' is installed, the files jobs//promotions//config.xml shall be archived This is Neither scm-sync-configuration nor thinBackup do currently not done backup these files Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [promoted-builds-plugin] (JENKINS-31151) scm-sync-configuration does not track promotions/config.xml
Title: Message Title aeschbacher updated an issue Jenkins / JENKINS-31151 scm-sync-configuration does not track promotions/config.xml Change By: aeschbacher Environment: scm-sync-configuration-plugin version 0.0.8 thinBackup plugin Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [promoted-builds-plugin] (JENKINS-31151) scm-sync-configuration does not track promotions/config.xml
Title: Message Title aeschbacher updated an issue Jenkins / JENKINS-31151 scm-sync-configuration does not track promotions/config.xml Change By: aeschbacher Environment: scm-sync-configuration-plugin version 0.0.8thinBackup plugin version 1.7.4 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [promoted-builds-plugin] (JENKINS-31151) scm-sync-configuration does not track promotions/config.xml
Title: Message Title aeschbacher updated an issue Jenkins / JENKINS-31151 scm-sync-configuration does not track promotions/config.xml Change By: aeschbacher Component/s: thinBackup Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-15128) Renaming job doesn't work with Git
Title: Message Title aeschbacher commented on JENKINS-15128 Re: Renaming job doesn't work with Git Do not rename a job; duplicate it, and remove the original. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [active-directory-plugin] (JENKINS-26737) AD can not log on with email address (regression in 1.39)
aeschbacher updated JENKINS-26737 AD can not log on with email address (regression in 1.39) Change By: aeschbacher (02/Feb/15 10:43 AM) Environment: Jenkinsver1.580.3/ DebianWheezy(amd64) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [active-directory-plugin] (JENKINS-26737) AD can not log on with email address (regression in 1.39)
aeschbacher created JENKINS-26737 AD can not log on with email address (regression in 1.39) Issue Type: Bug Assignee: Unassigned Components: active-directory-plugin Created: 02/Feb/15 10:40 AM Description: When using Active Directory, connection with email (e.g. john@company.com) + Domain password fails. But: connection with AD account (e.g. ADGROUP1\johndoe) + domain password works as expected. the "Test" connection button returns "success" when using the email (e.g "Bind DN = john@company.com" and "Bind Password = domain password") This is a regression of version 1.39 (versions = 1.38 work) Environment: Debian Wheezy (amd64) Project: Jenkins Priority: Minor Reporter: aeschbacher This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-23925) SSL weak ciphers
aeschbacher commented on JENKINS-23925 SSL weak ciphers After further investigation, it appears that sslscan discovers weak ciphers only if jenkins.war is started with java6. It is not the case with java7. For Debian Wheezy, this means java 6: 1.6.0_32 (weak ciphers discovered by sslscan) java 7: 1.7.0_65 (no weak ciphers) So I guess the ticket can be closed. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-10401) jenkins using 100% CPU if trying to archive unexisting artifact
aeschbacher commented on JENKINS-10401 jenkins using 100% CPU if trying to archive unexisting artifact Lloyd, First, thank you for your comments. Back in 2011, as I reported the issue, I was working with a poor HW, and with huge (45GB) workspaces. This is not the case anymore (migrated on better HW, workspaces are smaller) , so I did not reproduce the same problem since that time, even though I keep using Jenkins a intensively for many projects. I confirm that the issue can be closed. Best regards, Fabrice This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-15156) Builds disappear from build history after completion
aeschbacher commented on JENKINS-15156 Builds disappear from build history after completion Same main usage for us: heavy use of "copy artifacts" plugin, matrix projects (with "Matrix tie parent" plugin) ssh slaves At the beginning, we thought indeed this was related to renaming the build job. But the problem also occurs for example when modifying the slaves in the configuration matrix. But sometimes, it does occur with free-style (not multi-configuration) jobs too. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16175) Dashboard not showing job status
aeschbacher assigned JENKINS-16175 to aeschbacher Dashboard not showing job status Change By: aeschbacher (15/Jan/13 12:51 PM) Assignee: aeschbacher This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16117) sporadical unwanted suppression of build artifacts
aeschbacher created JENKINS-16117 sporadical unwanted suppression of build artifacts Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: core Created: 13/Dec/12 11:09 AM Description: Some build jobs regularly loose all their build artifacts. Then everything becomes as if these jobs have never been run before. This make depending projects (using copy-artifacts) fail. Such jobs have "Discard old builds" and "Max # of builds to keep" set. This occurs only for a few weeks, so this may be a regression. Currently affected version is 1.492 There is no obvious raison in which situation the artifacts get deleted. This can occur even if the be job is not run (e.g. nothing been committed) This began to occur shortly (but not immediately) after I started creating multi-configuration jobs. This can affect both multi-configuration and/or freestyle projects. Environment: Debian Squeeze Project: Jenkins Priority: Major Reporter: aeschbacher This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13910) git plugin: 'clean after checkout does not git clean -fdx on submodules
aeschbacher created JENKINS-13910: - Summary: git plugin: 'clean after checkout does not git clean -fdx on submodules Key: JENKINS-13910 URL: https://issues.jenkins-ci.org/browse/JENKINS-13910 Project: Jenkins Issue Type: Bug Components: git Affects Versions: current Environment: Debian amd64 Reporter: aeschbacher Assignee: Nicolas De Loof Priority: Minor [Jenkins 1.465 - git plugin 1.1.18] Clean after checkout checkbox does not run git clean -fdx on submodules. As a workaround, we have to run this command first: git submodule foreach --recursive git clean -fdx NOTE: apparently, this has been already reported and fixed (see: - https://issues.jenkins-ci.org/browse/JENKINS-7445 - https://issues.jenkins-ci.org/browse/JENKINS-7376 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-10401) jenkins using 100% CPU if trying to archive unexisting artifact
[ https://issues.jenkins-ci.org/browse/JENKINS-10401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160758#comment-160758 ] aeschbacher commented on JENKINS-10401: --- Hi, We used oe-classic, tag='release-2010.12' wget http://cgit.openembedded.org/openembedded/snapshot/release-2010.12.tar.bz2 I don't know whether the exact version of OE matters anyway; my thoughts were that with any _really_ big workspace (as can be workspaces created by OpenEmbedded: millions of files, 10th of GB) can cause the problem, when configuring the job with artifacts which can't be found. Fabrice jenkins using 100% CPU if trying to archive unexisting artifact --- Key: JENKINS-10401 URL: https://issues.jenkins-ci.org/browse/JENKINS-10401 Project: Jenkins Issue Type: Bug Components: core Affects Versions: current Environment: Linux (debian squeeze 32bits) Reporter: aeschbacher Assignee: aeschbacher [Jenkins ver. 1.420] If a jobs tries to archive an inexisting artifact, the jenkins process uses 100% CPU forever, until we do a '/etc/init.d/jenkins stop' The web interface can not anymore be used The problem is not new in 1.420, but exists for a long time, already in hudson (I did actually never see any linux version not having this problem). A significant information is that we have a huge workspace (up to 45G - we build distros with OpenEmbedded) shared between the jobs -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
