zrhoffman opened a new pull request #5710:
URL: https://github.com/apache/trafficcontrol/pull/5710


   <!--
   ************ STOP!! ************
   If this Pull Request is intended to fix a security vulnerability, DO NOT 
submit it! Instead, contact
   the Apache Software Foundation Security Team at 
[email protected] and follow the
   guidelines at https://www.apache.org/security/ regarding vulnerability 
disclosure.
   -->
   ## What does this PR (Pull Request) do?
   <!-- Explain the changes you made here. If this fixes an Issue, identify it 
by
   replacing the text in the checkbox item with the Issue number e.g.
   
   - [x] This PR fixes #9001 OR is not related to any Issue
   
   ^ This will automatically close Issue number 9001 when the Pull Request is
   merged (The '#' is important).
   
   Be sure you check the box properly, see the "The following criteria are ALL
   met by this PR" section for details.
   -->
   Currently, if you try to build the `trafficmonitor-debug`, 
`trafficops-debug`, and `trafficstatis-debug` images without the 
`trafficmonitor`, `trafficops`, and `trafficstats` existing,
   ```shell
   docker-compose -f docker-compose.yml -f 
optional/docker-compose.debugging.yml build --parallel trafficops
   ```
   it will fail to build with an error like
   ```dockerfile
    ---> 82cad2818884
   Step 5/6 : FROM trafficops
   pull access denied for trafficops, repository does not exist or may require 
'docker login': denied: requested access to the resource is denied
   Service 'trafficops' failed to build
   ```
   because you need to build those images first. You can get around that by 
simply attempting to build everything twice:
   ```
   docker-compose -f docker-compose.yml -f 
optional/docker-compose.debugging.yml build --parallel
   docker-compose -f docker-compose.yml -f 
optional/docker-compose.debugging.yml build --parallel
   ```
   But updating RPMs in the debug images is still annoying because it requires 
building everything twice in this way. This PR fixes that behavior.
   
   This PR
   - Makes the Traffic Monitor, Traffic Ops, and Traffic Ops debug images 
building stage targets within the non-debug Dockerfiles
   - Removes the `trafficmonitor-nondebug`, `trafficops-nondebug`, and 
`trafficstatis-nondebug` services from the `docker-compose.debugging.yml` 
compose file
   - Makes `edge` build the `edge` target of `cache/Dockerfile` and makes 
`mid-01` and `mid-02` build the `mid` target of `cache/Dockerfile`
   
   - [x] This PR is not related to any Issue <!-- You can check for an issue 
here: https://github.com/apache/trafficcontrol/issues -->
   
   
   ## Which Traffic Control components are affected by this PR?
   <!-- Please delete all components from this list that are NOT affected by 
this
   Pull Request. Also, feel free to add the name of a tool or script that is
   affected but not on the list.
   
   Additionally, if this Pull Request does NOT affect documentation, please
   explain why documentation is not required. -->
   
   - CDN in a Box
   
   ## What is the best way to verify this PR?
   <!-- Please include here ALL the steps necessary to test your Pull Request. 
If
   it includes tests (and most should), outline here the steps needed to run the
   tests. If not, lay out the manual testing procedure and please explain why
   tests are unnecessary for this Pull Request. -->
   Untag the `trafficmonitor`, `trafficops`, and `trafficstats` and then verify 
that running
   ```shell
   docker-compose -f docker-compose.yml -f 
optional/docker-compose.debugging.yml build --parallel
   ```
   succeeds
   
   ## If this is a bug fix, what versions of Traffic Control are affected?
   <!-- If this PR fixes a bug, please list here all of the affected versions - 
to
   the best of your knowledge. It's also pretty helpful to include a commit hash
   of where 'master' is at the time this PR is opened (if it affects master),
   because what 'master' means will change over time. For example, if this PR
   fixes a bug that's present in master (at commit hash '1df853c8'), in v4.0.0,
   and in the current 4.0.1 Release candidate (e.g. RC1), then this list would
   look like:
   
   - master (1df853c8)
   - 4.0.0
   - 4.0.1 (RC1)
   
   If you don't know what other versions might have this bug, AND don't know how
   to find the commit hash of 'master', then feel free to leave this section
   blank (or, preferably, delete it entirely).
    -->
   
   
   ## The following criteria are ALL met by this PR
   <!-- Check the boxes to signify that the associated statement is true. To
   "check a box", replace the space inside of the square brackets with an 'x'.
   e.g.
   
   - [ x] <- Wrong
   - [x ] <- Wrong
   - [] <- Wrong
   - [*] <- Wrong
   - [x] <- Correct!
   
   -->
   
   - [x] CiaB changed only, tests unnecessary
   - [x] Bugfix, documentation unnecessary
   - [x] An update to CHANGELOG.md is unnecessary
   - [x] This PR includes any and all required license headers
   - [x] This PR **DOES NOT FIX A SERIOUS SECURITY VULNERABILITY** (see [the 
Apache Software Foundation's security 
guidelines](https://www.apache.org/security/) for details)
   
   <!--
   Licensed to the Apache Software Foundation (ASF) under one
   or more contributor license agreements.  See the NOTICE file
   distributed with this work for additional information
   regarding copyright ownership.  The ASF licenses this file
   to you under the Apache License, Version 2.0 (the
   "License"); you may not use this file except in compliance
   with the License.  You may obtain a copy of the License at
   
       http://www.apache.org/licenses/LICENSE-2.0
   
   Unless required by applicable law or agreed to in writing,
   software distributed under the License is distributed on an
   "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
   KIND, either express or implied.  See the License for the
   specific language governing permissions and limitations
   under the License.
   -->


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to