[JIRA] [docker-plugin] (JENKINS-29417) Add option to configure container name
Title: Message Title Thorsten Roemer commented on JENKINS-29417 Re: Add option to configure container name Please, can you give some information and/or links how to how to customize the container name? 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] [docker-plugin] (JENKINS-29417) Add option to configure container name
Title: Message Title Thorsten Roemer created an issue Jenkins / JENKINS-29417 Add option to configure container name Issue Type: Improvement Assignee: Kanstantsin Shautsou Components: docker-plugin Created: 14/Jul/15 8:16 AM Environment: Jenkins ver. 1.580.3 Docker plugin 0.10.0 Token Macro Plugin 1.10 Priority: Minor Reporter: Thorsten Roemer I would like to be able to name the docker containers in relation to its running Jenkins job and build number. E.g.: SOME_TEXT-- Please add an option to configure the container names. May be in combination with the Token Macro Plugin? Add Comment
[JIRA] [maven] (JENKINS-16707) Ship Jenkins with Config File Provider included by default
Thorsten Roemer commented on JENKINS-16707 Ship Jenkins with Config File Provider included by default Give it a try to the slave setup plugin. It's much more flexible to configure different typed of nodes. If you connect the plugin's configured folders with a SCM, you get history etc. This way we configure our slaves automatically on startup with the configuration stored in SVN/Artifactory. 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] [dependency-check-jenkins] (JENKINS-21990) DependencyCheck aborted due to exception
Thorsten Roemer commented on JENKINS-21990 DependencyCheck aborted due to exception Sorry, report and log are not available anymore from that date. 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] [dependency-check-jenkins] (JENKINS-21990) DependencyCheck aborted due to exception
Thorsten Roemer commented on JENKINS-21990 DependencyCheck aborted due to exception OS: OpenSUSE 12.2 Jenkins master version: 1.522 Jenkins slave jar version: 2.28 Static analysis plugin version: 1.54 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17002) Option to disable "Default" ant version entry
Thorsten Roemer created JENKINS-17002 Option to disable "Default" ant version entry Issue Type: New Feature Affects Versions: current Assignee: Unassigned Components: ant Created: 28/Feb/13 11:46 AM Description: Please add an option (main configuration page, system property on startup, environment or whatever) to disable the "Default" ant version entry in the jobs's configuration page. I want to force my Jenkins users to select a specific version to ensure reproducible builds. Project: Jenkins Priority: Minor Reporter: Thorsten Roemer This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16963) Job filter
Thorsten Roemer updated JENKINS-16963 Job filter Change By: Thorsten Roemer (26/Feb/13 2:06 PM) Summary: job Job filter This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16963) job filter
Thorsten Roemer updated JENKINS-16963 job filter Change By: Thorsten Roemer (26/Feb/13 2:05 PM) Summary: Job job filter for This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16963) Job filter for
Thorsten Roemer created JENKINS-16963 Job filter for Issue Type: Improvement Affects Versions: current Assignee: Tomas Westling Components: build-failure-analyzer Created: 26/Feb/13 2:04 PM Description: What about a job filter, e.g. matching jobs with a cause found/not found? Project: Jenkins Priority: Minor Reporter: Thorsten Roemer This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-14084) Throttle per axis
Thorsten Roemer created JENKINS-14084 Throttle per axis Issue Type: Improvement Affects Versions: current Assignee: abayer Components: matrix, throttle-concurrents Created: 12/Jun/12 1:15 PM Description: I've written an integration test for different OS's and different databases. Now I've created a matrix job with two axis (slaves & "database"). The slaves have multiple executors, being able to run the integration tests in parallel. But for each database there exists only one account, therefor when running the build, axis combinations using the same database must not be running in parallel. How about a (throttle-) flag in the axis definition to mark this axis not to be used in parallel? As a workaround I'm using the "Run each configuration sequentially", but it's unnecessary slow's down the build. Environment: Linux x64 Fix Versions: current Project: Jenkins Priority: Minor Reporter: Thorsten Roemer This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13846) Upstream filter does show all dependencies
[ https://issues.jenkins-ci.org/browse/JENKINS-13846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thorsten Roemer updated JENKINS-13846: -- Priority: Minor (was: Major) > Upstream filter does show all dependencies > -- > > Key: JENKINS-13846 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13846 > Project: Jenkins > Issue Type: Bug > Components: view-job-filters >Affects Versions: current > Environment: Debian >Reporter: Thorsten Roemer >Assignee: Jacob Robertson >Priority: Minor > Fix For: current > > > When using the "upstream/downstram jobs filter" the view does not show all > dependencies. > It looks like the view contains only the entries found in the job's > configuration under > "Build after other projects are built" & "Build other projects"? > On the job's status page, the "upstream projects" & "downstream projects" > sections contain much more dependencies. > It looks like the missing ones are the maven dependencies, calculated > on-the-fly by jenkins? > These dependencies should be included in the view as well. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13846) Upstream filter does show all dependencies
[ https://issues.jenkins-ci.org/browse/JENKINS-13846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thorsten Roemer updated JENKINS-13846: -- Fix Version/s: current Affects Version/s: current > Upstream filter does show all dependencies > -- > > Key: JENKINS-13846 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13846 > Project: Jenkins > Issue Type: Bug > Components: view-job-filters >Affects Versions: current > Environment: Debian >Reporter: Thorsten Roemer >Assignee: Jacob Robertson > Fix For: current > > > When using the "upstream/downstram jobs filter" the view does not show all > dependencies. > It looks like the view contains only the entries found in the job's > configuration under > "Build after other projects are built" & "Build other projects"? > On the job's status page, the "upstream projects" & "downstream projects" > sections contain much more dependencies. > It looks like the missing ones are the maven dependencies, calculated > on-the-fly by jenkins? > These dependencies should be included in the view as well. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13846) Upstream filter does show all dependencies
Thorsten Roemer created JENKINS-13846: - Summary: Upstream filter does show all dependencies Key: JENKINS-13846 URL: https://issues.jenkins-ci.org/browse/JENKINS-13846 Project: Jenkins Issue Type: Bug Components: view-job-filters Environment: Debian Reporter: Thorsten Roemer Assignee: Jacob Robertson When using the "upstream/downstram jobs filter" the view does not show all dependencies. It looks like the view contains only the entries found in the job's configuration under "Build after other projects are built" & "Build other projects"? On the job's status page, the "upstream projects" & "downstream projects" sections contain much more dependencies. It looks like the missing ones are the maven dependencies, calculated on-the-fly by jenkins? These dependencies should be included in the view as well. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13748) Support for upstream/downstream jobs
Thorsten Roemer created JENKINS-13748: - Summary: Support for upstream/downstream jobs Key: JENKINS-13748 URL: https://issues.jenkins-ci.org/browse/JENKINS-13748 Project: Jenkins Issue Type: New Feature Components: view-job-filters Reporter: Thorsten Roemer Assignee: jacob_robertson Priority: Trivial I would like to have a filter for the job's upstream/downstream dependencies: What about a include/exclude filter, that sums up all upstream and/or downstream jobs of given job(s)? Example: - job "ab" has upstream jobs "a" & "b". - job "ac" has upstream jobs "a" & "c" - job "all" has upstream jobs "ab" & "ac" In the new job filter I can enter a regex for the jobs to care (in this case "all") and select something like "include upstream jobs". As a result in the view list I can see "a", "b" & "c" (but not "all"). This would be useful to get an overview of a special job and its upstream jobs its based on. When maven modules gets released and fixed versions in dependencies gets used, the according upstream dependencies will go away and the view list will automatically shrink. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
