[JIRA] (JENKINS-61199) Job Configuration History Plugin doesn't seem to honor "Max number of days to keep history entries" for deleted jobs
Title: Message Title Jochen A. Fürbacher commented on JENKINS-61199 Re: Job Configuration History Plugin doesn't seem to honor "Max number of days to keep history entries" for deleted jobs This might be a permission issue. Your ls shows two different users: lthy and ltphy. The files only have write permission for their own user, so the user lthy cannot delete a file of user ltphy and vice versa. What's your jenkins system user? If your jenkins system user isn't lthy nor ltphy, JobConfigHistory cannot delete these files. Could you also check the jenkins logfile? You should see some entries like Should delete: and maybe a warning like problem deleting history file: . Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204748.1582553922000.2010.1585472460238%40Atlassian.JIRA.
[JIRA] (JENKINS-61049) Move documentation from jenkins wiki to github
Title: Message Title Jochen A. Fürbacher assigned an issue to Jochen A. Fürbacher Jenkins / JENKINS-61049 Move documentation from jenkins wiki to github Change By: Jochen A. Fürbacher Assignee: Robin Schulz Jochen A. Fürbacher Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204529.1581422285000.2002.1585468200456%40Atlassian.JIRA.
[JIRA] (JENKINS-61049) Move documentation from jenkins wiki to github
Title: Message Title Jochen A. Fürbacher created an issue Jenkins / JENKINS-61049 Move documentation from jenkins wiki to github Issue Type: Task Assignee: Robin Schulz Components: jobconfighistory-plugin Created: 2020-02-11 11:58 Priority: Minor Reporter: Jochen A. Fürbacher We should move the documentation, that is currently posted in the Jenkins wiki, to Github, as described here. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-58419) CAS: No redirect after login after updating Monitoring plugin to 1.78.0
Title: Message Title Jochen A. Fürbacher commented on JENKINS-58419 Re: CAS: No redirect after login after updating Monitoring plugin to 1.78.0 Thanks! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200546.1562746885000.2504.1564379340239%40Atlassian.JIRA.
[JIRA] (JENKINS-58419) CAS: No redirect after login after updating Monitoring plugin to 1.78.0
Title: Message Title Jochen A. Fürbacher commented on JENKINS-58419 Re: CAS: No redirect after login after updating Monitoring plugin to 1.78.0 Hello! I installed your new build and the login with CAS works fine again. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200546.1562746885000.18473.1563858120347%40Atlassian.JIRA.
[JIRA] (JENKINS-58419) CAS: No redirect after login after updating Monitoring plugin to 1.78.0
Title: Message Title Jochen A. Fürbacher created an issue Jenkins / JENKINS-58419 CAS: No redirect after login after updating Monitoring plugin to 1.78.0 Issue Type: Bug Assignee: evernat Components: cas-plugin, monitoring-plugin Created: 2019-07-10 08:21 Environment: Jenkins core LTS 2.176.1 Monitoring plugin 1.78.0 CAS plugin 1.4.3 Priority: Minor Reporter: Jochen A. Fürbacher After updating Monitoring plugin from 1.77.0 to 1.78.0 there's no redirect to the Jenkins dashboard after login using CAS plugin. The browser url remains like this and there's no redirect: https://$MY_JENKINS_INSTANCE/securityRealm/finishLogin?ticket=$A_SAMPLE_TICKET_VALUE The status code of the url above is 200, however when I rollback the Monitoring plugin to 1.77.0, the status code of the url above is 302 and the server response also redirects to the Jenkins dashboard. When I rollback the Monitoring plugin to 1.77.0 the login works fine again.
[JIRA] (JENKINS-57657) SYSTEM user could be used to track changes during initialization process.
Title: Message Title Jochen A. Fürbacher resolved as Done Done in release 2.22. Jenkins / JENKINS-57657 SYSTEM user could be used to track changes during initialization process. Change By: Jochen A. Fürbacher Status: Open Resolved Resolution: Done Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199590.1558692597000.18733.1559551380329%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57159) Improve JobConfigHistory to support managed files
Title: Message Title Jochen A. Fürbacher resolved as Not A Defect Jenkins / JENKINS-57159 Improve JobConfigHistory to support managed files Change By: Jochen A. Fürbacher Status: Open Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198909.1556032358000.815.1557738240426%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57159) Improve JobConfigHistory to support managed files
Title: Message Title Jochen A. Fürbacher commented on JENKINS-57159 Re: Improve JobConfigHistory to support managed files You can view the diff between two history entries of this file: Go to JobConfigHistory action Click on the org.jenkinsci.plugins.configfiles.GlobalConfigFiles (system) link (not the View as XML link). A new page with the possibility to diff between history changes of the Manged Files get opened. The restore feature for this file isn't supported, yet. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-57237) ${HOME} in global configured data dir is ignored in pipeline dependencyCheckAnalyzer
Title: Message Title
Jochen A. Fürbacher updated an issue
Jenkins / JENKINS-57237
${HOME} in global configured data dir is ignored in pipeline dependencyCheckAnalyzer
Change By:
Jochen A. Fürbacher
When you configure the field {{Global Data Directory}} in the global Jenkins configuration page to use the {{$\{HOME}}} environment variable, e.g. {{${HOME}/owasp-nvd}}, then the {{$ \ {HOME}}} variable gets referenced corectly in freestyle jobs. You see something like this in the build log: {code :java }...[DependencyCheck] -dataDirectory = /opt/jenkins/owasp-nvd...{code} However, the {{$ \ {HOME}}} variable doesn't get referenced corectly in Pipeline jobs when using the {{dependencyCheckAnalyzer()}} step:{code :java }...[DependencyCheck] -dataDirectory = /opt/jenkins/ws/CheckOWASP_DataDir.Pipeline/${HOME}/owasp-nvd...{code} *Note*: The fields for the dateDirectory are neither configured in the freestyle job nor in the pipeline job! Just in the global configuration page!
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-57237) ${HOME} in global configured data dir is ignored in pipeline dependencyCheckAnalyzer
Title: Message Title
Jochen A. Fürbacher created an issue
Jenkins / JENKINS-57237
${HOME} in global configured data dir is ignored in pipeline dependencyCheckAnalyzer
Issue Type:
Bug
Assignee:
Unassigned
Components:
dependency-check-jenkins-plugin
Created:
2019-04-30 07:41
Environment:
Jenkins core: 2.164.2 Dependency Check Plugin: 4.0.2
Priority:
Minor
Reporter:
Jochen A. Fürbacher
When you configure the field Global Data Directory in the global Jenkins configuration page to use the ${HOME} environment variable, e.g. ${HOME}/owasp-nvd, then the ${HOME} variable gets referenced corectly in freestyle jobs. You see something like this in the build log:
...
[DependencyCheck] -dataDirectory = /opt/jenkins/owasp-nvd
...
However, the ${HOME} variable doesn't get referenced corectly in Pipeline jobs when using the dependencyCheckAnalyzer() step:
...
[DependencyCheck] -dataDirectory = /opt/jenkins/ws/CheckOWASP_DataDir.Pipeline/${HOME}/owasp-nvd
...
[JIRA] (JENKINS-57159) Improve JobConfigHistory to support managed files
Title: Message Title Jochen A. Fürbacher commented on JENKINS-57159 Re: Improve JobConfigHistory to support managed files Changes of Manged Files get already tracked by JobConfigHistory, as this is a system configuration change. You will see records as org.jenkinsci.plugins.configfiles.GlobalConfigFiles (system). While it might be nice to have an action for JobConfigHistory in the managed files section, I don't see any chance to track history changes of individual managed files, as all these managed files get persisted in a single XML file (org.jenkinsci.plugins.configfiles.GlobalConfigFiles.xml). Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-56023) JobConfigHistory plugin does not display Folder configs correctly
Title: Message Title Jochen A. Fürbacher resolved as Fixed Fixed in 2.20. Jenkins / JENKINS-56023 JobConfigHistory plugin does not display Folder configs correctly Change By: Jochen A. Fürbacher Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-49301) The Move action does not move job config history also
Title: Message Title Jochen A. Fürbacher resolved as Fixed Fixed in 2.20. Jenkins / JENKINS-49301 The Move action does not move job config history also Change By: Jochen A. Fürbacher Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-45821) JobConfigHistory is flooded by pipeline steps
Title: Message Title Jochen A. Fürbacher resolved as Fixed Fixed in 2.20. Jenkins / JENKINS-45821 JobConfigHistory is flooded by pipeline steps Change By: Jochen A. Fürbacher Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-49301) The Move action does not move job config history also
Title: Message Title Jochen A. Fürbacher started work on JENKINS-49301 Change By: Jochen A. Fürbacher Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-56023) JobConfigHistory plugin does not display Folder configs correctly
Title: Message Title Jochen A. Fürbacher assigned an issue to Jochen A. Fürbacher Jenkins / JENKINS-56023 JobConfigHistory plugin does not display Folder configs correctly Change By: Jochen A. Fürbacher Assignee: Stefan Brausch Jochen A. Fürbacher Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-56023) JobConfigHistory plugin does not display Folder configs correctly
Title: Message Title Jochen A. Fürbacher started work on JENKINS-56023 Change By: Jochen A. Fürbacher Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-53998) Job Config History plugin should not call User.current() during startup
Title: Message Title Jochen A. Fürbacher updated JENKINS-53998 Jenkins / JENKINS-53998 Job Config History plugin should not call User.current() during startup Change By: Jochen A. Fürbacher Status: Fixed but Unreleased Resolved Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-54146) Job History Plugin 2.18.2 - XML view not working
Title: Message Title Jochen A. Fürbacher edited a comment on JENKINS-54146 Re: Job History Plugin 2.18.2 - XML view not working Hello [~farukhkhan123],thanks for opening this issue. However, this is not an issue of JobConfigHistory.In Jenkins core 2.105 XML 1.1 was introduced (see: JENKINS-48463). Most XML parsers of webbrowsers do not support XML 1.1 yet. When you try to view config files persisted with an earlier jenkins core version than 2.105, there won't be any problem as the XML files are still of version 1.0.So the issue is related to the XML parser of your webbrowser.Jochen Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-54146) Job History Plugin 2.18.2 - XML view not working
Title: Message Title Jochen A. Fürbacher resolved as Not A Defect Hello farukh khan, thanks for opening this issue. However, this is not an issue of JobConfigHistory. In Jenkins core 2.105 XML 1.1 was introduced (see: JENKINS-48463). Most XML parsers do not support XML 1.1 yet. When you try to view config files persisted with an earlier jenkins core version than 2.105, there won't be any problem as the XML files are still of version 1.0. So the issue is related to the XML parser of your webbrowser. Jochen Jenkins / JENKINS-54146 Job History Plugin 2.18.2 - XML view not working Change By: Jochen A. Fürbacher Status: Open Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For
[JIRA] (JENKINS-53978) Less than sign (<) not correctly parsed in Agent Configuration History files
Title: Message Title Jochen A. Fürbacher resolved as Fixed Fixed in 2.18.3. Jenkins / JENKINS-53978 Less than sign (<) not correctly parsed in Agent Configuration History files Change By: Jochen A. Fürbacher Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-54223) Job configurations displayed incorrectly (raw)
Title: Message Title Jochen A. Fürbacher resolved as Fixed Fixed in 2.18.3. It will be available in the update center in the next couple of hours. Jenkins / JENKINS-54223 Job configurations displayed incorrectly (raw) Change By: Jochen A. Fürbacher Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-54223) Job configurations displayed incorrectly (raw)
Title: Message Title Jochen A. Fürbacher commented on JENKINS-54223 Re: Job configurations displayed incorrectly (raw) Jakub Bochenski: Thanks for reporting this issue. We already fixed this and looking forward to release a fixed version soon. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-53819) Job configurations displayed incorrectly
Title: Message Title Jochen A. Fürbacher commented on JENKINS-53819 Re: Job configurations displayed incorrectly Jakub Bochenski: Does ist still happening when showing the diff of two files? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-53819) Job configurations displayed incorrectly
Title: Message Title Jochen A. Fürbacher resolved as Fixed Thanks for reporting this issue! It's fixed in 2.18.2. Jenkins / JENKINS-53819 Job configurations displayed incorrectly Change By: Jochen A. Fürbacher Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-18949) Renaming Project causes content encoding error
Title: Message Title Jochen A. Fürbacher resolved as Cannot Reproduce No response. Jenkins / JENKINS-18949 Renaming Project causes content encoding error Change By: Jochen A. Fürbacher Status: Open Resolved Assignee: Mirko Friedenhagen Jochen A. Fürbacher Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because
[JIRA] (JENKINS-16496) latest version of jobConfigHistory fails on the first run when using a matrix job
Title: Message Title Jochen A. Fürbacher commented on JENKINS-16496 Re: latest version of jobConfigHistory fails on the first run when using a matrix job Can't reproduce with JCH 2.15 and core 2.52. Brian Murrell: Does your problem still occur? If so, what kind ob jobs fail? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-13288) Config history does not appear for certain jobs
Title: Message Title Jochen A. Fürbacher resolved as Postponed No response, so postponed. Jenkins / JENKINS-13288 Config history does not appear for certain jobs Change By: Jochen A. Fürbacher Status: Open Resolved Resolution: Postponed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-41402) Corner case in job deletion without history?
Title: Message Title Jochen A. Fürbacher resolved as Done Jenkins / JENKINS-41402 Corner case in job deletion without history? Change By: Jochen A. Fürbacher Status: Open Resolved Assignee: Stefan Brausch Jochen A. Fürbacher Resolution: Done Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-43155) Multiple links and graphics when there are several branches
Title: Message Title Jochen A. Fürbacher commented on JENKINS-43155 Re: Multiple links and graphics when there are several branches Yes, Pipeline Multibranch Plugin 2.14. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-43155) Multiple links and graphics when there are several branches
Title: Message Title Jochen A. Fürbacher created an issue Jenkins / JENKINS-43155 Multiple links and graphics when there are several branches Issue Type: Bug Assignee: Ulli Hafner Attachments: taskScanner01.png, tasksScanner02.png Components: tasks-plugin Created: 2017/Mar/28 8:46 AM Environment: Task Scanner Plug-in 4.50 Jenkins core 2.46 Priority: Minor Reporter: Jochen A. Fürbacher When we have several branches in one project, task scanner shows multiple links to open tasks (same link), as well as the same number of graphics (the same graphics). See the attached screenshots. Add Comment
[JIRA] (JENKINS-41375) JobConfigHistory fails to revert
Title: Message Title Jochen A. Fürbacher commented on JENKINS-41375 Re: JobConfigHistory fails to revert You don't need to test JCH on an existing node. You can create a new dumb slave node (e.g. "Launch slave agents via Java Web Start") that you don't start. Just create and reconfigure such a slave node. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-41375) JobConfigHistory fails to revert
Title: Message Title Jochen A. Fürbacher commented on JENKINS-41375 Re: JobConfigHistory fails to revert Three more things: JobConfigHistory does not only persist changes in job configurations, but also changes in node configurations. Could you try JobConfigHistory on a node? Did you configure JobConfigHistory to use an other directory than the default one or did you even configure JobConfigHistory? (Global jenkins configuration page) I am also wondering about the stack trace you provided. There's the line at hudson.plugins.jobConfigHistory.JobConfigHistoryProjectAction.doRestore(JobConfigHistoryProjectAction.java:219) , however in JobConfigHistory 2.15 there's no method or anything in line 219, as you can see here. Maybe there went something wrong during the upgrade of JobConfigHistory. Can you rollback to the earlier version you installed, try it there and upgrade to the newest version again? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because
[JIRA] (JENKINS-41402) Corner case in job deletion without history?
Title: Message Title Jochen A. Fürbacher commented on JENKINS-41402 Re: Corner case in job deletion without history? You are right. However, if a job is not disabled and you delete a job, the Jenkins core internally first disables the job and than deletes it. So in this case you get two history entries, the first one with a copy of the job config (job was enabled). Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-41375) JobConfigHistory fails to revert
Title: Message Title Jochen A. Fürbacher commented on JENKINS-41375 Re: JobConfigHistory fails to revert Ok, that should work. Have you tried to use JobConfigHistory when the Selenium grid hub is not running? I just want to be sure, that it doesn't have anything to do with it. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-41375) JobConfigHistory fails to revert
Title: Message Title Jochen A. Fürbacher commented on JENKINS-41375 Re: JobConfigHistory fails to revert Hello, I can't also reproduce this issue with running a Selenium grid hub on the same windows machine. Do you use some special characters (any character except a-z,A-Z,0-9) in your job names? Best regards, Jochen Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-41375) JobConfigHistory fails to revert
Title: Message Title Jochen A. Fürbacher assigned an issue to Jochen A. Fürbacher Jenkins / JENKINS-41375 JobConfigHistory fails to revert Change By: Jochen A. Fürbacher Assignee: Stefan Brausch Jochen A. Fürbacher Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-41375) JobConfigHistory fails to revert
Title: Message Title Jochen A. Fürbacher commented on JENKINS-41375 Re: JobConfigHistory fails to revert Hello, I cannot reproduce this issue even on Windows 7. But it looks like there's some problem with the SAX parser. What Java version are you using? Do you run Jenkins in an application server? If yes, what application server? Best regards, Jochen Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-42464) Job Configuration History not accessible from public IP address
Title: Message Title Jochen A. Fürbacher stopped work on JENKINS-42464 Change By: Jochen A. Fürbacher Status: In Progress Open Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-42464) Job Configuration History not accessible from public IP address
Title: Message Title Jochen A. Fürbacher resolved as Fixed Fix will be available in the next release version. Jenkins / JENKINS-42464 Job Configuration History not accessible from public IP address Change By: Jochen A. Fürbacher Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit
[JIRA] (JENKINS-42464) Job Configuration History not accessible from public IP address
Title: Message Title Jochen A. Fürbacher assigned an issue to Jochen A. Fürbacher Jenkins / JENKINS-42464 Job Configuration History not accessible from public IP address Change By: Jochen A. Fürbacher Assignee: Stefan Brausch Jochen A. Fürbacher Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-42464) Job Configuration History not accessible from public IP address
Title: Message Title Jochen A. Fürbacher started work on JENKINS-42464 Change By: Jochen A. Fürbacher Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-42429) Cannot view dependency of jobs
Title: Message Title Jochen A. Fürbacher commented on JENKINS-42429 Re: Cannot view dependency of jobs What happens, if you try to execute the graph.vz file, that you can download on the dependency view page of your project, manually on command line? E.g.: dot -Tpng graph.vz > graph.png Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-42429) Cannot view dependency of jobs
Title: Message Title
Jochen A. Fürbacher edited a comment on JENKINS-42429
Re: Cannot view dependency of jobs
I noticed, that this issue occures, if we use special characters in display names of projects, such as ampersands and that name get put in the label parameter of a diagraph node. Then dot also throws an error, if I manually run dot with the generated graph.vz file: {code:java}Error: not well-formed (invalid token) in line 1... X & Y ...in label of node X & Y{code} When I manually escape the ampersand character in the generated graph.vz file ("&" -> "") , then dot can gerate a valid image.I think, there's some problem with special characters that should get escaped. Maybe in [this|https://github.com/jenkinsci/depgraph-view-plugin/blob/master/src/main/java/hudson/plugins/depgraph_view/model/display/DotStringGenerator.java#L139-L142] method.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-42429) Cannot view dependency of jobs
Title: Message Title
Jochen A. Fürbacher edited a comment on JENKINS-42429
Re: Cannot view dependency of jobs
I noticed, that this issue occures, if we use special characters in display names of projects, such as ampersands and that name get put in the label parameter of a diagraph node. Then dot also throws an error, if I manually run dot with the generated graph.vz file: {code:java}Error: not well-formed (invalid token) in line 1... X & Y ...in label of node X & Y{code} When I manually escape the ampersand character in the generated graph.vz file ("&" -> ""), then dot can gerate a valid image.I think, there's some problem with special characters that should get escaped. Maybe in [this|https://github.com/jenkinsci/depgraph-view-plugin/blob/master/src/main/java/hudson/plugins/depgraph_view/model/display/DotStringGenerator.java#L139-L142] method.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-42429) Cannot view dependency of jobs
Title: Message Title
Jochen A. Fürbacher commented on JENKINS-42429
Re: Cannot view dependency of jobs
I noticed, that this issue occures, if we use special characters in display names of projects, such as ampersands and that name get put in the label parameter of a diagraph node. Then dot also throws an error, if I manually run dot with the generated graph.vz file:
Error: not well-formed (invalid token) in line 1
... "center" href="" class="code-quote" style="color: #009100">"http://myjenkinsinstance/job/MyJob/" >X & Y ...
in label of node X & Y
When I manually escape the ampersand character in the generated graph.vz file ("&" -> "&"), then dot can gerate a valid image. I think, there's some problem with special characters that should get escaped. Maybe in this method.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-42429) Cannot view dependency of jobs
Title: Message Title Jochen A. Fürbacher assigned an issue to Jochen A. Fürbacher Jenkins / JENKINS-42429 Cannot view dependency of jobs Change By: Jochen A. Fürbacher Assignee: wolfs Jochen A. Fürbacher Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-42429) Cannot view dependency of jobs
Title: Message Title Jochen A. Fürbacher assigned an issue to wolfs Jenkins / JENKINS-42429 Cannot view dependency of jobs Change By: Jochen A. Fürbacher Assignee: Jochen A. Fürbacher wolfs Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-42549) Git checkout fails when running multiple jobs on same slave with 'java.lang.IllegalStateException: zip file closed' exception
Title: Message Title Jochen A. Fürbacher commented on JENKINS-42549 Re: Git checkout fails when running multiple jobs on same slave with 'java.lang.IllegalStateException: zip file closed' exception Same problem here. Jenkins core 2.46 Maven Intergration Plugin 2.15.1 We have about 1000 job building every night. About 10-15 jobs of these 1000 fail with the exception Andrei Caragheorghii mentioned. They are not always the same jobs that fail. As a workaround deleting the workspace and rebuilding the jobs works for the moment. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-42432) All branches (SVN) get built periodically, even if nothing has changed (discard old builds)
Title: Message Title Jochen A. Fürbacher updated an issue Jenkins / JENKINS-42432 All branches (SVN) get built periodically, even if nothing has changed (discard old builds) Change By: Jochen A. Fürbacher Summary: All branches (SVN) get built periodically, even if nothing has changed (discard old builds) Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-39411) javax.servlet.ServletException on job save after adding quality gates post-build action
Title: Message Title Jochen A. Fürbacher commented on JENKINS-39411 Re: javax.servlet.ServletException on job save after adding quality gates post-build action Opened pull request that resolves this issue: https://github.com/jenkinsci/quality-gates-plugin/pull/51 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-39411) javax.servlet.ServletException on job save after adding quality gates post-build action
Title: Message Title Jochen A. Fürbacher edited a comment on JENKINS-39411 Re: javax.servlet.ServletException on job save after adding quality gates post-build action Cannot reproduce with Jenkins 2.28 (as well as 2.42) and Quality Gates Plugin 2.5. EDIT: Ok, I can reproduce this problem only if the sonar instance is connected via HTTPS. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-39411) javax.servlet.ServletException on job save after adding quality gates post-build action
Title: Message Title Jochen A. Fürbacher commented on JENKINS-39411 Re: javax.servlet.ServletException on job save after adding quality gates post-build action Cannot reproduce with Jenkins 2.28 (as well as 2.42) and Quality Gates Plugin 2.5. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-38536) Execution time of parallel blocks of in-flight jobs wrong
Title: Message Title
Jochen A. Fürbacher commented on JENKINS-38536
Re: Execution time of parallel blocks of in-flight jobs wrong
node() {
stage('Stage 1') {
parallel (
el1: { sleep 20 },
el2: { sleep 10 }
)
}
}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-38536) Execution time of parallel blocks of in-flight jobs wrong
Title: Message Title Jochen A. Fürbacher reopened an issue Even with workflow-api 2.8 the problem still occurs. Jenkins / JENKINS-38536 Execution time of parallel blocks of in-flight jobs wrong Change By: Jochen A. Fürbacher Resolution: Fixed Status: Closed Reopened Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit
[JIRA] (JENKINS-40031) Progress bar in stage not shown correctly if using parallel step in stage
Title: Message Title Jochen A. Fürbacher updated an issue Jenkins / JENKINS-40031 Progress bar in stage not shown correctly if using parallel step in stage Change By: Jochen A. Fürbacher Attachment: JENKINS-40031.png Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-40031) Progress bar in stage not shown correctly if using parallel step in stage
Title: Message Title
Jochen A. Fürbacher created an issue
Jenkins / JENKINS-40031
Progress bar in stage not shown correctly if using parallel step in stage
Issue Type:
Bug
Assignee:
Sam Van Oort
Components:
pipeline-stage-view-plugin
Created:
2016/Nov/25 9:38 AM
Priority:
Minor
Reporter:
Jochen A. Fürbacher
If I use a parallel step within a stage block, the progress bar of the stage during the build is not showing correctly the progress.
stage('Stage 3') {
parallel (
el1: { sleep 10 },
el2: { sleep 20 }
)
}
When building the example above, the progress bar of the stage shows finished after 10 seconds (with the duration of the first parallel thread). However, the main progress bar (of all stages) runs well. When the second parallel thread is finished (after 20 seconds), the duration of the stage changes to the complete duration of the stage (20 seconds).
Add Comment
[JIRA] (JENKINS-39240) OpenPGP support for Mailer plugin
Title: Message Title Jochen A. Fürbacher created an issue Jenkins / JENKINS-39240 OpenPGP support for Mailer plugin Issue Type: New Feature Assignee: Unassigned Components: mailer-plugin Created: 2016/Oct/25 12:35 PM Priority: Minor Reporter: Jochen A. Fürbacher I'd like to see that Mailer Plugin supports OpenPGP. Signing: E-Mails sent by Mailer plugin get signed and the receiver can verify that the mail really comes from Jenkins. Encrypting: This may be a little bit complicated. As an idea a user could upload his public key to his user account and if one is available, emails sent to him get encrypted. Add Comment
[JIRA] (JENKINS-34802) Exclude history collection for selected users
Title: Message Title Jochen A. Fürbacher resolved as Done New version is released. The new version will be available in the update center soon. Jenkins / JENKINS-34802 Exclude history collection for selected users Change By: Jochen A. Fürbacher Status: Open Resolved Resolution: Done Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more
[JIRA] (JENKINS-36744) Add optional approve / review process for job config changes
Title: Message Title Jochen A. Fürbacher resolved as Won't Do Jenkins / JENKINS-36744 Add optional approve / review process for job config changes Change By: Jochen A. Fürbacher Status: Open Resolved Resolution: Won't Do Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-36744) Add optional approve / review process for job config changes
Title: Message Title Jochen A. Fürbacher commented on JENKINS-36744 Re: Add optional approve / review process for job config changes This idea of this feature is good. However it's better to include this functionality in e.g. Script Security Plugin or a new plugin. JobConfigHistory is just for logging and recovering config changes and it won't perform any changes or security checks. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-36605) History plugin
Title: Message Title Jochen A. Fürbacher commented on JENKINS-36605 Re: History plugin If you have matrix based security enabled, it is possible to do config changes without logging in, if rights for user anonymous arent't removed. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-35021) JobConfigHistory: Max number of days to keep history entries parameter: Does not work as expected
Title: Message Title
Jochen A. Fürbacher edited a comment on JENKINS-35021
Re: JobConfigHistory: Max number of days to keep history entries parameter: Does not work as expected
Hi Carlos,thanks for providing the logs.If you check your log file {{Config-History-Defect.log.8}} then you can see after line 2096, that some of the entries get deleted:{{2016-07-08 04:11:41.865+0100 [id=96] FINE h.p.j.JobConfigHistoryPurger#doRun: checking for history files to purge (max age of 1 days allowed)2016-07-08 04:11:41.869+0100 [id=96] FINEST h.p.j.FileHistoryDao#isCreatedEntry: historyDir: C:\Jenkins\config-history\com.cloudbees.jenkins.plugins.requestfilter.Rules\2016-07-06_15-48-592016-07-08 04:11:41.869+0100 [id=96] FINEST h.p.j.FileHistoryDao#isCreatedEntry: histDescr.getOperation(): Changed2016-07-08 04:11:41.869+0100 [id=96] FINEST h.p.j.JobConfigHistoryPurger#purgeSystemOrJobHistory: Should delete: C:\Jenkins\config-history\com.cloudbees.jenkins.plugins.requestfilter.Rules\2016-07-06_15-48-59}}So these history entries get deleted and should'n get shown anymore.However, history entries with operation Created doesn't get deleted, even when they are older than the configuried max time. E.g.:You create a job on July 15th. Then you do a couple of config changed of the job. When you habe have JobConfigHistory configured to delete all entries after 2 days and it's for instance July 20th, then all entries of this job get deleted. But the entry, which contains the Created operation, doesn't get deleted. It stays remain in the history.You can test it with setting it to 1 day and leave it for 2 days. When you check your log, then you should see, that JobConfigHistory tries to deletes some entries (containing rows {{JobConfigHistoryPurger#doRun: checking for history files to purge (max age of 1 days allowed)}} and {{JobConfigHistoryPurger#purgeSystemOrJobHistory: Should delete: }})Jochen
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-35021) JobConfigHistory: Max number of days to keep history entries parameter: Does not work as expected
Title: Message Title
Jochen A. Fürbacher commented on JENKINS-35021
Re: JobConfigHistory: Max number of days to keep history entries parameter: Does not work as expected
Hi Carlos, thanks for providing the logs. If you check your log file Config-History-Defect.log.8 then you can see after line 2096, that some of the entries get deleted: {{2016-07-08 04:11:41.865+0100 [id=96] FINE h.p.j.JobConfigHistoryPurger#doRun: checking for history files to purge (max age of 1 days allowed) 2016-07-08 04:11:41.869+0100 [id=96] FINEST h.p.j.FileHistoryDao#isCreatedEntry: historyDir: C:\Jenkins\config-history\com.cloudbees.jenkins.plugins.requestfilter.Rules\2016-07-06_15-48-59 2016-07-08 04:11:41.869+0100 [id=96] FINEST h.p.j.FileHistoryDao#isCreatedEntry: histDescr.getOperation(): Changed 2016-07-08 04:11:41.869+0100 [id=96] FINEST h.p.j.JobConfigHistoryPurger#purgeSystemOrJobHistory: Should delete: C:\Jenkins\config-history\com.cloudbees.jenkins.plugins.requestfilter.Rules\2016-07-06_15-48-59}} So these history entries get deleted and should'n get shown anymore. However, history entries with operation Created doesn't get deleted, even when they are older than the configuried max time. E.g.: You create a job on July 15th. Then you do a couple of config changed of the job. When you habe JobConfigHistory configured to delete all entries after 2 days and it's for instance July 20th, then all entries of this job get deleted. But the entry, which contains the Created operation, doesn't get deleted. It stays remain in the history. You can test it with setting it to 1 day and leave it for 2 days. When you check your log, then you should see, that JobConfigHistory tries to deletes some entries (containing rows JobConfigHistoryPurger#doRun: checking for history files to purge (max age of 1 days allowed) and {{JobConfigHistoryPurger#purgeSystemOrJobHistory: Should delete: }}) Jochen
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-35021) JobConfigHistory: Max number of days to keep history entries parameter: Does not work as expected
Title: Message Title Jochen A. Fürbacher resolved as Cannot Reproduce If someone can reproduce this issue, feel free to reopen the ticket. Jenkins / JENKINS-35021 JobConfigHistory: Max number of days to keep history entries parameter: Does not work as expected Change By: Jochen A. Fürbacher Status: Open Resolved Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] (JENKINS-33682) on multi branch projects it creates a config file every sync period.
Title: Message Title Jochen A. Fürbacher commented on JENKINS-33682 Re: on multi branch projects it creates a config file every sync period. mor lajb: This problem is resolved, when you install version 0.5 of Multi-Branch Project Plugin. Thanks to Matthew DeTullio. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-30089) new config history created on each multibranch build
Title: Message Title Jochen A. Fürbacher commented on JENKINS-30089 Re: new config history created on each multibranch build Matthew DeTullio I noticed, that the Multi-Branch Project plugin deactivates all branches before syncing and reactivates them after syncing. This leads to some small changes of the branch config file (what gets tracked by JobConfigHistory). Is it necessary to do this deactivation / reactivation of the branches? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-35421) Exception: "Could not create rootDir"
Title: Message Title Jochen A. Fürbacher resolved as Cannot Reproduce If someone can explain or reproduce this scenario, then feel free to reopen this ticket. Jenkins / JENKINS-35421 Exception: "Could not create rootDir" Change By: Jochen A. Fürbacher Status: Open Resolved Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] (JENKINS-33682) on multi branch projects it creates a config file every sync period.
Title: Message Title Jochen A. Fürbacher commented on JENKINS-33682 Re: on multi branch projects it creates a config file every sync period. The problem is, that the Multi-Branch Project Plugin syncs the branches periodically (default is every 5 minutes), what leads to a temporary deactivation and reactivation of the branch. This deactivation/activation changes the branch config, what gets tracked by JobConfigHistory. I opened a thread in the Jenkins developer mailing list: https://groups.google.com/forum/#!topic/jenkinsci-dev/WEx2UOY4x1U In the upcoming version of JobConfigHistory it is possible, to exclude changes performed by some users from getting tracked. One workaround for this issue would be to exclude changes made my the SYSTEM user. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-35421) Exception: "Could not create rootDir"
Title: Message Title Jochen A. Fürbacher commented on JENKINS-35421 Re: Exception: "Could not create rootDir" I tried to reproduce this issue. JobConfigHistory stores config changes on the main project as well as on all branches and I don't see any exception like that one above. All directories exist. You mentioned, that the problematic jobs are all from June. Did you use JobConfigHistory before June without problems? Does this exception only occur on multi branch jobs or on all jobs? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jobconfighistory-plugin] (JENKINS-35421) Exception: "Could not create rootDir"
Title: Message Title Jochen A. Fürbacher commented on JENKINS-35421 Re: Exception: "Could not create rootDir" Yes, this is a exception of JobConfigHistory. Can you check, if the directory /var/lib/jenkins/config-history/jobs/Zodiac_gcc_all_branches_and_trunk/branches/trunk/2016-06-06_14-37-52 exists? Does this exception occur more ofter? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jobconfighistory-plugin] (JENKINS-34861) Job Config History Plugin failing when comparing diff between config files
Title: Message Title Jochen A. Fürbacher resolved as Fixed Jenkins / JENKINS-34861 Job Config History Plugin failing when comparing diff between config files Change By: Jochen A. Fürbacher Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jobconfighistory-plugin] (JENKINS-35021) JobConfigHistory: Max number of days to keep history entries parameter: Does not work as expected
Title: Message Title Jochen A. Fürbacher commented on JENKINS-35021 Re: JobConfigHistory: Max number of days to keep history entries parameter: Does not work as expected Hi Carlos, could you provide a log of this (FINEST)? I tried it and can't reproduce it (Jenkins 2.4, JobConfigHistory 2.14). The periodic checker runs once a day. NOTE: The periodic check does NOT delete entries with operation "created". Jochen Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [credentials-plugin] (JENKINS-33111) jobconfighistory-plugin does not track credential.xml changes
Title: Message Title Jochen A. Fürbacher commented on JENKINS-33111 Re: jobconfighistory-plugin does not track credential.xml changes Bing Shiao: As reporter of this issue, what would you prefer? Tracking der whole credentials.xml file with the possibility to restore old files (probably a security issue). Encrypt the content of credentials.xml randomly without the possibility of restoring the files. The user / admin can only see, that the file has changed, but not what exactly has changed. Daniel Beck: Do you also agree, that there are some security problems with recording credentials changes? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [credentials-plugin] (JENKINS-33111) jobconfighistory-plugin does not track credential.xml changes
Title: Message Title Jochen A. Fürbacher edited a comment on JENKINS-33111 Re: jobconfighistory-plugin does not track credential.xml changes Thanks, Stephen.Reopened: We still need to do some changes on JobConfigHistory. EDIT: At the moment JobConfigHistory tracks credentials.xml with the new version of the credentials plugin installed (thanks to Stephen Connolly). No new version of JobConfigHistory required. But we're looking forward to also implement a second encryption layer. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jobconfighistory-plugin] (JENKINS-30089) new config history created on each multibranch build
Title: Message Title Jochen A. Fürbacher updated an issue Jenkins / JENKINS-30089 new config history created on each multibranch build Philipp Moeller: I attached a screenshot of JobConfigHistory, showing you the option to not save duplicate histories. You find it in the global jenkins configuration. Change By: Jochen A. Fürbacher Attachment: doNotSaveDublicateHistory.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] [credentials-plugin] (JENKINS-33111) jobconfighistory-plugin does not track credential.xml changes
Title: Message Title Jochen A. Fürbacher reopened an issue Thanks, Stephen. Reopened: We still need to do some changes on JobConfigHistory. Jenkins / JENKINS-33111 jobconfighistory-plugin does not track credential.xml changes Change By: Jochen A. Fürbacher Resolution: Fixed Status: Resolved Reopened Assignee: Mirko Friedenhagen Jochen A. Fürbacher Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] [jobconfighistory-plugin] (JENKINS-34802) Exclude history collection for selected users
Title: Message Title Jochen A. Fürbacher commented on JENKINS-34802 Re: Exclude history collection for selected users Hi Noel, at the moment I can't say when the next release is planned to. Sorry. Jochen Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [credentials-plugin] (JENKINS-33111) jobconfighistory-plugin does not track credential.xml changes
Title: Message Title Jochen A. Fürbacher commented on JENKINS-33111 Re: jobconfighistory-plugin does not track credential.xml changes Thanks for your answer. It seems like SystemCredentialsProvider needs to notify the SaveableListener about changes in the credentials.xml file. At the moment JobConfigHistory gets notified by the SaveableListener (see here). I think the changes for JobConfigHistory shouldn't be too big. The idea of a second encryption layer is good. We are also having the idea of not saving the old credentials.xml files, but showing the information, that credentials have changed. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jobconfighistory-plugin] (JENKINS-34861) Job Config History Plugin failing when comparing diff between config files
Title: Message Title Jochen A. Fürbacher commented on JENKINS-34861 Re: Job Config History Plugin failing when comparing diff between config files Alex Taylor As creator of the issue: Do you still have the issue after upgrading to 2.13? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jobconfighistory-plugin] (JENKINS-34802) Exclude history collection for selected users
Title: Message Title Jochen A. Fürbacher commented on JENKINS-34802 Re: Exclude history collection for selected users In the next release version of JobConfigHistory you will be able to exclude users by their IDs. However at the moment there won't be a auto completion (may be added later). Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jobconfighistory-plugin] (JENKINS-34861) Job Config History Plugin failing when comparing diff between config files
Title: Message Title Jochen A. Fürbacher commented on JENKINS-34861 Re: Job Config History Plugin failing when comparing diff between config files In JobConfigHistory 2.12 we had such a nullpointerexception: JENKINS-33289 . This is fixed since version 2.13. Do you still have this nullpointerexception after upgrading to 2.13? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [quality-gates-plugin] (JENKINS-34427) Sonar user password is stored in plain text in every job configuration
Title: Message Title Jochen A. Fürbacher closed an issue as Fixed Fixed. Jenkins / JENKINS-34427 Sonar user password is stored in plain text in every job configuration Change By: Jochen A. Fürbacher Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [quality-gates-plugin] (JENKINS-34427) Sonar user password is stored in plain text in every job configuration
Title: Message Title Jochen A. Fürbacher commented on JENKINS-34427 Re: Sonar user password is stored in plain text in every job configuration Hi Ivana, thank you very much! We tested it and it workes well. Great job! It's great to have such a useful plugin, now. Cheers! Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jobconfighistory-plugin] (JENKINS-34861) Job Config History Plugin failing when comparing diff between config files
Title: Message Title Jochen A. Fürbacher commented on JENKINS-34861 Re: Job Config History Plugin failing when comparing diff between config files Hi, unfortunately the stack trace doesn't show where the problem with JobConfigHistory is. Can you provide a little more information? JobConfigHistory Version Jenkins core version Type of Job (Freestyle, Maven, Pipeline, ...) Thank you. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [quality-gates-plugin] (JENKINS-34427) Sonar user password is stored in plain text in every job configuration
Title: Message Title Jochen A. Fürbacher edited a comment on JENKINS-34427 Re: Sonar user password is stored in plain text in every job configuration Hi Ivana,I see two problems Stefan mentioned:- Security: When you configure the sonar instance globally and configure a job to use this sonar instance, then the CURRENT password of the sonar instance (that one, that's configured globally) get's also stored in the job configuration. All users (also those without admin rights) can see that password. It's not just the default password!- (Not sure about that) When the admin configures a sonar instance globally, and a job get's configured to use that instance (how discribed above), the vurrent current password get's stored in the job configuration. When the admin changes to password for one this sonar instance, then the old password stays remain in the job config.Stefan and I noticed another major security issue: When the admin does a global configuration, the credentials (incl. the sonar password) get's logged in plaintext! Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [quality-gates-plugin] (JENKINS-34427) Sonar user password is stored in plain text in every job configuration
Title: Message Title Jochen A. Fürbacher commented on JENKINS-34427 Re: Sonar user password is stored in plain text in every job configuration Hi Ivana, I see two problems Stefan mentioned: Security: When you configure the sonar instance globally and configure a job to use this sonar instance, then the CURRENT password of the sonar instance (that one, that's configured globally) get's also stored in the job configuration. All users (also those without admin rights) can see that password. It's not just the default password! (Not sure about that) When the admin configures a sonar instance globally, and a job get's configured to use that instance (how discribed above), the vurrent password get's stored in the job configuration. When the admin changes to password for one this sonar instance, then the old password stays remain in the job config. Stefan and I noticed another major security issue: When the admin does a global configuration, the credentials (incl. the sonar password) get's logged in plaintext! Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jobconfighistory-plugin] (JENKINS-30578) Error when trying to view job config history
Title: Message Title Jochen A. Fürbacher edited a comment on JENKINS-30578 Re: Error when trying to view job config history A bugfix will be available in the next release version of JobConfigHistory.The problem occurs in the current version of JobConfigHistory, if JobConfigHistory is installed and Maven Integration plugin is deactivated. So you have to activate Maven Integration plugin.In the next release version of JobConfigHistory the Maven Integration plugin doesn't need to be active. [~anorakgirl]: Note, since version 2.13 of JobConfigHistory, Jenkins core 1.650 or higher is required! Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jobconfighistory-plugin] (JENKINS-30578) Error when trying to view job config history
Title: Message Title Jochen A. Fürbacher assigned an issue to Jochen A. Fürbacher Jenkins / JENKINS-30578 Error when trying to view job config history Change By: Jochen A. Fürbacher Assignee: Mirko Friedenhagen Jochen A. Fürbacher Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jobconfighistory-plugin] (JENKINS-30578) Error when trying to view job config history
Title: Message Title Jochen A. Fürbacher resolved as Fixed A bugfix will be available in the next release version of JobConfigHistory. The problem occurs in the current version of JobConfigHistory, if JobConfigHistory is installed and Maven Integration plugin is deactivated. So you have to activate Maven Integration plugin. In the next release version of JobConfigHistory the Maven Integration plugin doesn't need to be active. Tamsin Slinn: Note, since version 2.13 of JobConfigHistory, Jenkins core 1.650 or higher is required! Jenkins / JENKINS-30578 Error when trying to view job config history Change By: Jochen A. Fürbacher Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and
[JIRA] [jobconfighistory-plugin] (JENKINS-30968) slave config history does not show changes after SYSTEM update
Title: Message Title Jochen A. Fürbacher closed an issue as Not A Defect Jenkins / JENKINS-30968 slave config history does not show changes after SYSTEM update Change By: Jochen A. Fürbacher Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [credentials-plugin] (JENKINS-33111) jobconfighistory-plugin does not track credential.xml changes
Title: Message Title Jochen A. Fürbacher commented on JENKINS-33111 Re: jobconfighistory-plugin does not track credential.xml changes Hi stephenconnolly, is there a possibility that you provide a listener in your credentials plugin? We need a listener to get notified, if there are changes on the credentials page. Furthermore we are also not really sure, if this could lead to any security issues. Thank you. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [credentials-plugin] (JENKINS-33111) jobconfighistory-plugin does not track credential.xml changes
Title: Message Title Jochen A. Fürbacher updated an issue Jenkins / JENKINS-33111 jobconfighistory-plugin does not track credential.xml changes Change By: Jochen A. Fürbacher Component/s: credentials-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] [jobconfighistory-plugin] (JENKINS-33670) On homepage, there is no preview of issues but rather it says: "Open issues jiraissues: Unable to determine if sort should be enabled." for jobConfigHi
Title: Message Title Jochen A. Fürbacher commented on JENKINS-33670 Re: On homepage, there is no preview of issues but rather it says: "Open issues jiraissues: Unable to determine if sort should be enabled." for jobConfigHistory. This is a common problem not only for JobConfigHistory, but also for all other plugins. I opened a thread in the Jenkins developer mailing list: https://groups.google.com/forum/#!topic/jenkinsci-dev/YBYmMDVgaIk Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jobconfighistory-plugin] (JENKINS-34151) Add support for Pipeline projects to display config changes in build history
Title: Message Title Jochen A. Fürbacher resolved as Done Resolved. It will be available in the upcoming release version of JobConfigHistory. Jenkins / JENKINS-34151 Add support for Pipeline projects to display config changes in build history Change By: Jochen A. Fürbacher Status: Open Resolved Assignee: Stefan Brausch Jochen A. Fürbacher Resolution: Done Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit
[JIRA] [jobconfighistory-plugin] (JENKINS-27643) Job Config History is not saved when perfoming config changes
Title: Message Title Jochen A. Fürbacher resolved as Fixed Problem disappears in newer version. Jenkins / JENKINS-27643 Job Config History is not saved when perfoming config changes Change By: Jochen A. Fürbacher Status: Open Resolved Assignee: Mirko Friedenhagen Jochen A. Fürbacher Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jobconfighistory-plugin] (JENKINS-27643) Job Config History is not saved when perfoming config changes
Title: Message Title Jochen A. Fürbacher edited a comment on JENKINS-27643 Re: Job Config History is not saved when perfoming config changes Resolved: Problem disappears in newer version. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jobconfighistory-plugin] (JENKINS-30828) Keep history of jobs config changes when they are moved across folders
Title: Message Title Jochen A. Fürbacher commented on JENKINS-30828 Re: Keep history of jobs config changes when they are moved across folders Folder have an additional hierarchical layout. At the moment this layout isn't implemented yet and it isn't very simply to solve that. Normally jobs are stored under jobs/JOBNAME. When moving to an folder, it's stored under jobs/FOLDERNAME/jobs/JOBNAME. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jobconfighistory-plugin] (JENKINS-27643) Job Config History is not saved when perfoming config changes
Title: Message Title Jochen A. Fürbacher commented on JENKINS-27643 Re: Job Config History is not saved when perfoming config changes Dominik Kaspar, is your problem fixed or does it still appear? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
