[JIRA] [ant-plugin] (JENKINS-13044) Ant multiple properties delimited by spaces parsed as a single property
Title: Message Title Ed Randall edited a comment on JENKINS-13044 Re: Ant multiple properties delimited by spaces parsed as a single property You can argue technical points 'til the cows come home, but bad user experience is bad user experience.Don't even fix the help text? It would have taken someone who knows the system less time than writing a comment here - certainly less than 4 years since I raised this in good faith . Just add the words "each on a new line" Why not, just leave it. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ant-plugin] (JENKINS-13044) Ant multiple properties delimited by spaces parsed as a single property
Title: Message Title Ed Randall edited a comment on JENKINS-13044 Re: Ant multiple properties delimited by spaces parsed as a single property You can argue technical points 'til the cows come home, but bad user experience is bad user experience.Don't even fix the help text? It wpuld have taken somepone who knows the system, less time than writing a comment here - certainly less than 4 years. Why not, just leave it. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ant-plugin] (JENKINS-13044) Ant multiple properties delimited by spaces parsed as a single property
Title: Message Title Ed Randall edited a comment on JENKINS-13044 Re: Ant multiple properties delimited by spaces parsed as a single property You can argue technical points 'til the cows come home, but bad user experience is bad user experience.Don't even fix the help text? It wpuld would have taken somepone someone who knows the system , less time than writing a comment here - certainly less than 4 years. Why not, just leave it. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ant-plugin] (JENKINS-13044) Ant multiple properties delimited by spaces parsed as a single property
Title: Message Title Ed Randall commented on JENKINS-13044 Re: Ant multiple properties delimited by spaces parsed as a single property You can argue technical points 'til the cows come home, but bad user experience is bad user experience. Don't even fix the help text? Why not, just leave it. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [token-macro-plugin] (JENKINS-32331) Performance problems on scan on huge Jenkins instances
Title: Message Title Tomas Westling commented on JENKINS-32331 Re: Performance problems on scan on huge Jenkins instances We have also seen some performance issues in the BFA, but only on our less powerful machines, that have other performance issues as well, so we haven't had the need to look further into the issues. As a Jenkins instance gets bigger, with more jobs, more rules and longer logs to analyze, this could get out of hand, we just haven't seen it in our installation yet, but it seems you have. Good find on the token-macro plugin, if the pull request can get merged, it seems like a cheap solution. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-32190) UsageStatistics Page Decorator may get called during initialization.
Title: Message Title Oliver Gondža updated an issue Jenkins / JENKINS-32190 UsageStatistics Page Decorator may get called during initialization. Change By: Oliver Gondža Labels: lts 1.642.2 - candidate 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] [core] (JENKINS-32567) Downgrade “termination trace” warnings in Jenkins logs
Title: Message Title Oliver Gondža commented on JENKINS-32567 Re: Downgrade “termination trace” warnings in Jenkins logs What Daniel had in mind is issues are usually tracked for master bugs and I consider them for backporting only after they are resoled (on master). I have updated the docs so users can recheck if their candidates do not get ignored: https://wiki.jenkins-ci.org/pages/diffpages.action?pageId=57180302&originalId=93456004. 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] [multiple-scms-plugin] (JENKINS-30243) NoClassDefFoundError during startup (Template Project plugin 1.5)
Title: Message Title Brantone edited a comment on JENKINS-30243 Re: NoClassDefFoundError during startup (Template Project plugin 1.5) [~tsniatowski] : - can you trace that error back to Template Plugin? If some cause it but others don't, might not be Template -EDIT:Let me take that back, I actually found how/why that's happening. That error itself is actually different than the one for this ticket, so new ticket should be created (unless I fix the bug first, it's a race :) ) Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-32567) Downgrade “termination trace” warnings in Jenkins logs
Title: Message Title Oliver Gondža updated an issue Jenkins / JENKINS-32567 Downgrade “termination trace” warnings in Jenkins logs Change By: Oliver Gondža Labels: lts 1.642.2 - candidate 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] [core] (JENKINS-31932) Performance regression after fixing synchronization issue when setting JDK installations. (issue 28292)
Title: Message Title Oliver Gondža updated an issue Jenkins / JENKINS-31932 Performance regression after fixing synchronization issue when setting JDK installations. (issue 28292) Change By: Oliver Gondža Labels: lts 1.642.2 - candidate fixed regression 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] [customtools-plugin] (JENKINS-32739) Unable to export path in matrix jobs.
Title: Message Title
Wenzheng Jiang updated an issue
Jenkins / JENKINS-32739
Unable to export path in matrix jobs.
Change By:
Wenzheng Jiang
When using customTools plugin, I export the installation path by putting them in "Exported paths". But these paths don't appear later in PATH in matrixjobs, while it works fine in freestylejobs. My installer configuration is :Name: phpenvExported paths; phpenv/bin,phpenv/shimsCommand :```export PHPENV_ROOT=$(pwd)/phpenvexport PATH="$PATH:$PHPENV_ROOT/bin"(if ! flock --exclusive --nonblock 9; thenflock --exclusive 9exit 1fiif test -d $PHPENV_ROOT; then echo 'phpenv installed'elsecurl -L http://git.io/phpenv-installer | bashfiif ! test -d $PHPENV_ROOT/shims; thenmkdir $PHPENV_ROOT/shimsfi) 9>phpenv.lockeval "$(phpenv init -)"```My Job configuration is Axis config:Name: PHP_VERSIONValue: 5.3.29 5.4.45 5.5.30Build config:```phpenv versions | grep ${PHP_VERSION} || phpenv install ${PHP_VERSION}```In the building process, I got 'phpenv not found' error and reason is the installation path is not in $PATH. This problem is solved !
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] [customtools-plugin] (JENKINS-32739) Unable to export path in matrix jobs.
Title: Message Title Wenzheng Jiang commented on JENKINS-32739 Re: Unable to export path in matrix jobs. Well, that problem seems to be disappeared for some reason ... So never mind 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] [customtools-plugin] (JENKINS-32739) Unable to export path in matrix jobs.
Title: Message Title
Wenzheng Jiang updated an issue
Jenkins / JENKINS-32739
Unable to export path in matrix jobs.
Change By:
Wenzheng Jiang
When using customTools plugin, I export the installation path by putting them in "Exported paths". But these paths don't appear later in PATH in matrixjobs, while it works fine in freestylejobs. My installer configuration is :Name: phpenvExported paths; phpenv/bin,phpenv/shimsCommand :```export PHPENV_ROOT=$(pwd)/phpenvexport PATH="$PATH:$PHPENV_ROOT/bin"(if ! flock --exclusive --nonblock 9; thenflock --exclusive 9exit 1fiif test -d $PHPENV_ROOT; then echo 'phpenv installed'elsecurl -L http://git.io/phpenv-installer | bashfiif ! test -d $PHPENV_ROOT/shims; thenmkdir $PHPENV_ROOT/shimsfi) 9>phpenv.lockeval "$(phpenv init -)"``` I also export the path in the installer command, but it also doesn't work My Job configuration is Axis config:Name: PHP_VERSIONValue: 5 . 3.29 5.4.45 5.5.30Build config:```phpenv versions | grep ${PHP_VERSION} || phpenv install ${PHP_VERSION}``` In the building process, I get got 'phpenv not found' error and reason is the installation path is not in $PATH.
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] [customtools-plugin] (JENKINS-32739) Unable to export path in matrix jobs.
Title: Message Title Wenzheng Jiang updated an issue Jenkins / JENKINS-32739 Unable to export path in matrix jobs. Change By: Wenzheng Jiang When using customTools plugin, I export the installation path by putting them in "Exported paths". But these paths don't appear later in PATH in matrixjobs, while it works fine in freestylejobs. My installer configuration is :Name: phpenvExported paths; phpenv/bin,phpenv/shimsCommand :```export PHPENV_ROOT=$(pwd)/phpenvexport PATH="$PATH:$PHPENV_ROOT/bin"(if ! flock --exclusive --nonblock 9; thenflock --exclusive 9exit 1fiif test -d $PHPENV_ROOT; then # phpenv update echo 'phpenv installed'elsecurl -L http://git.io/phpenv-installer | bashfiif ! test -d $PHPENV_ROOT/shims; thenmkdir $PHPENV_ROOT/shimsfi) 9>phpenv.lockeval "$(phpenv init -)"```I also export the path in the installer command, but it also doesn't work. In the building process, I get 'phpenv not found' error and reason is the installation path is not in $PATH. 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] [customtools-plugin] (JENKINS-32739) Unable to export path in matrix jobs.
Title: Message Title Wenzheng Jiang updated an issue Jenkins / JENKINS-32739 Unable to export path in matrix jobs. Change By: Wenzheng Jiang When using customTools plugin, I export the installation path by putting them in "Exported paths". But these paths don't appear later in PATH in matrixjobs, while it works fine in freestylejobs. My installer configuration is :Name: phpenvExported paths; phpenv/bin,phpenv/shimsCommand :```export PHPENV_ROOT=$(pwd)/phpenvexport PATH="$PATH:$PHPENV_ROOT/bin" # Use `flock` to ensure that we do not install/update `phpenv` simultaneously across different jobs. (if ! flock --exclusive --nonblock 9; then # Wait for the lock to be released and then continue. flock --exclusive 9exit 1fiif test -d $PHPENV_ROOT; then # phpenv update echo 'phpenv installed'elsecurl -L http://git.io/phpenv-installer | bashfiif ! test -d $PHPENV_ROOT/shims; thenmkdir $PHPENV_ROOT/shimsfi) 9>phpenv.lockeval "$(phpenv init -)"```I also export the path in the installer command, but it also doesn't work. In the building process, I get 'phpenv not found' error and reason is the installation path is not in $PATH. 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] [customtools-plugin] (JENKINS-32739) Unable to export path in matrix jobs.
Title: Message Title Wenzheng Jiang updated an issue Jenkins / JENKINS-32739 Unable to export path in matrix jobs. Change By: Wenzheng Jiang When using customTools plugin, I export the installation path by putting them in "Exported paths". But these paths don't appear later in PATH in matrixjobs, while it works fine in freestylejobs. My installer configuration is :Name: phpenvExported paths; phpenv/bin,phpenv/shimsCommand :```export PHPENV_ROOT=$(pwd)/phpenvexport PATH="$PATH:$PHPENV_ROOT/bin"# Use `flock` to ensure that we do not install/update `phpenv` simultaneously across different jobs.(if ! flock --exclusive --nonblock 9; then# Wait for the lock to be released and then continue.flock --exclusive 9exit 1fiif test -d $PHPENV_ROOT; then # phpenv update echo 'phpenv installed'elsecurl -L http://git.io/phpenv-installer | bashfiif ! test -d $PHPENV_ROOT/shims; thenmkdir $PHPENV_ROOT/shimsfi) 9>phpenv.lockeval "$(phpenv init -)"``` I also export the path in the installer command, but it also doesn't work. In the building process, I get 'phpenv not found' error and reason is the installation path is not in $PATH. 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] [customtools-plugin] (JENKINS-32739) Unable to export path in matrix jobs.
Title: Message Title Wenzheng Jiang commented on JENKINS-32739 Re: Unable to export path in matrix jobs. Updated description 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] [customtools-plugin] (JENKINS-32739) Unable to export path in matrix jobs.
Title: Message Title Wenzheng Jiang updated an issue Jenkins / JENKINS-32739 Unable to export path in matrix jobs. Change By: Wenzheng Jiang Attachment: 2.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] [customtools-plugin] (JENKINS-32739) Unable to export path in matrix jobs.
Title: Message Title Wenzheng Jiang updated an issue Jenkins / JENKINS-32739 Unable to export path in matrix jobs. Change By: Wenzheng Jiang When using customTools plugin, I export the installation path by putting them in "Exported paths". But these paths don't appear later in PATH in matrixjobs, while it works fine in freestylejobs. My installer configuration is :Name: phpenvExported paths; phpenv/bin,phpenv/shimsCommand : ``` export PHPENV_ROOT=$(pwd)/phpenvexport PATH="$PATH:$PHPENV_ROOT/bin"# Use `flock` to ensure that we do not install/update `phpenv` simultaneously across different jobs.(if ! flock --exclusive --nonblock 9; then# Wait for the lock to be released and then continue.flock --exclusive 9exit 1fiif test -d $PHPENV_ROOT; then # phpenv update echo 'phpenv installed'elsecurl -L http://git.io/phpenv-installer | bashfiif ! test -d $PHPENV_ROOT/shims; thenmkdir $PHPENV_ROOT/shimsfi) 9>phpenv.lockeval "$(phpenv init -)" ``` 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] [customtools-plugin] (JENKINS-32739) Unable to export path in matrix jobs.
Title: Message Title Wenzheng Jiang updated an issue Jenkins / JENKINS-32739 Unable to export path in matrix jobs. Change By: Wenzheng Jiang When using customTools plugin, I export the installation path by putting them in "Exported paths". But these paths don't appear later in PATH in matrixjobs, while it works fine in freestylejobs. My installer configuration is :Name: phpenvExported paths; phpenv/bin,phpenv/shimsCommand :export PHPENV_ROOT=$(pwd)/phpenvexport PATH="$PATH:$PHPENV_ROOT/bin"# Use `flock` to ensure that we do not install/update `phpenv` simultaneously across different jobs.(if ! flock --exclusive --nonblock 9; then# Wait for the lock to be released and then continue.flock --exclusive 9exit 1fiif test -d $PHPENV_ROOT; then # phpenv update echo 'phpenv installed'elsecurl -L http://git.io/phpenv-installer | bashfiif ! test -d $PHPENV_ROOT/shims; thenmkdir $PHPENV_ROOT/shimsfi) 9>phpenv.lockeval "$(phpenv init -)" Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-32742) Make environment contributors extensible
Title: Message Title Damien Coraboeuf created an issue Jenkins / JENKINS-32742 Make environment contributors extensible Issue Type: Improvement Assignee: Daniel Spilker Components: job-dsl-plugin Created: 03/Feb/16 6:10 AM Environment: 1.42 Priority: Major Reporter: Damien Coraboeuf Hi, The environmentVariables / contributors section should be made extensible in order to facilitate the inclusion of extensions. This is a simple update to do and I'm preparing the pull request. Damien. Add Comment
[JIRA] [customtools-plugin] (JENKINS-32739) Unable to export path in matrix jobs.
Title: Message Title Wenzheng Jiang updated an issue Jenkins / JENKINS-32739 Unable to export path in matrix jobs. Change By: Wenzheng Jiang Environment: Jenkins 1.646 Custom Tools Plugin 0.4.4 Matrix Project Plugin 1.6 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-31219) A CloudProvisioningListener can prevent provisioning of all clouds instead of just the targeted cloud
Title: Message Title Oliver Gondža updated an issue Jenkins / JENKINS-31219 A CloudProvisioningListener can prevent provisioning of all clouds instead of just the targeted cloud Change By: Oliver Gondža Labels: lts 1.642.2 - candidate 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] [core] (JENKINS-20327) “Form too large” errors submitting view configurations with many jobs
Title: Message Title Oliver Gondža updated an issue Jenkins / JENKINS-20327 “Form too large” errors submitting view configurations with many jobs Change By: Oliver Gondža Labels: jetty lts-candidate performance view Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-20327) “Form too large” errors submitting view configurations with many jobs
Title: Message Title Oliver Gondža commented on JENKINS-20327 Re: “Form too large” errors submitting view configurations with many jobs Not a candidate for 1.642 based LTS as it was fixed in 1.639. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-31321) Renaming a node over another is possible and destroys both configurations
Title: Message Title Oliver Gondža updated an issue Jenkins / JENKINS-31321 Renaming a node over another is possible and destroys both configurations Change By: Oliver Gondža Labels: lts 1.642.2 - candidate 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] [multiple-scms-plugin] (JENKINS-27638) GIT : Fatal : ClassCastException: hudson.scm.SCMRevisionState$None cannot be cast to org.jenkinsci.plugins.multiplescms.MultiSCMRevisionState
Title: Message Title Brantone commented on JENKINS-27638 Re: GIT : Fatal : ClassCastException: hudson.scm.SCMRevisionState$None cannot be cast to org.jenkinsci.plugins.multiplescms.MultiSCMRevisionState Was for 0.4, and 0.5 was released in July. 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] [ant-plugin] (JENKINS-13044) Ant multiple properties delimited by spaces parsed as a single property
Title: Message Title Nikolas Falco commented on JENKINS-13044 Re: Ant multiple properties delimited by spaces parsed as a single property Inline Help reports: Properties needed by your ant build can be specified here (in standard properties file format): # comment name1=value1 name2=$VAR2 These are passed to Ant like "-Dname1=value1 -Dname2=value2". ... The documentation clearly describes that in this box you have to write in it as a property file and is not as out of place as you are setup an Ant step, and Ant it's property based so there is nothing new. Moreover consider that changing this behaviour is not more backward compatible with current and people should checks impact on their job. All the expandableTextbox comes one line with a "dropdown" button to avoid waste the page space. If textbox has already a multiline value it is presented automatically expanded. It's not necessary see more line to understand users that could put here more than a single line property because it's a widget widely used by plugins. 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] [multiple-scms-plugin] (JENKINS-30243) NoClassDefFoundError during startup (Template Project plugin 1.5)
Title: Message Title Brantone commented on JENKINS-30243 Re: NoClassDefFoundError during startup (Template Project plugin 1.5) Tomasz Śniatowski : can you trace that error back to Template Plugin? If some cause it but others don't, might not be Template 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] [template-project-plugin] (JENKINS-19441) Add detection of the template projects renaming
Title: Message Title Brantone commented on JENKINS-19441 Re: Add detection of the template projects renaming For some reason didn't link PR: https://github.com/jenkinsci/template-project-plugin/pull/27 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] [template-project-plugin] (JENKINS-30436) template proxy/proxyscm does not output useful error if source project name doesn't exist
Title: Message Title Brantone commented on JENKINS-30436 Re: template proxy/proxyscm does not output useful error if source project name doesn't exist For some reason didn't link PR: https://github.com/jenkinsci/template-project-plugin/pull/27 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] [template-project-plugin] (JENKINS-30435) Renaming project doesn't update references in proxy scm configuration
Title: Message Title Brantone commented on JENKINS-30435 Re: Renaming project doesn't update references in proxy scm configuration For some reason didn't link PR: https://github.com/jenkinsci/template-project-plugin/pull/27 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] [template-project-plugin] (JENKINS-31712) Use SCM from another project is removed after upgrading to 1.5.1
Title: Message Title Brantone commented on JENKINS-31712 Re: Use SCM from another project is removed after upgrading to 1.5.1 I don't suppose you have Multiple-SCM plugin installed? If not, if you do install it, does it work? 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] [template-project-plugin] (JENKINS-31712) Use SCM from another project is removed after upgrading to 1.5.1
Title: Message Title Brantone commented on JENKINS-31712 Re: Use SCM from another project is removed after upgrading to 1.5.1 The mention of "1.5.2" looks like a silly typo and getting mixed up with new snapshot as opposed to completing 1.5.1, woops. Updated Wiki page Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [template-project-plugin] (JENKINS-24404) Environment variables not exported with "Use SCM from another project"
Title: Message Title Brantone commented on JENKINS-24404 Re: Environment variables not exported with "Use SCM from another project" While this technically works for explicit project names, it still has issues when a parameter is provided : because it need the env to get the param's value, which it's trying to set - so circular path 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] [amazon-ecs-plugin] (JENKINS-32741) Allow the log driver to be specified for an ECS Task
Title: Message Title Lee Webb created an issue Jenkins / JENKINS-32741 Allow the log driver to be specified for an ECS Task Issue Type: Improvement Assignee: Nicolas De Loof Components: amazon-ecs-plugin Created: 03/Feb/16 3:13 AM Environment: n/a Priority: Minor Reporter: Lee Webb This is a feature request to allow the LogConfiguration to be set within the ECS API such that an alternate log driver can be chosen for a particular TaskTemplate Intention is to allow for the usage of say the syslog driver so that you can get some sort of visibility happening on the Jenkins Slave remoting jar if you happen to be aggregating logs to a central place in your EC2 ECS optimised AMI's See https://github.com/jenkinsci/amazon-ecs-plugin/pull/16
[JIRA] [customtools-plugin] (JENKINS-32739) Unable to export path in matrix jobs.
Title: Message Title Oleg Nenashev commented on JENKINS-32739 Re: Unable to export path in matrix jobs. Cannot reproduce. Which versions of Matrix project and Custom Tools do you use? 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] [amazon-ecs-plugin] (JENKINS-32740) Slaves which never connect due to ECS resource constraints never get removed
Title: Message Title Lee Webb created an issue Jenkins / JENKINS-32740 Slaves which never connect due to ECS resource constraints never get removed Issue Type: Bug Assignee: Nicolas De Loof Components: amazon-ecs-plugin Created: 03/Feb/16 2:44 AM Environment: https://github.com/jenkinsci/amazon-ecs-plugin/commit/88f43cef39dfd6bd4e0f9856dbe91eba9f22fcc2 Priority: Critical Reporter: Lee Webb I've given a build of master a go in order to get mount points (among other things) happening in my ECS slaves. What I've noticed as part of https://github.com/jenkinsci/amazon-ecs-plugin/commit/88f43cef39dfd6bd4e0f9856dbe91eba9f22fcc2 is that any Slaves which are created but never have a matching ECS task created (such as due to resource constraints, ala. memory) never get cleaned up by Jenkins. At the moment I have some 2500+ ECS Slaves in Jenkins which don't appear to want to go away as I don't think that there's any Jenkins thread looking after them as a result of the RetentionStrategy.NOOP I'll make a PR as I believe that having a RetentionStrategy of some sort is actually needed, or there's a listener on the cloud provisioning bit to inhibit the creation of a slave if there are no ECS resources available to create a task
[JIRA] [envinject-plugin] (JENKINS-30069) versionnumber plugin should resolve vars from "envinject" plugin
Title: Message Title Rami Abughazaleh updated an issue Jenkins / JENKINS-30069 versionnumber plugin should resolve vars from "envinject" plugin Change By: Rami Abughazaleh Comment: Here's what worked for me:1. Install the "Pre SCM BuildStep Plugin"2. Enable to "Run buildstep before SCM runs" in job configuration3. Add a build step "Inject environment variables" within the "Pre SCM BuildStep"4. Now you can use the environment variable in the "Version Number Format String" 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-30069) versionnumber plugin should resolve vars from "envinject" plugin
Title: Message Title Rami Abughazaleh commented on JENKINS-30069 Re: versionnumber plugin should resolve vars from "envinject" plugin Here's what worked for me: 1. Install the "Pre SCM BuildStep Plugin" 2. Enable to "Run buildstep before SCM runs" in job configuration 3. Add a build step "Inject environment variables" within the "Pre SCM BuildStep" 4. Now you can use the environment variable in the "Version Number Format String" 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] [cloudformation-plugin] (JENKINS-31777) A job instance will delete other instance's Stack
Title: Message Title lsb want edited a comment on JENKINS-31777 Re: A job instance will delete other instance's Stack I have create a pull request for this issue, I am not sure if good, but it worked. I have a test https://github.com/jenkinsci/jenkins-cloudformation-plugin/ pulls pull/21 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] [cloudformation-plugin] (JENKINS-26304) Output variables missing while using AWS CloudFormation as build-step
Title: Message Title lsb want commented on JENKINS-26304 Re: Output variables missing while using AWS CloudFormation as build-step I got this issue too, I think this pull request also can fix this issue https://github.com/jenkinsci/jenkins-cloudformation-plugin/pull/22. @nickveenhof Sorry nickveenhof , I reference your patch. and make a little different. Would I to this. https://github.com/jenkinsci/jenkins-cloudformation-plugin/pull/23 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] [cloudformation-plugin] (JENKINS-31777) A job instance will delete other instance's Stack
Title: Message Title lsb want commented on JENKINS-31777 Re: A job instance will delete other instance's Stack I have create a pull request for this issue, I am not sure if good, but it worked. I have a test https://github.com/jenkinsci/jenkins-cloudformation-plugin/pulls 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] [cloudformation-plugin] (JENKINS-30391) Unable to run 2 builds of same job with CloudFormation plugin
Title: Message Title lsb want commented on JENKINS-30391 Re: Unable to run 2 builds of same job with CloudFormation plugin I think this pull request would fix this issue https://github.com/jenkinsci/jenkins-cloudformation-plugin/pull/24 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] [p4-plugin] (JENKINS-30353) Add perforce-plugin-style nodename hash to workspace environment variables expansion
Title: Message Title
Paul "TBBle" Hampson commented on JENKINS-30353
Re: Add perforce-plugin-style nodename hash to workspace environment variables expansion
If anyone else hits this issue, we're working around it locally with the following Groovy script, run before the SCM as a 'Execute system Groovy script' step:
// Work around https://issues.jenkins-ci.org/browse/JENKINS-30353
import hudson.model.*
def pa = new ParametersAction([
new StringParameterValue("NODE_NAME_HASH", String.valueOf(Thread.currentThread().executable.getBuiltOn().hashCode()))
])
// add variable to current job
Thread.currentThread().executable.addAction(pa)
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] [customtools-plugin] (JENKINS-32739) Unable to export path in matrix jobs.
Title: Message Title Wenzheng Jiang created an issue Jenkins / JENKINS-32739 Unable to export path in matrix jobs. Issue Type: Bug Assignee: Oleg Nenashev Attachments: 2.png Components: customtools-plugin Created: 03/Feb/16 1:12 AM Environment: Jenkins 1.646 Custom Tools Plugin 0.4.4 Priority: Minor Reporter: Wenzheng Jiang When using customTools plugin, I export the installation path by putting them in "Exported paths". But these paths don't appear later in PATH in matrixjobs, while it works fine in freestylejobs.
[JIRA] [pagerduty-plugin] (JENKINS-32738) on success, the plugin should resolve the issue
Title: Message Title Alex Gray created an issue Jenkins / JENKINS-32738 on success, the plugin should resolve the issue Issue Type: New Feature Assignee: Alexander Leibzon Components: pagerduty-plugin Created: 03/Feb/16 12:50 AM Priority: Major Reporter: Alex Gray It would be so cool if the plugin would auto-resolve the pager duty alert when a build passes. I think it would be a good enhancement to add to this plugin. Add Comment
[JIRA] [android-emulator-plugin] (JENKINS-32737) Certain configurations fail to create emulator due to specifying wrong ABI tag
Title: Message Title Christopher Orr created an issue Jenkins / JENKINS-32737 Certain configurations fail to create emulator due to specifying wrong ABI tag Issue Type: Bug Assignee: Christopher Orr Components: android-emulator-plugin Created: 03/Feb/16 12:11 AM Priority: Major Reporter: Christopher Orr From https://stackoverflow.com/questions/35059957/cannot-create-emulator-via-jenkins-android-emulator-plugin: — When Jenkins tries to generate my emulator, it errors out with: tools/android create avd -f -a -c 256M -s 1080x1920 -n hudson_de-DE_480_1080x1920_Google_Inc._Google_APIs_23_x86 -t "Google Inc.:Google APIs:23" --abi x86 Error: Invalid --tag default for the selected target. But tools/android list targets outputs id: 6 or "Google Inc.:Google APIs:23" ... Tag/ABIs : google_apis/x86 — Back when I implemented support for ABI tags, I seem to recall it being impossible to discover the correct tag in every single case, but from this report, it should be seemingly simple enough to determine automatically choose the correct tag for this case at least. I can't remember what the implementation looks
[JIRA] [performance-plugin] (JENKINS-28284) Images for Test Case trends is broken and generate exception
Title: Message Title dave davejenk commented on JENKINS-28284 Re: Images for Test Case trends is broken and generate exception Reverting to 1.11 fixed our problem (linus jenkins 1.637). 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] [workflow-plugin] (JENKINS-32731) Allow plugins to contribute to Pipeline global library
Title: Message Title
Michael Neale commented on JENKINS-32731
Re: Allow plugins to contribute to Pipeline global library
The only real problem I can forsee is that the names of DSL files in the global lib are, well, global.
eg:
builg.groovy is used as
build { .. }
In the script. If you install 2 plugins that each want to have a build.groovy - how is the conflict resolved? will the second one they install fail? (I fear to suggest qualified imports as that kind of harshes the vibe, but some way to resolve this may be warranted).
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] [performance-plugin] (JENKINS-28284) Images for Test Case trends is broken and generate exception
Title: Message Title Zhenya Frolov commented on JENKINS-28284 Re: Images for Test Case trends is broken and generate exception Thanks for the followup, dave davejenk. Unfortunately, we had config issues when trying the 1.14 build and other issues came up, which put this on the backburner. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-5150) Race condition for feature "Block build when upstream project is building"
Title: Message Title Dirk Thomas commented on JENKINS-5150 Re: Race condition for feature "Block build when upstream project is building" I think we have the same problem with the current LTS 1.642.1. Please see the detailed description of our case: https://github.com/ros-infrastructure/ros_buildfarm/pull/194 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] [versionnumber-plugin] (JENKINS-32736) Ability to support simple arithmetic with the build version number
Title: Message Title
Rami Abughazaleh updated an issue
Jenkins / JENKINS-32736
Ability to support simple arithmetic with the build version number
Change By:
Rami Abughazaleh
Thank you for the versionnumber Jenkins plugin.I would like the versionnumber Jenkins plugin to support simple arithmetic to calculate the build version number.An example version number format string: {code:java} 1.0.(1200 * ${YEARS_SINCE_PROJECT_START}) + ${BUILD_MONTH, X}${BUILD_DAY, XX}.${BUILDS_TODAY, X} {code} In this way, if my project started in 2015, the last build in that year would have a version number of 1.0.1231.1 for example.And then instead of having to increment the minor version number, the next build in the new year would be 1.0.1301.1 for example.It doesn't seem that the plugin currently supports this.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] [versionnumber-plugin] (JENKINS-32736) Ability to support simple arithmetic with the build version number
Title: Message Title
Rami Abughazaleh created an issue
Jenkins / JENKINS-32736
Ability to support simple arithmetic with the build version number
Issue Type:
Bug
Assignee:
Unassigned
Components:
versionnumber-plugin
Created:
02/Feb/16 10:28 PM
Environment:
Jenkins 1.646 Version Number Plug-In v1.6
Labels:
plugins
Priority:
Minor
Reporter:
Rami Abughazaleh
Thank you for the versionnumber Jenkins plugin.
I would like the versionnumber Jenkins plugin to support simple arithmetic to calculate the build version number.
An example version number format string: 1.0.(1200 * $ {YEARS_SINCE_PROJECT_START}
) + $ {BUILD_MONTH, X}
$ {BUILD_DAY, XX}
.$ {BUILDS_TODAY, X}
In this way, if my project started in 2015, the last build in that year would have a version
[JIRA] [next-build-number-plugin] (JENKINS-27958) Cannot reset the next build number
Title: Message Title Maninder Singh closed an issue as Cannot Reproduce Cannot reproduce Jenkins / JENKINS-27958 Cannot reset the next build number Change By: Maninder Singh 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] [next-build-number-plugin] (JENKINS-27958) Cannot reset the next build number
Title: Message Title Maninder Singh resolved as Cannot Reproduce Jenkins / JENKINS-27958 Cannot reset the next build number Change By: Maninder Singh Status: Reopened Resolved Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [promoted-builds-plugin] (JENKINS-31406) Promotion Status shows an excess of whitespace (missed one)
Title: Message Title Oleg Nenashev commented on JENKINS-31406 Re: Promotion Status shows an excess of whitespace (missed one) I do not commit to fix it soon. Too many high-priority tasks in the queue, the priority of this one is "Minor" Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [promoted-builds-plugin] (JENKINS-31406) Promotion Status shows an excess of whitespace (missed one)
Title: Message Title Oleg Nenashev assigned an issue to Oleg Nenashev Jenkins / JENKINS-31406 Promotion Status shows an excess of whitespace (missed one) Change By: Oleg Nenashev Assignee: Oleg Nenashev Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [promoted-builds-plugin] (JENKINS-31406) Promotion Status shows an excess of whitespace (missed one)
Title: Message Title jurgezero assigned an issue to Oleg Nenashev Jenkins / JENKINS-31406 Promotion Status shows an excess of whitespace (missed one) Change By: jurgezero Assignee: Manuel Jesús Recena Soto Oleg Nenashev Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [promoted-builds-plugin] (JENKINS-31406) Promotion Status shows an excess of whitespace (missed one)
Title: Message Title jurgezero assigned an issue to Unassigned Jenkins / JENKINS-31406 Promotion Status shows an excess of whitespace (missed one) Change By: jurgezero Assignee: Oleg Nenashev Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-32630) Branches to build does not take into account which branch is most recent
Title: Message Title Mark Waite commented on JENKINS-32630 Re: Branches to build does not take into account which branch is most recent Yes, I'm quite willing to accept proposed improvements to the help. Changing help has very little risk of regressing functionality, and may improve the experience for users that read it. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-32735) Swarm and Git SCM fails with java.lang.NoClassDefFoundError: Could not initialize class java.util.Currency
Title: Message Title Mark Waite commented on JENKINS-32735 Re: Swarm and Git SCM fails with java.lang.NoClassDefFoundError: Could not initialize class java.util.Currency I suspect that without Git SCM, you probably aren't making many remote file system calls, or are making different types of remote file system calls. My first hunch is that the issue is somehow in your choice of virtual machine on the swarm client side, or possibly an unexpected incompatibility between your Jenkins version and the swarm client version you're using. I'm not a big user of swarm clients, but I have a few, and they run git just fine. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client-plugin] (JENKINS-32712) Job with Git polling "succeeds" with "no changes" although the Git polling failed
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-32712 Job with Git polling "succeeds" with "no changes" although the Git polling failed Change By: Mark Waite Assignee: Nicolas De Loof 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] [hp-application-automation-tools-plugin] (JENKINS-32734) Please document that this plugin is Windows-only.
Title: Message Title Robert Vincent updated an issue Jenkins / JENKINS-32734 Please document that this plugin is Windows-only. Change By: Robert Vincent I have discovered that the hp-application-automation-tools-plugin requires Windows, as it deploys and attempts to run a Windows 32-bit executable.I would suggest that " win32 32-bit Windows " be added to the [Prerequisites list ]( | https://wiki.jenkins-ci.org/display/JENKINS/HP+Application+Automation+Tools#HPApplicationAutomationTools-UserGuide ) ] on the [plugin page ]( | https://wiki.jenkins-ci.org/display/JENKINS/HP+Application+Automation+Tools ) ] . Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-32735) Swarm and Git SCM fails with java.lang.NoClassDefFoundError: Could not initialize class java.util.Currency
Title: Message Title Jay Shirley commented on JENKINS-32735 Re: Swarm and Git SCM fails with java.lang.NoClassDefFoundError: Could not initialize class java.util.Currency Thanks Mark! To be clear, if I disable the Git SCM and put in a build script to fetch from Git everything is fine. This behavior only starts if the project is configured to use the Git SCM. It also doesn't seem to occur if I use the same configuration in a local Vagrant image that doesn't use Swarm… but that's not testing the same behavior, so not too relevant. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-32735) Swarm and Git SCM fails with java.lang.NoClassDefFoundError: Could not initialize class java.util.Currency
Title: Message Title Mark Waite commented on JENKINS-32735 Re: Swarm and Git SCM fails with java.lang.NoClassDefFoundError: Could not initialize class java.util.Currency I don't think the "class not found" message is related to the git plugin, other than the fact that the git plugin is trying to make a remote call. I've assigned this to core in hopes someone on core can assist. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-32735) Swarm and Git SCM fails with java.lang.NoClassDefFoundError: Could not initialize class java.util.Currency
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-32735 Swarm and Git SCM fails with java.lang.NoClassDefFoundError: Could not initialize class java.util.Currency Change By: Mark Waite Component/s: core Component/s: git-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] [git-plugin] (JENKINS-32735) Swarm and Git SCM fails with java.lang.NoClassDefFoundError: Could not initialize class java.util.Currency
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-32735 Swarm and Git SCM fails with java.lang.NoClassDefFoundError: Could not initialize class java.util.Currency Change By: Mark Waite Assignee: Mark Waite Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-32735) Swarm and Git SCM fails with java.lang.NoClassDefFoundError: Could not initialize class java.util.Currency
Title: Message Title Jay Shirley created an issue Jenkins / JENKINS-32735 Swarm and Git SCM fails with java.lang.NoClassDefFoundError: Could not initialize class java.util.Currency Issue Type: Bug Assignee: Mark Waite Attachments: consoleText.txt Components: git-plugin Created: 02/Feb/16 7:39 PM Environment: Jenkins 1.646, Git Plugin 2.4.1, Git client plugin 1.19.2; Ubuntu 14.04.1 java 1.7.0 p95, OpenJDK 7u95-2.6.4-0 64-bit build 24.95-b01, mixed mode Labels: plugin git-plugin swarm git-client Priority: Critical Reporter: Jay Shirley We are moving from a custom script to the Git SCM. Our previous script works fine, connecting to the remote agent and executing the script. The Git SCM errors out immediately, upon creating the git cl
[JIRA] [p4-plugin] (JENKINS-25145) Version Jenkins Configuration In Perforce
Title: Message Title
Jim Poje commented on JENKINS-25145
Re: Version Jenkins Configuration In Perforce
Current code for this functionality crashes for me. I do not see a mechanism to disable this feature entirely, so supplying empty values causes the crash.
{{Jan 26, 2016 3:13:36 PM hudson.model.listeners.SaveableListener fireOnChange WARNING: null java.lang.NullPointerException at org.jenkinsci.plugins.p4.ConfigurationListener.onChange(ConfigurationListener.java:38) at hudson.model.listeners.SaveableListener.fireOnChange(SaveableListener.java:81) at hudson.model.ComputerSet$1.save(ComputerSet.java:82) at hudson.util.PersistedList.onModified(PersistedList.java:173)}}
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] [hp-application-automation-tools-plugin] (JENKINS-32734) Please document that this plugin is Windows-only.
Title: Message Title Robert Vincent created an issue Jenkins / JENKINS-32734 Please document that this plugin is Windows-only. Issue Type: Bug Assignee: Ofir Shaked Components: hp-application-automation-tools-plugin Created: 02/Feb/16 7:27 PM Priority: Minor Reporter: Robert Vincent I have discovered that the hp-application-automation-tools-plugin requires Windows, as it deploys and attempts to run a Windows 32-bit executable. I would suggest that "win32" be added to the [Prerequisites list](https://wiki.jenkins-ci.org/display/JENKINS/HP+Application+Automation+Tools#HPApplicationAutomationTools-UserGuide) on the [plugin page](https://wiki.jenkins-ci.org/display/JENKINS/HP+Application+Automation+Tools). Add Comment
[JIRA] [publish-over-ssh-plugin] (JENKINS-32733) Publish over SSH plugin doesn't preserve permissions
Title: Message Title David Gloe created an issue Jenkins / JENKINS-32733 Publish over SSH plugin doesn't preserve permissions Issue Type: Bug Assignee: bap Components: publish-over-ssh-plugin Created: 02/Feb/16 7:24 PM Priority: Major Reporter: David Gloe The publish over SSH plugin isn't preserving executable permission for some scripts I would like to copy and run on a remote server. This is on Jenkins version 1.623. The remote server is on OpenSUSE 13.2, the Jenkins server is CentOS 7.1. Add Comment
[JIRA] [p4-plugin] (JENKINS-24591) Unable to run perforce commands within build steps
Title: Message Title Jim Poje reopened an issue Re-open to remove P4_TICKET environment variable Jenkins / JENKINS-24591 Unable to run perforce commands within build steps Change By: Jim Poje Resolution: Fixed Status: Closed Reopened 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] [p4-plugin] (JENKINS-24591) Unable to run perforce commands within build steps
Title: Message Title Jim Poje commented on JENKINS-24591 Re: Unable to run perforce commands within build steps Exposing the P4_TICKET value is a security risk, since the ticket value is essentially a credential value with access to a perforce server. In conjunction with the exported P4_USER and P4_PORT values, anyone with the ticket value has all the access to the perforce server that is granted to the P4_USER. Passing such a ticket value, in clear text, as an environment variable poses too great a risk. Let me request that the P4_TICKET environment variable be entirely removed, as passing credential values in environment variables is simply a very bad practice. If there is severe pushback to this request, a solution that allows the P4_TICKET environment to be conditionally set – with a default setting that disables it – could be considered as a less desirable alternative. 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] [jacoco-plugin] (JENKINS-28652) JaCoCo 0.7.5 incorrectly shows 0% coverage in Jenkins summary
Title: Message Title Maninder Singh edited a comment on JENKINS-28652 Re: JaCoCo 0.7.5 incorrectly shows 0% coverage in Jenkins summary I have upgraded Jenkins to use latest version 2.0.1 and started getting 0% coverage even thought I can see coverage.ec file have classes that have been covered. Also even though I am using "0.7.5.201505241946" in my android build.gradle Using Jenkins 1.628 . Surprised that I dit not have a problem with build.gradle using "0.7.5.201505241946" with Jenkins Plugin 1.0.19 Can someone please help me. I have to downgrade the my machine to plugin 1.0.19 for now. Which is working totally fine. 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] [token-macro-plugin] (JENKINS-32331) Performance problems on scan on huge Jenkins instances
Title: Message Title Damien Coraboeuf commented on JENKINS-32331 Re: Performance problems on scan on huge Jenkins instances I've created the https://github.com/jenkinsci/token-macro-plugin/pull/21 pull request in an attempt to solve this bottleneck 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] [jacoco-plugin] (JENKINS-28652) JaCoCo 0.7.5 incorrectly shows 0% coverage in Jenkins summary
Title: Message Title Maninder Singh edited a comment on JENKINS-28652 Re: JaCoCo 0.7.5 incorrectly shows 0% coverage in Jenkins summary I have upgraded Jenkins to use latest version 2.0.1 and started getting 0% coverage even thought I can see coverage.ec file have classes that have been covered. Also even though I am using "0.7.5.201505241946" in my android build.gradle Using Jenkins 1.628 Can someone please help me. I have to downgrade the plugin for now. 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] [token-macro-plugin] (JENKINS-32331) Performance problems on scan on huge Jenkins instances
Title: Message Title Damien Coraboeuf updated an issue Jenkins / JENKINS-32331 Performance problems on scan on huge Jenkins instances Change By: Damien Coraboeuf Component/s: token-macro-plugin Component/s: build-failure-analyzer-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] [jacoco-plugin] (JENKINS-28652) JaCoCo 0.7.5 incorrectly shows 0% coverage in Jenkins summary
Title: Message Title Maninder Singh reopened an issue I have upgraded Jenkins to use latest version 2.0.1 and started getting 0% coverage even thought I can see coverage.ec file have classes that have been covered. Also even though I am using "0.7.5.201505241946" in my android build.gradle Can someone please help me. I have to downgrade the plugin for now. Jenkins / JENKINS-28652 JaCoCo 0.7.5 incorrectly shows 0% coverage in Jenkins summary Change By: Maninder Singh Resolution: Fixed Status: Closed Reopened 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] [token-macro-plugin] (JENKINS-32331) Performance problems on scan on huge Jenkins instances
Title: Message Title Damien Coraboeuf commented on JENKINS-32331 Re: Performance problems on scan on huge Jenkins instances Moving this issue to the token-macro-plugin component. 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-binding-plugin] (JENKINS-32402) Credentials binding fails to find creds when using a Parameterized Expression, but only for timed jobs
Title: Message Title Nikolay Borisenko commented on JENKINS-32402 Re: Credentials binding fails to find creds when using a Parameterized _expression_, but only for timed jobs I am using "Role Strategy" plugin. The issue is not reproducible only if "Anonymous" has access to configure jobs. 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] [subversion-plugin] (JENKINS-32732) Using unix server every time build fail through SVN
Title: Message Title R. Tyler Croy assigned an issue to Unassigned Jenkins / JENKINS-32732 Using unix server every time build fail through SVN Change By: R. Tyler Croy Assignee: R. Tyler Croy Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-32218) buildsByBranchName is not set anymore
Title: Message Title Alex Nederlof commented on JENKINS-32218 Re: buildsByBranchName is not set anymore Thanks Mark! 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] [subversion-plugin] (JENKINS-32732) Using unix server every time build fail through SVN
Title: Message Title R. Tyler Croy moved an issue Jenkins / JENKINS-32732 Using unix server every time build fail through SVN Change By: R. Tyler Croy Project: Infrastructure Jenkins Key: INFRA JENKINS - 554 32732 Workflow: classic default workflow JNJira Component/s: subversion-plugin Component/s: svn 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 fro
[JIRA] [ownership-plugin] (JENKINS-28881) Add support for CloudBees folder plugin
Title: Message Title SCM/JIRA link daemon commented on JENKINS-28881 Re: Add support for CloudBees folder plugin Code changed in jenkins User: Oleg Nenashev Path: src/test/java/org/jenkinsci/plugins/ownership/model/folders/FolderOwnershipTest.java http://jenkins-ci.org/commit/ownership-plugin/b42f2937c1f91bfd521e00650cbee38cd565c6ba Log: JENKINS-28881 - Direct unit test for the issue discovered with folders (JENKINS-32359) 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] [ownership-plugin] (JENKINS-28881) Add support for CloudBees folder plugin
Title: Message Title SCM/JIRA link daemon commented on JENKINS-28881 Re: Add support for CloudBees folder plugin Code changed in jenkins User: Oleg Nenashev Path: src/test/java/org/jenkinsci/plugins/ownership/model/folders/FolderOwnershipTest.java http://jenkins-ci.org/commit/ownership-plugin/a188d3e4e76465b01eeac99deae2188ca470853b Log: JENKINS-28881 - Disable the JENKINS-32359 unit test till the CloudBees Folders Plugin gets released 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] [ownership-plugin] (JENKINS-28881) Add support for CloudBees folder plugin
Title: Message Title SCM/JIRA link daemon commented on JENKINS-28881 Re: Add support for CloudBees folder plugin Code changed in jenkins User: Oleg Nenashev Path: src/test/java/org/jenkinsci/plugins/ownership/security/jobrestrictions/OwnersListJobRestrictionTest.java http://jenkins-ci.org/commit/ownership-plugin/8d1fd0e36e7d36397708c2a657f6803ec3259bff Log: JENKINS-28881 - Tests of the JobRestrictions integration 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] [ownership-plugin] (JENKINS-28881) Add support for CloudBees folder plugin
Title: Message Title SCM/JIRA link daemon commented on JENKINS-28881 Re: Add support for CloudBees folder plugin Code changed in jenkins User: Oleg Nenashev Path: pom.xml src/main/java/com/synopsys/arc/jenkins/plugins/ownership/OwnershipDescription.java src/main/java/com/synopsys/arc/jenkins/plugins/ownership/OwnershipPluginConfiguration.java src/main/java/com/synopsys/arc/jenkins/plugins/ownership/extensions/item_ownership_policy/AssignCreatorPolicy.java src/main/java/com/synopsys/arc/jenkins/plugins/ownership/jobs/JobOwnerHelper.java src/main/java/com/synopsys/arc/jenkins/plugins/ownership/nodes/ComputerOwnerHelper.java src/main/java/com/synopsys/arc/jenkins/plugins/ownership/nodes/NodeOwnerHelper.java src/main/java/com/synopsys/arc/jenkins/plugins/ownership/nodes/NodeOwnerPropertyHelper.java src/main/java/com/synopsys/arc/jenkins/plugins/ownership/security/rolestrategy/AbstractOwnershipRoleMacro.java src/main/java/com/synopsys/arc/jenkins/plugins/ownership/util/AbstractOwnershipHelper.java src/main/java/org/jenkinsci/plugins/ownership/config/InheritanceOptions.java src/main/java/org/jenkinsci/plugins/ownership/model/OwnershipDescriptionSource.java src/main/java/org/jenkinsci/plugins/ownership/model/OwnershipHelperLocator.java src/main/java/org/jenkinsci/plugins/ownership/model/OwnershipInfo.java src/main/java/org/jenkinsci/plugins/ownership/model/folders/FolderItemListener.java src/main/java/org/jenkinsci/plugins/ownership/model/folders/FolderOwnershipAction.java src/main/java/org/jenkinsci/plugins/ownership/model/folders/FolderOwnershipActionFactory.java src/main/java/org/jenkinsci/plugins/ownership/model/folders/FolderOwnershipDescriptionSource.java src/main/java/org/jenkinsci/plugins/ownership/model/folders/FolderOwnershipHelper.java src/main/java/org/jenkinsci/plugins/ownership/model/folders/FolderOwnershipProperty.java src/main/java/org/jenkinsci/plugins/ownership/model/jobs/JobOwnershipDescriptionSource.java src/main/java/org/jenkinsci/plugins/ownership/model/nodes/NodeOwnershipDescriptionSource.java src/main/java/org/jenkinsci/plugins/ownership/model/runs/RunOwnershipHelper.java src/main/resources/com/synopsys/arc/jenkins/plugins/ownership/ItemOwnershipAction/ownershipSource.jelly src/main/resources/com/synopsys/arc/jenkins/plugins/ownership/ItemOwnershipAction/ownershipSource.properties src/main/resources/com/synopsys/arc/jenkins/plugins/ownership/ItemOwnershipAction/propertyConfig.jelly src/main/resources/com/synopsys/arc/jenkins/plugins/ownership/OwnershipPlugin/propertyConfig.jelly src/main/resources/com/synopsys/arc/jenkins/plugins/ownership/OwnershipPluginConfiguration/config.jelly src/main/resources/com/synopsys/arc/jenkins/plugins/ownership/jobs/JobOwnerJobAction/manage-owners.jelly src/main/resources/com/synopsys/arc/jenkins/plugins/ownership/jobs/JobOwnerJobAction/propertyConfig.jelly src/main/resources/com/synopsys/arc/jenkins/plugins/ownership/nodes/NodeOwnershipAction/manage-owners.jelly src/main/resources/com/synopsys/arc/jenkins/plugins/ownership/nodes/NodeOwnershipAction/propertyConfig.jelly src/main/resources/org/jenkinsci/plugins/ownership/config/InheritanceOptions/config.jelly src/main/resources/org/jenkinsci/plugins/ownership/config/InheritanceOptions/help-blockInheritanceFromItemGroups.html src/main/resources/org/jenkinsci/plugins/ownership/model/OwnershipDescriptionSource/DisabledSource/summary.jelly src/main/resources/org/jenkinsci/plugins/ownership/model/OwnershipDescriptionSource/DisabledSource/summary.properties src/main/resources/org/jenkinsci/plugins/ownership/model/folders/FolderOwnershipAction/index.jelly src/main/resources/org/jenkinsci/plugins/ownership/model/folders/FolderOwnershipAction/manage-owners.jelly src/main/resources/org/jenkinsci/plugins/ownership/model/folders/FolderOwnershipAction/summary.jelly src/main/resources/org/jenkinsci/plugins/ownership/model/folders/FolderOw
[JIRA] [cloudbees-folder-plugin] (JENKINS-32359) Folders do not always persist assigned folder properties
Title: Message Title SCM/JIRA link daemon commented on JENKINS-32359 Re: Folders do not always persist assigned folder properties Code changed in jenkins User: Oleg Nenashev Path: src/test/java/org/jenkinsci/plugins/ownership/model/folders/FolderOwnershipTest.java http://jenkins-ci.org/commit/ownership-plugin/b42f2937c1f91bfd521e00650cbee38cd565c6ba Log: JENKINS-28881 - Direct unit test for the issue discovered with folders (JENKINS-32359) 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] [cloudbees-folder-plugin] (JENKINS-32359) Folders do not always persist assigned folder properties
Title: Message Title SCM/JIRA link daemon commented on JENKINS-32359 Re: Folders do not always persist assigned folder properties Code changed in jenkins User: Oleg Nenashev Path: src/test/java/org/jenkinsci/plugins/ownership/model/folders/FolderOwnershipTest.java http://jenkins-ci.org/commit/ownership-plugin/a188d3e4e76465b01eeac99deae2188ca470853b Log: JENKINS-28881 - Disable the JENKINS-32359 unit test till the CloudBees Folders Plugin gets released 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] [ownership-plugin] (JENKINS-28881) Add support for CloudBees folder plugin
Title: Message Title SCM/JIRA link daemon commented on JENKINS-28881 Re: Add support for CloudBees folder plugin Code changed in jenkins User: Oleg Nenashev Path: src/main/java/org/jenkinsci/plugins/ownership/folders/FolderItemListener.java src/main/java/org/jenkinsci/plugins/ownership/folders/FolderOwnershipAction.java src/main/java/org/jenkinsci/plugins/ownership/folders/FolderOwnershipActionFactory.java src/main/java/org/jenkinsci/plugins/ownership/folders/FolderOwnershipDescriptionSource.java src/main/java/org/jenkinsci/plugins/ownership/folders/FolderOwnershipHelper.java src/main/java/org/jenkinsci/plugins/ownership/folders/FolderOwnershipProperty.java src/main/java/org/jenkinsci/plugins/ownership/model/folders/FolderItemListener.java src/main/java/org/jenkinsci/plugins/ownership/model/folders/FolderOwnershipAction.java src/main/java/org/jenkinsci/plugins/ownership/model/folders/FolderOwnershipActionFactory.java src/main/java/org/jenkinsci/plugins/ownership/model/folders/FolderOwnershipDescriptionSource.java src/main/java/org/jenkinsci/plugins/ownership/model/folders/FolderOwnershipHelper.java src/main/java/org/jenkinsci/plugins/ownership/model/folders/FolderOwnershipProperty.java src/main/resources/org/jenkinsci/plugins/ownership/folders/FolderOwnershipAction/index.jelly src/main/resources/org/jenkinsci/plugins/ownership/folders/FolderOwnershipAction/manage-owners.jelly src/main/resources/org/jenkinsci/plugins/ownership/folders/FolderOwnershipAction/summary.jelly src/main/resources/org/jenkinsci/plugins/ownership/folders/FolderOwnershipDescriptionSource/summary.jelly src/main/resources/org/jenkinsci/plugins/ownership/folders/FolderOwnershipProperty/config.jelly src/main/resources/org/jenkinsci/plugins/ownership/folders/FolderOwnershipProperty/summary.jelly src/main/resources/org/jenkinsci/plugins/ownership/model/folders/FolderOwnershipAction/index.jelly src/main/resources/org/jenkinsci/plugins/ownership/model/folders/FolderOwnershipAction/manage-owners.jelly src/main/resources/org/jenkinsci/plugins/ownership/model/folders/FolderOwnershipAction/summary.jelly src/main/resources/org/jenkinsci/plugins/ownership/model/folders/FolderOwnershipDescriptionSource/summary.jelly src/main/resources/org/jenkinsci/plugins/ownership/model/folders/FolderOwnershipProperty/config.jelly src/main/resources/org/jenkinsci/plugins/ownership/model/folders/FolderOwnershipProperty/summary.jelly src/test/java/com/synopsys/arc/jenkins/plugins/ownership/wrappers/OwnershipBuildWrapperTest.java src/test/java/org/jenkinsci/plugins/ownership/folders/FolderOwnershipHelperTest.java src/test/java/org/jenkinsci/plugins/ownership/folders/FolderOwnershipTest.java src/test/java/org/jenkinsci/plugins/ownership/model/folders/FolderOwnershipHelperTest.java src/test/java/org/jenkinsci/plugins/ownership/model/folders/FolderOwnershipTest.java src/test/java/org/jenkinsci/plugins/ownership/model/runs/RunOwnershipActionTest.java src/test/java/org/jenkinsci/plugins/ownership/security/rolestrategy/OwnershipBasedSecurityTest.java http://jenkins-ci.org/commit/ownership-plugin/e5039a9220b6718501a5aa40c5e1d9a394c3426e Log: JENKINS-28881 - Move Folder files. Folders belong to the model Add Comment
[JIRA] [ownership-plugin] (JENKINS-28881) Add support for CloudBees folder plugin
Title: Message Title SCM/JIRA link daemon commented on JENKINS-28881 Re: Add support for CloudBees folder plugin Code changed in jenkins User: Oleg Nenashev Path: src/main/java/com/synopsys/arc/jenkins/plugins/ownership/OwnershipPluginConfiguration.java src/main/java/com/synopsys/arc/jenkins/plugins/ownership/jobs/JobOwnerHelper.java src/main/java/org/jenkinsci/plugins/ownership/config/InheritanceOptions.java src/main/java/org/jenkinsci/plugins/ownership/model/folders/FolderOwnershipHelper.java src/main/resources/com/synopsys/arc/jenkins/plugins/ownership/OwnershipPluginConfiguration/config.jelly src/main/resources/org/jenkinsci/plugins/ownership/config/InheritanceOptions/config.jelly src/main/resources/org/jenkinsci/plugins/ownership/config/InheritanceOptions/help-blockInheritanceFromItemGroups.html src/test/java/org/jenkinsci/plugins/ownership/model/folders/FolderOwnershipTest.java src/test/java/org/jenkinsci/plugins/ownership/test/util/OwnershipPluginConfigurer.java http://jenkins-ci.org/commit/ownership-plugin/3589ce8e035701e42b8aeb926d84df59f3b68967 Log: JENKINS-28881 - Allow blocking ItemGroup inheritance 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] [ownership-plugin] (JENKINS-28881) Add support for CloudBees folder plugin
Title: Message Title SCM/JIRA link daemon commented on JENKINS-28881 Re: Add support for CloudBees folder plugin Code changed in jenkins User: Oleg Nenashev Path: src/test/java/org/jenkinsci/plugins/ownership/security/rolestrategy/OwnershipBasedSecurityTest.java src/test/java/org/jenkinsci/plugins/ownership/security/rolestrategy/OwnershipBasedSecurityTestHelper.java http://jenkins-ci.org/commit/ownership-plugin/535baec000a54decbd214ba6a3206f28f4736e34 Log: JENKINS-28881 - Add unit tests for Ownership-based security 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] [ownership-plugin] (JENKINS-28881) Add support for CloudBees folder plugin
Title: Message Title SCM/JIRA link daemon commented on JENKINS-28881 Re: Add support for CloudBees folder plugin Code changed in jenkins User: Oleg Nenashev Path: src/main/java/com/synopsys/arc/jenkins/plugins/ownership/extensions/item_ownership_policy/AssignCreatorPolicy.java src/main/java/org/jenkinsci/plugins/ownership/folders/FolderItemListener.java src/main/java/org/jenkinsci/plugins/ownership/folders/FolderOwnershipProperty.java src/test/java/org/jenkinsci/plugins/ownership/folders/FolderOwnershipTest.java http://jenkins-ci.org/commit/ownership-plugin/206a36c085f35c2a06966af6aca6ea8f80772bc3 Log: JENKINS-28881 - Support AssignCreatorPolicy for Folders 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] [ownership-plugin] (JENKINS-28881) Add support for CloudBees folder plugin
Title: Message Title SCM/JIRA link daemon commented on JENKINS-28881 Re: Add support for CloudBees folder plugin Code changed in jenkins User: Oleg Nenashev Path: src/main/java/com/synopsys/arc/jenkins/plugins/ownership/jobs/JobOwnerHelper.java src/main/java/com/synopsys/arc/jenkins/plugins/ownership/nodes/ComputerOwnerHelper.java src/main/java/com/synopsys/arc/jenkins/plugins/ownership/nodes/NodeOwnerHelper.java src/main/java/com/synopsys/arc/jenkins/plugins/ownership/nodes/NodeOwnerPropertyHelper.java src/main/java/com/synopsys/arc/jenkins/plugins/ownership/util/AbstractOwnershipHelper.java src/main/java/org/jenkinsci/plugins/ownership/folders/FolderOwnershipDescriptionSource.java src/main/java/org/jenkinsci/plugins/ownership/folders/FolderOwnershipHelper.java src/main/java/org/jenkinsci/plugins/ownership/model/OwnershipDescriptionSource.java src/main/java/org/jenkinsci/plugins/ownership/model/OwnershipHelperLocator.java src/main/java/org/jenkinsci/plugins/ownership/model/OwnershipInfo.java src/main/java/org/jenkinsci/plugins/ownership/model/jobs/JobOwnershipDescriptionSource.java src/main/java/org/jenkinsci/plugins/ownership/model/nodes/NodeOwnershipDescriptionSource.java src/main/java/org/jenkinsci/plugins/ownership/model/runs/RunOwnershipHelper.java src/main/resources/com/synopsys/arc/jenkins/plugins/ownership/ItemOwnershipAction/ownershipSource.jelly src/main/resources/com/synopsys/arc/jenkins/plugins/ownership/ItemOwnershipAction/ownershipSource.properties src/main/resources/com/synopsys/arc/jenkins/plugins/ownership/jobs/JobOwnerJobAction/manage-owners.jelly src/main/resources/com/synopsys/arc/jenkins/plugins/ownership/nodes/NodeOwnershipAction/manage-owners.jelly src/main/resources/org/jenkinsci/plugins/ownership/folders/FolderOwnershipAction/manage-owners.jelly src/main/resources/org/jenkinsci/plugins/ownership/folders/FolderOwnershipDescriptionSource/summary.jelly src/main/resources/org/jenkinsci/plugins/ownership/model/OwnershipDescriptionSource/DisabledSource/summary.jelly src/main/resources/org/jenkinsci/plugins/ownership/model/OwnershipDescriptionSource/DisabledSource/summary.properties src/main/resources/org/jenkinsci/plugins/ownership/model/jobs/JobOwnershipDescriptionSource/summary.jelly src/main/resources/org/jenkinsci/plugins/ownership/model/nodes/NodeOwnershipDescriptionSource/summary.jelly src/test/java/org/jenkinsci/plugins/ownership/folders/FolderOwnershipTest.java http://jenkins-ci.org/commit/ownership-plugin/cd1568f63f2c1480a0b57c69768ae19eb824c521 Log: JENKINS-28881 - Extend the internal implementation to allow displaying the ownership info source Add Comment
[JIRA] [ownership-plugin] (JENKINS-28881) Add support for CloudBees folder plugin
Title: Message Title SCM/JIRA link daemon commented on JENKINS-28881 Re: Add support for CloudBees folder plugin Code changed in jenkins User: Oleg Nenashev Path: src/main/java/com/synopsys/arc/jenkins/plugins/ownership/jobs/JobOwnerHelper.java src/main/java/com/synopsys/arc/jenkins/plugins/ownership/jobs/OwnershipActionFactory.java src/main/resources/com/synopsys/arc/jenkins/plugins/ownership/ItemOwnershipAction/ownershipSource.properties http://jenkins-ci.org/commit/ownership-plugin/6302e837890622d69b99a7534cf1b5523afd96c4 Log: JENKINS-28881 - Amend ownershipSource warning message according to comments from @olivergondza Also fixes minor formatting issues 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] [ownership-plugin] (JENKINS-28881) Add support for CloudBees folder plugin
Title: Message Title SCM/JIRA link daemon commented on JENKINS-28881 Re: Add support for CloudBees folder plugin Code changed in jenkins User: Oleg Nenashev Path: src/test/java/com/synopsys/arc/jenkins/plugins/ownership/wrappers/OwnershipBuildWrapperTest.java src/test/java/org/jenkinsci/plugins/ownership/model/runs/RunOwnershipActionTest.java http://jenkins-ci.org/commit/ownership-plugin/1e3e70fb08a59ca70359fd22379c98f13c7b5745 Log: JENKINS-28881 - Add Folder ownership tests for Run components 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] [ownership-plugin] (JENKINS-28881) Add support for CloudBees folder plugin
Title: Message Title SCM/JIRA link daemon commented on JENKINS-28881 Re: Add support for CloudBees folder plugin Code changed in jenkins User: Oleg Nenashev Path: src/main/java/org/jenkinsci/plugins/ownership/folders/FolderOwnershipProperty.java http://jenkins-ci.org/commit/ownership-plugin/0be133350496b89778cb0434e05ababccfb4cea3 Log: JENKINS-28881 - Prevent FolderOwnershipProperty changes on the configuration submission 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] [ownership-plugin] (JENKINS-28881) Add support for CloudBees folder plugin
Title: Message Title SCM/JIRA link daemon commented on JENKINS-28881 Re: Add support for CloudBees folder plugin Code changed in jenkins User: Oleg Nenashev Path: src/main/java/com/synopsys/arc/jenkins/plugins/ownership/security/rolestrategy/AbstractOwnershipRoleMacro.java src/main/java/org/jenkinsci/plugins/ownership/model/runs/RunOwnershipHelper.java http://jenkins-ci.org/commit/ownership-plugin/74b81be6cf8d5197abf8dc03e8bdf9984c7589a2 Log: JENKINS-28881 - Fix several issues with explicit JobOwnerProperty usage impacting the inheritance 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] [ownership-plugin] (JENKINS-28881) Add support for CloudBees folder plugin
Title: Message Title SCM/JIRA link daemon commented on JENKINS-28881 Re: Add support for CloudBees folder plugin Code changed in jenkins User: Oleg Nenashev Path: pom.xml src/main/java/com/synopsys/arc/jenkins/plugins/ownership/jobs/OwnershipActionFactory.java src/main/java/org/jenkinsci/plugins/ownership/folders/FolderOwnershipAction.java src/main/java/org/jenkinsci/plugins/ownership/folders/FolderOwnershipActionFactory.java src/main/java/org/jenkinsci/plugins/ownership/folders/FolderOwnershipHelper.java src/main/java/org/jenkinsci/plugins/ownership/folders/FolderOwnershipProperty.java src/main/resources/com/synopsys/arc/jenkins/plugins/ownership/ItemOwnershipAction/propertyConfig.jelly src/main/resources/org/jenkinsci/plugins/ownership/folders/FolderOwnershipAction/index.jelly src/main/resources/org/jenkinsci/plugins/ownership/folders/FolderOwnershipAction/manage-owners.jelly src/main/resources/org/jenkinsci/plugins/ownership/folders/FolderOwnershipProperty/config.jelly src/main/resources/org/jenkinsci/plugins/ownership/folders/FolderOwnershipProperty/summary.jelly src/test/java/org/jenkinsci/plugins/ownership/folders/FolderOwnershipTest.java http://jenkins-ci.org/commit/ownership-plugin/1458f9358784c43f1369fa53e4c66722873f3b16 Log: JENKINS-28881 - Implementation of Ownership property injection 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.
