-
Task
-
Resolution: Fixed
-
L3 - Default
-
None
-
None
-
Not defined
It is sometimes required for us to create cloud generations using Optimize images from a dev branch. However, developers don't have permission to push to an internal repository when we want to test this. In some of our Jenkins jobs, we already push docker images to these repositories, so the credentials are available in Jenkins. We could create a Jenkins job that runs on request (not on a schedule), that builds and pushes a docker image to an internal repository, making it available for cloud generation selection for testing.
ATs:
- We can push docker images based on development branches to an internal repository, to allow them to be used in cloud generations for testing
- This is not done from developer's machines
- The job does not run unless manually triggered
- The job is parameterised with a branch name
- (Optional) - the image is tagged with the branch name for easier use in cloud generation management
This is the controller panel for Smart Panels app
[OPT-6376] Push docker images to GCR via GitHub actions job
| Status | Original: Triage [ 10612 ] | New: Backlog [ 11212 ] |
| Epic Link | New: OPT-6436 [ 76876 ] |
| Assignee | New: Giuliano Rodrigues Lima [ giuliano.rodrigues-lima ] |
| Remote Link | New: This issue links to "Page (camunda confluence)" [ 17763 ] |
| Status | Original: Backlog [ 11212 ] | New: Ready [ 10005 ] |
| Assignee | Original: Giuliano Rodrigues Lima [ giuliano.rodrigues-lima ] | New: Andromachi Rozaki [ andromachi.rozaki ] |
| Status | Original: Ready [ 10005 ] | New: In Development [ 10312 ] |
| Description |
Original:
It is sometimes required for us to create cloud generations using Optimize images from a dev branch. However, developers don't have permission to push to an internal repository when we want to test this. In some of our Jenkins jobs, we already push docker images to these repositories, so the credentials are available in Jenkins. We could create a Jenkins job that runs on request (not on a schedule), that builds and pushes a docker image to an internal repository, making it available for cloud generation selection for testing.
*ATs:* * We can push docker images based on development branches to an internal repository, to allow them to be used in cloud generations for testing * This is not done from developer's machines * The job does not run unless manually triggered * The job is parameterised with a branch name |
New:
It is sometimes required for us to create cloud generations using Optimize images from a dev branch. However, developers don't have permission to push to an internal repository when we want to test this. In some of our Jenkins jobs, we already push docker images to these repositories, so the credentials are available in Jenkins. We could create a Jenkins job that runs on request (not on a schedule), that builds and pushes a docker image to an internal repository, making it available for cloud generation selection for testing.
*ATs:* * We can push docker images based on development branches to an internal repository, to allow them to be used in cloud generations for testing * This is not done from developer's machines * The job does not run unless manually triggered * The job is parameterised with a branch name * (Optional) - the image is tagged with the branch name for easier use in cloud generation management |
| Summary | Original: Push docker images to GCR via Jenkins job | New: Push docker images to GCR via GitHub actions job |
| Assignee | Original: Andromachi Rozaki [ andromachi.rozaki ] | New: Giuliano Rodrigues Lima [ giuliano.rodrigues-lima ] |
| Status | Original: In Development [ 10312 ] | New: In Review [ 10212 ] |