[JIRA] (JENKINS-49496) Dutch translation of 'allow users to sign-up' is wrong and creates a security hazard
Title: Message Title Jan Vansteenkiste updated an issue Jenkins / JENKINS-49496 Dutch translation of 'allow users to sign-up' is wrong and creates a security hazard Change By: Jan Vansteenkiste Summary: Dutch translation of 'allow users to sign-up' is wrong and creates a securit security hazard 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-49496) Dutch translation of 'allow users to sign-up' is wrong and creates a securit hazard
Title: Message Title Jan Vansteenkiste created an issue Jenkins / JENKINS-49496 Dutch translation of 'allow users to sign-up' is wrong and creates a securit hazard Issue Type: Bug Assignee: Unassigned Components: core Created: 2018-02-12 07:33 Labels: security Priority: Critical Reporter: Jan Vansteenkiste The dutch translation of 'Allow a user to sign up' translates back to 'allow a user to sign in'. The current translation is confusing and dangerous to jenkins administrators since it will open up your jenkins to allow random users to register themselves. Add Comment
[JIRA] (JENKINS-38081) Shared Workspace with empty Name becomes the default Shared Workspace in new jobs
Title: Message Title Jan Vansteenkiste updated an issue Jenkins / JENKINS-38081 Shared Workspace with empty Name becomes the default Shared Workspace in new jobs I updated this to critical since it is a real source of problems in our jenkins with 400+ jobs. Change By: Jan Vansteenkiste Priority: Minor Critical 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-26660) Add another '-f' to git clean to remove deleted submodules or other repos checked out in workspace in pipeline
Title: Message Title Jan Vansteenkiste commented on JENKINS-26660 Re: Add another '-f' to git clean to remove deleted submodules or other repos checked out in workspace in pipeline Adding the extra -f did not resolve the issue of submodules not being there yet in different branches: git rev-parse --verify HEAD # timeout=10 Resetting working tree > git reset --hard # timeout=10 > git clean -ffdx # timeout=10 > git submodule foreach --recursive git reset --hard # timeout=10 > git submodule foreach git clean -fdx # timeout=10 Checking out Revision ab59656484b83bd33e8bdcca07116db660a27b61 (origin/feature/mcollective_modules) > git config core.sparsecheckout # timeout=10 > git checkout -f ab59656484b83bd33e8bdcca07116db660a27b61 > git rev-list ab59656484b83bd33e8bdcca07116db660a27b61 # timeout=10 Cleaning workspace > git rev-parse --verify HEAD # timeout=10 Resetting working tree > git reset --hard # timeout=10 > git clean -ffdx # timeout=10 > git submodule foreach --recursive git reset --hard # timeout=10 > git submodule foreach git clean -fdx # timeout=10 > git remote # timeout=10 > git submodule init # timeout=10 > git submodule sync # timeout=10 > git config --get remote.origin.url # timeout=10 > git config --get-regexp ^submodule # timeout=10 > git config --get submodule.modules/upstream/accounts.url # timeout=10 ... > git submodule update modules/upstream/locales FATAL: Command "git submodule update modules/upstream/locales" returned status code 1: stdout: stderr: error: pathspec 'modules/upstream/locales' did not match any file(s) known to git. Did you forget to 'git add'? hudson.plugins.git.GitException: Command "git submodule update modules/upstream/locales" returned status code 1: stdout: stderr: error: pathspec 'modules/upstream/locales' did not match any file(s) known to git. Did you forget to 'git add'? at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1765) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1509) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$300(CliGitAPIImpl.java:67) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$7.execute(CliGitAPIImpl.java:1052) at hudson.plugins.git.extensions.impl.SubmoduleOption.onCheckoutCompleted(SubmoduleOption.java:102) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1149) at hudson.scm.SCM.checkout(SCM.java:485) at hudson.model.AbstractProject.checkout(AbstractProject.java:1269) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:607) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:529) at hudson.model.Run.execute(Run.java:1738) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:410) In this case, the modules/upstream/locales was added in a previous build from a different branch. my solution was to remove submodule processing and execute git submodule init / sync / update myself.
[JIRA] [ansicolor-plugin] (JENKINS-11752) ANSI color plugin adds garbage to log
Title: Message Title Jan Vansteenkiste updated an issue Jenkins / JENKINS-11752 ANSI color plugin adds garbage to log Change By: Jan Vansteenkiste Priority: Minor Major Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ansicolor-plugin] (JENKINS-11752) ANSI color plugin adds garbage to log
Title: Message Title Jan Vansteenkiste commented on JENKINS-11752 Re: ANSI color plugin adds garbage to log I updated the prio on this to major because nodejs projects tend to have MASSIVE logs when this is enabled. 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] [delivery-pipeline-plugin] (JENKINS-34084) Allow using relative links in the delivery pipeline view for easier navigation.
Title: Message Title Jan Vansteenkiste commented on JENKINS-34084 Re: Allow using relative links in the delivery pipeline view for easier navigation. https://github.com/Diabol/delivery-pipeline-plugin/pull/162 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] [delivery-pipeline-plugin] (JENKINS-34084) Allow using relative links in the delivery pipeline view for easier navigation.
Title: Message Title Jan Vansteenkiste created an issue Jenkins / JENKINS-34084 Allow using relative links in the delivery pipeline view for easier navigation. Issue Type: New Feature Assignee: Patrik Boström Components: delivery-pipeline-plugin Created: 2016/Apr/07 11:51 AM Priority: Minor Reporter: Jan Vansteenkiste Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You recei
[JIRA] [join-plugin] (JENKINS-28979) Trigger if a failed dependency is retried and succeeds
Title: Message Title Jan Vansteenkiste created an issue Jenkins / JENKINS-28979 Trigger if a failed dependency is retried and succeeds Issue Type: Improvement Assignee: mdonohue Components: join-plugin Created: 19/Jun/15 6:22 AM Priority: Major Reporter: Jan Vansteenkiste We have a basic join trigger setup: deploy-test splits out in deploy-test-A, deploy-test-B and the join plugin triggers deploy-test-joined. Sometimes, the A or B job fails due to whatever reason. A retry of these jobs works most of the time but does not trigger the join job. It would be very useful if on a retry of a child job, the parent join is triggered. Add Comment
[JIRA] [ansicolor-plugin] (JENKINS-11752) ANSI color plugin adds garbage to log
Title: Message Title Jan Vansteenkiste commented on JENKINS-11752 Re: ANSI color plugin adds garbage to log Still true for ansicolor 0.4.1 :/ 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] [delivery-pipeline-plugin] (JENKINS-28055) Pipeline arrows are not displaying or displayed incorrectly
Title: Message Title Jan Vansteenkiste commented on JENKINS-28055 Re: Pipeline arrows are not displaying or displayed incorrectly Removing jquery-ui plugin fixes this for me. Feel free to close the issue Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [delivery-pipeline-plugin] (JENKINS-28055) Pipeline arrows are not displaying or displayed incorrectly
Title: Message Title Jan Vansteenkiste commented on JENKINS-28055 Re: Pipeline arrows are not displaying or displayed incorrectly We have: Jenkins ver. 1.596.2 jQuery plugin 1.11.2-0 jQuery UI plugin: 1.0.2 Delivery Pipeline Plugin: 0.9.1 On firefox it is as the screenshot shows. On Mac the arrows are completely invisible. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-pipeline-plugin] (JENKINS-25666) Wrong view for build pipeline plugin
Jan Vansteenkiste commented on JENKINS-25666 Wrong view for build pipeline plugin Looks like the jenkins version is not the issue. my bad To reproduce: Create a dashboard view, add the 'Build pipeline view' as a portlet. 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] [build-pipeline-plugin] (JENKINS-25666) Wrong view for build pipeline plugin
Jan Vansteenkiste edited a comment on JENKINS-25666 Wrong view for build pipeline plugin beneath, see the attached screenshot: 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] [build-pipeline-plugin] (JENKINS-25666) Wrong view for build pipeline plugin
Jan Vansteenkiste commented on JENKINS-25666 Wrong view for build pipeline plugin beneath, see the attached screenshot. 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] [delivery-pipeline-plugin] (JENKINS-28055) Pipeline arrows are not displaying or displayed incorrectly
Jan Vansteenkiste created JENKINS-28055 Pipeline arrows are not displaying or displayed incorrectly Issue Type: Bug Assignee: Patrik Boström Attachments: jenkins_layout_fail.png Components: delivery-pipeline-plugin Created: 23/Apr/15 6:16 AM Description: After the update to the latest LTS (v1.596.2), the arrows are no longer displaying correctly. Project: Jenkins Priority: Minor Reporter: Jan Vansteenkiste 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] [build-pipeline-plugin] (JENKINS-25666) Wrong view for build pipeline plugin
Jan Vansteenkiste updated JENKINS-25666 Wrong view for build pipeline plugin dashboard view ui failure Change By: Jan Vansteenkiste (23/Apr/15 6:05 AM) Attachment: jenkins_layout_fail.png 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] [build-pipeline-plugin] (JENKINS-25666) Wrong view for build pipeline plugin
Jan Vansteenkiste reopened JENKINS-25666 Wrong view for build pipeline plugin With Jenkins v1.596.2, layout is broken again. Change By: Jan Vansteenkiste (23/Apr/15 6:01 AM) Resolution: Fixed Status: Resolved Reopened 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] [scm-sync-configuration-plugin] (JENKINS-24993) scm-sync-configration plugin keeps on adding directory structure scm-sync-configuration/checkoutConfiguration
Jan Vansteenkiste updated JENKINS-24993 scm-sync-configration plugin keeps on adding directory structure scm-sync-configuration/checkoutConfiguration Change By: Jan Vansteenkiste (05/Nov/14 7:34 AM) Priority: Critical Blocker 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] [scm-sync-configuration-plugin] (JENKINS-24993) scm-sync-configration plugin keeps on adding directory structure scm-sync-configuration/checkoutConfiguration
Jan Vansteenkiste commented on JENKINS-24993 scm-sync-configration plugin keeps on adding directory structure scm-sync-configuration/checkoutConfiguration I noticed this after adding a custom include for the first time. 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] [jira] (JENKINS-25014) Allow specifying what jira-plugin matches against other than a commit message.
Jan Vansteenkiste
created JENKINS-25014
Allow specifying what jira-plugin matches against other than a commit message.
Issue Type:
New Feature
Assignee:
Unassigned
Components:
jira
Created:
07/Oct/14 6:21 AM
Description:
Our developers like to create new feature branches for each ticket they are working on. I would like to have the ability to match against the ${GIT_BRANCH} instead of the commit message.
Perhaps allow overriding the text to match against in the job configuration.
Project:
Jenkins
Labels:
jira
Priority:
Minor
Reporter:
Jan Vansteenkiste
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] [ansicolor] (JENKINS-11752) ANSI color plugin adds garbage to log
Jan Vansteenkiste commented on JENKINS-11752 ANSI color plugin adds garbage to log This also increases the log sizes considerably. 100k -> 16mb 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] [promoted-builds] (JENKINS-22094) Promoted builds not picking up injected env settings as of 2.17 (2.15 is ok)
Jan Vansteenkiste commented on JENKINS-22094 Promoted builds not picking up injected env settings as of 2.17 (2.15 is ok) Probably linked to JENKINS-22679 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] [repository-connector] (JENKINS-24243) Add ability to disable using the global configured proxy
Jan Vansteenkiste created JENKINS-24243 Add ability to disable using the global configured proxy Issue Type: Bug Assignee: Unassigned Components: repository-connector Created: 13/Aug/14 11:32 AM Description: After upgrading to 1.0.0, the artifact resolver stopped working for us since we have a global proxy configured but it should not be used for resolving artifacts (these servers run internally). Please add the ability to disable the use of a proxy for all (or certain) repositories. Project: Jenkins Priority: Blocker Reporter: Jan Vansteenkiste 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-12655) GIT_BRANCH is incorrect in build steps when branch choosing strategy is set to inverse (but it is correct in build name macro)
Jan Vansteenkiste commented on JENKINS-12655 GIT_BRANCH is incorrect in build steps when branch choosing strategy is set to inverse (but it is correct in build name macro) Still broken in 1.1.25 :/ 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-9016) Git creates usernames based on 'name' not the email.
Jan Vansteenkiste edited a comment on JENKINS-9016 Git creates usernames based on 'name' not the email. I have created some initial code on this subject. The only question that remains is whether the plugin is the right place for my UserEmailResolver. I also had some troubles getting the tests going and had to add a newer jenkins-core, ui-samples-plugin, jenkins-test-harness and javadoc to the dependencies. https://github.com/vStone/git-plugin/commit/63612268d832edc7a77d0be55e650e31fc5442a9 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-9016) Git creates usernames based on 'name' not the email.
Jan Vansteenkiste commented on JENKINS-9016 Git creates usernames based on 'name' not the email. I have created some initial code on this subject. The only question that remains is whether the plugin is the right place for my UserEmailResolver. I also had some troubles getting the tests going and had to add a newer jenkins-core, ui-samples-plugin, jenkins-test-harness and javadoc to the dependencies. https://github.com/vStone/git-plugin/commit/63612268d832edc7a77d0be55e650e31fc5442a9 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-14663) Allow running of scripts on the local filesystem.
Jan Vansteenkiste edited a comment on JENKINS-14663 Allow running of scripts on the local filesystem. I would like to add a 'path to a script' on the local filesystem in stead of pasting the complete script in. I also realize I could just call the local script from the managed script, so maybe this is a nice to have feature but not really worth the effort. I'll leave that decision up to you 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-14663) Allow running of scripts on the local filesystem.
Jan Vansteenkiste commented on JENKINS-14663 Allow running of scripts on the local filesystem. I would like to add a 'path to a script' on the local filesystem in stead of pasting the complete script in. 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-14663) Allow running of scripts on the local filesystem.
Jan Vansteenkiste created JENKINS-14663 Allow running of scripts on the local filesystem. Issue Type: New Feature Assignee: domi Components: config-file-provider, managed-scripts Created: 02/Aug/12 10:19 AM Description: Sometimes, it might make sense to deploy scripts to jenkins using external packaging or pretty much anything. Having scripts behave more as tools can improve on manageability and keeping your scripts in version control. Project: Jenkins Priority: Major Reporter: Jan Vansteenkiste 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-14662) Allow upload of a script file
Jan Vansteenkiste created JENKINS-14662 Allow upload of a script file Issue Type: New Feature Assignee: domi Components: config-file-provider, managed-scripts Created: 02/Aug/12 10:18 AM Description: For long scripts, It can be a hastle to copy paste them if you already have them locally. Allowing an upload of a file could improve on this. Project: Jenkins Priority: Major Reporter: Jan Vansteenkiste 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
