[JIRA] [envinject-plugin] (JENKINS-31469) Global option to mask passwords
Title: Message Title Victor Engmark updated an issue Jenkins / JENKINS-31469 Global option to mask passwords Change By: Victor Engmark Environment: EnvInject 1.92.1Jenkins 1.541 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [envinject-plugin] (JENKINS-31469) Global option to mask passwords
Title: Message Title Victor Engmark created an issue Jenkins / JENKINS-31469 Global option to mask passwords Issue Type: Improvement Assignee: Oleg Nenashev Components: envinject-plugin Created: 10/Nov/15 9:14 AM Labels: security Priority: Major Reporter: Victor Engmark Rather than having to set masking of passwords in each job individually it would be good to have a global option for this, which could not be overridden in individual jobs. Add Comment
[JIRA] [buildresult-trigger-plugin] (JENKINS-25753) BuildResultTrigger doesn't trigger build
Victor Engmark updated JENKINS-25753 BuildResultTrigger doesnt trigger build Change By: Victor Engmark (24/Nov/14 9:44 AM) Description: Thejobwiththefollowingconfigurationnevertriggers,evenafteranunstableacceptance_testrun:triggersorg.jenkinsci.plugins.buildresulttrigger.BuildResultTriggerplugin=buildresult-trigger@0.17spec05***/speccombinedJobsfalse/combinedJobsjobsInfoorg.jenkinsci.plugins.buildresulttrigger.model.BuildResultTriggerInfojobNamesacceptance_test/jobNamescheckedResultsorg.jenkinsci.plugins.buildresulttrigger.model.CheckedResultcheckedSUCCESS/checked/org.jenkinsci.plugins.buildresulttrigger.model.CheckedResultorg.jenkinsci.plugins.buildresulttrigger.model.CheckedResultcheckedUNSTABLE/checked/org.jenkinsci.plugins.buildresulttrigger.model.CheckedResult/checkedResults/org.jenkinsci.plugins.buildresulttrigger.model.BuildResultTriggerInfo/jobsInfo/org.jenkinsci.plugins.buildresulttrigger.BuildResultTrigger/triggers Similarissue:https://issues.jenkins-ci.org/browse/JENKINS-12427 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] [buildresult-trigger-plugin] (JENKINS-25753) BuildResultTrigger doesn't trigger build
Victor Engmark created JENKINS-25753 BuildResultTrigger doesnt trigger build Issue Type: Bug Assignee: Unassigned Components: buildresult-trigger-plugin Created: 24/Nov/14 9:44 AM Description: The job with the following configuration never triggers, even after an unstable acceptance_test run: triggers org.jenkinsci.plugins.buildresulttrigger.BuildResultTrigger plugin="buildresult-trigger@0.17" spec0 5 * * */spec combinedJobsfalse/combinedJobs jobsInfo org.jenkinsci.plugins.buildresulttrigger.model.BuildResultTriggerInfo jobNamesacceptance_test/jobNames checkedResults org.jenkinsci.plugins.buildresulttrigger.model.CheckedResult checkedSUCCESS/checked /org.jenkinsci.plugins.buildresulttrigger.model.CheckedResult org.jenkinsci.plugins.buildresulttrigger.model.CheckedResult checkedUNSTABLE/checked /org.jenkinsci.plugins.buildresulttrigger.model.CheckedResult /checkedResults /org.jenkinsci.plugins.buildresulttrigger.model.BuildResultTriggerInfo /jobsInfo /org.jenkinsci.plugins.buildresulttrigger.BuildResultTrigger /triggers Environment: BuildResultTrigger 0.17 Project: Jenkins Labels: plugin build Priority: Blocker Reporter: Victor Engmark 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] [thinBackup] (JENKINS-20837) Differential backups should not cause Jenkins to stop running new jobs
Victor Engmark created JENKINS-20837 Differential backups should not cause Jenkins to stop running new jobs Issue Type: Improvement Assignee: Thomas Fürer Components: thinBackup Created: 02/Dec/13 1:58 PM Description: How to reproduce: 1. Set a thinBackup schedule. 2. Create a periodic (or SCM-triggered) job which runs for a long time. 3. Create other jobs which run quickly. What happens: 1. The slow job starts. 2. thinBackup triggers, and sets Jenkins to "quiet down" mode, not allowing any more jobs to start. 3. Any triggered or scheduled fast jobs now have to wait for the slow job and the backup to finish before continuing. 4. While thinBackup is waiting for the jobs to finish, "Jenkins is going to shut down" is prominently shown on every page. As this waiting time could be very long, this can mean a large amount of time wasted because of idling machines and waiting developers. The warning message is also misleading enough to make this a major issue. To be able to run frequent backups without losing time, it would be nice if thinBackup could simply not set Jenkins to "quiet down" mode, and instead back up only builds which are finished. If this is done in a similar fashion to rsync (copying only files which are newer than the target) there shouldn't even be any problems with jobs modifying older builds (for example as part of post-build tasks). Workaround: Set the schedule to back up only when people aren't using Jenkins. Project: Jenkins Priority: Major Reporter: Victor Engmark 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/groups/opt_out.
