[jira] [Commented] (TC-72) docker build to use local directory rather than cloning from github
[ https://issues.apache.org/jira/browse/TC-72?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15906026#comment-15906026 ] ASF GitHub Bot commented on TC-72: -- Github user limited commented on the issue: https://github.com/apache/incubator-trafficcontrol/pull/338 merged to 2.0.x! > docker build to use local directory rather than cloning from github > --- > > Key: TC-72 > URL: https://issues.apache.org/jira/browse/TC-72 > Project: Traffic Control > Issue Type: Improvement > Components: all >Affects Versions: 2.0.0, 1.9.0 >Reporter: Dan Kirkwood >Assignee: Dan Kirkwood >Priority: Minor > Fix For: 2.1.0 > > > docker build of trafficcontrol requires connecting to github. Should be > able to use the local directory instead. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[GitHub] incubator-trafficcontrol issue #338: [TC-72] BACKPORT Dockerfile build local
Github user limited commented on the issue: https://github.com/apache/incubator-trafficcontrol/pull/338 merged to 2.0.x! --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Commented] (TC-182) Traffic Ops seeds.sql missing data from the status table
[
https://issues.apache.org/jira/browse/TC-182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15905945#comment-15905945
]
ASF GitHub Bot commented on TC-182:
---
Github user MattMills closed the pull request at:
https://github.com/apache/incubator-trafficcontrol/pull/345
> Traffic Ops seeds.sql missing data from the status table
>
>
> Key: TC-182
> URL: https://issues.apache.org/jira/browse/TC-182
> Project: Traffic Control
> Issue Type: Bug
> Components: Traffic Ops
>Reporter: Matt Mills
>Priority: Minor
>
> Currently seeds.sql contains the following for the status table:
> {code:sql}
> -- statuses
> insert into status (name, description) values ('PRE_PROD', 'Pre Production.
> Not active in any configuration.') ON CONFLICT DO NOTHING;
> {code}
> After startup, trying to add a server without the OFFLINE status in the table
> throws a SQL error. This can be resolved by adding the additional statuses:
> {code}
> OFFLINE| Edge: Puts server in CCR config file in this state, but CCR will
> never route traffic to it. Mid: Server will not be included in parent.config
> files for its edge caches
> ONLINE | Edge: Puts server in CCR config file in this state, and CCR will
> always route traffic to it. Mid: Server will be included in parent.config
> files for its edges
> REPORTED | Edge: Puts server in CCR config file in this state, and CCR will
> adhere to the health protocol. Mid: N/A for now
> ADMIN_DOWN | Temporary down. Edge: XMPP client will send status OFFLINE to
> CCR, otherwise similar to REPORTED. Mid: Server will not be included in
> parent.config files for its edge caches
> CCR_IGNORE | Edge: 12M will not include caches in this state in CCR config
> files. Mid: N/A for now
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[GitHub] incubator-trafficcontrol pull request #345: [TC-182] Add additional statuses...
Github user MattMills closed the pull request at: https://github.com/apache/incubator-trafficcontrol/pull/345 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Commented] (TC-182) Traffic Ops seeds.sql missing data from the status table
[
https://issues.apache.org/jira/browse/TC-182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15905943#comment-15905943
]
ASF GitHub Bot commented on TC-182:
---
Github user MattMills commented on the issue:
https://github.com/apache/incubator-trafficcontrol/pull/345
After looking at this more with Dave, there is a larger underlying problem
here affecting more than just statuses.
> Traffic Ops seeds.sql missing data from the status table
>
>
> Key: TC-182
> URL: https://issues.apache.org/jira/browse/TC-182
> Project: Traffic Control
> Issue Type: Bug
> Components: Traffic Ops
>Reporter: Matt Mills
>Priority: Minor
>
> Currently seeds.sql contains the following for the status table:
> {code:sql}
> -- statuses
> insert into status (name, description) values ('PRE_PROD', 'Pre Production.
> Not active in any configuration.') ON CONFLICT DO NOTHING;
> {code}
> After startup, trying to add a server without the OFFLINE status in the table
> throws a SQL error. This can be resolved by adding the additional statuses:
> {code}
> OFFLINE| Edge: Puts server in CCR config file in this state, but CCR will
> never route traffic to it. Mid: Server will not be included in parent.config
> files for its edge caches
> ONLINE | Edge: Puts server in CCR config file in this state, and CCR will
> always route traffic to it. Mid: Server will be included in parent.config
> files for its edges
> REPORTED | Edge: Puts server in CCR config file in this state, and CCR will
> adhere to the health protocol. Mid: N/A for now
> ADMIN_DOWN | Temporary down. Edge: XMPP client will send status OFFLINE to
> CCR, otherwise similar to REPORTED. Mid: Server will not be included in
> parent.config files for its edge caches
> CCR_IGNORE | Edge: 12M will not include caches in this state in CCR config
> files. Mid: N/A for now
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[GitHub] incubator-trafficcontrol issue #345: [TC-182] Add additional statuses into t...
Github user MattMills commented on the issue: https://github.com/apache/incubator-trafficcontrol/pull/345 After looking at this more with Dave, there is a larger underlying problem here affecting more than just statuses. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] incubator-trafficcontrol pull request #347: Add global build script.
GitHub user alficles opened a pull request: https://github.com/apache/incubator-trafficcontrol/pull/347 Add global build script. This splits out the somewhat messy docker build command into its own script and adds a global build script. Thereâs still work to be done to clean up docker build scripts, but this provides a basic way to build top to bottom In a single, simple command. This is a step toward addressing TC-180, but falls short of cleaning up everything that requires cleaning up. You can merge this pull request into a Git repository by running: $ git pull https://github.com/alficles/incubator-trafficcontrol global-build-script Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-trafficcontrol/pull/347.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #347 commit 64e18cb57756ed995adc29ab8018abb1d60e73d6 Author: Chris Lemmons Date: 2017-03-10T18:18:57Z Add global build script. This splits out the somewhat messy docker build command into its own script and adds a global build script. Thereâs still work to be done to clean up docker build scripts, but this provides a basic way to build top to bottom In a single, simple command. This is a step toward addressing TC-180, but falls short of cleaning up everything that requires cleaning up. commit 0eb9eddc1b850a8adb934e6b5cc48511fb7ac672 Author: Chris Lemmons Date: 2017-03-10T20:20:51Z Updated default build instructions to refer to the build script. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Commented] (TC-176) 2.0.x traffic router will not build
[ https://issues.apache.org/jira/browse/TC-176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15905685#comment-15905685 ] ASF GitHub Bot commented on TC-176: --- Github user limited commented on the issue: https://github.com/apache/incubator-trafficcontrol/pull/333 Merged this in #331, please close this one > 2.0.x traffic router will not build > --- > > Key: TC-176 > URL: https://issues.apache.org/jira/browse/TC-176 > Project: Traffic Control > Issue Type: Bug > Components: Traffic Router >Affects Versions: 2.0.0 >Reporter: Dan Kirkwood >Assignee: Dan Kirkwood > Labels: easyfix > Fix For: 2.0.0 > > > traffic_router (in 2.0.x branch only!!) build fails with this error: > ```Downloading: > https://repo.maven.apache.org/maven2/com/comcast/cdn/traffic_control/traffic_router/traffic_router/2.0..0/traffic_router-2.0..0.pom > ^M[ERROR] [ERROR] Some problems were encountered while processing the POMs: > [FATAL] Non-resolvable parent POM for > com.comcast.cdn.traffic_control.traffic_router:traffic_router_rpm:[unknown-version]: > Could not find artifact > com.comcast.cdn.traffic_control.traffic_router:traffic_router:pom:2.0..0 in > central (https://repo.maven.apache.org/maven2) and 'parent.relativePath' > points at wrong local POM @ line 22, column 10 > @ > [ERROR] The build could not read 1 project -> [Help 1] > [ERROR] > [ERROR] The project > com.comcast.cdn.traffic_control.traffic_router:traffic_router_rpm:[unknown-version] > (/opt/incubator-trafficcontrol/traffic_router/build/pom.xml) has 1 error > [ERROR] Non-resolvable parent POM for > com.comcast.cdn.traffic_control.traffic_router:traffic_router_rpm:[unknown-version]: > Could not find artifact > com.comcast.cdn.traffic_control.traffic_router:traffic_router:pom:2.0..0 in > central (https://repo.maven.apache.org/maven2) and 'parent.relativePath' > points at wrong local POM @ line 22, column 10 -> [Help 2] > [ERROR] > [ERROR] To see the full stack trace of the errors, re-run Maven with the -e > switch. > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > [ERROR] > /incubator-trafficcontrol/traffic_monitor/target/rpm/traffic_monitor/tmp-buildroot/opt > > /incubator-trafficcontrol/traffic_monitor/target/rpm/traffic_monitor/tmp-buildroot/var > > /incubator-trafficcontrol/traffic_monitor/target/rpm/traffic_monitor/buildroot``` -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[GitHub] incubator-trafficcontrol issue #333: [TC-176] fix minor typo in --...
Github user limited commented on the issue: https://github.com/apache/incubator-trafficcontrol/pull/333 Merged this in #331, please close this one --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] incubator-trafficcontrol issue #331: Fixing typo in traffic_router/build/pom...
Github user limited commented on the issue: https://github.com/apache/incubator-trafficcontrol/pull/331 Merged this to 2.0.x --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Commented] (TC-180) docker-compose build file structure is a bit messy
[ https://issues.apache.org/jira/browse/TC-180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15905659#comment-15905659 ] ASF GitHub Bot commented on TC-180: --- GitHub user alficles opened a pull request: https://github.com/apache/incubator-trafficcontrol/pull/347 Add global build script. This splits out the somewhat messy docker build command into its own script and adds a global build script. There’s still work to be done to clean up docker build scripts, but this provides a basic way to build top to bottom In a single, simple command. This is a step toward addressing TC-180, but falls short of cleaning up everything that requires cleaning up. You can merge this pull request into a Git repository by running: $ git pull https://github.com/alficles/incubator-trafficcontrol global-build-script Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-trafficcontrol/pull/347.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #347 commit 64e18cb57756ed995adc29ab8018abb1d60e73d6 Author: Chris Lemmons Date: 2017-03-10T18:18:57Z Add global build script. This splits out the somewhat messy docker build command into its own script and adds a global build script. There’s still work to be done to clean up docker build scripts, but this provides a basic way to build top to bottom In a single, simple command. This is a step toward addressing TC-180, but falls short of cleaning up everything that requires cleaning up. commit 0eb9eddc1b850a8adb934e6b5cc48511fb7ac672 Author: Chris Lemmons Date: 2017-03-10T20:20:51Z Updated default build instructions to refer to the build script. > docker-compose build file structure is a bit messy > -- > > Key: TC-180 > URL: https://issues.apache.org/jira/browse/TC-180 > Project: Traffic Control > Issue Type: Improvement > Components: all >Affects Versions: 2.0.0 >Reporter: Dan Kirkwood >Priority: Minor > Fix For: 2.1.0 > > > Need to come up with a cleaner build structure -- currently in > infrastructure/docker/build/* so initial build command is a little daunting.. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[GitHub] incubator-trafficcontrol pull request #346: Update default profiles for Edge...
GitHub user dneuman64 opened a pull request: https://github.com/apache/incubator-trafficcontrol/pull/346 Update default profiles for Edges and Mids Updated the default profiles to match our latest. You can merge this pull request into a Git repository by running: $ git pull https://github.com/dneuman64/incubator-trafficcontrol update_profiles_32017 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-trafficcontrol/pull/346.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #346 commit 78b342e4a93181813debec513f7530a7826df507 Author: Dave Neuman Date: 2017-03-10T20:15:34Z updated default profiles commit 75b8d7fcf471a061077a8aa3c110dfe411d16149 Author: Dave Neuman Date: 2017-03-10T20:18:59Z update params --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Updated] (TC-183) api/1.2/servers/:id returns 'offline_reason' instead of the expected 'offlineReason'
[
https://issues.apache.org/jira/browse/TC-183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeremy Mitchell updated TC-183:
---
Affects Version/s: 2.0.0
> api/1.2/servers/:id returns 'offline_reason' instead of the expected
> 'offlineReason'
>
>
> Key: TC-183
> URL: https://issues.apache.org/jira/browse/TC-183
> Project: Traffic Control
> Issue Type: Bug
> Components: Traffic Ops API
>Affects Versions: 1.8.0, 2.0.0
>Reporter: Jason Tucker
>Assignee: Jeremy Mitchell
>Priority: Minor
>
> {{GET /api/1.2/servers/:id}} returns 'offline_reason', but {{PUT
> /api/1.2/servers/:id}} is expecting 'offlineReason'. This is causes problems
> if you are fetching, modifying, and resubmitting server properties.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Assigned] (TC-183) api/1.2/servers/:id returns 'offline_reason' instead of the expected 'offlineReason'
[
https://issues.apache.org/jira/browse/TC-183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeremy Mitchell reassigned TC-183:
--
Assignee: Jeremy Mitchell
> api/1.2/servers/:id returns 'offline_reason' instead of the expected
> 'offlineReason'
>
>
> Key: TC-183
> URL: https://issues.apache.org/jira/browse/TC-183
> Project: Traffic Control
> Issue Type: Bug
> Components: Traffic Ops API
>Affects Versions: 1.8.0, 2.0.0
>Reporter: Jason Tucker
>Assignee: Jeremy Mitchell
>Priority: Minor
>
> {{GET /api/1.2/servers/:id}} returns 'offline_reason', but {{PUT
> /api/1.2/servers/:id}} is expecting 'offlineReason'. This is causes problems
> if you are fetching, modifying, and resubmitting server properties.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (TC-183) api/1.2/servers/:id returns 'offline_reason' instead of the expected 'offlineReason'
Jason Tucker created TC-183:
---
Summary: api/1.2/servers/:id returns 'offline_reason' instead of
the expected 'offlineReason'
Key: TC-183
URL: https://issues.apache.org/jira/browse/TC-183
Project: Traffic Control
Issue Type: Bug
Components: Traffic Ops API
Affects Versions: 1.8.0
Reporter: Jason Tucker
Priority: Minor
{{GET /api/1.2/servers/:id}} returns 'offline_reason', but {{PUT
/api/1.2/servers/:id}} is expecting 'offlineReason'. This is causes problems if
you are fetching, modifying, and resubmitting server properties.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[GitHub] incubator-trafficcontrol pull request #345: [TC-182] Add additional statuses...
GitHub user MattMills opened a pull request: https://github.com/apache/incubator-trafficcontrol/pull/345 [TC-182] Add additional statuses into traffic ops seeds.sql This pr adds additional required statuses into the traffic ops status table fixing TC-182. You can merge this pull request into a Git repository by running: $ git pull https://github.com/MattMills/incubator-trafficcontrol TC-182_fix Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-trafficcontrol/pull/345.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #345 commit 536bfe21971c1a757bf3d6a03f3d1fe75acbc4f4 Author: Matt Mills Date: 2017-03-10T15:51:47Z Add additional statuses into traffic ops seeds.sql (TC-182) --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Commented] (TC-182) Traffic Ops seeds.sql missing data from the status table
[
https://issues.apache.org/jira/browse/TC-182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15905297#comment-15905297
]
ASF GitHub Bot commented on TC-182:
---
GitHub user MattMills opened a pull request:
https://github.com/apache/incubator-trafficcontrol/pull/345
[TC-182] Add additional statuses into traffic ops seeds.sql
This pr adds additional required statuses into the traffic ops status table
fixing TC-182.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/MattMills/incubator-trafficcontrol TC-182_fix
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-trafficcontrol/pull/345.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #345
commit 536bfe21971c1a757bf3d6a03f3d1fe75acbc4f4
Author: Matt Mills
Date: 2017-03-10T15:51:47Z
Add additional statuses into traffic ops seeds.sql (TC-182)
> Traffic Ops seeds.sql missing data from the status table
>
>
> Key: TC-182
> URL: https://issues.apache.org/jira/browse/TC-182
> Project: Traffic Control
> Issue Type: Bug
> Components: Traffic Ops
>Reporter: Matt Mills
>Priority: Minor
>
> Currently seeds.sql contains the following for the status table:
> {code:sql}
> -- statuses
> insert into status (name, description) values ('PRE_PROD', 'Pre Production.
> Not active in any configuration.') ON CONFLICT DO NOTHING;
> {code}
> After startup, trying to add a server without the OFFLINE status in the table
> throws a SQL error. This can be resolved by adding the additional statuses:
> {code}
> OFFLINE| Edge: Puts server in CCR config file in this state, but CCR will
> never route traffic to it. Mid: Server will not be included in parent.config
> files for its edge caches
> ONLINE | Edge: Puts server in CCR config file in this state, and CCR will
> always route traffic to it. Mid: Server will be included in parent.config
> files for its edges
> REPORTED | Edge: Puts server in CCR config file in this state, and CCR will
> adhere to the health protocol. Mid: N/A for now
> ADMIN_DOWN | Temporary down. Edge: XMPP client will send status OFFLINE to
> CCR, otherwise similar to REPORTED. Mid: Server will not be included in
> parent.config files for its edge caches
> CCR_IGNORE | Edge: 12M will not include caches in this state in CCR config
> files. Mid: N/A for now
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (TC-182) Traffic Ops seeds.sql missing data from the status table
Matt Mills created TC-182:
-
Summary: Traffic Ops seeds.sql missing data from the status table
Key: TC-182
URL: https://issues.apache.org/jira/browse/TC-182
Project: Traffic Control
Issue Type: Bug
Components: Traffic Ops
Reporter: Matt Mills
Priority: Minor
Currently seeds.sql contains the following for the status table:
{code:sql}
-- statuses
insert into status (name, description) values ('PRE_PROD', 'Pre Production. Not
active in any configuration.') ON CONFLICT DO NOTHING;
{code}
After startup, trying to add a server without the OFFLINE status in the table
throws a SQL error. This can be resolved by adding the additional statuses:
{code}
OFFLINE| Edge: Puts server in CCR config file in this state, but CCR will
never route traffic to it. Mid: Server will not be included in parent.config
files for its edge caches
ONLINE | Edge: Puts server in CCR config file in this state, and CCR will
always route traffic to it. Mid: Server will be included in parent.config files
for its edges
REPORTED | Edge: Puts server in CCR config file in this state, and CCR will
adhere to the health protocol. Mid: N/A for now
ADMIN_DOWN | Temporary down. Edge: XMPP client will send status OFFLINE to CCR,
otherwise similar to REPORTED. Mid: Server will not be included in
parent.config files for its edge caches
CCR_IGNORE | Edge: 12M will not include caches in this state in CCR config
files. Mid: N/A for now
{code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Resolved] (TC-72) docker build to use local directory rather than cloning from github
[ https://issues.apache.org/jira/browse/TC-72?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phil Sorber resolved TC-72. --- Resolution: Fixed > docker build to use local directory rather than cloning from github > --- > > Key: TC-72 > URL: https://issues.apache.org/jira/browse/TC-72 > Project: Traffic Control > Issue Type: Improvement > Components: all >Affects Versions: 2.0.0, 1.9.0 >Reporter: Dan Kirkwood >Assignee: Dan Kirkwood >Priority: Minor > Fix For: 2.1.0 > > > docker build of trafficcontrol requires connecting to github. Should be > able to use the local directory instead. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (TC-72) docker build to use local directory rather than cloning from github
[ https://issues.apache.org/jira/browse/TC-72?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phil Sorber updated TC-72: -- Affects Version/s: 2.0.0 Fix Version/s: (was: 2.0.0) 2.1.0 > docker build to use local directory rather than cloning from github > --- > > Key: TC-72 > URL: https://issues.apache.org/jira/browse/TC-72 > Project: Traffic Control > Issue Type: Improvement > Components: all >Affects Versions: 2.0.0, 1.9.0 >Reporter: Dan Kirkwood >Assignee: Dan Kirkwood >Priority: Minor > Fix For: 2.1.0 > > > docker build of trafficcontrol requires connecting to github. Should be > able to use the local directory instead. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (TC-72) docker build to use local directory rather than cloning from github
[ https://issues.apache.org/jira/browse/TC-72?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15905250#comment-15905250 ] ASF GitHub Bot commented on TC-72: -- Github user asfgit closed the pull request at: https://github.com/apache/incubator-trafficcontrol/pull/327 > docker build to use local directory rather than cloning from github > --- > > Key: TC-72 > URL: https://issues.apache.org/jira/browse/TC-72 > Project: Traffic Control > Issue Type: Improvement > Components: all >Affects Versions: 1.9.0 >Reporter: Dan Kirkwood >Assignee: Dan Kirkwood >Priority: Minor > Fix For: 2.0.0 > > > docker build of trafficcontrol requires connecting to github. Should be > able to use the local directory instead. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[GitHub] incubator-trafficcontrol pull request #327: [TC-72] Dockerfile build local
Github user asfgit closed the pull request at: https://github.com/apache/incubator-trafficcontrol/pull/327 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
