[JIRA] [parameterized-trigger-plugin] (JENKINS-25936) Maven environment variables are not expanded when triggering another project.
Johan Raedemaeker
commented on JENKINS-25936
Maven environment variables are not expanded when triggering another project.
Hi,
Thanks for looking at this issue.
Your test scenario also works for me. I see now that my steps to reproduce are not completely accurate.
The "upstream" maven project is also parameterized with 1 parameter (otherparam)
this has ${POM_ARTIFACTID}-${BUILD_ID} configured as the default value
then this projects triggers downstream with
myparam=${otherparam}
The downstream build outputs ${POM_ARTIFACT_ID}-2014-12-07_09-57-07 in the console
So the expansion is working for "normal" jenkins variables like ${BUILD_ID} but not for the maven variables
I am using jenkins 1.564 , maven-plugin 2.7, parameterized-trigger-plugin 2.24
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-flow-plugin] (JENKINS-25952) Build flow job does not release thread pools
Mable Schmidt
created JENKINS-25952
Build flow job does not release thread pools
Issue Type:
Bug
Assignee:
Nicolas De Loof
Components:
build-flow-plugin
Created:
07/Dec/14 9:28 AM
Description:
Given the following build flow job:
parallel(
build_list.collect { a_build_name - return {
guard{
run_build = build(a_build_name)
} rescue {
if (run_build.result.name == "ABORTED"){
build("Job B")
}//if
}//rescue
}// return
}// collect
)//parallel
When the build flow is "aborted" or its parent is aborted,
And I view .../jenkins/monitoring url
Then I see a list of threads "cryptically-named" pool-X-thread-Y (ex. pool-16-thread-100) in a "WAITING" state. It seems the thread pool is allocated for those jobs and never gets executed or released
These threads will never get out of the "WAITING" state, except I run the following script (alternatively kill the threads individually on the threads table):
Thread.getAllStackTraces().keySet().each(){ item -
if(item.getName().contains(thread_name_string)){
println "Interrupting thread " + item.getId() + " " + item.getName();
item.interrupt()
}
}
The above script will cause the rescue block to execute for each of the jobs in the build flow, i.e. the job queue on jenkins will show a list of "Job B" queued and their info thinks it was triggered by an already aborted job
If a user attempts the above actions multiple times without killing the threads (i.e. run jobs, and abort), the thread count will continue to increase. Eventually jenkins will be inaccessible from the web as it has exceeded the number of threads
It seems that when a build flow job is aborted, "scheduled/queued jobs" and "running" jobs are cancelled as expected, but jobs that will kick in via the rescue block seem to be orphaned, and taking up resources with regards to maximum thread count jenkins will generate
Project:
Jenkins
Priority:
Major
Reporter:
Mable Schmidt
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [parameterized-trigger-plugin] (JENKINS-25936) Maven environment variables are not expanded when triggering another project.
ikedam commented on JENKINS-25936 Maven environment variables are not expanded when triggering another project. I don't think variables in default valies work. Rather it's surprising to me that BUILD_ID is expanded. That doesn't sound a problem with parameterrized-trigger-plugin. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [parameterized-trigger-plugin] (JENKINS-25936) Maven environment variables are not expanded when triggering another project.
Johan Raedemaeker
commented on JENKINS-25936
Maven environment variables are not expanded when triggering another project.
The expansion of variables is working fine for the upstream project when executing a shell in a pre- or post-build step then echo %otherparam% is showing the resolved variables.
It is only when used in a post-build action that the variables are not resolved.
This seems to happen for all post-build actions not only the "Trigger parameterized build on other projects"
for example when I add a post-build-action "Archive the artifacts" with "files to archive" = ${otherparam}
then the console of upstream shows:
No artifacts found that match the file pattern "${POM_ARTIFACTID}-2014-12-07_11-22-57"
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-25953) Layout - Tabs in job view are layouted in wrong way
Piotr Wielgołaski created JENKINS-25953 Layout - Tabs in job view are layouted in wrong way Issue Type: Bug Assignee: Unassigned Attachments: Screen Shot 2014-12-07 at 13.36.22.png, Screen Shot 2014-12-07 at 13.36.38.png Components: core Created: 07/Dec/14 12:39 PM Description: Take a look at screen shots, when I select tab "test4" there is extra padding in whole next line, "test7" begin just after "test4" in second line. When "test6" is selected it looks fine. Environment: Jenkins ver. 1.580.1. Mac. Chrome browser Project: Jenkins Labels: layout Priority: Major Reporter: Piotr Wielgołaski This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-25953) Layout - Tabs in job view are layouted in wrong way
Piotr Wielgołaski commented on JENKINS-25953 Layout - Tabs in job view are layouted in wrong way it seems that one of solution to fix it is to add: "padding-bottom: 6px;" into https://github.com/jenkinsci/jenkins/blob/master/war/src/main/webapp/css/style.css#L412 In this way all tabs have the same height. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-25953) Layout - Tabs in job view are layouted in wrong way
Piotr Wielgołaski updated JENKINS-25953 Layout - Tabs in job view are layouted in wrong way Screenshot with fix attached Change By: Piotr Wielgołaski (07/Dec/14 12:57 PM) Attachment: ScreenShot2014-12-07at13.55.50.png This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [parameterized-trigger-plugin] (JENKINS-25936) Maven environment variables are not expanded when triggering another project.
ikedam commented on JENKINS-25936 Maven environment variables are not expanded when triggering another project. Write steps to reproduce the problem. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cloudfoundry-plugin] (JENKINS-25884) configure name of manifest.yml
Daniel Beck updated JENKINS-25884 configure name of manifest.yml Change By: Daniel Beck (07/Dec/14 2:26 PM) Assignee: DanielBeck WilliamGautier This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cloudfoundry-plugin] (JENKINS-25882) Integrate with credentials plugin
Daniel Beck updated JENKINS-25882 Integrate with credentials plugin Change By: Daniel Beck (07/Dec/14 2:26 PM) Assignee: DanielBeck WilliamGautier This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [parameterized-trigger-plugin] (JENKINS-25936) Maven environment variables are not expanded when triggering another project.
Johan Raedemaeker
commented on JENKINS-25936
Maven environment variables are not expanded when triggering another project.
1) Create a freestyle project "downstream"
2) Define a string parameter "dparam" for "downstream", this has no default value
3) Add a "Execute Windows batch command" or "Execute shell" to echo %dparam%
4) Create a Maven Project named "upstream" with the same maven artifactid
5) Define a string parameter "uparam" for "upstream" with a default value ${POM_ARTIFACTID}-${BUILD_ID}
7) In the pre-build-steps Add a "Execute Windows batch command" or "Execute shell" to echo %uparam%
8) In the post-build-steps Add a "Execute Windows batch command" or "Execute shell" to echo %uparam%
9) Configure Add Trigger parameterized build on other projects" in the Post-build Actions:
Projects to build: downstream
Add "Predefined parameters" and specify "dparam=${uparam}
10) Run a build of "upstream" (build number X)
11) Verify that the console output for "upstream" contains 2 occurences upstream-X (both as pre post build step)
12) "downstream" is now triggered by "upstream".
13) Verify the console output of "downstream" which shows "${POM_ARTIFACTID}-X
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext-plugin] (JENKINS-20355) email-ext emails no longer include JUnit results
Pedro Algarvio commented on JENKINS-20355 email-ext emails no longer include JUnit results I'm not getting the traceback, so I should probably open a new issue.. I have Maven Integration plugin 2.8 installed and enabled.. Also, this is not a maven project, it's a freestyle project(if that makes a difference) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext-plugin] (JENKINS-20355) email-ext emails no longer include JUnit results
Pedro Algarvio commented on JENKINS-20355 email-ext emails no longer include JUnit results I'm also not getting the warnings reports in the email either... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext-plugin] (JENKINS-20355) email-ext emails no longer include JUnit results
Pedro Algarvio commented on JENKINS-20355 email-ext emails no longer include JUnit results My email template https://gist.github.com/s0undt3ch/8d220faaa3b0614ee3b0 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext-plugin] (JENKINS-20355) email-ext emails no longer include JUnit results
Pedro Algarvio commented on JENKINS-20355 email-ext emails no longer include JUnit results Actually, after your comment I did enable the maven integration plugin, previously disabled. Tried a test run with no success. Today I tried again, and it's working again. Sorry for the confusion. I'm still unable to get the violations report though... (if only I know jenkins java classes better and jelly for that matter)... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext-plugin] (JENKINS-20355) email-ext emails no longer include JUnit results
Alex Earl commented on JENKINS-20355 email-ext emails no longer include JUnit results Yes, please open a new issue and provide more information. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-14190) Wrong autocompletion of node names with spaces
Catalin Poitasu commented on JENKINS-14190 Wrong autocompletion of node names with spaces Seems to be fixed on Jenkins ver. 1.594. I created a slave with the name "a b c" and a project for which I added the restriction to that slave. While typing the name of the slave I got the suggestion "a b c" without the quotes. Pressing ENTER, the name of the slave without the quotes was added to the text field. After saving the configuration of the job, the label appeared with quotes, which is correct. Furthermore, every functionality related to this label could be verified: the project was sent to the proper slave the project was tied to the assigned slave, when opening the page of the slave So this is either fixed or it is something Jenkins handles automatically once the configuration page of the job is saved, since there was no need to add the quotes manually in the test. Using quotes make sense due to more complex constructions: e.g: user:... || role:... || "a b c" This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [repository-connector-plugin] (JENKINS-24781) Repository Connector Plugin failed to resolve dependency after upgrade (0.8.2 - 1.0.1)
Dejan Stojadinovic reopened JENKINS-24781 Repository Connector Plugin failed to resolve dependency after upgrade (0.8.2 - 1.0.1) Thanx Mathieu POUSSE! I'll change resolution to duplicate for this one. Change By: Dejan Stojadinovic (07/Dec/14 7:54 PM) Resolution: NotADefect Status: Resolved Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [repository-connector-plugin] (JENKINS-24781) Repository Connector Plugin failed to resolve dependency after upgrade (0.8.2 - 1.0.1)
Dejan Stojadinovic resolved JENKINS-24781 as Duplicate Repository Connector Plugin failed to resolve dependency after upgrade (0.8.2 - 1.0.1) Duplicate (see JENKINS-25620). Change By: Dejan Stojadinovic (07/Dec/14 7:56 PM) Status: Reopened Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-25922) Add support for Publish Over SSH
Wisen Tanasa commented on JENKINS-25922 Add support for Publish Over SSH config.xml generated with mandatory fields jenkins.plugins.publish__over__ssh.BapSshBuilderPlugin plugin="publish-over-ssh@1.12" delegate consolePrefixSSH: /consolePrefix delegate publishers jenkins.plugins.publish__over__ssh.BapSshPublisher configNamemy-server/configName verbosefalse/verbose transfers jenkins.plugins.publish__over__ssh.BapSshTransfer remoteDirectory/remoteDirectory sourceFiles/sourceFiles excludes/excludes removePrefix/removePrefix remoteDirectorySDFfalse/remoteDirectorySDF flattenfalse/flatten cleanRemotefalse/cleanRemote noDefaultExcludesfalse/noDefaultExcludes makeEmptyDirsfalse/makeEmptyDirs patternSeparator[, ]+/patternSeparator execCommand/execCommand execTimeout12/execTimeout usePtyfalse/usePty /jenkins.plugins.publish__over__ssh.BapSshTransfer /transfers useWorkspaceInPromotionfalse/useWorkspaceInPromotion usePromotionTimestampfalse/usePromotionTimestamp /jenkins.plugins.publish__over__ssh.BapSshPublisher /publishers continueOnErrorfalse/continueOnError failOnErrorfalse/failOnError alwaysPublishFromMasterfalse/alwaysPublishFromMaster hostConfigurationAccess class="jenkins.plugins.publish_over_ssh.BapSshPublisherPlugin" reference="../.."/ /delegate /delegate /jenkins.plugins.publish__over__ssh.BapSshBuilderPlugin This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-25922) Add support for Publish Over SSH
Wisen Tanasa commented on JENKINS-25922 Add support for Publish Over SSH config.xml generated with complex and advance configuration jenkins.plugins.publish__over__ssh.BapSshBuilderPlugin plugin="publish-over-ssh@1.12" delegate consolePrefixSSH: /consolePrefix delegate publishers jenkins.plugins.publish__over__ssh.BapSshPublisher configNamemy-server-01/configName verbosetrue/verbose transfers jenkins.plugins.publish__over__ssh.BapSshTransfer remoteDirectory/remoteDirectory sourceFilesfiles/sourceFiles excludesexclude files/excludes removePrefix/removePrefix remoteDirectorySDFtrue/remoteDirectorySDF flattentrue/flatten cleanRemotefalse/cleanRemote noDefaultExcludestrue/noDefaultExcludes makeEmptyDirstrue/makeEmptyDirs patternSeparator[| ]+/patternSeparator execCommandcommand/execCommand execTimeout1/execTimeout usePtytrue/usePty /jenkins.plugins.publish__over__ssh.BapSshTransfer jenkins.plugins.publish__over__ssh.BapSshTransfer remoteDirectory/remoteDirectory sourceFilesfiles2/sourceFiles excludes/excludes removePrefix/removePrefix remoteDirectorySDFfalse/remoteDirectorySDF flattenfalse/flatten cleanRemotefalse/cleanRemote noDefaultExcludesfalse/noDefaultExcludes makeEmptyDirsfalse/makeEmptyDirs patternSeparator[, ]+/patternSeparator execCommandcommand2/execCommand execTimeout12/execTimeout usePtyfalse/usePty /jenkins.plugins.publish__over__ssh.BapSshTransfer /transfers useWorkspaceInPromotionfalse/useWorkspaceInPromotion usePromotionTimestampfalse/usePromotionTimestamp retry class="jenkins.plugins.publish_over_ssh.BapSshRetry" retries10/retries retryDelay1/retryDelay /retry label class="jenkins.plugins.publish_over_ssh.BapSshPublisherLabel" labelserver-01/label /label credentials class="jenkins.plugins.publish_over_ssh.BapSshCredentials" secretPassphraseZ5obSeg7txeq0ekz7T8S9Sa9o1ZCGap8/fKBtYzkOkg=/secretPassphrase keykey01/key keyPathpath01/keyPath usernameuser01/username /credentials /jenkins.plugins.publish__over__ssh.BapSshPublisher jenkins.plugins.publish__over__ssh.BapSshPublisher configNamemy-server-02/configName verbosetrue/verbose transfers jenkins.plugins.publish__over__ssh.BapSshTransfer remoteDirectory/remoteDirectory sourceFilesfiles3/sourceFiles excludes/excludes removePrefix/removePrefix remoteDirectorySDFfalse/remoteDirectorySDF flattenfalse/flatten cleanRemotefalse/cleanRemote noDefaultExcludesfalse/noDefaultExcludes makeEmptyDirsfalse/makeEmptyDirs patternSeparator[, ]+/patternSeparator execCommandcommand3/execCommand execTimeout12/execTimeout usePtyfalse/usePty /jenkins.plugins.publish__over__ssh.BapSshTransfer /transfers useWorkspaceInPromotionfalse/useWorkspaceInPromotion usePromotionTimestampfalse/usePromotionTimestamp retry class="jenkins.plugins.publish_over_ssh.BapSshRetry" retries20/retries retryDelay2/retryDelay /retry label class="jenkins.plugins.publish_over_ssh.BapSshPublisherLabel" labelserver-02/label /label credentials class="jenkins.plugins.publish_over_ssh.BapSshCredentials" secretPassphrasezhVrTkQChda84cQjT46Ezg==/secretPassphrase key/key keyPath/keyPath
[JIRA] [job-dsl-plugin] (JENKINS-25922) Add support for Publish Over SSH
Wisen Tanasa edited a comment on JENKINS-25922 Add support for Publish Over SSH config.xml generated with complex and advance configuration jenkins.plugins.publish__over__ssh.BapSshBuilderPlugin plugin="publish-over-ssh@1.12" delegate consolePrefixSSH: /consolePrefix delegate publishers jenkins.plugins.publish__over__ssh.BapSshPublisher configNamemy-server-01/configName verbosetrue/verbose transfers jenkins.plugins.publish__over__ssh.BapSshTransfer remoteDirectorydirectory/remoteDirectory sourceFilesfiles/sourceFiles excludesexclude files/excludes removePrefixprefix/removePrefix remoteDirectorySDFtrue/remoteDirectorySDF flattentrue/flatten cleanRemotefalse/cleanRemote noDefaultExcludestrue/noDefaultExcludes makeEmptyDirstrue/makeEmptyDirs patternSeparator[| ]+/patternSeparator execCommandcommand/execCommand execTimeout1/execTimeout usePtytrue/usePty /jenkins.plugins.publish__over__ssh.BapSshTransfer jenkins.plugins.publish__over__ssh.BapSshTransfer remoteDirectory/remoteDirectory sourceFilesfiles2/sourceFiles excludes/excludes removePrefix/removePrefix remoteDirectorySDFfalse/remoteDirectorySDF flattenfalse/flatten cleanRemotefalse/cleanRemote noDefaultExcludesfalse/noDefaultExcludes makeEmptyDirsfalse/makeEmptyDirs patternSeparator[, ]+/patternSeparator execCommandcommand2/execCommand execTimeout12/execTimeout usePtyfalse/usePty /jenkins.plugins.publish__over__ssh.BapSshTransfer /transfers useWorkspaceInPromotionfalse/useWorkspaceInPromotion usePromotionTimestampfalse/usePromotionTimestamp retry class="jenkins.plugins.publish_over_ssh.BapSshRetry" retries10/retries retryDelay1/retryDelay /retry label class="jenkins.plugins.publish_over_ssh.BapSshPublisherLabel" labelserver-01/label /label credentials class="jenkins.plugins.publish_over_ssh.BapSshCredentials" secretPassphraseZ5obSeg7txeq0ekz7T8S9Sa9o1ZCGap8/fKBtYzkOkg=/secretPassphrase keykey01/key keyPathpath01/keyPath usernameuser01/username /credentials /jenkins.plugins.publish__over__ssh.BapSshPublisher jenkins.plugins.publish__over__ssh.BapSshPublisher configNamemy-server-02/configName verbosetrue/verbose transfers jenkins.plugins.publish__over__ssh.BapSshTransfer remoteDirectory/remoteDirectory sourceFilesfiles3/sourceFiles excludes/excludes removePrefix/removePrefix remoteDirectorySDFfalse/remoteDirectorySDF flattenfalse/flatten cleanRemotefalse/cleanRemote noDefaultExcludesfalse/noDefaultExcludes makeEmptyDirsfalse/makeEmptyDirs patternSeparator[, ]+/patternSeparator execCommandcommand3/execCommand execTimeout12/execTimeout usePtyfalse/usePty /jenkins.plugins.publish__over__ssh.BapSshTransfer /transfers useWorkspaceInPromotionfalse/useWorkspaceInPromotion usePromotionTimestampfalse/usePromotionTimestamp retry class="jenkins.plugins.publish_over_ssh.BapSshRetry" retries20/retries retryDelay2/retryDelay /retry label class="jenkins.plugins.publish_over_ssh.BapSshPublisherLabel" labelserver-02/label /label credentials class="jenkins.plugins.publish_over_ssh.BapSshCredentials" secretPassphrasezhVrTkQChda84cQjT46Ezg==/secretPassphrase key/key keyPath/keyPath
[JIRA] [openid-plugin] (JENKINS-23431) Google is phasing out OpenID endpoint. Need to move on to G+ sign-in
Joshua Spiewak commented on JENKINS-23431 Google is phasing out OpenID endpoint. Need to move on to G+ sign-in Has anyone gotten the new Google Login Plugin working with the Matrix Authorization and the default authenticated pseudo-group? My own account already had an entry, and another user who tried this weekend got an "Access Denied, user is missing the Overall/Read permission" even though that is checked for the authenticated psuedo-group. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [parameterized-trigger-plugin] (JENKINS-25936) Maven environment variables are not expanded when triggering another project.
ikedam
commented on JENKINS-25936
Maven environment variables are not expanded when triggering another project.
I succeeded to reproduce that.
Jenkins looks resolve variables each other in first.
Running following scripts from Manage Jenkins Script Console
Jenkins.instance.getItemByFullName("upstream").getLastBuild().getEnvironment();
outputs
POM_ARTIFACTID=parameterized-trigger
uparam=${POM_ARTIFACTID}-2014-12-08_08-14-23
, and it might be a problem in Jenkins core.
I should see why it works for Execute shell or Execute Windows batch command (How do they access environments?)
Anyway, please try to not to reference variables from other variables, as each-other-resolving looks unstable.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [parameterized-trigger-plugin] (JENKINS-25936) Maven environment variables are not expanded when triggering another project.
ikedam commented on JENKINS-25936 Maven environment variables are not expanded when triggering another project. EnvInject plugin may help you. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [email-ext-plugin] (JENKINS-25954) Allow email-ext to include the violations report in emails
Pedro Algarvio created JENKINS-25954 Allow email-ext to include the violations report in emails Issue Type: New Feature Assignee: Alex Earl Components: email-ext-plugin, violations-plugin Created: 08/Dec/14 2:09 AM Description: Allow email-ext to include the violations report in emails. If this is already possible, I have not yet seen a doc, howto, anything when goolging about this support. Project: Jenkins Priority: Minor Reporter: Pedro Algarvio This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext-plugin] (JENKINS-25954) Allow email-ext to include the violations report in emails
Alex Earl commented on JENKINS-25954 Allow email-ext to include the violations report in emails It will depend on how you are using the plugin. Are you using one of the built-in templates, or you own? If you are using one of the built-in templates, it is definitely possible it doesn't show violations, since the default templates are pretty generic. There is information on the wiki on how to write your own template (it basically points you to the source on github for one of the built-in templates). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext-plugin] (JENKINS-25954) Allow email-ext to include the violations report in emails
Pedro Algarvio commented on JENKINS-25954 Allow email-ext to include the violations report in emails I have derived from the provided templates in github, and the static code analysis part on one of them is not working for me, nothing is shown. My current state of the template is here. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext-plugin] (JENKINS-25954) Allow email-ext to include the violations report in emails
Alex Earl commented on JENKINS-25954 Allow email-ext to include the violations report in emails Have you checked that the correct plugins are installed and activated for the job? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext-plugin] (JENKINS-25954) Allow email-ext to include the violations report in emails
Pedro Algarvio commented on JENKINS-25954 Allow email-ext to include the violations report in emails All I can think of. Is there a documented list? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext-plugin] (JENKINS-25954) Allow email-ext to include the violations report in emails
Alex Earl
commented on JENKINS-25954
Allow email-ext to include the violations report in emails
At least analysis-core, if that is not installed, then an empty list will be returned by ${it.staticAnalysisActions}. Then, if there are no actions on the build that subclass AbstractResultAction or MavenResultAction an empty list will be returned. So, check those two things.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client-plugin] (JENKINS-22706) Warn that space in TEMP or TMP causes msysgit ssh credentials failure
Mark Waite closed JENKINS-22706 as Fixed Warn that space in TEMP or TMP causes msysgit ssh credentials failure Change By: Mark Waite (08/Dec/14 3:16 AM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client-plugin] (JENKINS-25194) Private key with passphrase does not seem to work
Mark Waite closed JENKINS-25194 as Duplicate Private key with passphrase does not seem to work Change By: Mark Waite (08/Dec/14 3:18 AM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client-plugin] (JENKINS-25677) Failed to connect to Git repository : Remote host closed connection during handshake
Mark Waite closed JENKINS-25677 as Not A Defect Failed to connect to Git repository : Remote host closed connection during handshake Change By: Mark Waite (08/Dec/14 3:19 AM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client-plugin] (JENKINS-25172) GIT_SSH not always used for git fetch
Mark Waite closed JENKINS-25172 as Fixed GIT_SSH not always used for git fetch Change By: Mark Waite (08/Dec/14 3:18 AM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-10271) Git plugin breaks job api at depth=1
Mark Waite closed JENKINS-10271 as Duplicate Git plugin breaks job api at depth=1 Change By: Mark Waite (08/Dec/14 4:03 AM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [disk-usage-plugin] (JENKINS-22224) one job configuration change results in three Job Config History entries
Dmitry Maslakov updated JENKINS-4 one job configuration change results in three Job Config History entries I do not use Disk Usage plug-in, but it's enabled. On some job I see: $ grep DiskUsageProperty jobs/job-name/config.xml |wc -l 4228 I.e., the line `hudson.plugins.disk__usage.DiskUsageProperty plugin="disk-usage@0.24"/` appeared 4228 times! And it continues to add more and more. Adding these lines is not related to configuration changes neither new builds of the job (this is not very actively used job). Another thing to note is I have about 200 jobs, and all of them are suffered: $ grep DiskUsageProperty jobs/*/config.xml |wc -l 78483 But this is still not the end of that sad story. Using scm-sync-configuration-plugin for Jenkins configuration backup it lead to thousands of commits in backup SCM repository per day: it spams the log and increases the repository size without real need. So let me raise the bug priority. Change By: Dmitry Maslakov (08/Dec/14 4:52 AM) Priority: Minor Critical This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
